http://bugzilla.suse.com/show_bug.cgi?id=929471 --- Comment #1 from Dennis Golden --- I have been able to create a work around by adding the command "/bin/hostname -F /etc/hostname" to /etc/init.d/boot.local -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 Dennis Golden changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dgolden@golden-consulting.c | |om -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 Dennis Golden changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|hostname is not initialized |hostname is not initialized |so postfix default |so postfix default |hostname/domainnam fail |hostname/domain name fail -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|ms@suse.com |yast-internal@suse.de --- Comment #2 from Marcus Schaefer --- looks more like a yast think not setting the hostname on install or is this referring to another kind of system ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c9 Pawel Wieczorkiewicz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pwieczorkiewicz@suse.com Assignee|wicked-maintainers@suse.de |systemd-maintainers@suse.de --- Comment #9 from Pawel Wieczorkiewicz --- It's systemd's responsibility, reassigning to systemd-maintainers then. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c11 Dennis Golden changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dgolden@golden-co | |nsulting.com) | --- Comment #11 from Dennis Golden --- Created attachment 643513 --> http://bugzilla.suse.com/attachment.cgi?id=643513&action=edit output of journalctl -axb This is output of "journalctl -axb" after booting with systemd.log_level=debug. I verified that the kernel hostname had NOT been initialized. To initialize required that I enter "/bin/hostname -F /etc/hostname". This is the same behaviour of the original bug. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c13 --- Comment #13 from Dr. Werner Fink --- Could it be that here the DNS/FQDN (Fully Qualified Domain Name) is mixed with the static hostname which is given in /proc/sys/kernel/hostname? The first is bind normally to the first (ether)net device whereas the second is set by systemd-hostnamed.service(8) (compare with man:hostnamectl(1) and hostname(7)). In common practice the names before the very first dot do agree but this is not required. Beside this there also exist YP/NIS domain names which may or may not agree with the DSN domain name. hostname - show or set the system's host name domainname - show or set the system's NIS/YP domain name dnsdomainname - show the system's DNS domain name nodename - show or set the system's DECnet node name For any MTA the Fully Qualified Domain Name of the host is the one which (IMHO) should be used as e.g. relay hosts/servers do check for this name. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c15 --- Comment #15 from Dennis Golden --- (In reply to Dr. Werner Fink from comment #13)

Could it be that here the DNS/FQDN (Fully Qualified Domain Name) is mixed with the static hostname which is given in /proc/sys/kernel/hostname?

The first is bind normally to the first (ether)net device whereas the second is set by systemd-hostnamed.service(8) (compare with man:hostnamectl(1) and hostname(7)). In common practice the names before the very first dot do agree but this is not required. Beside this there also exist YP/NIS domain names which may or may not agree with the DSN domain name.

hostname - show or set the system's host name domainname - show or set the system's NIS/YP domain name dnsdomainname - show the system's DNS domain name nodename - show or set the system's DECnet node name

For any MTA the Fully Qualified Domain Name of the host is the one which (IMHO) should be used as e.g. relay hosts/servers do check for this name.

The value in /proc/sys/kernel/hostname is set by the hostname command of which is contained within the /etc/hostname file. Regards, Dennis -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c17 --- Comment #17 from Dr. Werner Fink --- (In reply to Dennis Golden from comment #14) The static hostname is set by systemd-hostnamed.service and with this you may check this systemctl is-enabled systemd-hostnamed.service systemctl status -a systemd-hostnamed.service journalctl --unit systemd-hostnamed.service you may check this out (In reply to Dennis Golden from comment #15) I know ;) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c19 --- Comment #19 from Thomas Blume --- I think this issue is the same as reported here: https://lists.debian.org/debian-user/2015/03/msg00287.html The kernel.hostname sysctl is set without domain: -->-- dg-linux:~ # sysctl -a | grep hostname kernel.hostname = dg-linux --<-- This is then used as the transient hostname by systemd. The hostname call is correcting this: -->-- dg-linux:~ # hostname -F /etc/hostname dg-linux:~ # sysctl -a | grep hostname kernel.hostname = dg-linux.golden-consulting.com --<-- It is also corrected when you remove the transient hostname via: hostnamectl --transient set-hostname "" This will then use the correct static hostname. The question is, what is setting kernel.hostname to the wrong value? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c21 --- Comment #21 from Dennis Golden --- Then the assertion that systemd is compatible with sysvinit is false. Postfix (for one) assumes that the gethostname() returns the FQDM. Under sysvinit the hostname has always allowed postfix to use the correct host/domain name. We were promised that systemd would be compatible. In fact it is not and I for one have a problem when there is no apparent interest in making it so. Regards, Dennis -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c23 Thomas Blume changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(dgolden@golden-co | |nsulting.com) --- Comment #23 from Thomas Blume --- (In reply to Dennis Golden from comment #21)

