Invalid Lather request made from agent

[jutsu]

Hi All,

This is from the server's log

ERROR [tomcat-http--29] [org.hyperic.lather.server.LatherServlet@219] Invalid Lather request made from xxx.xxx.xxx.xxx

This is from the agent's log

DEBUG [PluginStatusSender] [AgentCallbackClient@190] IO error: Connection failure: HTTP/1.1 503 Invalid Lather request made from xxx.xxx.xxx.xxx

WARN  [PluginStatusSender] [AgentDaemon@776] could not send plugin status to server, will retry:  org.hyperic.hq.bizapp.client.AgentCallbackClientException: IO error: Connection failure: HTTP/1.1 503 Invalid Lather request made from xxx.xxx.xxx.xxx

Anybody encountered the same problem??

I'm using version 5.8.0 for both the agent and the server
Both are running on Linux CentOS release 6.5

Tried using with and without SSL, but still encounter the same problem.

Been searching through the forum but none of the solution works for me.

Thanks for reading this.

[admin]

Does this error happens all the time? metrics don't arrive to server? inventory?

Do you have more agents which work? if yes, are they on the same O/S?

[jutsu]

This is a fresh installation which i just started trying.

None of the agents work.

The HQ server and the agents are running on different VMs

telnet from agent to server works for port 7443 and 7080

All servers are running on Linux CentOS release 6.5

[jutsu]

I just installed the agent on the server itself and everything is working fine.

Still unable to figure out why I'm getting the error from other agents on other nodes.

Any help is appreciated!!

[jutsu · Accepted solution]

Finally able to solve this problem.

Just in case others may need to know this in future.

The MTU of the HQ server and the agents are set to 2000.

This may be too big which resulted in the loss of packets being transmitted from the agents to the HQ server.

Due to the loss of packet, it may become an invalid requests. (My guess)

To set the eth interface to a lower MTU

use the following command

ip link set eth0 mtu 1500

The above solve my problem. Hope this may come in handy for others

[admin]

Thanks for sharing your solution with us. We have never seen that in our environments but it is good to know that it is a potential problem that you can face using the agent --> server communication channel.