On Wed, Apr 11, 2012 at 3:45 PM, Christer Edwards <christer...@gmail.com> wrote: > On Wed, Apr 11, 2012 at 4:05 PM, Wayne Fiori <dev9...@gmail.com> wrote: >>>> > I've been deploying saltstack (salt-0.9.8) recently. The installation >>>> > has be trouble free on all my Gentoo, Ubuntu, and most FreeBSD >>>> > servers. I have three FreeBSD servers that have the following python >>>> > trace: > ...[snip]... > > ports or packages? I've never run into this issue on my FreeBSD > servers, but I strictly build from ports..
I built salt from the ports.
The problem looks like python. The python on the servers that show this issue does not include the PyGILState symbol. The PyGILState is related to threading. Just checked and the python installed on these bad servers is not configured for threading. The python installed on the good servers was configured with threading. It looks like M2Crypto is looking for a threaded environment, not finding it, it simply crashes.
ns-test-1# cd /usr/local/lib ; readelf -d -a libpython2.6.so | grep PyGILState
I have no clue how/why I configured three out of 15 servers to no use threading in python, but there you have it. I'm off to rebuild ports on these three servers and have a good install of salt at the end. -- =Wayne