[opensuse] systemd fails to start famd
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Look: Telcontar:~ # date;systemctl status fam.service Sun Jun 16 14:41:51 CEST 2013 fam.service - LSB: file access monitoring Loaded: loaded (/etc/init.d/fam) Active: failed (Result: exit-code) since Sun, 2013-06-16 14:41:44 CEST; 7s ago Process: 8738 ExecStart=/etc/init.d/fam start (code=exited, status=7) CGroup: name=systemd:/system/fam.service Jun 16 14:41:44 Telcontar.valinor systemd[1]: Starting LSB: file access monitoring... Jun 16 14:41:44 Telcontar.valinor fam[8738]: Starting File Access Monitoring Daemon..failed Jun 16 14:41:44 Telcontar.valinor systemd[1]: Failed to start LSB: file access monitoring. Jun 16 14:41:44 Telcontar.valinor systemd[1]: Unit fam.service entered failed state Telcontar:~ # journalctl -n Jun 16 14:43:23 Telcontar.valinor famd[8826]: can't register with portmapper. Please start a portmapper (for example rpcbind), then try again to start famd. Jun 16 14:43:23 Telcontar.valinor fam[8818]: Starting File Access Monitoring Daemon..failed Jun 16 14:43:23 Telcontar.valinor systemd[1]: fam.service: control process exited, code=exited status=7 Jun 16 14:43:23 Telcontar.valinor systemd[1]: Failed to start LSB: file access monitoring. Jun 16 14:43:23 Telcontar.valinor systemd[1]: Unit fam.service entered failed state lines 1-11/11 (END) Why does it want portmapper? Is it not needed for NFS? Ie, network filesystems? Surely, NFS is also failing. Telcontar:~ # date;systemctl status nfsserver.service Sun Jun 16 14:44:55 CEST 2013 nfsserver.service - LSB: Start the kernel based NFS daemon Loaded: loaded (/etc/init.d/nfsserver) Active: failed (Result: exit-code) since Sun, 2013-06-16 13:57:46 CEST; 47min ago CGroup: name=systemd:/system/nfsserver.service └ 3152 /usr/sbin/rpc.idmapd Jun 16 13:57:46 Telcontar.valinor systemd[1]: Starting LSB: Start the kernel based NFS daemon... Jun 16 13:57:46 Telcontar.valinor startproc[4700]: startproc: exit status of parent of /usr/sbin/rpc.mountd: 1 Jun 16 13:57:46 Telcontar.valinor nfsserver[4661]: Starting kernel based NFS server: idmapd mountd..failed Jun 16 13:57:46 Telcontar.valinor systemd[1]: Failed to start LSB: Start the kernel based NFS daemon. Jun 16 13:57:46 Telcontar.valinor systemd[1]: Unit nfsserver.service entered failed state Telcontar:~ # Telcontar:~ # date;systemctl status rpcbind.service Sun Jun 16 14:46:12 CEST 2013 rpcbind.service - RPC Bind Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; disabled) Active: inactive (dead) CGroup: name=systemd:/system/rpcbind.service Telcontar:~ # Starting and or enabling them: Telcontar:~ # date;systemctl enable rpcbind.service Sun Jun 16 14:46:34 CEST 2013 ln -s '/usr/lib/systemd/system/rpcbind.service' '/etc/systemd/system/multi-user.target.wants/rpcbind.service' ln -s '/usr/lib/systemd/system/rpcbind.socket' '/etc/systemd/system/sockets.target.wants/rpcbind.socket' Telcontar:~ # date;systemctl start rpcbind.service Sun Jun 16 14:46:40 CEST 2013 Telcontar:~ # date;systemctl status rpcbind.service Sun Jun 16 14:46:43 CEST 2013 rpcbind.service - RPC Bind Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; enabled) Active: active (running) since Sun, 2013-06-16 14:46:40 CEST; 2s ago Main PID: 8968 (rpcbind) CGroup: name=systemd:/system/rpcbind.service └ 8968 /sbin/rpcbind -w -f Jun 16 14:46:40 Telcontar.valinor systemd[1]: Started RPC Bind. Telcontar:~ # Telcontar:~ # date;systemctl restart nfsserver.service Sun Jun 16 14:47:30 CEST 2013 Telcontar:~ # date;systemctl status nfsserver.service Sun Jun 16 14:47:36 CEST 2013 nfsserver.service - LSB: Start the kernel based NFS daemon Loaded: loaded (/etc/init.d/nfsserver) Active: active (running) since Sun, 2013-06-16 14:47:30 CEST; 5s ago Process: 8995 ExecStart=/etc/init.d/nfsserver start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/nfsserver.service ├ 3152 /usr/sbin/rpc.idmapd ├ 9016 /usr/sbin/rpc.mountd └ 9019 /usr/sbin/rpc.statd --no-notify Jun 16 14:47:30 Telcontar.valinor systemd[1]: Starting LSB: Start the kernel based NFS daemon... Jun 16 14:47:30 Telcontar.valinor rpc.mountd[9016]: Version 1.2.7 starting Jun 16 14:47:30 Telcontar.valinor rpc.statd[9019]: Version 1.2.7 starting Jun 16 14:47:30 Telcontar.valinor rpc.statd[9019]: Flags: TI-RPC Jun 16 14:47:30 Telcontar.valinor nfsserver[8995]: Starting kernel based NFS server: idmapd mountd statd nfsd sm-notify..done Jun 16 14:47:30 Telcontar.valinor systemd[1]: Started LSB: Start the kernel based NFS daemon. Telcontar:~ # Telcontar:~ # date;systemctl status fam.service Sun Jun 16 14:48:05 CEST 2013 fam.service - LSB: file access monitoring Loaded: loaded (/etc/init.d/fam) Active: failed (Result: exit-code) since Sun, 2013-06-16 14:43:23 CEST; 4min 41s ago CGroup: name=systemd:/system/fam.service Jun 16 14:43:23 Telcontar.valinor systemd[1]: Starting LSB: file access monitoring... Jun 16 14:43:23 Telcontar.valinor fam[8818]: Starting File Access Monitoring Daemon..failed Jun 16 14:43:23 Telcontar.valinor systemd[1]: Failed to start LSB: file access monitoring. Jun 16 14:43:23 Telcontar.valinor systemd[1]: Unit fam.service entered failed state Telcontar:~ # date;systemctl restart fam.service Sun Jun 16 14:48:11 CEST 2013 Telcontar:~ # date;systemctl status fam.service Sun Jun 16 14:48:13 CEST 2013 fam.service - LSB: file access monitoring Loaded: loaded (/etc/init.d/fam) Active: active (running) since Sun, 2013-06-16 14:48:11 CEST; 2s ago Process: 9059 ExecStart=/etc/init.d/fam start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/fam.service └ 9067 /usr/sbin/famd -t 4 -T 0 Jun 16 14:48:11 Telcontar.valinor systemd[1]: Starting LSB: file access monitoring... Jun 16 14:48:11 Telcontar.valinor fam[9059]: Starting File Access Monitoring Daemon..done Jun 16 14:48:11 Telcontar.valinor systemd[1]: Started LSB: file access monitoring. Telcontar:~ # - -- Cheers Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlG9tX0ACgkQtTMYHG2NR9XPZQCfQaiWRG3b1B0rRSYhAWYtwR/x ASAAn0pC2GzVY6TpRsLyiWM59pc1igYO =xSsO -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 В Sun, 16 Jun 2013 14:54:21 +0200 (CEST) "Carlos E. R." <robin.listas@telefonica.net> пишет:
Jun 16 14:43:23 Telcontar.valinor famd[8826]: can't register with portmapper. Please start a portmapper (for example rpcbind), then try again to start famd.
please show systemctl show fam.service systemctl show rpcbind.service -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlG9vLEACgkQR6LMutpd94xDagCeP3Dy82Hqrux12zK2taFRJ0r+ unMAn2Mp4tkk0fLKD3leIQe2GBMQgpoU =zs+9 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 В Sun, 16 Jun 2013 17:25:04 +0400 Andrey Borzenkov <arvidjaar@gmail.com> пишет:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
В Sun, 16 Jun 2013 14:54:21 +0200 (CEST) "Carlos E. R." <robin.listas@telefonica.net> пишет:
Jun 16 14:43:23 Telcontar.valinor famd[8826]: can't register with portmapper. Please start a portmapper (for example rpcbind), then try again to start famd.
please show
systemctl show fam.service systemctl show rpcbind.service
Forget it. systemd translates initscript dependencies to ordering dependencies (After/Before) which means, if rpcbind is enabled, fam will be started after it, but it will not be required (i.e. it will not be started when you start fam). So there is nothing wrong here. You need to enable rpcbind, that's all. If it fails to start even when rpcbind is enabled, that deserves attention.
systemd fails to start famd
Why to you start every e-mail with "systemd fails ..."? It has absolutely nothing to do with systemd. You would have exactly the same problem in case of "chkconfig rpcbind off" with sysvinit. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlG9vlUACgkQR6LMutpd94zzZACeLpiC218GQLgNF3fnUzOe+H+r YOoAniz9WibWY/OIjiWDBSstH1k/kUxC =cg2W -----END PGP SIGNATURE----- N▀╖╡ФЛr╦⌡yИ ┼Z)z{.╠О╝·к⌡╠йБmЙ)z{.╠Й+│: ╒{Zrшaz▄'z╥╕j)h╔ИЛ╨г╬ё ч╝┼^·к╛z┼Ю
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-06-16 at 17:32 +0400, Andrey Borzenkov wrote:
So there is nothing wrong here. You need to enable rpcbind, that's all. If it fails to start even when rpcbind is enabled, that deserves attention.
I did that on the previous post, I printed the command. But why does famd require rpcbind?
systemd fails to start famd
Why to you start every e-mail with "systemd fails ..."? It has absolutely nothing to do with systemd. You would have exactly the same problem in case of "chkconfig rpcbind off" with sysvinit.
Nope. :-) This system was upgraded from 12.1 to 12.3, and in 12.1 it was working with systemv correctly. Upgrade, puf, all service status are not migrated to systemd, and I had to review many of them. What I see is messages from systemd that this or that message is faling. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlG9wGEACgkQtTMYHG2NR9X2WACfRGEr7Zc7kFqM6QI3tM69lcFw mz8Anj6t1d/mV2Q0L5mnLNQST1phnkb6 =vHi2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R. <robin.listas@telefonica.net> [06-16-13 09:42]: [...]
This system was upgraded from 12.1 to 12.3, and in 12.1 it was working with systemv correctly. Upgrade, puf, all service status are not migrated to systemd, and I had to review many of them.
What I see is messages from systemd that this or that message is faling.
Understand that in many cases you are blaming the messenger, systemd, rather than the cause of the failing process. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-06-16 at 09:45 -0400, Patrick Shanahan wrote:
* Carlos E. R. <> [06-16-13 09:42]: [...]
This system was upgraded from 12.1 to 12.3, and in 12.1 it was working with systemv correctly. Upgrade, puf, all service status are not migrated to systemd, and I had to review many of them.
What I see is messages from systemd that this or that message is faling.
Understand that in many cases you are blaming the messenger, systemd, rather than the cause of the failing process.
Yes, possibly, till I know the real cause at least. With systemv they did not fail, which is also true. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlG9wysACgkQtTMYHG2NR9Wx5QCcCRlYMI/AxS6ijNElwnOt++1F NH8AnA+t9lYlNbguHxBwQJ67ry6AfWVW =e77E -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 16 Jun 2013 15:40:49 Carlos E. R. wrote:
[...] This system was upgraded from 12.1 to 12.3, and in 12.1 it was working with systemv correctly. Upgrade, puf, all service status are not migrated to systemd, and I had to review many of them.
This may be part of the problem. I did a clean install of 12.3 after formatting all partitions except /home and a couple of other data (i.e. Non- system) partitions and it has all worked virtually flawlessly. There was a minor niggle with ACPI being disabled but that was easily fixed once I figured out how to massage grub2, and a couple of minor niggles with NFS (which experimented briefly but don't use because samba is much easier for my use- case). Part of the reason for doing a clean install is that I also migrated from 32 to 64 bit and didn't want any 32-bit crud left hanging around that might cause problems later (call me conservative if you want). In any case, a clean install of 12.3 may be in order. Regards, Rodney. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2013-06-17 at 02:43 +0930, Rodney Baker wrote: ...
In any case, a clean install of 12.3 may be in order.
Never on my life! That is admitting defeat. :-| - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEUEARECAAYFAlG+ATYACgkQtTMYHG2NR9V8pgCY/+uUG786h5WWrGjlpyvHkhD4 PwCfX7CHyudeaL2eJJXyytiys/yqWQk= =+yqR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Andrey Borzenkov -
Carlos E. R. -
Patrick Shanahan -
Rodney Baker