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:
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