https://bugzilla.novell.com/show_bug.cgi?id=744293
https://bugzilla.novell.com/show_bug.cgi?id=744293#c8
Harald Koenig
Do you have an DHCPv6 server in your network or only DHCPv4?
no, only v4
When you don't have DHCPv6 server, change to use BOOTPROTO=dhcp4 in /etc/sysconfig/network/ifcfg-eth0 -- this will speed up the network start / cause to not wait for DHCPv6.
ok, I'll change that. but (a) it should work anyway and (b) that small speedup should be no significant help if you check the timestamps in my syslog output...
It looks like systemd would start vdr after network, but would not wait until it finished...?
maybe it only waits for the "lo" device setup being finished ?! that's at least the sequence which syslog shows. maybe lo-setup is just "too fast" doesn't let vdr pass ?!?
The error message is:
Jan 31 17:45:45 t3 vdr: [1141] ERROR: /var/spool/video: No such file or directory
this means that the mount-point is not there, so nfs script can't even mount the nfs export.
vdr shall not start before NFS is available. period. once NFS is up, that directory exists (as a later successfull "rcvdr start" proofs)
Please fix it using:
mkdir /var/spool/video
NAK: /var/spool/video is a symlink pointing into the NFS share: lrwxrwxrwx 1 koenig root 26 Jan 19 08:39 /var/spool/video -> /data.hps/video.m2.3/video # df /data.hps/video.m2.3/video Filesystem 1K-blocks Used Available Use% Mounted on hps1:/t2 5768579072 1460928512 4014623744 27% /data.hps (In reply to comment #5)
Harald, are you using autofs to mount it or nfs script? Can you provide the fstab entry / autofs config please?
nothing magic, just plain fstab. voila (using nfs3 aka nfs makes no difference, just in case... ;-) # grep data /etc/fstab hps1:/t2 /data.hps nfs4 please have another look into my syslog messages and the timetamps (selected line in original sequence): 17:45:45 t3 vdr: [1141] ERROR: /var/spool/video: No such file or directory 17:45:45 t3 ifup: eth0 device: Intel Corporation 82573E Gigabit Ethernet Con 17:45:46 t3 kernel: [ 17.380683] ADDRCONF(NETDEV_UP): eth0: link is not ready 17:45:50 t3 kernel: [ 20.586734] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready vdr starts even before "ifup eth0", and way before "link becomes ready", no way this can be fixed by e.g. not waiting for dhcpv6;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.