Hi,
I have this document from Legato:
Hope it helps....
[PARA]Troubleshooting '! no output'[NL][NL]ERROR MESSAGES:[NL][NL]The '! no
output' error gets generated when the networker server and client lose
connection to each other.[NL]The daemon.log may also show these errors:[NL]-
'lost connection errors' [NL]- [saveset] unexpectedly exited[NL]- [saveset]
' for client [client] was terminated by a signal(9).[NL][NL][NL]When the
saveset terminates, if the savegrp will retry to connected to client, and
retry to backup the terminated saveset. For example,[NL][NL]- [saveset]
unexpectedly exited[NL]- [saveset] ! no output[NL]- [saveset] will retry 1
more time[NL]- [saveset] starts over from beginning.[NL][NL]Often the 2nd or
3rd retry is successful, because the loss of connection issue is
intermittent.[NL][NL][NL]EXPLANATIONS:[NL][NL]1) Client crashed, or lost its
network connection (i.e.. a router between the[NL]client and server crashed)
while the client was being[NL]backed up. (ref: man pages for
savegrp)[NL][NL]2) On client, a disk on which the client status was being
logged filled up (perform a df[NL]/nsr/tmp to see if this was the case).
(Reference: man pages for savegrp)[NL][NL]3) Server over loaded issues:[NL]-
Does the error occur on all clients, or only specific ones?[NL]- How busy is
the networker server, when the specific clients are being backed up? What is
the server/client parallel ratio? Are there other clients, running in just
as busy times, that don't get the error? [NL]If the problem does not go
away, by varying the load on the nsrd server, then eliminate server
issues.[NL][NL]4) Client tcp settings:[NL][NL]Test with manual backup,
rather than savegrp. If problem persists, then it's likely that the tcp
settings on the client and the server do not match closely. [NL][NL]For
example, when the client may be configured to send a larger tcp packet,
(tcp_xmit_hiwat) than the server can accept (tcp_recv_hiwat). Then the
client and server "negotiate" a packet size (or tcp window) that both can
live with. However, while this negotiation is going on, there are timers
measuring inactivity (tcp_rexmit_interval_initial, tcp_rexmit_interval_min,
tcp_ip_abort_interval), and depending on the amount of negotiation
happening, the time required for a packet to get from client to server and
return, and the length of the timeouts, it's possible that the client tcp
settings may cause a lost connection to server, and therefore the '! no
output' errors.[NL][NL]To eliminate this, nfs mount a filesystem from the
client, to the server, and backup via the server. For example:[NL][NL]nfs
mount [client]:/var [server]:/mnt/[client]/var[NL][NL]If this test backup is
successful, the you can focus on the client's tcp setup.[NL][NL]5) Client OS
patches and devices:[NL]Because NetWorker expects to maximize network
components, it will send as much data as the TCP settings (see above) will
allow. However, we have seen in the past, where the OS required patches,
upgrades, updated device drivers, or new network adapters, in order for the
tcp sessions to remain connected. Please check OS web sites for lastest
patches.
[NL]Here is the problem or goal:
Error: '!no output'
Error: 'save: lost connection to server, exiting'
Error: [client name]:[saveset] unexpectedly exited'
Error: '[saveset] ' for client [client] was terminated by a signal'
Troubleshooting '! no output'
[NL]Problem Environment:
Solaris
Tru64
NetWorker for UNIX
Hostname resolution is not a problem
Blaster and ftp is successfull between client and server
Problem remains when client/server parallelism is reduced.
Network bandwidth issues not a problem.
-----Mensagem original-----
De: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]Em
nome de Garant, Sonia
Enviada em: sexta-feira, 22 de novembro de 2002 14:13
Para: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Assunto: [Networker] S15c903:E:\! no output
Hi!
Do you know, what mean this error message in my report backup.
! no output
Thanks you!
Sonia Garant
Ministère de l'Emploi et de la Solidarité Sociale
Direction de l' Infrastructure Technologique et des Services Spécialisés
sonia.garant AT mess.gouv.qc DOT ca
(418) 643-6985
--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
