ActiveSpaces - FATAL [assertion_failure] failed _cond=error == 0,
Article ID: KB0085010
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveSpaces | - |
| Not Applicable | - |
Description
Description:
Symptoms:
Cause:
There is an OS limit on the number of threads per user which is being exceeded.
Received the exception after the following activity.
1). During creation of the space, the space was created but the seeder did not join the space.
2). After issuing leave metaspace on that member.
inetziapls015.sigwseeder1.log.1:[2016-02-18T10:42:22.516][13057][139780132214528][FATAL][][Thread.cpp:94][start] [assertion_failure] failed _cond=error == 0, _error=11
inetziapls015.sigwseeder1.log.1:[2016-02-18T10:42:22.519][13057][139780132214528][FATAL][][Thread.cpp:94][start] [assertion_failure] failed _cond=error == 0, _error=11
inetziapls015.sigwseeder1.log.1:[2016-02-18T10:53:47.838][13057][139780116424448][FATAL][][Thread.cpp:94][start] [assertion_failure] failed _cond=error == 0, _error=11
Symptoms:
Cause:
There is an OS limit on the number of threads per user which is being exceeded.
Issue/Introduction
ActiveSpaces - FATAL [assertion_failure] failed _cond=error == 0,
Resolution
Either change the max processors per user from 1024 to 2048 (ulimit -u / 'nproc' in the /etc/security/limits.conf file) or set nproc (number of processes allowed by that user) via limits.conf as an alternative way to set resource limits. Users can also set this via ulimit –u <2048>, which is the same as setting it via limits.conf, but the user has to do it in every shell instance.
Feedback
Yes
No
Powered by
