I think I created a problem with NetworkManager.service

Hello,

I have Searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata

OpenMandriva Lx version:
Lx release 6.0 (Vanadium) Rock for x86_64

Desktop environment (KDE, LXQT…):
KDE

Description of the issue (screenshots if relevant):
I was attempting to enable automatic mounting of a cifs file share (QNAP NAS) using /etc/fstab. For reasons not relevant to this question, I was not able to successfully mount the share during the boot process (I can mount it manually after booting). I was experimenting with various settings in /etc/fstab related to waiting for the network to be online before attempting to mount the share. I did a bit more reading and found a solution that may not have been ideal for this system-

My specific issue right now is this: I think I created a problem by following instructions possibly intended for a different distro - In trying to force the cifs mount, I entered the following commands:

systemctl start NetworkManager.service
systemctl enable NetworkManager.service
systemctl start NetworkManager-wait-online.service
systemctl enable NetworkManager-wait-online.service

I noticed that after the second line it created a number of symlinks, but since that didn’t fix the issue I had with mounting my NAS, I figured that approach wasn’t helping, so I then entered the following:

systemctl disable NetworkManager-wait-online.service
systemctl stop NetworkManager-wait-online.service
systemctl disable NetworkManager.service
systemctl stop NetworkManager.service

It was at that moment I knew…
Actually, I think after the 3rd line my wifi disconnected and I realised I would have to fix something.
So now every time I reboot, I have no network until I run the command
“sudo systemctl start NetworkManager.service”
But I have to do that again each reboot.
If I enter the additional command
“sudo systemctl enable NetworkManager.service”
again it creates a number of symlinks. So the fact that it had to create these symlinks makes me think they didn’t already exist. So I think that this NetworkManager.service is not the way that my OMA install was previously handling the network. How do I just go back to the original way - is that using “systemd.networkd”, and if so, how?

Relevant informations (hardware involved, software version, logs or output…):
(Right now I just want to return to the default settings for network access for this install, I will leave mounting of my NAS in /etc/fsctab for a separate post one this issue is resolved)

edit: if at all relevant, the symlinks created were as follows:

Created symlink '/etc/systemd/system/network-manager.service' → '/usr/lib/systemd/system/NetworkManager.service'.
Created symlink '/etc/systemd/system/multi-user.target.wants/NetworkManager.service' → '/usr/lib/systemd/system/NetworkManager.service'.
Created symlink '/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service' → '/usr/lib/systemd/system/NetworkManager-dispatcher.service'.
Created symlink '/etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service' → '/usr/lib/systemd/system/NetworkManager-wait-online.service'.

Thanks for your help!

@Froozle
welcome1

1 Like

Hi @Froozle and welcome,
That would be normal behaviour, disabling networkmanager removed the symlinks so it wont start on boot, enabling it again recreats the same symlinks so that it will. You are ok to just

sudo systemctl enable NetworkManager.service

If you need help with mounting your NAS feel free to create a new topic I am sure someone here will be able to point you in the right direction.

1 Like

I do believe the script creates symlinks using -sf so that doesn’t really factor in. My system never had this service modified and enables and starts it by default. Automounting of network file systems have to occur after the network connection is established. In the case of SMB, it will be after the client is started successfully, as well.

We will need to see the entry.

1 Like

Thanks @richp, I can confirm my system is booting with network again with the NetworkManager service enabled, everything seems ok. I just wasn’t sure if I had inadvertently used a method different to the default, and/or if I was creating a duplicate or redundant service in the process.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.