DX Application Performance Management

Expand all | Collapse all

TIM Connection issues - 404 Error

Jump to Best Answer
  • 1.  TIM Connection issues - 404 Error

    Posted 07-28-2015 03:56 PM

    Hi!

     

    I'm configuring TIM for the first time, and I'm having some communication issues. I can see it from CEM Console ( [APM_Host]:[WebServer_Port]/wily ) // Setup // Monitors , as disabled. When I click on Enable, I get "Communication Error 404" in Status.

     

    When checking TIM logs (/opt/CA/APM/tim/logs/timlog.txt), I see just:

     

     

    Mon Jul 27 17:18:46 2015  1562   hub: WebServer: cmd=POST url=/wily/cem/tim/tess/settimconfig status=404 message=Not Found

     

    I'm working with 9.7.1.16 version of EM and its respective TIM

     

    Is this error familiar to anyone?

     

    Thanks and regards,

    Roger



  • 2.  Re: TIM Connection issues - 404 Error

    Broadcom Employee
    Posted 07-28-2015 04:12 PM

    Is port 80 open between the MOM and TIM?



  • 3.  Re: TIM Connection issues - 404 Error

    Posted 07-28-2015 04:23 PM

    Thanks for answering

     

    Its listening on 81 MOM sees it.

    Actually its a file not found http error.



  • 4.  Re: TIM Connection issues - 404 Error

    Broadcom Employee
    Posted 07-28-2015 04:31 PM

    The MOM talks to the TIM over port 80: https://wiki.ca.com/display/APMDEVOPS97/CA+APM+Ports

    Is this is a standalone TIM or on a Multiple Monitor?



  • 5.  Re: TIM Connection issues - 404 Error

    Posted 07-28-2015 04:47 PM

    Its standalone, also using a standalone EM.

     

    Restored TIM Port to 80, and TIM http port parameter on the EM to 80, so now I'm on a standard port.

     

    But the issue persists. The strange thing is TIM is reporting the error, so MOM gets to it. Is that url part of TIM service itself?

     

    Regards,

    Roger



  • 6.  Re: TIM Connection issues - 404 Error
    Best Answer

    Posted 07-28-2015 05:05 PM

    Roger,

    Did you chose to deploy private Httpd instance when installing TIM ?

    If yes then port should be 8080 or whatever was chosen, otherwise default port for httpd is 80.

    Port 81 is internal port that TIM uses to talk to CEM and shouldn't need to be changed.

     

    Regards,

    Kulbir.



  • 7.  Re: TIM Connection issues - 404 Error

    Posted 07-28-2015 08:36 PM

    Thanks, Kulbir!

     

    I was confused about ports. So now I'm using ports 80 and 81. The issue has changed, so I now from the EM I see this error:

     

    Connection Failure

    Error retrieving response http://10.1.0.76:80/wily/cem/tim/tess/settimconfig: Read timed out

     

     

    If I check httpd error log, I see:

    [Tue Jul 28 20:00:05 2015] [error] [client 192.168.50.1] (104)Connection reset by peer: proxy: error reading status line from remote server localhost

    [Tue Jul 28 20:00:05 2015] [error] [client 192.168.50.1] proxy: Error reading from remote server returned by /wily/cem/tim/tess/settimconfig

     

     

    So no I think TIM service is not responding to httpd script, and times out.

    Then, checking timlog.txt (not sure if the same issue), I see a set of:

     

    Tue Jul 28 21:30:13 2015 17826 **ERROR: hub: ApmPacketComm: timapmpacketcomm:

    Tue Jul 28 21:30:13 2015 17826 **ERROR: hub: ApmPacketComm: config client response error from timapmpacketcomm

    Tue Jul 28 21:30:13 2015 17826 **ERROR: hub: hubmanager: could not configure apmpacket. Retrying ...

     

    per second

     

    Going to apmpacket logs, I see:

     

     

     

    Tue Jul 28 21:31:30 2015 10180   CommServer: received config request from client tim

    Tue Jul 28 21:31:30 2015 10180   ClientManager: updating client "tim"

    Tue Jul 28 21:31:30 2015 10180   ClientManager: client: tim

    Tue Jul 28 21:31:30 2015 10180   ClientManager:  packet directory: /opt/CA/APM/apmpacket/data/pcap/clients/tim

    Tue Jul 28 21:31:30 2015 10180   ClientManager:  configuration:

    Tue Jul 28 21:31:30 2015 10180   ClientManager:  interfaces:

    Tue Jul 28 21:31:30 2015 10180   ClientManager:   eth3

    Tue Jul 28 21:31:30 2015 10180   ClientManager:  no server filters

    Tue Jul 28 21:31:30 2015 10180   ClientManager:  no client filters

    Tue Jul 28 21:31:30 2015 10180   ClientManager:  end of configuration

    Tue Jul 28 21:31:30 2015 10180   ClientManager: #clients: 2

    Tue Jul 28 21:31:30 2015 10180   ClientManager: writing client config file /opt/CA/APM/apmpacket/config/clients/tim.data

    Tue Jul 28 21:31:30 2015 10180   NetworkManager: updating configuration

    Tue Jul 28 21:31:30 2015 10180   NetworkManager: continuing to monitor interface eth3

    Tue Jul 28 21:31:30 2015 10180   NetworkManager: continuing to monitor "eth3"

    Tue Jul 28 21:31:30 2015 10180   DeviceCtl: "eth1": setting device status to "down"

    Tue Jul 28 21:31:31 2015 10180   DeviceCtl: ifdown eth1: usage: ifdown <device name>

    Tue Jul 28 21:31:31 2015 10180   DeviceCtl: "eth1": setting device status to "up"

    Tue Jul 28 21:31:31 2015 10180   DeviceCtl: ifup eth1: /sbin/ifup: configuration for eth1 not found.

    Tue Jul 28 21:31:31 2015 10180   DeviceCtl: ifup eth1: Usage: ifup <device name>

    Tue Jul 28 21:31:31 2015 10180   DeviceCtl: running: /usr/sbin/ethtool -k eth1 2>&1

    Tue Jul 28 21:31:31 2015 10180   DeviceCtl: eth1: ethtool: Cannot get device feature names: No such device

    Tue Jul 28 21:31:31 2015 10180   DeviceCtl: eth1: end of output from ethtool

    Tue Jul 28 21:31:31 2015 10180   DeviceCtl: eth1: generic-receive-offload option not found

    Tue Jul 28 21:31:31 2015 10180   NetworkManager: opening device eth1

    Tue Jul 28 21:31:31 2015 10180   NetworkManager: "eth1": receive buffer size for is 20971520

    Tue Jul 28 21:31:31 2015 10180 **ERROR: NetworkManager: Cannot activate device eth1

    Tue Jul 28 21:31:31 2015 10180   NetworkManager: "eth1": closing network device

    Tue Jul 28 21:31:31 2015 10180 **ERROR: NetworkManager:

    Tue Jul 28 21:31:31 2015 10180   NetworkManager: compiling BPF

     

    I have not eth1 interface, so I guess there is some eth1 interface configured somewhere, that I should delete.

     

    I'll keep working on this, if you have any guess, its welcome.

     

    Regards,

    Roger



  • 8.  Re: TIM Connection issues - 404 Error

    Posted 07-28-2015 10:15 PM

    So I finally found the problem for my prior response. There was an old client for apmpacket referring to a deprecated interface. I've moved the VM I'm hosting TIM in, and the new Host OS gave me two different interfaces. So I deleted the client reference in /opt/CA/APM/apmpacket/config/clients/ and restarted both apmpacket and tim services.

     

    Everything works apparently well now.

    I'll keep on configuring TIM, but I'm sure this connection issue is closed.

     

    Thank you guys, your responses were really helpful!

     

    Regards,

    Roger



  • 9.  Re: TIM Connection issues - 404 Error

    Posted 07-28-2015 10:45 PM

    Hi Roger,

    Thanks for this investigative work and sharing solution for subproblem with us.

    We are glad to be able to provide you assistance in addressing this multifaceted problem.

     

    Regards,

    Kulbir.