tt_authfile_entry_missing
Is anybody often using SPECRE RF to design RF circuit?
My MSN: carmine_rene@hotmail.com
welcome to contact me!
:)
if you are running the simulation on a computer with quota set, you might be exceeding your quota.
I think it is not the problem of quota set since when I log into the workstation there is no warning about quota set.
I change workstation and simulate again. Same error occur.
Now I get the error log of workstation as following:
Jun 27 12:43:09 shhp3 syslog: libtt[21399]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 27 12:43:09 shhp3 syslog: libtt[21400]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 27 12:43:09 shhp3 syslog: libtt[21402]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 27 12:43:09 shhp3 syslog: libtt[21404]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 27 13:50:14 shhp3 rpcbind: cannot accept connection: bad call sequence numb
er (current state 4)
Jun 27 13:50:14 shhp3 rpcbind: cannot accept connection: bad call sequence numb
er (current state 4)
Jun 30 08:51:24 shhp3 rpcbind: cannot accept connection: bad call sequence numb
er (current state 4)
Jun 30 08:51:24 shhp3 rpcbind: cannot accept connection: bad call sequence numb
er (current state 4)
Jun 30 10:18:55 shhp3 syslog: libtt[21651]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 10:18:55 shhp3 syslog: libtt[21659]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:45:25 shhp3 syslog: libtt[21789]: ttdt_Xt_input_handler(): tttk_messag
e_receive(): TT_ERR_NOMP^INo ttsession process is running, probably because tt_o
pen() has not been called yet. If this code is returned from tt_open() it means
ttsession could not be started, which generally means ToolTalk is not installed
on this system.
Jun 30 11:45:25 shhp3 syslog: libtt[22222]: ttdt_Xt_input_handler(): tttk_messag
e_receive(): TT_ERR_NOMP^INo ttsession process is running, probably because tt_o
pen() has not been called yet. If this code is returned from tt_open() it means
ttsession could not be started, which generally means ToolTalk is not installed
on this system.
Jun 30 11:45:25 shhp3 syslog: libtt[21797]: ttdt_Xt_input_handler(): tttk_messag
e_receive(): TT_ERR_NOMP^INo ttsession process is running, probably because tt_o
pen() has not been called yet. If this code is returned from tt_open() it means
ttsession could not be started, which generally means ToolTalk is not installed
on this system.
Jun 30 11:49:02 shhp3 syslog: libtt[26594]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:49:02 shhp3 syslog: libtt[26602]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:50:17 shhp3 syslog: libtt[26716]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:50:17 shhp3 syslog: libtt[26724]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:50:31 shhp3 syslog: libtt[26819]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:50:31 shhp3 syslog: libtt[26827]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:50:45 shhp3 syslog: libtt[26914]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:50:45 shhp3 syslog: libtt[26922]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:51:31 shhp3 syslog: libtt[26999]: clnt_create for rpc.ttdbserverd on s
hbkser failed: RPC: Program not registered
Jun 30 11:54:35 shhp3 : su : + 16 hfeng-sysfh
Jun 30 11:54:44 shhp3 : su : + 16 hfeng-cmren
Jun 30 11:51:31 shhp3 syslog: libtt[26999]: clnt_create for rpc.ttdbserverd on s
hbkser failed: RPC: Program not registered
Jun 30 12:00:07 shhp3 above message repeats 3 times
Jun 30 12:00:07 shhp3 syslog: libtt[27465]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 12:00:07 shhp3 syslog: libtt[27473]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
I think it is not the problem of quota set since when I log into the workstation there is no warning about quota set.
I change workstation and simulate again. Same error occur.
Now I get the error log of workstation as following:
Jun 27 12:43:09 shhp3 syslog: libtt[21399]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 27 12:43:09 shhp3 syslog: libtt[21400]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 27 12:43:09 shhp3 syslog: libtt[21402]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 27 12:43:09 shhp3 syslog: libtt[21404]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 27 13:50:14 shhp3 rpcbind: cannot accept connection: bad call sequence numb
er (current state 4)
Jun 27 13:50:14 shhp3 rpcbind: cannot accept connection: bad call sequence numb
er (current state 4)
Jun 30 08:51:24 shhp3 rpcbind: cannot accept connection: bad call sequence numb
er (current state 4)
Jun 30 08:51:24 shhp3 rpcbind: cannot accept connection: bad call sequence numb
er (current state 4)
Jun 30 10:18:55 shhp3 syslog: libtt[21651]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 10:18:55 shhp3 syslog: libtt[21659]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:45:25 shhp3 syslog: libtt[21789]: ttdt_Xt_input_handler(): tttk_messag
e_receive(): TT_ERR_NOMP^INo ttsession process is running, probably because tt_o
pen() has not been called yet. If this code is returned from tt_open() it means
ttsession could not be started, which generally means ToolTalk is not installed
on this system.
Jun 30 11:45:25 shhp3 syslog: libtt[22222]: ttdt_Xt_input_handler(): tttk_messag
e_receive(): TT_ERR_NOMP^INo ttsession process is running, probably because tt_o
pen() has not been called yet. If this code is returned from tt_open() it means
ttsession could not be started, which generally means ToolTalk is not installed
on this system.
Jun 30 11:45:25 shhp3 syslog: libtt[21797]: ttdt_Xt_input_handler(): tttk_messag
e_receive(): TT_ERR_NOMP^INo ttsession process is running, probably because tt_o
pen() has not been called yet. If this code is returned from tt_open() it means
ttsession could not be started, which generally means ToolTalk is not installed
on this system.
Jun 30 11:49:02 shhp3 syslog: libtt[26594]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:49:02 shhp3 syslog: libtt[26602]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:50:17 shhp3 syslog: libtt[26716]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:50:17 shhp3 syslog: libtt[26724]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:50:31 shhp3 syslog: libtt[26819]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:50:31 shhp3 syslog: libtt[26827]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:50:45 shhp3 syslog: libtt[26914]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:50:45 shhp3 syslog: libtt[26922]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 11:51:31 shhp3 syslog: libtt[26999]: clnt_create for rpc.ttdbserverd on s
hbkser failed: RPC: Program not registered
Jun 30 11:54:35 shhp3 : su : + 16 hfeng-sysfh
Jun 30 11:54:44 shhp3 : su : + 16 hfeng-cmren
Jun 30 11:51:31 shhp3 syslog: libtt[26999]: clnt_create for rpc.ttdbserverd on s
hbkser failed: RPC: Program not registered
Jun 30 12:00:07 shhp3 above message repeats 3 times
Jun 30 12:00:07 shhp3 syslog: libtt[27465]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
Jun 30 12:00:07 shhp3 syslog: libtt[27473]: _Tt_session::client_session_init():
TT_AUTHFILE_ENTRY_MISSING
to check if the quota system is enabled, you can use "quota -v". From the logs you have posted, I understand that you might have problems with ToolTalk, but I believe it shouldn't affect you simulations, it should affect some small software like dtpad, but not spectre. I have a problem with ToolTalk on the workstation I am working, when I try to run dtpad from a remote terminal it gives an error for ToolTalk protocol, but I am able to run simulations without errors from the remote terminal.
