"libgcc_s.so.1 must be installed for pthread_cancel to work" error for non-root users

We have many cPanel servers all fairly similar except their ages. It appears that after upgrading from PHP v5.3.x to PHP v5.4.x the older servers are having a problem running PHP from the command line for non-root users. I'm not completly confident that the PHP upgrade was the cause though.

Log into the server as a normal user and run "php -v" and an error appears.
# php -v
libgcc_s.so.1 must be installed for pthread_cancel to work
Aborted (core dumped)

The root user does not have this problem:
# php -v
PHP 5.4.33 (cli) (built: Oct 9 2014 21:26:41)
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-2014 Zend Technologies
with the ionCube PHP Loader v4.6.1, Copyright (c) 2002-2014, by ionCube Ltd.


I Googled and found some others with the same issue but those fixes did not help here.

1. RLimitMEM set too low.
We don't have that set in our Apache config, this command returns nothing:
grep RLimit /usr/local/apache/conf/httpd.conf


2. cPanel's "Max cPanel process memory" is too low.
That was already set to 512. I increased it to 1024, rebooted the server (to make sure it's updating) and it still has the issue:
# grep -i maxmem /var/cpanel/cpanel.config
maxmem=1024
# php -v
libgcc_s.so.1 must be installed for pthread_cancel to work
Aborted (core dumped)


Three of our servers have this issue while the rest do not. Some of the servers that work fine have always been at PHP v 5.4 and a few others were upgrade from PHP v5.3 to v5.4. All servers are on CentOS 6.x

I looked through this forum also but there was nothing that I didn't try or didn't apply

Any help would be appreciated.

Thanks,
Stephane

 

[SOLVED] Re: "libgcc_s.so.1 must be installed for pthread_cancel to work" error for non-root users

cPanelMichael,

Thanks for your response.

The issue has now been resolved but I'm not entirely sure why. I failed to test for the issue *before* trying to fix it so it may have been a cPanel update overnight that solved it.

Here is what I did.

I went to test your suggestion, "try disabling shell fork bomb protection", and I saw that the server already had that disabled. This is strange because our standard setup is to turn this on. I checked and several of our servers had this off. I enabled it for all servers that had it off.

I then tested for my PHP CLI error and it's gone on all three servers, they are working as expected.

So I don't know the exact reason but maybe it was related to the Fork Bomb Protection being *off*.

Thanks for you assistance.
Stephane