topic Re: tftpd notification on syslog in Operating System - HP-UX

tftpd notification on syslog

Musa I. S. — Tue, 29 Jul 2008 07:12:58 GMT

Hello,

can someone interpret what the message below means. Its on all my servers. Is it a security threat?

tftpd[7725]: Timeout (no requests in 10 minutes)
tftpd[8081]: Timeout (no requests in 10 minutes)
tftpd[8316]: Timeout (no requests in 10 minutes)
tftpd[8551]: Timeout (no requests in 10 minutes)
tftpd[8785]: Timeout (no requests in 10 minutes)
tftpd[9034]: Timeout (no requests in 10 minutes)
tftpd[9269]: Timeout (no requests in 10 minutes)
tftpd[9501]: Timeout (no requests in 10 minutes)
tftpd[9745]: Timeout (no requests in 10 minutes)

Re: tftpd notification on syslog

Fabio Ettore — Tue, 29 Jul 2008 07:19:53 GMT

Hi,

have you an Ignite-UX server? You should let active the deamon for an Ignite-UX Server. Otherwise you could consider to disable it by commenting out the related line in /etc/inetd.conf:

#tftp dgram udp wait root /usr/lbin/tftpd tftpd

Then to reread the configuration
inetd -c

This should stop messages.

HTH.

Best regards,
Fabio

Re: tftpd notification on syslog

Musa I. S. — Tue, 29 Jul 2008 07:34:26 GMT

I have ignite server and I don't want to disable it. How do activate the Ignite daemon.

Regards.

Re: tftpd notification on syslog

Musa I. S. — Tue, 29 Jul 2008 08:05:33 GMT

I have commented the line on the ignite server and the message has stopped for 5 minutes now. what effect does that have on ignite process.

Re: tftpd notification on syslog

Fabio Ettore — Tue, 29 Jul 2008 08:06:24 GMT

Consider that tftp has to be active for Ignite-UX server for example when restoring an Ignite-UX client. It's not needed to have the daemon always activated. However the timeout message sounds like a tftp config. problem, the same issue was indicated in the following thread:

http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1217322124293+28353475&threadId=94274

Apart this I'd suggest trying my suggestion anyway, I mean try to disable it just temporarly as indicated in my previous post, then enable it again by uncommenting the same line and "inetd -c".

If this doesn't help I'd suggest reviewing the /etc/inetd.conf file and checking tftp entry, for example check that the directories on the tftpd line exist.

HTH.

Best regards,
Fabio