Update:
I cleared my browser cache and restarted my browser. Now I get an error in the
icinga-web UI:
The server encountered an error:
Internal Exception, check your logs!
The Web UI is now completedly "Greyed" and I only can get access again when
reloading the page with the browser reload button.
This is what occurs in the httpd error log:
[Tue Oct 30 15:21:44 2012] [error] [client 10.207.2.175] PHP Fatal error:
Cannot redeclare printplainmessage() (previously declared in
/usr/share/icinga-web/app/templates/exceptions/web.php:95) in
/usr/share/icinga-web/app/templates/exceptions/web.php on line 108, referer:
I retried several times, but could not reproduce the "command was sent
successfully" response in the Icinga Web UI anymore.
-----Original message-----
From:Linux IT Services Support <supp...@linux-it-services.nl>
Sent:Tue 30-10-2012 14:34
Subject:Icinga-web 1.8.0/Icinga 1.8.1: (forced) hostcheck from icinga_web is
not executed, but works ok from classic ui.
To:icinga-users@lists.sourceforge.net;
CC:Linux IT Services Support <supp...@linux-it-services.nl>;
Hello,
I upgraded icinga from 1.7.1 to 1.8.1 and icinga-web from 1.7.1 to 1.8.0. I
updated the database schema using the provided sql files. I restored some of my
configurations. I used rpmbuild to rpm packages from the tar files with the
included specfiles, so I could restore config files from config.rpmsave files
most of the time, and a few from backup.
The problem I run into is, that I can have a forced host check command
submitted from the icinga_web gui without errors (it says that the command was
sent successfully.) . In the icinga.log I see the following message:
[1351603312] EXTERNAL COMMAND: SCHEDULE_FORCED_HOST_CHECK;NN01-02-GW;1351606909
But no host check is performed. I used tcpdump to verify this.
If I perform the same action on the Classic UI I see the following in the
icinga.log file:
[1351603526] EXTERNAL COMMAND: SCHEDULE_FORCED_HOST_CHECK;NN01-02-GW;1351603525
With tcpdump I see icmp echo request messages immediately be sent to the host.
I have looked in http logs, icinga-web and icinga logs, but could find no clue
to what the problem is.
Where do I need to look further to investigate and solve this problem?
Regards,
Hans Feringa
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
