Comment # 28 on bug 1181970 from
(In reply to Walddys Emmanuel Dorrejo C���spedes from comment #27)
> (In reply to Franck Bui from comment #21)
> > It sounds like restarting apache2 is the action that would mask var.mount,
> > which sounds strange.
> > 
> > But looking at your logs, it appears that var.mount was masked already
> > before:
> > 
> > > [40367.178540] mercurio systemd[1]: logrotate.timer: Failed to queue unit startup job: Unit var.mount is masked.
> > 
> > When the problem is present, can you please attach the output of:
> > 
> >  # find /run/systemd -name var\*.mount -exec ls -l {} \;
> > 
> > ?
> 
> find /run/systemd -name var\*.mount -exec ls -l {} \;
> -rw-r--r-- 1 root root 254 Jul  8 22:40 /run/systemd/generator/var.mount
> lrwxrwxrwx 1 root root 12 Jul  8 22:40
> /run/systemd/generator/local-fs.target.requires/var.mount -> ../var.mount
> lrwxrwxrwx 1 root root 9 Jul  8 21:06 /run/systemd/system/var.mount ->
> /dev/null
> lrwxrwxrwx 1 root root 9 Jul  8 21:06 /run/systemd/system/var-run.mount ->
> /dev/null
> lrwxrwxrwx 1 root root 9 Jul  8 21:06 /run/systemd/system/var-lock.mount ->
> /dev/null
> lrwxrwxrwx 1 root root 9 Jul  8 21:06
> /run/systemd/system/var-lib-machines.mount -> /dev/null
> 
> i think is snapd, because i use certbot, but will have to change to pip to
> install certbot.

but have to test more.


You are receiving this mail because: