syslog: couldn't send reply to 2130706433

Joseph S D Yao jsdy at cospo.osis.gov
Wed Sep 1 18:33:14 UTC 1999


> What could be the cause of the following message? 
> 
> Sep  1 15:37:22 XXXXXXXX syslog: couldn't send reply to 2130706433
> Sep  1 15:37:22 XXXXXXXX syslog: couldn't send reply to -2035727767
> 
> Pinging 2130706433 results in
> 
> # ping 2130706433
> PING 2130706433: 64 byte packets
> 64 bytes from 127.0.0.1: icmp_seq=0. time=0. ms
> 64 bytes from 127.0.0.1: icmp_seq=1. time=0. ms
>  
> The system is a C200 running HP-UX 10.20. 
> 
> TIA,
> 
> Ralf
> -- 
> Ralf Hildebrandt <R.Hildebrandt at tu-bs.de> www.stahl.bau.tu-bs.de/~hildeb

Is this bind-related????

I would have said that someone might have used a %d instead of a %s,
except that, as you point out, 2130706433(10) is IP address 127.0.0.1.
Looking at the other one, -2035727767(10) is IP address 134.169.66.105,
which is "statws05.stat.bau.tu-bs.de".

I still find it odd that someone would send this a message formatted in
this manner to syslog ... or from syslog, as it appears.  Did you check
the logged PID?

--
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.


More information about the bind-users mailing list