[DragonFlyBSD - Bug #2566] No space available for static Thread Local Storage

[Francois Tigeot via Redmine]

Issue #2566 has been updated by ftigeot.


$ ldd -a bootstrap/bin/java

/red/@@-1:00007/dports/java/openjdk7/work/bootstrap/bin/java:
        libz.so.3 => /usr/lib/libz.so.3 (0x800828000)
        libpthread.so.0 => /usr/lib/libpthread.so.0 (0x800a3c000)
        libc.so.7 => /usr/lib/libc.so.7 (0x800c53000)
/usr/lib/libz.so.3:
        libc.so.8 => /usr/lib/libc.so.8 (0x800f8d000)
/usr/lib/libpthread.so.0:
        libc.so.8 => /usr/lib/libc.so.8 (0x800f8d000)
----------------------------------------
Bug #2566: No space available for static Thread Local Storage
http://bugs.dragonflybsd.org/issues/2566

Author: eric.j.christeson
Status: New
Priority: Normal
Assignee: 
Category: 
Target version: 


I noticed some of my cron jobs not running and upon investigation I found this in /var/log/messages:

cron: in try_dlopen(): /usr/lib/security/pam_opie.so.2: /usr/lib/libc.so.7: No space available for static Thread Local Storage

su seems to have a similar problem:

su: in try_dlopen(): /usr/lib/security/pam_opie.so.2: /usr/lib/libc.so.7: No space available for static Thread Local Storage

As a work-around I edited /etc/pam.d/system and commented out the first two auth lines that include pam_opie.so and pam_opieaccess.so
obviously if you're not using opie, this won't affect much.

I first noticed it after building a quickworld from master on Monday, June 3.  The previous known good was Thursday, May 30.



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account