[BlueOnyx:24449] Re: strange issue vsite and hostname

Gerrit Haas Gerrit.Haas at blackpoint.de
Mon Nov 2 01:59:04 -05 2020


Hi Michael,

perfect, now it is working.

Thank you!

Mit freundlichen Grüßen aus Bad Vilbel 

Gerrit Haas 
Systemadministrator  

 
blackpoint GmbH – Friedberger Straße 106b – 61118 Bad Vilbel 

Tel.: +49 6101 65788 32 
IT-Support: +49 6101 65788 - 30 
Fax: +49 6101 65788 - 99
eMail: Gerrit.Haas at blackpoint.de
Tel. Rufbereitschaft (Außerhalb der Arbeitszeiten) +49 6101 65788 - 40 

Vertretungsberechtigt Dirk Estenfeld und Mario Di Rienzo HRB 50093 Frankfurt
am Main USt.-IdNr. de210106871 

Besuchen Sie uns im Internet unter www.blackpoint.de
Problemlos Domains registrieren: www.edns.de
Einfach und günstig Daten sichern: Veeam Cloud Connect


Confidentiality Notice: 
This e-mail message, including any attachments,is for the sole use of the
intended recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, please contact the sender
by reply e-mail and destroy all copies of the original message. 
-----Ursprüngliche Nachricht-----
Von: Blueonyx <blueonyx-bounces at mail.blueonyx.it> Im Auftrag von Michael
Stauber
Gesendet: Samstag, 31. Oktober 2020 20:33
An: blueonyx at mail.blueonyx.it
Betreff: [BlueOnyx:24448] Re: strange issue vsite and hostname

Hi Gerrit,

> Is there possible to see one common thing here?
> - vsite name was part of the first part of the server name.
> 
> Our server: 
> Vsite: *abc*.def.net
> Server: *abc*.xyz.net
> 
> Your server: 
> Vsite: 5210r. ??
> Server: 5210r.smd.net

This was actually the root cause of the issue that caused hostname flippage
between just hostname and FQDN.

I just went through all handlers and constructors on 5209R and 5210R to find
where this happens and identified the issue.

When we update /etc/hostname, we used to only set the hostname, not the
FQDN.

When we set the server name via "hostnamectl set-hostname host.example.com
--static", then this removes the transient hostname from the hostnamectl
output. The restart of systemd-hostnamed or any network related transaction
via NetworkManager parses /etc/hostname, encounters the "short" hostname and
then sets this as Transient hostname again. Then we end up with having both
transient and static hostname.

The fix was to always write the full FQDN into /etc/hostname. That way it
doesn't flip and the transient hostname is no longer set or used, as it's
superseded by the static hostname.

I just published YUM updates for 5209R and 5210R which have that fixed.

--
With best regards

Michael Stauber
_______________________________________________
Blueonyx mailing list
Blueonyx at mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5537 bytes
Desc: not available
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20201102/936e88b7/attachment.p7s>


More information about the Blueonyx mailing list