07.09.2015 11:10, Daniel Spannbauer wrote:
Sep 04 14:56:04 fry systemd[1]: Trying to enqueue job
multi-user.target/start/replace
Sep 04 14:56:04 fry systemd[1]: ESC[1;39mFound ordering cycle on
remote-fs-pre.target/startESC[0m
Sep 04 14:56:04 fry systemd[1]: Walked on cycle path to
nss-lookup.target/start
Sep 04 14:56:04 fry systemd[1]: Walked on cycle path to named.service/start
Sep 04 14:56:04 fry systemd[1]: Walked on cycle path to ldap.service/start
Sep 04 14:56:04 fry systemd[1]: Walked on cycle path to
remote-fs.target/start
Sep 04 14:56:04 fry systemd[1]: Walked on cycle path to
owncloud_all.mount/start
Sep 04 14:56:04 fry systemd[1]: Walked on cycle path to
remote-fs-pre.target/start
Sep 04 14:56:04 fry systemd[1]: ESC[1;31mBreaking ordering cycle by
deleting job nss-lookup.target/startESC[0m
Sep 04 14:56:04 fry systemd[1]: Deleting job postfix.service/start as
dependency of job nss-lookup.target/start
Which service generates the trouble and what should I do to get rid of this?
None of the services in particular generates the trouble. The trouble is
from the fact that they all say, collectively, that they need each
other. To troubleshoot this, you would need to answer these questions:
Do you mount any remote filesystem using the server name, as opposed to
its IP address?
Do you really need a local instance of named?
Does the local named actually get any of its zones from LDAP?
Does your LDAP server use any databases stored on a remote filesystem?
Do you actually use the owncloud mount?
--
Alexander E. Patrakov
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
