[DragonFlyBSD - Bug #2566] No space available for static Thread Local Storage
Francois Tigeot via Redmine
bugtracker-admin at leaf.dragonflybsd.org
Sun Jun 9 03:01:10 PDT 2013
Issue #2566 has been updated by ftigeot.
This issue also occurs when trying to run the openjdk7 bootstrap binary on DragonFly 3.5
The bootstrap has been built on a previous DragonFly release and thus depends on libc.so.7
readelf -a bootstrap/bin/java reports:
Dynamic section at offset 0xc5c8 contains 22 entries:
0x0000000000000001 (NEEDED) Shared library: [libc.so.7]
libc.so.7 is the only libc name present in the ELF binary. Nothing unusual so far.
Yet, ldd reports bootstrap/bin/java is linked to both libc.so.7 and libc.so.8:
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)
libc.so.8 => /usr/lib/libc.so.8 (0x800f8d000)
Bug #2566: No space available for static Thread Local Storage
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
More information about the Bugs