The first maintenance release of the NAV 4.2 series is now available.
The source code is available for download at Launchpad [1]. A new package for Debian Wheezy has been published in our APT repository [2], as usual.
Changes =======
The following reported issues have been fixed:
* LP#1395710 (api token can not be refreshed from the api) * LP#1396514 (Status tool in NAV 4.2 shows no events if API call returns a 500 error) * LP#1396516 (Status API in NAV 4.2 crashes when there are old deviant alerts present) * LP#1396517 (Status tool makes hyperlinks out of alert subjects that have no defined URL) * LP#1396531 (logengine spams the error message "KeyError: 'LINK'") * LP#1396914 (netmap filter on location excludes links)
In the NAV 4.2.0 release announcement and changelog, four bugfixes were omitted by accident, because they had originally been committed to the 4.1.x release branch. The changelog has been updated. These were the bugfixes in question:
* LP#1385121 ("Add graph to dashboard" does nothing under certain Apache configurations) * LP#1386716 (Maintenance task with no end time displays incorrectly in edit form) * LP#1389121 (when searching for an ip-address with space in it, NAV crashes) * LP#1389145 (Netbiostracker crash on unparseable MAC Address)
Please refer to the release notes [3] for further information on upgrading.
Happy NAVing everyone!
Links =====
[1] https://launchpad.net/nav/4.2/4.2.1 [2] https://nav.uninett.no/wiki/nav_on_debian [3] https://nav.uninett.no/doc/4.2/release-notes.html#nav-4-2
morten.brekkevold@uninett.no said:
The following reported issues have been fixed: ... (Status tool
I'm not sure everything turned out ok. Now those of us who was not seeing events in the status page sees some events, but a lot of it just makes no sense:
500 hobbitServiceDown 09:13:59 22 minutes 200 hobbitServiceDown 06:10:37 3 hours 200 hobbitServiceDown 27.Nov 22:09:16 11 hours 100 hobbitServiceDown 27.Nov 11:08:38 a day PowerSupplyOrFan object psuNotOK 26.Nov 22:05:11 2 days PowerSupplyOrFan object psuNotOK 26.Nov 22:05:10 2 days
I am also missing a couple of devices (all of category OTHER, one SW) that I know is down.
I truly love the idea of a configurable status page, but I am beginning to long for a static (a la NAV 3.15) no filters, no nonsense status page in addition. This page would then be the autorative place people could check that they haven't filtered away stuff they want to see.
--Ingeborg
On Fri, 28 Nov 2014 09:53:11 +0100 Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
I'm not sure everything turned out ok. Now those of us who was not seeing events in the status page sees some events, but a lot of it just makes no sense:
500 hobbitServiceDown 09:13:59 22 minutes 200 hobbitServiceDown 06:10:37 3 hours 200 hobbitServiceDown 27.Nov 22:09:16 11 hours 100 hobbitServiceDown 27.Nov 11:08:38 a day
Are you testing this on your "verktøykasse"?
I know these won't make sense. You're seeing these (which you never would see before) because these events are posted externally from UNINETT's Hobbit-NAV integration. The 500/200/100 values are internal hobbit service references - NAV really has no idea what to do with those, I'm afraid.
This issue is not mainly one with NAV, but with how our custom Hobbit integration works in our network monitoring toolkit service. It's not really a discussion for the nav-users list, but possibly for the closed vk customers list.
PowerSupplyOrFan object psuNotOK 26.Nov 22:05:11 2 days PowerSupplyOrFan object psuNotOK 26.Nov 22:05:10 2 days
Nice catch, we can fix these. File another bug report, pretty please? :)
I am also missing a couple of devices (all of category OTHER, one SW) that I know is down.
I used to have a login to your installation, but I can never remember my credentials. If you drop me a private e-mail with some details, I can check it out.
I truly love the idea of a configurable status page, but I am beginning to long for a static (a la NAV 3.15) no filters, no nonsense status page in addition. This page would then be the autorative place people could check that they haven't filtered away stuff they want to see.
Just clear the filters on the new Status page. You will see it all. Even the old gritty things that the old Status page never showed you.
For comparison, the old status page is still available in 4.2 under the /status-old/ URL. It will be removed in 4.3.
morten.brekkevold@uninett.no said:
Are you testing this on your "verktøykasse"?
No, we use xymon (hobbit) too.
morten.brekkevold@uninett.no said:
I know these won't make sense. You're seeing these (which you never would see before) because these events are posted externally from UNINETT's Hobbit-NAV integration. The 500/200/100 values are internal hobbit service references - NAV really has no idea what to do with those, I'm afraid.
But I would really like to see the hostnames like we did in NAV 4.2 and earlier.
morten.brekkevold@uninett.no said:
I used to have a login to your installation, but I can never remember my credentials. If you drop me a private e-mail with some details, I can check it out.
Will do.
morten.brekkevold@uninett.no said:
For comparison, the old status page is still available in 4.2 under the / status-old/ URL. It will be removed in 4.3.
Cool!
--Ingeborg
On Fri, 28 Nov 2014 10:25:22 +0100 Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
morten.brekkevold@uninett.no said:
Are you testing this on your "verktøykasse"?
No, we use xymon (hobbit) too.
Then you must have lifted our integration code from your toolkit server :)
morten.brekkevold@uninett.no said:
I know these won't make sense. You're seeing these (which you never would see before) because these events are posted externally from UNINETT's Hobbit-NAV integration. The 500/200/100 values are internal hobbit service references - NAV really has no idea what to do with those, I'm afraid.
But I would really like to see the hostnames like we did in NAV 4.2 and earlier.
Well, you didn't actually see the hobbit alerts at all in earlier versions of NAV - you just received them via e-mail/sms/jabber. And Hobbit alerts do not necessarily refer to any Netbox that NAV knows of, so the netbox attribute may not even be filled.
-
Ingeborg Hellemo -
Morten Brekkevold