Cannot run OpenLDAP server and client on the same host

English Applications
1

Hi,

I’m upgrading my server from openSUSE-Leap 42.1 to 42.3 and I got issue below when I setup server itself as OpenLDAP server and client.

I configure it as OpenLDAP server for other machines authentication.

Also I configure the machine itself as OpenLDAP client, for Samba use purpose.

And the machine unable to boot with errors below.

If openSUSE-Leap itself only set as either OpenLDAP server or client it is working fine.

Anybody face this issue and how to overcome it?

Thank you in advance.

https://lh3.googleusercontent.com/U6mdwhpSa4wuZtjDWeEa51z5Yzhj4Ya5XQy7Y-OYN6FkobCMXbw_J7kuClJZHWh14gylPBNnSr-Z4tgzkbekwZvgOPCEkhB8xuLECaxd0vtk4mmxCfvpcuEvlel9HGPs7NGW8SBrI6LRfbYnAax5WcmyK8hUo_wNyKAjL-X1wJr1tFhsacyu65o3q5u7rb7Zridysdl1XjPQZjFdubXjsD0j7LuRQK7nrl6IvQ6nZqRuHryBzAnPWcWDNNEwvrKqolV5hi1l3k8MWu1rM6xc_ND9cCpBceJRt1GOxBrhP4sKJATXAuiDlvXydYP83cB7hlGjFXXbVcAhhfmstCZYZF_1I0iOEzvVnevX4R3BQgDxDsRRiL6Egs7qStkYFBDl7Lhu8uDSEMXtJoiyCY9w42E0o_OdJszUeT-ErE-3bIFpz6FvJhQDwtcPYWRYuHzq4_mmcDfI1oVrq-YxBuCuPrM9MKRO1_UpFq69xNbK6q7awAL6N5jmheS3rzyIvWN3uj-54x-5OCor3cXCnSyi1JAUijl-t7dzidadxJApw0R9cy6zmWZ3_5GASI6V6WWyX1EM66fEHLHugESI-_q5CwJo2JIrRi-pN7QEXZ4=w1632-h918-no

https://lh3.googleusercontent.com/gV_D4YsKryPUcBzbZMKXTcmzRTDxFLV-NgNcan0s3u_saZD9LME5PawCbn0jYRFuEfmA8tijBRWPlHF9fdyHX99jEJpYCOMqdXpGoMXqHV6Qrs0XWPSJjGKgc3rcQzb-B7RAKBcUvlTj6PQmSuDhzFhRl9nSlgDVf1Ry8KOUN4YkwjoaJ_PzRyuEUkVPGwlOx8E9bB6rnctmwdSBxYgLJ8p-ELvVkgcgMklVeLYpsyKt1eHszxoTaqWAAJkZjKEOTI4EJSBCb8qF-h_M4Dkv4lbvWwKu7Avb9ZVT4SHCXhplPUmeLmexk06ZPzjycHT3VDBgTyrDVpGJHnpxyMYnKdAsRKeHwPG6a4NTWDESHk28APkLZNptAl9DymsAlafXBsDvHktdkhXRPKkUBnexXvU9nBvOBaOka14mfe36utH9_uYYfk2ZB13FQya-lNhuaUL6DGY05hV-Yxfi3dIgn2jfAGPgQ0s5OthoPgNGu7R8sKFpGRmc41K-Rji1SBxjo7rYMLba7CBpZr5zaWgFpyisl9CUbs8ho_3yGWvHPyLFzlhvu2-V-QgCjsYzjdUVltlLiz5Urhb6GKBlLapV1QOvcGNnLAguinqbrSs=w1632-h918-no

2

Nothing to be seen.

3

Hi,

Sorry I have some issue with the hosting.

Can you see below?

http://download.poly.my/01.jpg

http://download.poly.my/06.jpg

Thank you.

4

According to what you posted,
It looks to me that your Internet connection is broken, and because you have Network Manager enabled, various network related Server services are broken.

So,
Probably a good start is why you’re using Network Manager and the type of Internet connection you have which might require NM.
Possibly the next step could be whether you want to perform that network connectivity on your openSUSE server, although it can save a little bit of money I personally generally separate any kind of special network connectivity from my servers, ie using an ISP recommended gateway device. At the least, deploying essential functionality on more devices makes it easier and more obvious to see what is actually broken.

But if you prefer to build an “everything” server that performs everything, it’s possible… but you’ll need to recognize that the more functions your Server performs, the more complex it becomes unless you implement things like isolation and virtualization.

TSU

5

Yes, we can see.

BTW, you can put pictures on https://paste.opensuse.org
(use the Image button right upper).

