The update did not complete successfully

[[email protected]]

The last 2 updates failed with: The update did not complete successfully. Please try updating manually.

Currently we're running Ngios XI 5.2.1 The first upgrade was done using the web interface. It gave this error but I could not find anything wrong.

The second upgrade was done by hand. Before starting it the configuration was verified using Core Config Manager, Tools, Write Config Files, verify. There were several warnings, no errors. I solved all warnings and launched the upgrade by hand, but the problem remains.

As far as I can see everyhting is working OK. The only problem I see is when scheduling a down time or acknowledging a problem it remains visible. At first I believed this to be a bug. But it could be due to the upgrade.

This leads to the folowing questions
- How can I verify if everyhting is running OK
- How can I reset this error message
- What do I have to do to hide acknowleged problems.

Regards,

Bart

[tgriep]

Scheduled downtime and acknowledging are run by the cron daemon.
Try and restart it to see if that fixes the issue by running this command.

Code: Select all

service crond start

Then can you run this and post the output here so we can see if the cron daemon started?

Code: Select all

ps aux |grep cron

When you ran the upgrade manually, did it complete?

[[email protected]]

As far as I can tell both upgrades completed succesfully. I could not find any relevant error

Here is the output of the commands

Code: Select all

[root@nagios ~]# ps aux |grep cron
root      2013  0.0  0.0 117328  1292 ?        Ss   Nov12   0:21 crond
nagios   19261  0.0  0.0   9232  1064 ?        Ss   09:52   0:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/sysstat.php > /usr/local/nagiosxi/var/sysstat.log 2>&1
nagios   19262  0.0  0.0   9232  1060 ?        Ss   09:52   0:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/eventman.php > /usr/local/nagiosxi/var/eventman.log 2>&1
nagios   19263  0.0  0.0   9232  1064 ?        Ss   09:52   0:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/cmdsubsys.php > /usr/local/nagiosxi/var/cmdsubsys.log 2>&1
nagios   19265  0.0  0.0   9232  1060 ?        Ss   09:52   0:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/perfdataproc.php > /usr/local/nagiosxi/var/perfdataproc.log 2>&1
nagios   19266  0.0  0.0   9232  1064 ?        Ss   09:52   0:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/feedproc.php > /usr/local/nagiosxi/var/feedproc.log 2>&1
nagios   19267  0.2  0.5 222932 22360 ?        S    09:52   0:00 /usr/bin/php -q /usr/local/nagiosxi/cron/sysstat.php
nagios   19268  0.2  0.5 223164 22036 ?        S    09:52   0:00 /usr/bin/php -q /usr/local/nagiosxi/cron/cmdsubsys.php
nagios   19269  0.2  0.5 223228 22124 ?        S    09:52   0:00 /usr/bin/php -q /usr/local/nagiosxi/cron/perfdataproc.php
nagios   19270  0.3  0.8 233240 31700 ?        S    09:52   0:00 /usr/bin/php -q /usr/local/nagiosxi/cron/eventman.php
nagios   19271  0.2  0.5 222900 21772 ?        S    09:52   0:00 /usr/bin/php -q /usr/local/nagiosxi/cron/feedproc.php
root     20328  0.0  0.0 103252   832 pts/0    S+   09:52   0:00 grep cron
[root@nagios ~]# service crond start
[root@nagios ~]# ps aux |grep cron
root      2013  0.0  0.0 117328  1292 ?        Ss   Nov12   0:21 crond
nagios   21276  0.0  0.0   9232  1060 ?        Ss   09:53   0:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/cmdsubsys.php > /usr/local/nagiosxi/var/cmdsubsys.log 2>&1
nagios   21277  0.0  0.0   9232  1064 ?        Ss   09:53   0:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/feedproc.php > /usr/local/nagiosxi/var/feedproc.log 2>&1
nagios   21279  3.0  0.5 223164 22040 ?        S    09:53   0:00 /usr/bin/php -q /usr/local/nagiosxi/cron/cmdsubsys.php
nagios   21281  0.0  0.0   9232  1060 ?        Ss   09:53   0:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/perfdataproc.php > /usr/local/nagiosxi/var/perfdataproc.log 2>&1
nagios   21282  0.0  0.0   9232  1060 ?        Ss   09:53   0:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/sysstat.php > /usr/local/nagiosxi/var/sysstat.log 2>&1
nagios   21283  0.0  0.0   9232  1060 ?        Ss   09:53   0:00 /bin/sh -c /usr/bin/php -q /usr/local/nagiosxi/cron/eventman.php > /usr/local/nagiosxi/var/eventman.log 2>&1
nagios   21286  2.6  0.5 222900 21764 ?        S    09:53   0:00 /usr/bin/php -q /usr/local/nagiosxi/cron/feedproc.php
nagios   21287  3.0  0.5 222776 22344 ?        S    09:53   0:00 /usr/bin/php -q /usr/local/nagiosxi/cron/sysstat.php
nagios   21288  2.6  0.5 223228 22112 ?        S    09:53   0:00 /usr/bin/php -q /usr/local/nagiosxi/cron/perfdataproc.php
nagios   21291  4.0  0.8 233240 31708 ?        S    09:53   0:00 /usr/bin/php -q /usr/local/nagiosxi/cron/eventman.php
root     21519  0.0  0.0 103252   832 pts/0    S+   09:53   0:00 grep cron

[ssax]

Please attach the upgrade.log file from your XI installation directory when you manually upgraded so that we can take a look at it.

[[email protected]]

I did the upgrade in /tmp/nagiosxi but the folder seems to be empty. So I re-did the upgrade. (upgrade23nov.zip)
I also found the old upgrade.log which is still displayed in the web interface (upgrade20oct.zip)

I attached both files zipped.

Regards,

Bart

[lmiltchev]

As far as I can tell both upgrades completed succesfully. I could not find any relevant error

I believe they did.

The "bogus" error in the web UI ("The update did not complete successfully. Please try updating manually.") was actually a bug, which was fixed in 5.2.2.
Any upgrades to a higher than 5.2.2 version won't be showing this error in the web UI.

Keep an eye on the system and let us know if you run into some issues, but I believe you were able to upgrade just fine regardless of the message in the GUI.

[[email protected]]

which was fixed in 5.2.2.

The web interface claims to be running 5.2.2, but I still see the problem. It will be fixed in the next version?

And the only problem I'm seeing is I can no longer schedule a down time for a server with problems. In fact I can schedule a down time, but it still appears in the Operations screen. This behavior started with upgrade to version 5.

Is this also a known bug?

Regards,

Bart

[hsmith]

Can you go to Admin --> System Extensions --> Manage Components and then check for updates? Install any component updates that need to be done, and see if you're still having the issue.

In versions going forward, the upgrade failed bug should be squashed.

[[email protected]]

There were several components which needed an update. The same for config wizards. I updated all of them, received some errors about not having an internet connection (which is not true)

All of them are now up-to-date.

But the problem is still there:
- running 5.2.2 but claiming the update did not complete succesfully
- Not possible to acknowledge service or host problems

[lmiltchev]

- running 5.2.2 but claiming the update did not complete succesfully

Does this message go away when you press the "go back" button?

- Not possible to acknowledge service or host problems

Can you elaborate on this? Are you seeing any errors in the web UI? Are you trying to acknowledge problems logged in as "nagiosadmin" or a regular user?