NetXMS Support Forum

English Support => General Support => Topic started by: lindeamon on July 09, 2017, 03:25:28 PM

Title: node status after v2.1 upgrade
Post by: lindeamon on July 09, 2017, 03:25:28 PM
hi,

i have upgraded to v2.1 on windows 2012 r2 with pgsql 9.5.
on one of my nodes i see that the status is warning. did some checks and found that user system found a MAC change, posted and cleared the alarm but the status of the node didn't change.
tried db check with tables and nothing happened, everything passed.
what can i do ?

10x
Lindeamon
Title: Re: node status after v2.1 upgrade
Post by: lindeamon on July 09, 2017, 10:32:04 PM
hi,

just did an upgrade on my home computer.
windows 2008 r2 with all updates. using embedded sqlite.
got the same kind of error. for some reason, system account does not terminate alarms correctly.
in the alarm log i can see the alarm as "outstanding" even though there is no alarm.
went to the db and changed the alarm to terminate, restart server service and the status changed back to normal.
disabled the network card an enable it and the alarm was not clear.
what could be wrong ?

10x,
lindeamon
Title: Re: node status after v2.1 upgrade
Post by: lindeamon on July 09, 2017, 10:47:30 PM
ok,

went and enabled the "system" user.
changed it's password.
logged in with it and terminated the alarm.
logged in with admin again and disabled the system account.
now the status is as should be.
is this a regular process one must follow after upgrading {maybe installing...} to v2.1 ?

10x,
lindeamon
Title: Re: node status after v2.1 upgrade
Post by: Victor Kirhenshtein on July 10, 2017, 11:08:13 AM
Hi,

seems that global permissions was not updated during upgrade. In 2.1 we introduce alarm categories, and new global access right "access to all alarm categories" which should be enabled for all users to keep behavior compatible with 2.0. Make sure your user/group has this access right set.

Best regards,
Victor
Title: Re: node status after v2.1 upgrade
Post by: lindeamon on July 10, 2017, 11:17:17 AM
Hi Victor,

adding the permission solved he problem.

thank you very much,
Lindeamon