You are here

Upgrading to 5.4 from 5.3 breaks opsview-web

3 posts / 0 new
Last post
flubit
flubit's picture
Upgrading to 5.4 from 5.3 breaks opsview-web

I just ran an upgrade following the manual installation instructions: https://knowledge.opsview.com/v5.1/docs/manual-installation. Now in the web UI I see "Opsview Apache Error: 500 - An internal error occurred". In /var/log/opsview/opsview-web.log I see the error "[Catalyst] [ERROR] Couldn't render template "file error - login: not found". If I run "/opt/opsview/watchdog/bin/opsview-monit summary opsview-web" I see that the status for opsview-web is stuck in state "Initializing".

I assume there is some kind of template cache that needs to be cleared but I can't see any information about this online. Any ideas?

 

Duncan Ferguson
dferguson's picture
The cache files are stored in

The cache files are stored in /usr/local/nagios/tmp/par-* and should be automatically removed on an upgrade.  

Check to make sure all your opsview packages have been upgraded, and then as the nagios user:

opsview_watchdog all stop
rm -rf /usr/local/nagios/tmp/par-*
ospview_watchdog all start

and see if that helps at all.

  Duncs

flubit
flubit's picture
Thank you for the quick

Thank you for the quick response. I checked the free memory on the server and it was very low so I think this may have been the cause and the template error was merely a symptom. After a reboot of the server all opsview processes inclusing opsview-web started up without an issue.