Comment 4 for bug 1801389

The issue is that on a fresh installation the maas-syslog service is not running yet. The regiond or rackd will then try to use the syslog socket that maas-syslog should create and listen on, but with it not being up yet its failing.

The code needs to handle delaying the writting of the syslog until the maas-syslog service is up and running, which MAAS actually configures and starts.

Its a chicken and egg problem really, but we can solve it by handling the failure case in MAAS better.