when startup delays become bugs

[Chris Murphy]

On May 14, 2013, at 4:10 PM, Igor Gnatenko <i.gnatenko.brain at gmail.com> wrote:
>> 
> See this bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=962038
> Can you provide from console hostnamectl ?



Static hostname: f19q
Takes about 20 seconds before I can ssh into the VM, but sendmail takes forever to start. Not graceful.
[root at f19q ~]# systemd-analyze blame
      1min 372ms sendmail.service
      1min 281ms sm-client.service
         12.249s chronyd.service
         11.852s restorecond.service
          9.306s NetworkManager.service
          8.026s NetworkManager-wait-online.service


Static hostname: f19q.localdomain
Takes 1.5 minutes before I can ssh into the VM, but the sendmail.service is now about 2 seconds instead of a minute.

[root at f19q ~]# systemd-analyze blame
         51.688s firewalld.service
         50.696s restorecond.service
         16.989s avahi-daemon.service
         16.023s systemd-logind.service
         11.908s NetworkManager-wait-online.service


So either way, I get nailed with unreasonable startup times. And avahi doesn't play nice with the localdomain extension anyway. Without the extension I ssh into boxes just like I do from Windows or OS X:

ssh chris at f19q.local

Whereas if I change the hostname to f19q.localdomain, to ssh into the system now I have to use a non-obvious, nonstandard:

ssh chris at f19qlocaldomain


So the addition of localdomain doesn't seem like the right fix. sendmail is just being stupid in my view, and not failing gracefully.

I do not have control over my DNS server, so if it's misconfigured by my ISP, there's nothing I can do about it which means the system I use needs to be smarter about such eventualities.


Chris Murphy