6

Sorry, but I am missing something here. I nowhere see that he said or showed that he is using Network manager.
On the contrary, in his pictures you can see that wicked is started (and fails).

Now, I am missing a lot of knowledge here (never used LDAP) and I only posted because of the missing information in the hope that the OP can deliver that 9which he did) so that he can be helped (sort of moderator action to get the helping going). But I also try to learn new things and thus am interested in the logic that you see here and I don’t.

7

It is running wickedd, I didn’t switch to NetworkManager.

8

After several tries, I found the openSUSE Leap 42.3 get broke when I configure the machine with OpenLDAP client + NFS server, with default installation.

Hopefully somebody can guide how to solve this.

Thank you.

9

Sorry,
Yes, I see the line “Network Manager is not enabled”
That’s plain and I don’t know how I read that differently.

But,
am not sure why a modem manager is started, and assume that would happen only if regular ethernet was not working properly.

Have you checked basic network connectivity and configuration like pinging other local hosts as well as the Internet?

And, perhaps most importantly, what is the result of the following command?

systemctl status wickedd

TSU

10

The problem only occur when I configure the machine OpenLDAP client + OpenLDAP server / NFS server.

Before that everything working well including network connection.

11

You have to start troubleshooting somewhere.
Starting from where you thought was your last action before you noticed problems is a try, but circumstantial and will involve additional guesswork before you hit on what your problem is.

What I suggest starts to collect real evidence,
Based on your screenshots, a number of services failed to start.
If you run “systemctl status <service>” the result will display a number of useful data points, and include a snippet of system events which are likely related to current status, which is likely “failed.”

You can run “systemctl status” against any or even all of the failed services, I just selected what I felt was likely the most basic service which has to run successfully before the others can also be successful.

This is just one of the “new” troubleshooting tools that are available to us since the change to systemd.

TSU

12

The problem is the system stuck during startup with the failed messages.

There is no way for me to run “system status wickedd”. Maybe you have any idea to run the command when it get stuck there?

13

Below the “systemctl status wickedd” before I configure OpenLDAP client + OpenLDAP server


â wickedd.service - wicked network management service daemon
   Loaded: loaded (/usr/lib/systemd/system/wickedd.service; indirect; vendor preset: disabled)
   Active: active (running) since Sun 2018-01-14 09:21:14 +08; 13min ago
 Main PID: 806 (wickedd)
    Tasks: 1 (limit: 512)
   CGroup: /system.slice/wickedd.service
           ââ806 /usr/sbin/wickedd --systemd --foreground


Jan 14 09:21:14 andor systemd[1]: Starting wicked network management service daemon...
Jan 14 09:21:14 andor systemd[1]: Started wicked network management service daemon.

And below the “systemctl status wickedd” after I configure OpenLAP client + OpenLDAP server. I restarted wickedd few times, the service status the same.


â wickedd.service - wicked network management service daemon
   Loaded: loaded (/usr/lib/systemd/system/wickedd.service; indirect; vendor preset: disabled)
   Active: active (running) since Sun 2018-01-14 09:51:07 +08; 5min ago
 Main PID: 802 (wickedd)
    Tasks: 1 (limit: 512)
   CGroup: /system.slice/wickedd.service
           ââ802 /usr/sbin/wickedd --systemd --foreground


Jan 14 09:51:07 andor systemd[1]: Starting wicked network management service daemon...
Jan 14 09:51:07 andor systemd[1]: Started wicked network management service daemon.

The machine stuck with the error when I reboot.

Thanks.

14

I have exactly the same situation, but with a different configuration:

I have two machines with exactly the same hardware configuration and LEAP 42.3.

One of them configured OpenLAP client + OpenLDAP server + NFS server + NFS client. This one woks OK.

The second one configured OpenLAP client + NFS client. This machine presents exactly the same problem discussed in this thread.

Moreover 30 minutes after appears the first Failed messages, the boot resume with an infinite loop:

[FAILED] Failed to start Login Service.
See ‘systemctl status systemd-logind.service’ for details
OK ] Stopped Login Service.
Starting Login Service.

The systemctl status systemd-logind.service output is:

systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled)
Active: active (start) since jue 2018-02-01 17:49:38 -05; 2s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
logind
multiseat
Main PID: 1668 (systemd-logind)
Tasks: 1 (limit: 512)
CGroup: /system.slice/systemd-logind.service
└─1668 /usr/lib/systemd/systemd-logind
feb 01 17:49:38:46 slave1 systemd[1]: Starting Login Service…

Thank you for your comments.

Pipelu