MonitorWare Knowledge Base

"sddev05-vip" shows up in the logs. The hostname is "sddev05".

Dan

• Custom written rsyslog.conf?
• Maintenance Contract?
• Installation support?

It looks like "sddev05-vip" is what your system returns on gethostname(). I have written a quick verification tool. Please download, compile and run:

http://git.adiscon.com/?p=rsyslog.git;a ... ads/master

You can compile it simply with "cc gethostn.c" and then run "./a.out".

Let me know the outcome. If it is as I expect, a work-around may be to create a functionality to allow the config file to set the hostname (actually, you can do this with templates right now). But first let's look how it works...

Rainer

ah, I overlooked one thing: you need to delete the #include "config.h" line. You do not have it if you compile outside of rsyslog's build system.

It returns the correct hostname.

Code: Select all

[dflores@sddev05 ~]$ ./a.out
hostname of this system is 'sddev05'.


That's interesting. I probably need to create a specially-instrumented version to see where it screws up. I have to admit I did not expect this result

This is also occurring on five other hosts, but the host I've been posting information about is the only one I can play around on.

Dan

Yeah - I think there is enough evidence there is something incorrect in rsyslog. As I said, it should use the value from gethostname() but rsyslog's output and the output of the diag program is different, so there must be a problem. I don't think it is in the OS

Please let me know if there's anything I can do to help resolve the issue.

Dan.

Was this issue ever addressed? If so, which release? Thanks.

Dan

I think it was, but all I can do now is refer you to the change log.

Rainer

Thanks. I had looked, but there were no entries that clearly identified it as being addressed.

Dan

I would appreciate if you could give the most recent version a try and report back. I most probably have same time to work on this around the end of the week, if it still is an issue.

Thanks,
Rainer

Same issue with 3.20.0, which was released today.

Dan