Then the assertion that systemd is compatible with sysvinit is false. Postfix (for one) assumes that the gethostname() returns the FQDM.

Under sysvinit the hostname has always allowed postfix to use the correct host/domain name.

We were promised that systemd would be compatible. In fact it is not and I for one have a problem when there is no apparent interest in making it so.

What about simply putting: kernel.hostname = dg-linux.golden-consulting.com in /etc/sysctl.conf? I've tested with the gethostname function: -->-- #include #include #include int main (int argc, char *argv[]) { char host[MAXHOSTNAMELEN]; char domain[64]; gethostname (host, sizeof host); printf ("host: %s\n", host); getdomainname(domain, 64); return printf ("domain: %s\n", domain); } --<-- And it returned the desired output: dg-linux:/tmp # /tmp/a.out host: dg-linux.golden-consulting.com domain: (none) Before setting the sysctl, it was: dg-linux:/tmp # ./a.out host: dg-linux domain: (none) Since postfix is using gethostname, that should fix it for you. However, I'm not really sure what else is using gethostname and might create undesired side effects. Actually, if it is only postfix that created problems for you, the simplest way is IMHO, if you just put: myhostname = dg-linux.golden-consulting.com in /etc/postfix/main.cf I still don't understand why this isn't set on your machine. postfix.service has an entry: ExecStartPre=/etc/postfix/system/config_postfix which calls /usr/sbin/config.postfix the first time you start the service. As noted in comment#12 /usr/sbin/config.postfix will write the configuration into main.cf and postfix wouldn't use gethostname anymore. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c25 --- Comment #25 from Dr. Werner Fink --- (In reply to Dennis Golden from comment #22) Hmm ... from attachment #643931 I can see dg-linux:~ # journalctl --unit systemd-hostnamed.service -- Logs begin at Fri 2015-02-20 20:53:14 CST, end at Fri 2015-08-14 12:04:23 CDT. -- Feb 20 19:55:36 linux-sbf4 systemd[1]: Starting Hostname Service... Feb 20 19:55:36 linux-sbf4 systemd[1]: Started Hostname Service. -- Reboot -- Aug 11 12:24:36 dg-linux systemd[1]: Enqueued job systemd-hostnamed.service/start as 1444 Aug 11 12:24:36 dg-linux systemd[1]: Starting Hostname Service... Aug 11 12:24:36 dg-linux systemd[1]: About to execute: /usr/lib/systemd/systemd-hostnamed Aug 11 12:24:36 dg-linux systemd[1]: Forked /usr/lib/systemd/systemd-hostnamed as 2577 Aug 11 12:24:36 dg-linux systemd[1]: systemd-hostnamed.service changed dead -> start ... why do you think this had not happen? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c27 --- Comment #27 from Dr. Werner Fink --- Rational for choosing a hostname without domain name can be found in RFC 1178 and RFC 1123 https://tools.ietf.org/html/rfc1178 [...] Avoid domain names. For technical reasons, domain names should be avoided. In particular, name resolution of non-absolute hostnames is problematic. Resolvers will check names against domains before checking them against hostnames. But we have seen instances of mailers that refuse to treat single token names as domains. For example, assume that you mail to "libes@rutgers" from yale.edu. Depending upon the implementation, the mail may go to rutgers.edu or rutgers.yale.edu (assuming both exist). [...] https://tools.ietf.org/html/rfc1123 2.1 Host Names and Numbers The syntax of a legal Internet host name was specified in RFC-952 [DNS:4]. One aspect of host name syntax is hereby changed: the restriction on the first character is relaxed to allow either a letter or a digit. Host software MUST support this more liberal syntax. Host software MUST handle host names of up to 63 characters and SHOULD handle host names of up to 255 characters. [...] Btw: the array for the hostname in /proc/sys/kernel/hostname has 64 characters which includes the trailing ASCII null as well as the hostname. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c29 --- Comment #29 from Dennis Golden --- (In reply to Thomas Blume from comment #23)

