mount cifs from fstab with networkmanager

[lynn]

12.3
Hi
NetworkManager is not up in time to mount cifs shares from fstab. I have
to use ifup or the automounter.

Is there any way to get NetworkManager up in time? My Ubuntu laptop
manages it OK.

Thanks,
L x

[Andrey Borzenkov]

В Sun, 08 Sep 2013 10:23:41 +0200

Post by lynn
12.3
Hi
NetworkManager is not up in time to mount cifs shares from fstab. I have
to use ifup or the automounter.
Is there any way to get NetworkManager up in time? My Ubuntu laptop
manages it OK.

Make sure NetworkManager-wait-online service is enabled:

systemctl enable NetworkManager-wait-online.service

Set NM_ONLINE_TIMEOUT in /etc/sysconfig/network/config to a value
greater than required to establish connection.

[lynn]

Post by Andrey Borzenkov
В Sun, 08 Sep 2013 10:23:41 +0200

Post by lynn
12.3
Hi
NetworkManager is not up in time to mount cifs shares from fstab. I have
to use ifup or the automounter.
Is there any way to get NetworkManager up in time? My Ubuntu laptop
manages it OK.

systemctl enable NetworkManager-wait-online.service
Set NM_ONLINE_TIMEOUT in /etc/sysconfig/network/config to a value
greater than required to establish connection.

Thanks. It works fine.
L x

[lynn]

Post by Andrey Borzenkov
В Sun, 08 Sep 2013 10:23:41 +0200

Post by lynn
12.3
Hi
NetworkManager is not up in time to mount cifs shares from fstab. I have
to use ifup or the automounter.
Is there any way to get NetworkManager up in time? My Ubuntu laptop
manages it OK.

systemctl enable NetworkManager-wait-online.service
Set NM_ONLINE_TIMEOUT in /etc/sysconfig/network/config to a value
greater than required to establish connection.

Thanks, but unfortunately, it does not start at boot even though I've
enabled it.

Any ideas to get it to fire up at boot?
Thanks,
L x

[Andrey Borzenkov]

В Fri, 13 Sep 2013 19:30:02 +0200

Post by lynn

Post by Andrey Borzenkov
В Sun, 08 Sep 2013 10:23:41 +0200

Post by lynn
12.3
Hi
NetworkManager is not up in time to mount cifs shares from fstab. I have
to use ifup or the automounter.
Is there any way to get NetworkManager up in time? My Ubuntu laptop
manages it OK.

systemctl enable NetworkManager-wait-online.service
Set NM_ONLINE_TIMEOUT in /etc/sysconfig/network/config to a value
greater than required to establish connection.

Thanks, but unfortunately, it does not start at boot even though I've
enabled it.

What "systemctl status NetworkManager-wait-online.service" says?

Post by lynn
Any ideas to get it to fire up at boot?
Thanks,
L x

[lynn]

Post by Andrey Borzenkov
В Fri, 13 Sep 2013 19:30:02 +0200

Post by lynn

Post by Andrey Borzenkov
В Sun, 08 Sep 2013 10:23:41 +0200

Post by lynn
12.3
Hi
NetworkManager is not up in time to mount cifs shares from fstab. I have
to use ifup or the automounter.
Is there any way to get NetworkManager up in time? My Ubuntu laptop
manages it OK.

systemctl enable NetworkManager-wait-online.service
Set NM_ONLINE_TIMEOUT in /etc/sysconfig/network/config to a value
greater than required to establish connection.

Thanks, but unfortunately, it does not start at boot even though I've
enabled it.

What "systemctl status NetworkManager-wait-online.service" says?

Post by lynn
Any ideas to get it to fire up at boot?
Thanks,
L x

NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded
(/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled)
Active: inactive (dead) since Fri, 2013-09-13 23:46:50 CEST;
1min 48s ago
Process: 3382 ExecStart=/bin/bash -c if [ ${NM_ONLINE_TIMEOUT}
-gt 0 ]; then /usr/bin/nm-online -q --timeout=${NM_ONLINE_TIMEOUT} ;
else /bin/true ; fi (code=exited, status=0/SUCCESS)
CGroup:
name=systemd:/system/NetworkManager-wait-online.service

What sort of values for NM_ONLINE_TIMEOUT are we thinking about? In time
honoured fashion I've tried 2 4 8 16 31 and 65 so far.

Thanks,
L x

[Andrey Borzenkov]

В Fri, 13 Sep 2013 23:51:45 +0200

Post by lynn

Post by Andrey Borzenkov
В Fri, 13 Sep 2013 19:30:02 +0200

Post by lynn

Post by Andrey Borzenkov
В Sun, 08 Sep 2013 10:23:41 +0200

Post by lynn
12.3
Hi
NetworkManager is not up in time to mount cifs shares from fstab. I have
to use ifup or the automounter.
Is there any way to get NetworkManager up in time? My Ubuntu laptop
manages it OK.

systemctl enable NetworkManager-wait-online.service
Set NM_ONLINE_TIMEOUT in /etc/sysconfig/network/config to a value
greater than required to establish connection.

Thanks, but unfortunately, it does not start at boot even though I've
enabled it.

What "" says?

Post by lynn
Any ideas to get it to fire up at boot?
Thanks,
L x

NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded
(/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled)
Active: inactive (dead) since Fri, 2013-09-13 23:46:50 CEST;
1min 48s ago
Process: 3382 ExecStart=/bin/bash -c if [ ${NM_ONLINE_TIMEOUT}
-gt 0 ]; then /usr/bin/nm-online -q --timeout=${NM_ONLINE_TIMEOUT} ;
else /bin/true ; fi (code=exited, status=0/SUCCESS)
name=systemd:/system/NetworkManager-wait-online.service
What sort of values for NM_ONLINE_TIMEOUT are we thinking about? In time
honoured fashion I've tried 2 4 8 16 31 and 65 so far.

As much time as your NetworkManager needs to configure interfaces.

Please show your /etc/fstab and also output of

systemctl status NetworkManager-wait-online.service path-to-your-cifs-mount-point.mount

Where /foo/bar becomes foo-bar.mount.

And please show ALL output, not the parts you think are important.
Journal log entries that are output by systemctl status are important to
see relative timing.

[lynn]

Post by Andrey Borzenkov
As much time as your NetworkManager needs to configure interfaces.
Please show your /etc/fstab and also output of
systemctl status NetworkManager-wait-online.service path-to-your-cifs-mount-point.mount
Where /foo/bar becomes foo-bar.mount.
And please show ALL output, not the parts you think are important.
Journal log entries that are output by systemctl status are important to
see relative timing.

Hi
We just converted to autofs with ifup and it works fine but the same
problem with NetworkManager, so I'd still like to sort it out. But for
autofs.

Do I have to start another thread for NetworkManager with autofs?

Thanks
L x

[lynn]

Post by Andrey Borzenkov
As much time as your NetworkManager needs to configure interfaces.
Please show your /etc/fstab and also output of
systemctl status NetworkManager-wait-online.service path-to-your-cifs-mount-point.mount
Where /foo/bar becomes foo-bar.mount.
And please show ALL output, not the parts you think are important.
Journal log entries that are output by systemctl status are important to
see relative timing.

OK, I can't get it going with fstab but I think I've got it going with
autofs:

Here are the fstab entries which I've commented:
#//altea/users /home/users cifs sec=krb5,username=cifsuser,multiuser 0 0
#//altea/shared /home/shared cifs sec=krb5,username=cifsuser,multiuser 0
0

Here it is converted to autofs:

dn: CN=auto.master,CN=HH3,CN=defaultMigrationContainer30,DC=hh3,DC=site
objectClass: top
objectClass: nisMap
cn: auto.master
name: auto.master

dn:
cn=/home/users,CN=auto.master,CN=HH3,CN=defaultMigrationContainer30,DC=hh3,DC=site
objectClass: top
objectClass: nisObject
cn: /home/users
name: /home/users
nisMapName: auto.master
nisMapEntry: auto.users

dn: CN=auto.users,CN=HH3,CN=defaultMigrationContainer30,DC=hh3,DC=site
objectClass: top
objectClass: nisMap
cn: auto.users
name: auto.users
nisMapName: auto.users

dn:
cn=*,CN=auto.users,CN=HH3,CN=defaultMigrationContainer30,DC=hh3,DC=site
objectClass: top
objectClass: nisObject
cn: *
name: *
msSFU30Name: *
msSFU30NisDomain: hh3
nisMapName: auto.users
nisMapEntry:
-fstype=cifs,sec=krb5,username=cifsuser,multiuser ://altea/users/&


systemctl status NetworkManager-wait-online.service

NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded
(/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled)
Active: inactive (dead) since Sat, 2013-09-14 18:17:05 CEST; 2min 11s
ago
Process: 413 ExecStart=/bin/bash -c if [ ${NM_ONLINE_TIMEOUT} -gt 0 ];
then /usr/bin/nm-online -q --timeout=${NM_ONLINE_TIMEOUT} ;
else /bin/true ; fi (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/NetworkManager-wait-online.service

Which I think is correct as it runs only at boot and then dies.

systemctl status NetworkManager-wait-online.service /home/users/.mount
NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded
(/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled)
Active: inactive (dead) since Sat, 2013-09-14 18:17:05 CEST; 4min 53s
ago
Process: 413 ExecStart=/bin/bash -c if [ ${NM_ONLINE_TIMEOUT} -gt 0 ];
then /usr/bin/nm-online -q --timeout=${NM_ONLINE_TIMEOUT} ;
else /bin/true ; fi (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/NetworkManager-wait-online.service

home-users.mount
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)

BUT, the automounter has made the mountpoint, so the network MUST have
been available:

mount | grep home
auto.users on /home/users type autofs
(rw,relatime,fd=7,pgrp=535,timeout=600,minproto=5,maxproto=5,indirect)


If I then log in, here is the request for the cifs ticket:

Kerberos: TGS-REQ ***@HH3.SITE from ipv4:192.168.1.21:53019 for
cifs/***@HH3.SITE [canonicalize, renewable]
Kerberos: TGS-REQ authtime: 2013-09-14T18:31:09 starttime: 2013
-09-14T18:31:11 endtime: 2013-09-15T04:31:09 renew till:
2013-09-15T18:31:07

and it's mounted:
mount | grep lynn
//altea/users/lynn2 on /home/users/lynn2 type cifs
(rw,relatime,vers=1.0,sec=krb5,cache=strict,unc=\\altea
\users,multiuser,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.100,unix,posixpaths,serverino,acl,noperm,rsize=1048576,wsize=65536,actimeo=1)

OK. I'll go through the same motions with fstab and then maybe we can
compare? Or is there anything here to point at the problem? Or maybe
we're not comparing like with like.

Thanks,
L x