Bug 46156

GemStone/S 64 Bit

3.3, 3.2.14, 3.2.13, 3.2.12, 3.2.11, 3.2.10, 3.2.9, 3.2.8.1, 3.2.8, 3.2.7, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2, 3.1.0.6, 3.1.0.5, 3.1.0.4, 3.1.0.3, 3.1.0.2, 3.1.0.1, 3.1

All Platforms

3.4, 3.3.1, 3.2.15

netldi frozen in getnameinfo

If the DNS name server has not been configured properly, it's possible for the netldi process to get stuck in an infinite loop, with gslist -v showing a status of "frozen".  If a stack trace of the netldi process is taken (either using gdb/dbx or kill -USR1), the following entries will be noted:

    getnameinfo( )
    SocketGetPeerInfo( )
    NetGetPeerName( )

Workaround

Shutdown and restart the netldi.

Check the host name / IP address used for the stone name and gemnetid on the last attempted login before the netldi hang.  Confirm that the DNS name server can correctly map the IP address to the associated host name.


Last updated: 3/14/17