(In reply to Dennis Golden from comment #21)

...

Then the assertion that systemd is compatible with sysvinit is false. Postfix (for one) assumes that the gethostname() returns the FQDM.

Under sysvinit the hostname has always allowed postfix to use the correct host/domain name.

We were promised that systemd would be compatible. In fact it is not and I for one have a problem when there is no apparent interest in making it so.

What about simply putting:

kernel.hostname = dg-linux.golden-consulting.com

in /etc/sysctl.conf?

I've tested with the gethostname function:

Yes I understand. I try not to hard code FQDN in any configuration files since yast2 network configuration updates the /etc/hostname file (and other configuration files). If there are changes made to the network configuration, the administrator has to remember exactly which configuration files were modified.

-->-- #include #include #include

int main (int argc, char *argv[]) { char host[MAXHOSTNAMELEN]; char domain[64];

gethostname (host, sizeof host); printf ("host: %s\n", host);

getdomainname(domain, 64); return printf ("domain: %s\n", domain); } --<--

And it returned the desired output:

dg-linux:/tmp # /tmp/a.out host: dg-linux.golden-consulting.com domain: (none)

Before setting the sysctl, it was:

dg-linux:/tmp # ./a.out host: dg-linux domain: (none)

Since postfix is using gethostname, that should fix it for you. However, I'm not really sure what else is using gethostname and might create undesired side effects.

Actually, if it is only postfix that created problems for you, the simplest way is IMHO, if you just put:

myhostname = dg-linux.golden-consulting.com

in /etc/postfix/main.cf

See above comment.

I still don't understand why this isn't set on your machine. postfix.service has an entry:

ExecStartPre=/etc/postfix/system/config_postfix

which calls /usr/sbin/config.postfix the first time you start the service. As noted in comment#12 /usr/sbin/config.postfix will write the configuration into main.cf and postfix wouldn't use gethostname anymore.

I have moved my configuration files (main.cf and master.cf) from one system to new releases of openSUSE for over 10 years, only modifying the files for new functionality of postfix. I never update an existing system. I always do a new install and reconfigure after testing and I would really be upset if config_postfix were to overwrite my existing configuration. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c31 --- Comment #31 from Dr. Werner Fink --- (In reply to Dennis Golden from comment #30) The hostname/domainname used in uname(1), set with sysctl(8) or gethostname(2)/getdomainname(2), and accessible at /proc/sys/kernel/hostname or /proc/sys/kernel/domainname has nothing todo with the full qualified hostname for the network device of the system which has to be used by a MTA like postfix or sendmail. The domainname with is NIS/YP and the hostname is for the local system only! It is very common to use the same short hostname for the local system as for the first part, aka without domainname, of the full qualified hostname of the first network device but the configuration of a MTA should use the name space of the network device and never the that of the local system! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c35 Thomas Blume changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jen142@promessage.com --- Comment #35 from Thomas Blume --- *** Bug 858385 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c37 Thomas Blume changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|systemd-maintainers@suse.de |yast2-maintainers@suse.de --- Comment #37 from Thomas Blume --- Reassigning to yast maintainers, since this seems to be an issue of the installer. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c39 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@suse.com --- Comment #39 from Josef Reidinger --- michal ping -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=929471 http://bugzilla.suse.com/show_bug.cgi?id=929471#c41 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P5 - None Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #41 from Stefan Hundhammer --- Resetting bug priority. This is meant for project managers, not for bug reporters. According to Martin's comment #40, this is a user error, not a bug. -> INVALID -- You are receiving this mail because: You are on the CC list for the bug.