I'm running Fedora Core 6 on a workstation. I want to use it as a syslog server and a nagios server. Everything seems to work fine but the syslogging. When I recieve logs from other machines they all are prepended with the machine name of the server not the machine it is coming from. For example:

Jan 5 12:23:39 orla2cwx dhclient: bound to xxx.xxx.xxx.xxx -- renewal in 1713 seconds.
Jan 5 12:51:39 orla27dx cups: cupsd shutdown succeeded
Jan 5 12:51:39 orla27dx cups: cupsd startup succeeded
Jan 5 12:52:10 orla2cwx nagios: Auto-save of retention data completed successfully.


orla2cwx is the syslog server set up to recieve. The first event is the syslog server. the second and third event are both from another machine on the network where I've restarted CUPS to get an event generated. From my experience it should look like this.

Jan 5 12:23:39 orla2cwx dhclient: bound to xxx.xxx.xxx.xxx -- renewal in 1713 seconds.
Jan 5 12:51:39 jumpjet cups: cupsd shutdown succeeded
Jan 5 12:51:39 jumpjet cups: cupsd startup succeeded
Jan 5 12:52:10 orla2cwx nagios: Auto-save of retention data completed successfully.

Where jumpjet is the name of my workstation. This is exactly the case on all my other syslogging boxes. The only difference is that they are Solaris. I've done a bit of searching today but I don't see anything about a bug in syslog in the latest Fedora release. I'm running a yum update now to see what happens.

orla2cwx is not the same as orla27dx. It's not syslog misbehaving. Somewhere in your name resolution the machine that you think is called "jumpjet" is actually called "orla27dx". Check the /etc/hosts file on your syslog server.

LOL too funny. I *just* figured that out a second ago. I think I need a break. I'm almost crosseyed from setting up nagios.

BTW my DNS c-name is jumpjet and the a-record is orla27dx.

Thanks for pointing that out. mistake