Dialogic® PowerMedia™ Extended Media Server (PowerMedia XMS) - more articles
How to collect core dump from xmsrest process?
Symptom:
When troubleshooting an issue where the Dialogic® PowerMedia™ XMS xmsrest service has crashed, it is useful to supply Dialogic technical services and support team a core file for analysis. However, what is observed after the xmsrest services crashed is that there is no core file found on the PowerMedia XMS server.
Reason for the issue:
By default, PowerMedia XMS processes do not generate crash dumps. Each process needs to be enabled to generate a core dump.
How to configure the process to generate a core dump?
In this case, the ability to generate a core dump will be enabled for the for xmsrest process.
- Login to XMS via ssh and then open the file /etc/sysconfig/xmsrest
- Carefully add "ulimit -c unlimited" without quotes.
- Save the file and restart xms.
Please note:
If the server where PowerMedia XMS is installed does not have linux abrtd (Automatic Bug Reporting Tool) installed, the core should be stored under / folder.
If the abrtd deamon is installed, it will *delete* the core automatically unless the configuration of abrtd deamon is changed and the daemon restarted. The changes required to the abrtd daemon are outlined below:
- Edit the file /etc/abrt/abrt-action-save-package-data.conf.
- Set OpenGPGCheck = no
- ProcessUnpackaged = yes.
- Save the file and restart abrtd deamon (service abrtd start)
When the core happens, there will be a message in /var/log/messages that shows where the core is stored.
For example:
June 22 11:05:41 xms abrt[16589]: Saved core dump of pid 36460 (/usr/bin/xmsrest) to /var/spool/abrt/ccpp-2014-06-22-11:05:41-36460 (50025210 bytes)
Product List
Dialogic® PowerMedia™ Extended Media Server (XMS) version 2.3 or earlier.
First published: 12-Dec-2014
Open access: Product rule: open; Page rule: Auto