Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Apache monitoring with CentOS

Hello,

I'm having problems using the Apache template provided with APM. I have added the following to my CentOS httpd.conf file:

SetHandler server-status

Order Deny,Allow

Deny from all

Allow from "172.28.28.11"

</Location>

ExtendedStatus On

I have cheked the SSH access and the firewall, all is good:

When I try to add the server, I get the following error message:

Testing on node jbv-dmz-epia03: failed with 'NotAvailable' status

The script returned status code DOWN. unable access to localhost

Find more posts tagged with

Accepted answers

jiri.tomek

Grab script source code from monitor details (Edit Apache application template and expand one of monitors) and try to run it directly on target machine as a standard Perl script. If it won't work, you can at least debug it to see what is actually wrong with it.

All comments

jiri.tomek

Hello,
Apache template uses Linux scripts written in Perl to get required data. Error you get means that script is not able to connect to server using "">http://localhost/...". Verify that server is accessible on that URL. Also note that script is executed on server itself so if you have "Allow from 172.28.28.11", it probably blocks request. Try to add "Allow from 127.0.0.1".

xlamtor

Hello,

Thanks for the reply

I have tried to change it to 127.0.0.1 and restarted the service, still the same reslt. The server respond on port 80 for localhost:

telnet 127.0.0.1 80
Trying 127.0.0.1...
Connected to XXX (127.0.0.1).
Escape character is '^]'.

But the result from SolarWinds is still the same. I have checked logs from the Firewall and tried turning off iptables just to be sure as well. Can it be a perl problem?

jiri.tomek