Xymon server fqdn

Ok...adding to /etc/hosts made no difference.  I had to set the hostname to
the fqdn so it would get picked up by uname -a and hostname as the fqdn.
Of course, I had to restart xymon server to get that picked up correctly (I
always forget to do that).

On Thu, Jan 5, 2017 at 5:23 PM, Galen Johnson <user-fc632e705d24@xymon.invalid> wrote:

I already did that.  I'm currently setting the fqdn first in /etc/hosts
since I've been bitten by gethostbyname before with name sensitive
services.  I'll let you know if that works. (only had the default localhost
stuff before)

=G=

On Thu, Jan 5, 2017 at 5:20 PM, Japheth Cleaver <user-87556346d4af@xymon.invalid>
wrote:

On 1/5/2017 2:14 PM, Galen Johnson wrote:

This was a fresh install (switched over when I replaced the old Centos 6
server).  It started fresh with 4.3.27.  Both hostname and uname -n provide
the shortname.

=G=


Ahh, that'll do it then.

IIRC $HOSTNAME is used if available, but the uname syscall, followed by a
fork to `uname -n` itself, are then used to derive the local name.

Just modify XYMONSERVERWWWNAME by hand in xymonserver.cfg to whatever the
external view of the WWW address should be and it should work.

HTH,
-jc


On Thu, Jan 5, 2017 at 5:04 PM, Japheth Cleaver <user-87556346d4af@xymon.invalid>
wrote:

Yeah, this was a change around 4.3.18:

From: xymon.CHANGES.terabithia

- On new server installs, $XYMONSERVERHOSTNAME will be set to the
MACHINEDOTS value
  given by xymoncmd (which derives it from $HOSTNAME or `uname -n`).
  $XYMONSERVERWWWNAME will be set to the XYMONSERVERHOSTNAME value.


I believe this was related to the migration of settings from wrapper
scripts to xymoncmd settings, as how $MACHINEDOTS was needed to be inverted
in systemd-land...

This *should* have been handled by the RPM upgrade process around this
time... Not sure why it wasn't in this case :/

-jc


On 1/5/2017 1:42 PM, Galen Johnson wrote:

Yeah, I thought that was odd, too.  I checked my old configs
(non-terabithia) and they are set exactly like you mention.  Are you using
the terabithia rpms?  I suspect it is something specific to those.

=G=

On Thu, Jan 5, 2017 at 4:39 PM, Ralph Mitchell <user-00a5e44c48c0@xymon.invalid>
wrote:

$MACHINEDOTS should be being set in xymonserver.cfg, I think.  In my
installation (xymon-4.3.12) I have it the other way around:

XYMONSERVERHOSTNAME="server.domain.com"      # The hostname of your
server
MACHINEDOTS="$XYMONSERVERHOSTNAME"        # This systems hostname

And for some reason I don't remember, the WWW name is set explicitly:

XYMONSERVERWWWNAME="server.domain.com"        # The name used for this
servers' webserver


Ralph Mitchell


On Thu, Jan 5, 2017 at 4:24 PM, Galen Johnson <user-fc632e705d24@xymon.invalid>
wrote:

Interestingly, emails from my work address don't seem to be making it
to the list...

Hey,

I'm at a loss here.  I'm using the Terabithia RPM for my Xymon server
and the links that are provided in emails only use the shortname of my
xymon server.  For example,

https://shortname/xymon

instead of

https://shortname.example.com/xymon

I've dug through the xymonserver.cfg file to see where this is being
set and I can trace it to

XYMONSERVERWWWNAME="$XYMONSERVERHOSTNAME"       # The name used for
this hosts' webserver

where XYMONSERVERHOSTNAME is defined as

XYMONSERVERHOSTNAME="$MACHINEDOTS"              # The hostname of
your server. In the RPM, xymoncmd sets this before we get here

I have FQDN="TRUE" set as well.

Any idea where I can set this to give me the actual fqdn of the
server?  I'm assuming that 'xymoncmd' is just pulling in 'hostname' rather
than 'hostname -f'.  I must be missing something.

Anyone have any insight into what I may be missing?

=G=

Xymon mailing user-d459c9d661b6@xymon.invalid