[opensuse] openSUSE 13.2 x86_64 apparent nis trouble
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Finally pushed one of my desktop machines to 13.2 and things didn't go quite as I had hoped for :( The behavior I am observing is consistent with behavior I have seen in the past when there was trouble with NIS, i.e. everything login, starting of a terminal session, the appearance of the login screen takes forever. Could use some help trying to sort this out. systemd provides the following information: # systemctl restart systemd-logind.service Job for systemd-logind.service failed. See "systemctl status systemd-logind.service" and "journalctl -xn" for details. # journalctl -xn - -- Logs begin at Sat 2015-03-07 19:07:33 EST, end at Sun 2015-03-08 06:53:21 EDT. -- Mar 08 06:52:30 lion systemd-logind[7781]: Failed to fully start up daemon: Connection timed out Mar 08 06:52:30 lion dbus[876]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Mar 08 06:52:30 lion systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory. Mar 08 06:52:56 lion dbus[876]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Mar 08 06:52:56 lion systemd-logind[7787]: Failed to fully start up daemon: Connection timed out Mar 08 06:52:56 lion systemd[1]: Failed to start Login Service. - -- Subject: Unit systemd-logind.service has failed - -- Defined-By: systemd - -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel - -- - -- Unit systemd-logind.service has failed. - -- - -- The result is failed. Mar 08 06:53:21 lion systemd-logind[7789]: Failed to enable subscription: Connection timed out Mar 08 06:53:21 lion systemd-logind[7789]: Failed to fully start up daemon: Connection timed out Mar 08 06:53:21 lion dbus[876]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Mar 08 06:53:21 lion systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory. ypwhich returns the name of the nis server thus I think it is not an nis issue, but the behavior certainly is the same. - From the output, obviously cups has issues, but I do not understand why that would delays w.r.t. login or starting applications. Help is much appreciated. Thanks, Robert - -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJU/C0WAAoJEE4FgL32d2UkUtoH/2EaDkQuRRJtNCYdbkzzMmdh dWnfxE40bgczPeCE2spaEUWv+UBx+K0mNxkH2UjeQf7DytYIvtCzmk9+VGD1bMsv sZPJXGHZ6KT8OxBz6+3I8o7SQ3pYmZ6g30Zhe2osy88SxBSywfVh7tDA1KXc8apj bx9BAR36Q8wgAXOuGjdAsA/CQhWjfA2Jys4tnxEfXoc6b28Ef9cyzLwv7QpKwqxw ianU9DexLigE9kcdcOIvcDTEBUGyhUFb27SoSVbdNPGVVdUgSnky4dwjxkYa9mkg 2KmrRq7aEucgS4h8XJFN9ZyCKOX7dlx21US3LKViZF/jS/4BUD1wekJrNy64cdU= =kv2U -----END PGP SIGNATURE----- -- 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 03/08/2015 07:05 AM, Robert Schweikert wrote:
Hi,
<snip>
Mar 08 06:52:30 lion systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory.
OK, I guess I should have done the obvious first # ls /usr/lib/systemd/system/cups.socket ls: cannot access /usr/lib/systemd/system/cups.socket: No such file or directory # rpm -ql cups | grep system /etc/dbus-1/system.d/cups.conf /usr/lib/systemd/system/cups.service /usr/share/doc/packages/cups/systemd /usr/share/doc/packages/cups/systemd/cups.path /usr/share/doc/packages/cups/systemd/cups.socket So the package I would expect to supply cups.socket does not :( # rpm -qa | grep cups cups-libs-1.5.4-21.6.1.x86_64 cups-filters-foomatic-rip-1.0.58-2.4.1.x86_64 cups-libs-32bit-1.5.4-21.6.1.x86_64 cups-1.5.4-21.6.1.x86_64 cups-filters-ghostscript-1.0.58-2.4.1.x86_64 cups-client-1.5.4-21.6.1.x86_64 python-cupshelpers-1.4.5-2.5.1.noarch cups-pk-helper-0.2.5-4.1.4.x86_64 python-cups-1.9.66-2.1.3.x86_64 If I modify configure-printer@.service to depend on cups.service instead of cups.socket the start of systemd-logind.service still fails but there is different information now: journalctl -xn - -- Logs begin at Sat 2015-03-07 19:07:33 EST, end at Sun 2015-03-08 07:11:17 EDT. -- Mar 08 07:10:27 lion dbus[876]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Mar 08 07:10:35 lion unix2_chkpwd[7971]: gkr-pam: unlocked login keyring Mar 08 07:10:52 lion systemd-logind[7969]: Failed to fully start up daemon: Connection timed out Mar 08 07:10:52 lion dbus[876]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Mar 08 07:10:57 lion org.gtk.Private.UDisks2VolumeMonitor[2186]: (process:2320): GVFS-RemoteVolumeMonitorDaemon-WARNING **: monitor says it's not supported Mar 08 07:11:01 lion org.gtk.Private.UDisks2VolumeMonitor[2186]: (process:2320): GVFS-RemoteVolumeMonitorDaemon-WARNING **: monitor says it's not supported Mar 08 07:11:01 lion org.freedesktop.thumbnails.Thumbnailer1[2186]: (tumblerd:8315): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not s Mar 08 07:11:17 lion dbus[876]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Mar 08 07:11:17 lion systemd-logind[8405]: Failed to fully start up daemon: Connection timed out Mar 08 07:11:17 lion systemd[1]: Failed to start Login Service. Later, Robert - -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJU/C/zAAoJEE4FgL32d2UkyJ8H/Ruy0mQvgmDOeeAWyHg/+XxZ QKLoG/WiKhqaRBZbqIvgVpNW5GmyJWG+pDS9I0ydHzPykAZ3EAO5OAPE101WcdXp feTNXBdXV4zXJKmYHHGibOrpAYIXW79GsOG1Kj8BlFj7E74JvLf7E+JGHP63pUyI zucs5KcNrJph92ALwLBpF7Hepge10+7S5/1Psa97kO7eJbHZlP85WxnWQ1an1I6b BVylrHa+SRBvN5GNFAIJvgb5n36mo8p6r1i9ptfyUGl4m7VcoZhphHz9LB/dsQW1 RqXqwm6VWTY25+lmR0DoPbxmNSZ39/ehqv1w+rkIYZOSCkgAPYP9TJfPmgEUGp0= =aUHa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 В Sun, 08 Mar 2015 07:05:58 -0400 Robert Schweikert <rjschwei@suse.com> пишет:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Finally pushed one of my desktop machines to 13.2 and things didn't go quite as I had hoped for :(
The behavior I am observing is consistent with behavior I have seen in the past when there was trouble with NIS, i.e. everything login, starting of a terminal session, the appearance of the login screen takes forever. Could use some help trying to sort this out.
systemd provides the following information:
# systemctl restart systemd-logind.service Job for systemd-logind.service failed. See "systemctl status systemd-logind.service" and "journalctl -xn" for details.
# journalctl -xn - -- Logs begin at Sat 2015-03-07 19:07:33 EST, end at Sun 2015-03-08 06:53:21 EDT. -- Mar 08 06:52:30 lion systemd-logind[7781]: Failed to fully start up daemon: Connection timed out
Do you have autofs active by any chance? Are you using NetworkManager? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlT8cn4ACgkQR6LMutpd94wlKQCgvq7Dz3LcIZvP8EaJQJQOFE+2 1ykAniO18/TYtjvLGuNNJDeOYpQ1EHOr =rBZT -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/08/2015 12:02 PM, Andrei Borzenkov wrote:
В Sun, 08 Mar 2015 07:05:58 -0400 Robert Schweikert <rjschwei@suse.com> пишет:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Finally pushed one of my desktop machines to 13.2 and things didn't go quite as I had hoped for :(
The behavior I am observing is consistent with behavior I have seen in the past when there was trouble with NIS, i.e. everything login, starting of a terminal session, the appearance of the login screen takes forever. Could use some help trying to sort this out.
systemd provides the following information:
# systemctl restart systemd-logind.service Job for systemd-logind.service failed. See "systemctl status systemd-logind.service" and "journalctl -xn" for details.
# journalctl -xn - -- Logs begin at Sat 2015-03-07 19:07:33 EST, end at Sun 2015-03-08 06:53:21 EDT. -- Mar 08 06:52:30 lion systemd-logind[7781]: Failed to fully start up daemon: Connection timed out
Do you have autofs active by any chance?
No, it is not
Are you using NetworkManager?
No, NetworkManager is not enabled. Later, Robert - -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJU/u0sAAoJEE4FgL32d2Uk7a4H/jOvWb0ItLxK9P101+YUujko r83QNKyNnOPppo3rGzKtIhazaVf/BddeLj5fRSJtKmr9qaZCSeByItsM9yCgQ/rc 8acDTsizpDQp8iOxFyW4Dn6+8b4cEun/IHUXiY3SfNQQPqUVj/AMOg974c823nXU w37/lQXMOlQEmfbQV1Tydmx10DEH8HmmQBhTbuB69xTLlO7UVUXUXFKjrLaXsRFB PX51qq+ZFBU6x+XmJ0E+OtnOZDqbPUWULE0B0FGmZKRJHR34aONc+XM9mEl3nrfA h5uggctPymHeRvypeezeNHOlQaZu0GjPO1B/Y4FFGZnaMC3cB2a3AW/6SRKrIHM= =4Q5D -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Andrei Borzenkov -
Robert Schweikert