Page 2 of 3
Re: Error: No output from backend!
Posted: Tue Jun 05, 2018 10:20 am
by blalande
You're right, I have another problem on this server:
Each time I try to restore a configuration snapshot ie: 2018-06-05 13:36:02 Config Ok 1528205762.tar.gz
I have:
NagiosQL Snapshot Restored.
Apply Configuration View Config
then when I apply configuration:
Command submitted for processing...
Waiting for configuration verification.........
Configuration verification failed.
An error occurred while attempting to apply your configuration to Nagios Core. Monitoring engine configuration files have been rolled back to their last known good checkpoint.
View error:
Error: Could not find a service matching host name 'lindhnexoag19' and description 'check_app_log_susan1_jboss' (config file '/opt/SP/home/nagios/etc/servicegroups.cfg', starting on line 72)
Error: Could not expand members specified in servicegroup 'V4_CHECK_APP_LOG_ONCALL' (config file '/opt/SP/home/nagios/etc/servicegroups.cfg', starting at line 72)
I thought that configuration snapshot with "config OK" status should be working fine??
Re: Error: No output from backend!
Posted: Tue Jun 05, 2018 11:34 am
by scottwilkerson
If you have included files outside of the normal paths it is possible that if that files doesn't exist any more, the snapshots could fail.
I would attempt to correct the service groups and get a current config working and then remove any old snapshot before you made these changes
Re: Error: No output from backend!
Posted: Wed Jun 06, 2018 3:07 am
by blalande
I'm using symlinks pointing from /usr/local to /opt/SP/home/ so there is no issue with path.
The server was working fine before I tried to relocate mysql db on remote server.
In order to test CCM I have cloned a service, and tryied to apply conf, hten deleted it (while I was having issue discussed in this thread...)
I think this lead to the error I'm having now.
I thought I could apply a working snapshot to revert to a working conf, but this is not working...
So my situation now is that in CCM I have the same configuration as before, but it's not working and I'm unable to apply a working snapshot...
Any idea how to get to my previous configuration?
Re: Error: No output from backend!
Posted: Wed Jun 06, 2018 7:53 am
by blalande
I'm going back to the initial issue:
I still have the Error: No output from backend! error message displayed
monitring-engine-status.JPG
I focused on the process not showing up in the montoring engine process tab and missed this point...
I'm sending you the updated profile in PM
Re: Error: No output from backend!
Posted: Wed Jun 06, 2018 8:55 am
by scottwilkerson
Your apache error log is showing a error in /opt/SP/home/nagiosxi/html/includes/utils-backend.inc.php
Code: Select all
[Wed Jun 06 12:33:54 2018] [error] [client 10.107.59.44] PHP Warning: simplexml_load_string(): Entity: line 2: parser error : Start tag expected, '<' not found in /opt/SP/home/nagiosxi/html/includes/utils-backend.inc.php on line 27, ...
Could you send us this file?
Re: Error: No output from backend!
Posted: Wed Jun 06, 2018 9:06 am
by blalande
Sent in PM
Re: Error: No output from backend!
Posted: Wed Jun 06, 2018 9:25 am
by scottwilkerson
By chance did you turn error output on in your php.ini?
This is going to be very difficult to decipher because you are running a version of XI that is over 3 years old. But the error suggests that the output that is expected to be XML doesn't start with a <
Re: Error: No output from backend!
Posted: Wed Jun 06, 2018 9:32 am
by blalande
Here are error related parameters in php.ini:
error_reporting = E_ALL & ~E_DEPRECATED
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
track_errors = Off
html_errors = Off
mssql.min_error_severity = 10
Tell me if you want me to modify one, or need a specific log file
Re: Error: No output from backend!
Posted: Wed Jun 06, 2018 10:58 am
by scottwilkerson
This all looks OK, PM sent.
Re: Error: No output from backend!
Posted: Sun Jun 24, 2018 10:12 am
by blalande
Issue is solved, thread can be closed.
Cheers