Internal Server Error When Attempting to Schedule Downtime
-
jdalrymple
- Skynet Drone
- Posts: 2620
- Joined: Wed Feb 11, 2015 1:56 pm
Re: Internal Server Error When Attempting to Schedule Downti
Simple lab - create a host, no services on that host, that host not in any hostgroups or anything - schedule downtime works A-OK from the Core Interface. Incidentally so does schedule downtime for all services. What could my lab possibly be doing that is not representative of your environment do you suppose?
Re: Internal Server Error When Attempting to Schedule Downti
It looks like this may be a platform issue after all. Over a period of time (with no changes to the configuration), the problem resurfaced.
While the functions were working, I noticed the apache error_log had some more detailed error messages. I attached those for your review.
We have plenty of x86 gear, so I will try and build Nagios there and see if I can reproduce this problem. I will post the results. Thanks again for your assistance.
While the functions were working, I noticed the apache error_log had some more detailed error messages. I attached those for your review.
We have plenty of x86 gear, so I will try and build Nagios there and see if I can reproduce this problem. I will post the results. Thanks again for your assistance.
- Attachments
-
error_log.txt- (4.09 KiB) Downloaded 134 times
-
jdalrymple
- Skynet Drone
- Posts: 2620
- Joined: Wed Feb 11, 2015 1:56 pm
Re: Internal Server Error When Attempting to Schedule Downti
I would tend to agree - again.
If you cared to continue the uphill battle the next path would probably be recompile glibc, apache and mod_cgi from source instead of using packages. I'm not sure that would fix it, but that would be my next step if I wanted desperately to make this work.
The simpler route is definitely the x86 route.
If you cared to continue the uphill battle the next path would probably be recompile glibc, apache and mod_cgi from source instead of using packages. I'm not sure that would fix it, but that would be my next step if I wanted desperately to make this work.
The simpler route is definitely the x86 route.