rpc.ttdbserverd[6127]: NetISAM: read failed

[Grant Zhou]

Our Solaris server report the following messages:
XECUTE COMMAND: tail -200 /var/adm/messages
Jul 6 10:14:24 LZ-PPP2-HOST1 rpc.ttdbserverd[6127]: NetISAM: read failed:
requested 1024 bytes, got 0
Jul 6 10:14:24 LZ-PPP2-HOST1 ToolTalk/ISAM[6127]: Fatal error: read failed:
requested 1024 bytes, got 0 - File exists
Jul 6 10:14:24 LZ-PPP2-HOST1 inetd[162]: /usr/dt/bin/rpc.ttdbserverd:
Hangup
Jul 6 10:14:25 LZ-PPP2-HOST1 rpc.ttdbserverd[2819]: NetISAM: read failed:
requested 1024 bytes, got 0
Jul 6 10:14:25 LZ-PPP2-HOST1 ToolTalk/ISAM[2819]: Fatal error: read failed:
requested 1024 bytes, got 0 - File exists
Jul 6 10:14:25 LZ-PPP2-HOST1 inetd[162]: /usr/dt/bin/rpc.ttdbserverd:
Hangup
Jul 6 10:14:26 LZ-PPP2-HOST1 rpc.ttdbserverd[2820]: NetISAM: read failed:
requested 1024 bytes, got 0
Jul 6 10:14:26 LZ-PPP2-HOST1 ToolTalk/ISAM[2820]: Fatal error: read failed:
requested 1024 bytes, got 0 - File exists
Jul 6 10:14:26 LZ-PPP2-HOST1 inetd[162]: /usr/dt/bin/rpc.ttdbserverd:
Hangup
Jul 7 10:35:56 LZ-PPP2-HOST1 rpc.ttdbserverd[2821]: NetISAM: read failed:
requested 1024 bytes, got 0
Jul 7 10:35:56 LZ-PPP2-HOST1 ToolTalk/ISAM[2821]: Fatal error: read failed:
requested 1024 bytes, got 0 - File exists
Jul 7 10:35:56 LZ-PPP2-HOST1 inetd[162]: /usr/dt/bin/rpc.ttdbserverd:
Hangup
Jul 7 10:35:57 LZ-PPP2-HOST1 rpc.ttdbserverd[4949]: NetISAM: read failed:
requested 1024 bytes, got 0
Jul 7 10:35:57 LZ-PPP2-HOST1 ToolTalk/ISAM[4949]: Fatal error: read failed:
requested 1024 bytes, got 0 - File exists
Jul 7 10:35:57 LZ-PPP2-HOST1 inetd[162]: /usr/dt/bin/rpc.ttdbserverd:
Hangup
Jul 7 10:35:58 LZ-PPP2-HOST1 rpc.ttdbserverd[4950]: NetISAM: read failed:
requested 1024 bytes, got 0
Jul 7 10:35:58 LZ-PPP2-HOST1 ToolTalk/ISAM[4950]: Fatal error: read failed:
requested 1024 bytes, got 0 - File exists
Jul 7 10:35:58 LZ-PPP2-HOST1 inetd[162]: /usr/dt/bin/rpc.ttdbserverd:
Hangup


What's the problem? The server is running abnormal??

Regards,
Grant

[Michael Tosch]

In article <ccim25$scc@netnews.proxy.lucent.com>, "Grant Zhou" <goddabao@yahoo.com> writes:

> Our Solaris server report the following messages:
> XECUTE COMMAND: tail -200 /var/adm/messages
> Jul 6 10:14:24 LZ-PPP2-HOST1 rpc.ttdbserverd[6127]: NetISAM: read failed:
> requested 1024 bytes, got 0
> Jul 6 10:14:24 LZ-PPP2-HOST1 ToolTalk/ISAM[6127]: Fatal error: read failed:
> requested 1024 bytes, got 0 - File exists
> Jul 6 10:14:24 LZ-PPP2-HOST1 inetd[162]: /usr/dt/bin/rpc.ttdbserverd:
> Hangup
> Jul 6 10:14:25 LZ-PPP2-HOST1 rpc.ttdbserverd[2819]: NetISAM: read failed:
> requested 1024 bytes, got 0
> Jul 6 10:14:25 LZ-PPP2-HOST1 ToolTalk/ISAM[2819]: Fatal error: read failed:
> requested 1024 bytes, got 0 - File exists
> Jul 6 10:14:25 LZ-PPP2-HOST1 inetd[162]: /usr/dt/bin/rpc.ttdbserverd:
> Hangup
> Jul 6 10:14:26 LZ-PPP2-HOST1 rpc.ttdbserverd[2820]: NetISAM: read failed:
> requested 1024 bytes, got 0
> Jul 6 10:14:26 LZ-PPP2-HOST1 ToolTalk/ISAM[2820]: Fatal error: read failed:
> requested 1024 bytes, got 0 - File exists
> Jul 6 10:14:26 LZ-PPP2-HOST1 inetd[162]: /usr/dt/bin/rpc.ttdbserverd:
> Hangup
> Jul 7 10:35:56 LZ-PPP2-HOST1 rpc.ttdbserverd[2821]: NetISAM: read failed:
> requested 1024 bytes, got 0
> Jul 7 10:35:56 LZ-PPP2-HOST1 ToolTalk/ISAM[2821]: Fatal error: read failed:
> requested 1024 bytes, got 0 - File exists
> Jul 7 10:35:56 LZ-PPP2-HOST1 inetd[162]: /usr/dt/bin/rpc.ttdbserverd:
> Hangup
> Jul 7 10:35:57 LZ-PPP2-HOST1 rpc.ttdbserverd[4949]: NetISAM: read failed:
> requested 1024 bytes, got 0
> Jul 7 10:35:57 LZ-PPP2-HOST1 ToolTalk/ISAM[4949]: Fatal error: read failed:
> requested 1024 bytes, got 0 - File exists
> Jul 7 10:35:57 LZ-PPP2-HOST1 inetd[162]: /usr/dt/bin/rpc.ttdbserverd:
> Hangup
> Jul 7 10:35:58 LZ-PPP2-HOST1 rpc.ttdbserverd[4950]: NetISAM: read failed:
> requested 1024 bytes, got 0
> Jul 7 10:35:58 LZ-PPP2-HOST1 ToolTalk/ISAM[4950]: Fatal error: read failed:
> requested 1024 bytes, got 0 - File exists
> Jul 7 10:35:58 LZ-PPP2-HOST1 inetd[162]: /usr/dt/bin/rpc.ttdbserverd:
> Hangup
>
>
> What's the problem? The server is running abnormal??
>
> Regards,
> Grant
>
>

Hi,

a TT_DB is corrupted (i.e. disk was full or rpc.ttdbserverd
was patched).

Remove it like this:

rm -r /TT_DB

There are probably some more to remove,
the following (not exact) expression will show them:

df -F ufs | awk '{print $NF}' | xargs -IXX ls -ld XX/TT_DB

Then kill the rpc.ttdbserverd process.

--
Michael Tosch
IT Specialist
HP Managed Services Germany
Phone: +49 2407 575 313
Mail: michael.tosch:hp.com