Comment # 20 on bug 1055641 from Olli Tuominen

So I'm guessing it is something to do with not able to unmount /var/log

Sep 11 16:05:07 linux-ml6n.suse systemd[1]: Received SIGCHLD from PID 3812
(umount).
Sep 11 16:05:07 linux-ml6n.suse systemd[1]: Child 3812 (umount) died
(code=exited, status=32/n/a)
Sep 11 16:05:07 linux-ml6n.suse systemd[1]: var-log.mount: Child 3812 belongs
to var-log.mount
Sep 11 16:05:07 linux-ml6n.suse systemd[1]: var-log.mount: Mount process
exited, code=exited status=32
Sep 11 16:05:07 linux-ml6n.suse systemd[1]: var-log.mount: Changed unmounting
-> mounted
Sep 11 16:05:07 linux-ml6n.suse systemd[1]: var-log.mount: Job
var-log.mount/stop finished, result=failed
Sep 11 16:05:07 linux-ml6n.suse systemd[1]: Failed unmounting /var/log.
Sep 11 16:05:07 linux-ml6n.suse systemd[1]: libmount event [rescan: yes]
Sep 11 16:05:07 linux-ml6n.suse systemd[1]: libmount event [rescan: yes]
Sep 11 16:05:07 linux-ml6n.suse umount[3812]: umount: /var/log: target is busy
Sep 11 16:05:07 linux-ml6n.suse umount[3812]:         (In some cases useful
info about processes that
Sep 11 16:05:07 linux-ml6n.suse umount[3812]:          use the device is found
by lsof(8) or fuser(1).)
Sep 11 16:05:07 linux-ml6n.suse systemd[1]: Unmounted /var/spool.
Sep 11 16:05:07 linux-ml6n.suse systemd[1]: Child 3836 (umount) died
(code=exited, status=0/SUCCESS)