After restarting the Tim process, the following error occurs in the Tim logs: "ERROR: hub: hubmanager: could not configure apmpacket."
Article ID: 41057
Updated On:
Products
Issue/Introduction
Issue:
After restarting the TIM process, the following error occurs in the TIM logs: "ERROR: hub: hubmanager: could not configure apmpacket".
Environment:
Occurs for APM 10.x TIMs (that are not MTPs) on supported RHEL environments.
Cause:
This error can be caused by the networking interfaces monitored by the TIM not being up.
Resolution:
1. The interfaces monitored by the TIM will be read on TIM startup in the following lines:
hub: InterfaceFilter: interfacefilter.xml loaded
hub: InterfaceFilter: interface list:
hub: InterfaceFilter: "eth1" IPv4=1 IPv6=1
hub: InterfaceFilter: "eth2" IPv4=1 IPv6=1
In this example, the TIM is monitoring the eth1 and eth2 interfaces, but this may be different in other environments.
2. From the command line, run the command: ifconfig. This command should return each networking interface on the server that is currently up. If any of the interfaces listed in either interfacefilter.xml or the Tim logs do not appear up, run the following command:
ifconfig <interface> up
Example:
ifconfig eth2 up
This command should bring up the interface for network monitoring by the Tim and likely prevent the "ERROR: hub: hubmanager: could not configure apmpacket" message.
Additional Information:
As a permanent solution, networking interfaces can be configured to start automatically whenever the server is rebooted.
To do this, navigate to /etc/sysconfig/network-scripts and look for the configuration file ifcfg-<interface> file (For example: ifcfg-eth02).
In this configuration file, the property "Onboot=yes" can be specified to automatically start the networking interface.
Consult with your Network Administrators before making any changes to this configuration file.
Environment
Component:
Feedback
