Page 1 of 1

Upgrade to 2026R1.4 breaks Login

Posted: Thu Apr 23, 2026 7:55 am
by CBoekhuis
After upgrade from 2026R1.3.1 to latest the login page got spinning. Cleared cache,cookies,data and rebooted the rhel8 server without any success.
Had to restore from the auto backup. Retryed another time and after pushing on the Finish button browser hangs.

Any suggestions? I was trying to solve an issue with where a user wasn't able to submit scheduleddowtime for his hosts and got stuk in the next issue. :cry:

Re: Upgrade to 2026R1.4 breaks Login

Posted: Thu Apr 23, 2026 11:07 am
by DoubleDoubleA
Hi @CBoekhuis,

This is an interesting report. We have had upgrades break things, and when we do we typically get several reports from multiple users. I checked with support and they don't have any cases so far regarding this, and I don't see any other traffic here or in other means of contact.

Could be a lot of things, including network. At this point I'd say put in a support case and they can help troubleshoot. It might be an issue with the release but I don't see other evidence of that so far.

Aaron

Re: Upgrade to 2026R1.4 breaks Login

Posted: Mon Apr 27, 2026 8:40 pm
by GldRush98
Are you paying attention to the log window when you click upgrade?
Is it actually completing successfully or erroring?
My upgrade from 2026R1.3.1 to 2026R1.4 errored out and broke things, but the log window made it obvious with the last 3 lines being:
Result: FAIL
Failed 16/16 test programs. 32/33 subtests failed.
make: *** [Makefile:862: test_dynamic] Error 255
Instead of the usual success message.

Re: Upgrade to 2026R1.4 breaks Login

Posted: Thu Apr 30, 2026 12:55 pm
by browan
Hello @CBoekhuis!

Im particularly curious as to whether there are any errors in your web browsers dev tools, whether in the console or the network tab, while you are attempting to login.

I am also wondering if we have some DB failure here, perhaps could you run systemctl status httpd php-fpm mysqld nagios npcd, and just making sure these are running

I am also interested in the php-fpm logs, should be located at /var/log/php-fpm/www-error.log

Another thing to check that might be worth it, is NDO.

Thank you!
Benjamin