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

KB46831: Scheduled subscriptions sometimes fail when the MicroStrategy Intelligence Server is running on Linux


Community Admin

• Strategy


Scheduled subscriptions fail occasionally in MicroStrategy when the Intelligence Server is running on Linux.

SYMPTOM:
 
Scheduled subscriptions fail occasionally in Strategy when the Intelligence Server is running on Linux.
 
The following errors are seen in the DSSErrors.log:
 


 2014-04-01 16:00:03.820-05:00 [HOST:xxxxxxxxxx][PID:1136][THR:4151568080][MultiProcess][Error] Quiting child process because of error: ::pthread_create failed
System Error (EAGAIN): --- Resource temporarily unavailable
2014-04-01 16:00:03.880-05:00 [HOST:xxxxxxxxxx][PID:2247][THR:588744448][Database Classes][Error] Connection::Connect failed. Unable to connect.
Error type: System call error. ::pthread_create failed

 
CAUSE:
 
The Linux machine is running into the thread limit when the Strategy Intelligence Server is trying to create new threads.
 
ACTION:
 
Consult the System Administrator to increase the maximum number of threads allowed for the user who is running the Intelligence Server process.  This change might need to be made in different ways depending on the configuration of the machine where the Intelligence Server is running.  One possible way is to modify the /etc/security/limits.conf file and add the following line (in this example, the Intelligence Server is run by a user named mstruser and the desired number of threads is 4096):
 

mstruser soft nproc 4096

 
After the change is made, the Strategy Intelligence Server must be restarted to apply the change.
 
WORKAROUND:
 
Restarting the Intelligence Server will provide temporary relief to the situation by freeing all of the currently used threads.


Comment

0 comments

Details

Knowledge Article

Published:

April 1, 2017

Last Updated:

April 1, 2017