Re: [Evergreen] upgraded my 13.1 desktop, now fails to start (sistemad dependency, claims an nfs drive wasn't mounted).
Carlos E. R. wrote: > On 2016-03-16 09:05, Per Jessen wrote: >> I updated my 13.1 office desktop last week, I saw somebody mention a >> new 3.12 kernel. On start-up, it now claims one of two NFS drives >> couldn't be mounted, although in fact they were both mounted. This >> caused postfix and X not to be started. I commented out of the >> mounts in /etc/fstab and rebooted, now it worked. > > I have an nfs mount, but it is done manually, not on boot, and there > is no issue :-? Right, with one manual mount it works fine. -- Per Jessen, Zürich (1.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] upgraded my 13.1 desktop, now fails to start (sistemad dependency, claims an nfs drive wasn't mounted).
Patrick Schaaf wrote: > On Wednesday 16 March 2016 10:16:22 Carlos E. R. wrote: >> On 2016-03-16 09:05, Per Jessen wrote: >> > I updated my 13.1 office desktop last week, I saw somebody mention >> > a >> > new 3.12 kernel. On start-up, it now claims one of two NFS drives >> > couldn't be mounted, although in fact they were both mounted. This >> > caused postfix and X not to be started. I commented out of the >> > mounts in /etc/fstab and rebooted, now it worked. >> >> I have an nfs mount, but it is done manually, not on boot, and there >> is no issue :-? > > I also ran into this issue, some weeks ago. See > > http://bugzilla.suse.com/show_bug.cgi?id=968042 > > It is pretty much analyzed. > > /etc/init.d/xdm > /etc/init.d/ntp > and > /usr/lib/systemd/system/postfix.service > > all have dependencies on remote-fs which they would better not have. The real solution is to have a systemd service unit for rpc-statd when you use NFSv3 mounts. That's what was done in 13.2 and Leap. -- Per Jessen, Zürich (2.0°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] upgraded my 13.1 desktop, now fails to start (sistemad dependency, claims an nfs drive wasn't mounted).
On Wednesday 16 March 2016 10:16:22 Carlos E. R. wrote: > On 2016-03-16 09:05, Per Jessen wrote: > > I updated my 13.1 office desktop last week, I saw somebody mention a > > new 3.12 kernel. On start-up, it now claims one of two NFS drives > > couldn't be mounted, although in fact they were both mounted. This > > caused postfix and X not to be started. I commented out of the mounts > > in /etc/fstab and rebooted, now it worked. > > I have an nfs mount, but it is done manually, not on boot, and there is no > issue :-? I also ran into this issue, some weeks ago. See http://bugzilla.suse.com/show_bug.cgi?id=968042 It is pretty much analyzed. /etc/init.d/xdm /etc/init.d/ntp and /usr/lib/systemd/system/postfix.service all have dependencies on remote-fs which they would better not have. Just updated that bug report with the workarounds I use to cope with the issue. best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] upgraded my 13.1 desktop, now fails to start (sistemad dependency, claims an nfs drive wasn't mounted).
On 2016-03-16 12:40, Patrick Schaaf wrote: > I also ran into this issue, some weeks ago. See > > http://bugzilla.suse.com/show_bug.cgi?id=968042 > > It is pretty much analyzed. > > /etc/init.d/xdm > /etc/init.d/ntp > and > /usr/lib/systemd/system/postfix.service > > all have dependencies on remote-fs which they would better not have. > > Just updated that bug report with the workarounds I use to cope with the > issue. I just had an nfs client problem: when shutting down the machine, it hanged at umounting or stopping the nfs mount. I don't know if it is related. I had to press the power button hard. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] upgraded my 13.1 desktop, now fails to start (sistemad dependency, claims an nfs drive wasn't mounted).
On 2016-03-16 09:05, Per Jessen wrote: > I updated my 13.1 office desktop last week, I saw somebody mention a > new 3.12 kernel. On start-up, it now claims one of two NFS drives > couldn't be mounted, although in fact they were both mounted. This > caused postfix and X not to be started. I commented out of the mounts > in /etc/fstab and rebooted, now it worked. I have an nfs mount, but it is done manually, not on boot, and there is no issue :-? AmonLanc:~ # systemctl status nfs.service nfs.service - LSB: NFS client services Loaded: loaded (/etc/init.d/nfs) Drop-In: /run/systemd/generator/nfs.service.d └─50-insserv.conf-$remote_fs.conf Active: active (running) since Tue 2016-03-15 23:36:17 CET; 10h ago Process: 2487 ExecStart=/etc/init.d/nfs start (code=exited, status=0/SUCCESS) CGroup: /system.slice/nfs.service └─2562 /usr/sbin/rpc.gssd -D -p /var/lib/nfs/rpc_pipefs Mar 16 10:12:07 AmonLanc rpc.gssd[2562]: ERROR: gssd_refresh_krb5_machine_credential: no usable keytab entry found in keytab /etc/krb5.keytab ...r.valinor Mar 16 10:12:07 AmonLanc rpc.gssd[2562]: ERROR: No credentials found for connection to server Telcontar.valinor Mar 16 10:12:07 AmonLanc rpc.gssd[2562]: ERROR: gssd_refresh_krb5_machine_credential: no usable keytab entry found in keytab /etc/krb5.keytab ...r.valinor Mar 16 10:12:07 AmonLanc rpc.gssd[2562]: ERROR: No credentials found for connection to server Telcontar.valinor Mar 16 10:12:08 AmonLanc rpc.gssd[2562]: ERROR: gssd_refresh_krb5_machine_credential: no usable keytab entry found in keytab /etc/krb5.keytab ...r.valinor Mar 16 10:12:08 AmonLanc rpc.gssd[2562]: ERROR: No credentials found for connection to server Telcontar.valinor Mar 16 10:12:08 AmonLanc rpc.gssd[2562]: ERROR: gssd_refresh_krb5_machine_credential: no usable keytab entry found in keytab /etc/krb5.keytab ...r.valinor Mar 16 10:12:08 AmonLanc rpc.gssd[2562]: ERROR: No credentials found for connection to server Telcontar.valinor Mar 16 10:12:08 AmonLanc rpc.gssd[2562]: ERROR: gssd_refresh_krb5_machine_credential: no usable keytab entry found in keytab /etc/krb5.keytab ...r.valinor Mar 16 10:12:08 AmonLanc rpc.gssd[2562]: ERROR: No credentials found for connection to server Telcontar.valinor Hint: Some lines were ellipsized, use -l to show in full. AmonLanc:~ # systemctl status var-cache-zypp-nfs_packages.mount var-cache-zypp-nfs_packages.mount - /var/cache/zypp/nfs_packages Loaded: loaded (/etc/fstab) Active: active (mounted) since Wed 2016-03-16 10:12:08 CET; 1min 9s ago Where: /var/cache/zypp/nfs_packages What: telcontar.valinor:/data/storage_c/repositorios_zypp AmonLanc:~ # -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] upgraded my 13.1 desktop, now fails to start (sistemad dependency, claims an nfs drive wasn't mounted).
Per Jessen wrote: > Wolfgang Rosenauer wrote: > >> Hi, >> >> yes, you are basically on the right list. Just not sure if the right >> people are here to help directly. Therefore I would kindly ask you to >> open a bug in bugzilla still for 13.1. I'll try to involve the right >> people. It's not a guarantee for resolution though. > > Okay, willdo. > https://bugzilla.opensuse.org/show_bug.cgi?id=971331 -- Per Jessen, Zürich (3.0°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] upgraded my 13.1 desktop, now fails to start (sistemad dependency, claims an nfs drive wasn't mounted).
Wolfgang Rosenauer wrote: > Hi, > > yes, you are basically on the right list. Just not sure if the right > people are here to help directly. Therefore I would kindly ask you to > open a bug in bugzilla still for 13.1. I'll try to involve the right > people. It's not a guarantee for resolution though. Okay, willdo. -- Per Jessen, Zürich (2.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] upgraded my 13.1 desktop, now fails to start (sistemad dependency, claims an nfs drive wasn't mounted).
Hi, yes, you are basically on the right list. Just not sure if the right people are here to help directly. Therefore I would kindly ask you to open a bug in bugzilla still for 13.1. I'll try to involve the right people. It's not a guarantee for resolution though. Wolfgang Am 16.03.2016 um 09:05 schrieb Per Jessen: > I updated my 13.1 office desktop last week, I saw somebody mention a > new 3.12 kernel. On start-up, it now claims one of two NFS drives > couldn't be mounted, although in fact they were both mounted. This > caused postfix and X not to be started. I commented out of the mounts > in /etc/fstab and rebooted, now it worked. > > As 13.1 is out of maintenance, I guess I'm on the right list? > > office11:~ # systemctl status home-london.mount > home-london.mount - /home/london >Loaded: loaded (/etc/fstab) >Active: failed (Result: exit-code) since Wed 2016-03-16 09:00:15 CET; 1min > 13s ago > Where: /home/london > What: fileserver:/home/london > Process: 2712 ExecMount=/bin/mount -n -t nfs -o > v3,rsize=8192,wsize=8192,fsc fileserver:/home/london /home/london > (code=exited, status=32) > > Mar 16 09:00:15 office11 mount[2712]: Starting rpc.statd .done > Mar 16 09:00:15 office11 systemd[1]: home-london.mount mount process exited, > code=exited status=32 > Mar 16 09:00:15 office11 systemd[1]: Failed to mount /home/london. > Mar 16 09:00:15 office11 systemd[1]: Unit home-london.mount entered failed > state. > Mar 16 09:00:15 office11 mount[2712]: mount.nfs: rpc.statd is not running but > is required for remote locking. > Mar 16 09:00:15 office11 mount[2712]: mount.nfs: Either use '-o nolock' to > keep locks local, or start statd. > Mar 16 09:00:15 office11 mount[2712]: mount.nfs: an incorrect mount option > was specified > > > Looks like a timing issue wrt rpc.statd ? On one boot-up it'll be > /home/london, on another it'll be /home/barcelona > > > ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
