Mailinglist Archive: opensuse-bugs (4215 mails)

< Previous Next >
[Bug 744293] New: systemd: vdr starts before nfs-client-mount ?!
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 31 Jan 2012 13:21:35 +0000
  • Message-id: <bug-744293-21960@http.bugzilla.novell.com/>

https://bugzilla.novell.com/show_bug.cgi?id=744293

https://bugzilla.novell.com/show_bug.cgi?id=744293#c0


Summary: systemd: vdr starts before nfs-client-mount ?!
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: koenig@xxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Blocker: ---


I've setup a new PC with 12.1 running VDR, the video storage is on a NFS4
server.

after reboot vdr did not start, because NFS (and local network on eth0) is not
yet ready.
from /var/log/messages (no lines missing between):

Jan 31 08:35:19 t2 lirc[745]: Starting lircd (/dev/lirc0)..done
Jan 31 08:35:19 t2 network[887]: lo
Jan 31 08:35:19 t2 ifup: lo
Jan 31 08:35:19 t2 ifup: lo
Jan 31 08:35:19 t2 ifup: IP address: 127.0.0.1/8
Jan 31 08:35:19 t2 network[887]: lo IP address: 127.0.0.1/8
Jan 31 08:35:19 t2 ifup:
Jan 31 08:35:20 t2 vdr: [1136] cTimeMs: using monotonic clock (resolution is 1
ns)
Jan 31 08:35:20 t2 vdr: [1174] cTimeMs: using monotonic clock (resolution is 1
ns)
Jan 31 08:35:20 t2 vdr: [1174] ERROR: /var/spool/video: No such file or
directory
Jan 31 08:35:20 t2 network[887]: ..done eth0 device: Intel Corporation
82573E Gigabit Ethernet Con
Jan 31 08:35:20 t2 ifup: eth0 device: Intel Corporation 82573E Gigabit
Ethernet Con
Jan 31 08:35:20 t2 vdr[1083]: Starting Video Disk Recorder ..missing
Jan 31 08:35:20 t2 systemd[1]: vdr.service: control process exited, code=exited
status=3
Jan 31 08:35:20 t2 systemd[1]: Unit vdr.service entered failed state.
Jan 31 08:35:21 t2 kernel: [ 17.683974] e1000e 0000:01:00.0: irq 45 for
MSI/MSI-X
Jan 31 08:35:21 t2 kernel: [ 17.735108] e1000e 0000:01:00.0: irq 45 for
MSI/MSI-X
Jan 31 08:35:21 t2 kernel: [ 17.736697] ADDRCONF(NETDEV_UP): eth0: link is
not ready
Jan 31 08:35:21 t2 ifup-dhcp: eth0 Starting DHCP4+DHCP6 client
Jan 31 08:35:21 t2 dhcpcd[1310]: eth0: dhcpcd 3.2.3 starting
Jan 31 08:35:21 t2 dhcpcd[1310]: eth0: hardware address = 00:13:20:e0:6c:1c
Jan 31 08:35:21 t2 kernel: [ 17.792870] NET: Registered protocol family 17
Jan 31 08:35:21 t2 dhcpcd[1310]: eth0: broadcasting for a lease
Jan 31 08:35:21 t2 ifup-dhcp: .
Jan 31 08:35:22 t2 dhclient[1328]: send_packet6: Network is unreachable
Jan 31 08:35:22 t2 dhclient[1328]: dhc6: send_packet6() sent -1 of 58 bytes
Jan 31 08:35:23 t2 dhclient[1328]: send_packet6: Network is unreachable
Jan 31 08:35:23 t2 dhclient[1328]: dhc6: send_packet6() sent -1 of 58 bytes
Jan 31 08:35:24 t2 ifup-dhcp: .
Jan 31 08:35:24 t2 kernel: [ 21.170991] e1000e: eth0 NIC Link is Up 1000 Mbps
Full Duplex, Flow Control: Rx/Tx
Jan 31 08:35:24 t2 kernel: [ 21.171709] ADDRCONF(NETDEV_CHANGE): eth0: link
becomes ready
Jan 31 08:35:25 t2 dhclient[1328]: send_packet6: Cannot assign requested
address
Jan 31 08:35:25 t2 dhclient[1328]: dhc6: send_packet6() sent -1 of 58 bytes
Jan 31 08:35:26 t2 avahi-daemon[819]: Registering new address record for
fe80::213:20ff:fee0:6c1c on eth0.*.
Jan 31 08:35:26 t2 ifup-dhcp: .
Jan 31 08:35:29 t2 ifup-dhcp: .
Jan 31 08:35:31 t2 dhcpcd[1310]: eth0: offered 192.168.178.47 from
192.168.178.1
Jan 31 08:35:31 t2 ifup-dhcp: .
Jan 31 08:35:34 t2 ifup-dhcp: .
Jan 31 08:35:35 t2 kernel: [ 32.162016] eth0: no IPv6 routers present
Jan 31 08:35:36 t2 dhcpcd[1310]: eth0: checking 192.168.178.47 is available on
attached networks
Jan 31 08:35:36 t2 ifup-dhcp: .
Jan 31 08:35:37 t2 dhcpcd[1310]: eth0: leased 192.168.178.47 for 864000 seconds
Jan 31 08:35:37 t2 dhcpcd[1310]: eth0: adding IP address 192.168.178.47/24
Jan 31 08:35:37 t2 avahi-daemon[819]: Joining mDNS multicast group on interface
eth0.IPv4 with address 192.168.178.47.
Jan 31 08:35:37 t2 dhcpcd[1310]: eth0: adding default route via 192.168.178.1
metric 0
Jan 31 08:35:37 t2 avahi-daemon[819]: New relevant interface eth0.IPv4 for
mDNS.
Jan 31 08:35:37 t2 avahi-daemon[819]: Registering new address record for
192.168.178.47 on eth0.IPv4.
Jan 31 08:35:38 t2 ifdown: eth0 device: Intel Corporation 82573E
Gigabit Ethernet Controller (Copper) (rev 03)
Jan 31 08:35:38 t2 dhcpcd[1310]: eth0: setting hostname to `t2'
Jan 31 08:35:38 t2 rsyslogd: [origin software="rsyslogd" swVersion="5.8.5"
x-pid="803" x-info="http://www.rsyslog.com";] rsyslogd was HUPed
Jan 31 08:35:38 t2 ifup: eth0 device: Intel Corporation 82573E Gigabit
Ethernet Controller (Copper) (rev 03)
Jan 31 08:35:39 t2 ifup-dhcp: .
Jan 31 08:35:40 t2 network[887]: eth0 Starting DHCP4+DHCP6 client. . . . .
. .
Jan 31 08:35:40 t2 ifup-dhcp:
Jan 31 08:35:40 t2 network[887]: eth0 DHCP4 continues in background
Jan 31 08:35:40 t2 ifup-dhcp: eth0 DHCP4 continues in background
Jan 31 08:35:40 t2 network[887]: eth0 DHCP6 continues in background
Jan 31 08:35:40 t2 ifup-dhcp: eth0 DHCP6 continues in background
Jan 31 08:35:40 t2 network[887]: [1Awaiting
Jan 31 08:35:41 t2 network[887]: Waiting for mandatory devices: eth0
Jan 31 08:35:50 t2 network[887]: 8 7 5 4 3 1 0
Jan 31 08:35:50 t2 network[887]: eth0 device: Intel Corporation 82573E
Gigabit Ethernet Con
Jan 31 08:35:50 t2 network[887]: eth0 . . . is just beeing set up
Jan 31 08:35:50 t2 network[887]: eth0 IP address: 192.168.178.47/24
Jan 31 08:35:50 t2 network[887]: eth0 is up
Jan 31 08:35:50 t2 network[887]: [1Awaiting
Jan 31 08:35:50 t2 network[887]: eth0 interface could not be set up until
now
Jan 31 08:35:50 t2 network[887]: ..failedSetting up service (localfs) network
. . . . . . . . ...failed
Jan 31 08:35:50 t2 systemd[1]: network.service: control process exited,
code=exited status=7
Jan 31 08:35:50 t2 systemd[1]: Unit network.service entered failed state.


when I finally logged in, the network was up, NFS was mounted and "rcvdr start"
worked fine.

why does vdr get started before local net/nfs_client (aka remote-fs.target?!) ?

# systemctl show vdr.service | grep After
After=lirc.service dvb.service earlysyslog.service remote-fs.target
systemd-stdout-syslog-bridge.socket basic.target
^^^^^^^^^^^^^^^^
but:


# systemctl | grep fail
network.service loaded failed failed LSB: Configure the
localfs depending network interfaces
NetworkManager.service loaded failed failed Network Manager
systemd-...s-load.service loaded failed failed Load Kernel Modules


how can I get/provide more information ?

--
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.

< Previous Next >