If service processing freezes

If any operations with the service: opening, deleting, enabling, or disabling freeze, check the following:

• core parameters;
• processing module processes;
• processing module log.

Troubleshooting is performed on the BILLmanager server.

Kernel parameters

If service processing freezes, increasing core settings in /etc/sysctl.conf may help:

• net.core.somaxconn — sets the maximum number of open sockets waiting to connect;
• net.core.netdev_max_backlog — defines the maximum number of packets in the queue for processing.

To apply the settings, run the command:

sysctl -p /etc/sysctl.conf

Processing module processes

The service operation will not complete if the process freezes.

To check and disable the problematic process:

1. Check for frozen processing module processes with the command:

   ps aux | grep pm<mgrname>

   Comment

   <mgrname> — short platform name, for example vmmgr or ipmgr

2. Disable the faulty process with the command:

   kill <PID>

   Comment

   <PID> — ID of the faulty process
   Double-check the process ID before disabling it. An error in the ID will disable the wrong process, which may cause the platform to work incorrectly.

Processing module log

When a service operation is performed, the main log of the platform billmgr.log will display information similar to the following:

Mar 12 04:06:29 [14203:1] processing INFO RUN with: processing/pmispmgr5 --runningoperation 97 --command open --item 509

If the main log shows an error on the processing module side, you should check the processing module logs.

The name of the processing module log appears in the format pm<mgrname>.log, where <mgrname> is the short name of the platform, for example vmmgr or ipmgr. Thus, for the virtual server service in VMmanager 6, you should check the log /usr/local/mgr5/var/pmvmmgr6.log.