EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB42918: What is the "abrtd" process found in Redhat Enterprise Linux 6.x and how can it affect the MicroStrategy Intelligence Server 9.x


Community Admin

• Strategy


On RedHat systems starting with version 6.0, there has been,among other features, an additional service. The Automatic Bug Reporting Tool, commonly abbreviated as ABRT, consists of the "abrtd" daemon and a number of system services and utilities to process, analyze, and report detected problems with running applications and services.

DETAILED DESCRIPTION
On RedHat systems starting with version 6.0, there has been,among other features, an additional service:
The Automatic Bug Reporting Tool, commonly abbreviated as ABRT, consists of the "abrtd" daemon and a number of system services and utilities to process, analyze, and report detected problems with running applications and services. The daemon runs silently in the background most of the time, and springs into action when an application crashes is detected. The daemon then collects the relevant problem data such as a core file (if it has been generated), the crashing application's command line parameters, and other data.
It has been noted that when an Intelligence Server crash occurs, that no core file is found.  In the Linux system log "/var/log/messages", the following entry can be seen:
 


Feb 8 09:28:13 TESTSERVER kernel: MSTRSvr: segfault at 48 ip 00007fa9252ddefb
sp 00007fa9129f3090 error 4 in libMHOBJSRV.so.9.3.020.055
Feb 8 09:28:32 TESTSERVER abrt: saved core dump of pid 14256 
(/appserv/MSTR9/MicroStrategy/install/IntelligenceServer/bin/MSTRSvr.9.3.000.
055) to /var/spool/abrt/ccpp-2013-02-08-09:28:13-14256.new/coredump 
(4225028096 bytes)
Feb 8 09:28:32 TESTSERVER abrtd: Directory 'ccpp-2013-02-08-09:28:13-14256' 
creation detected
Feb 8 09:28:32 TESTSERVER abrtd: Executable'/appserv/MSTR9/Strategy
/install/IntelligenceServer/bin/MSTRSvr.9.3.000.055' doesn't belong to any 
package
Feb 8 09:28:32 TESTSERVER abrtd: Corrupted or bad dump 
/var/spool/abrt/ccpp-2013-02-08-09:28:13-14256 (res:2), deleting

 
CAUSE
On all UNIX systems, the default behaviour is that the core file is generated in the directory in which process is executed from.
The error referenced in the messages log shows that the core file was generated and moved to an output directory, set in the ABRT configuration.
 
This can be seen in the following line:

Feb 8 09:28:32 ESLP22732 abrt: saved core dump of pid 14256 
(/dw/WWDDWP02/appserv/MSTR9/MicroStrategy/install/IntelligenceServer/bin/
MSTRSvr.9.3.000.055) to /var/spool/abrt/ccpp-2013-02-08-09:28:13-14256.new/
coredump (4225028096 bytes)

 
Additionally, the log also shows that the core file was deleted since it wasn't captured properly.  A common reason on why the core file wasn't captured, is due to insufficient disk space.
 
ACTION
If the ABRT is in operation and the Intelligence Server has crashed, the Linux System Administrator must be notified and system log checked for the location of the Intelligence Server core file.
 
Third Party Software Installation
WARNING:
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

April 26, 2017

Last Updated:

April 26, 2017