0
Answered

Local agent and amout of monitors

InteractMarketing 5 years ago updated by Ilya (Here to help) 5 years ago 12
I have installed local Anturis agent on a deducted box (linux) which was working fine since I have added another website to monitor (via HTTP). All available monitors are working fine except that local one. Also I have another websites on same server where new site is set and those are working fine with a local agent monitors. Are there any limitations for local agent monitors? Also how Anturis monitor comes on an Apache logs?

Thanks
Under review
Hi,

There are no limitations for local agents. Could you please provide us problem monitor name and agent? We will check what was wrong.
About apache log. In apache log you will see http request from our ip addresses. You can find all our IP addresses here http://wiki.anturis.com/index.php?title=Public_Agents_IP_Addresses
This is what I’m getting on a local Anturis monitor in that case:

HTTP Response

Headers

Status

406

Reason

Not Acceptable

Date

Thu, 16 Jul 2015 15:23:29 GMT

Server

Apache

Content-Length

226

Connection

close

Content-Type

text/html; charset=iso-8859-1

Body

<head><title>Not Acceptable!</title></head><body><h1>Not Acceptable!</h1><p>An appropriate representation of the requested resource could not be found on this server. This error was generated by Mod_Security.</p></body></html>

Any clue what is going on?
Hi,

It is response from web server which you are trying to monitor. So, you need modify mod_security on your web server.
Interesting because I have another 4 websites on the same box monitored by Anturis and any of them are not returning that kind of error by a local monitor agent.
Local agent just receive this status from your web server and transfer it to anturis.com.
We can check it if you provide us monitor name and agent name.
Agent name: logmon.interacthosting.net
Monitor name: USCIB.com (HTTP)
3 requests to uscib from your local agent works ok but after your server responded with 406 status. Looks like your server consider this requests like suspicious. I suggest to add IP address of local agent to white list in mod_security.

Interesting that local agent is not showing as Anturis Agent in the logs - one of the reason why I wasn't able to solve that issue from the beginning.
Yes, old agent doesn't introduce like Anturis Agent. I suggest you to update agent. For last two year a lot of bug was fixed and many improvements was implemented. To update agent open anturis console->Locations&Agents tab->Press 'Update available' near the agent
Well, it looks like another topic got resolved.

Thanks