Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] nm-dispatcher spam (Read 509 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[SOLVED] nm-dispatcher spam

I have a fresh install of the artix-base-openrc on a x220. No gui, the only packages I installed are sudo and lynx. Upon start-up this is what the login screen looks like:
Code: [Select]
Artix Linux 4.19.2-artix1-1-ARTIX (tty1)

hostname login: nm-dispatcher: req3 'up' [enp0xxx] : new request (1 scripts)
nm-dispatcher  req:3 'up' [enp0xxx]: start running ordered scripts
nm-dispatcher req:4 'connectivity-change' : new request (1 scripts)
nm-dispatcher req:4 'connectivity-change' : start running ordered scripts
The closest thing i could find to my problem is here:
https://forums.gentoo.org/viewtopic-t-1055866-start-0.html
The problem is a logger was not running for that person.  Here is what I did but it did not work:
Code: [Select]
$pacman -S syslog-ng
$cp /bin/syslog-ng /etc/init.d
$cd /etc/runlevel/boot
$ln -s /bin/syslog-ng
As far as i can tell the internet is working fine, i can ping with zero package loss.

Re: nm-dispatcher spam

Reply #1
You said you're on openrc, what you did is (roughly...) for runit; remove syslog-ng from /etc/init.d and /etc/runlevel/boot, install syslog-ng-openrc and activate  it:
Code: [Select]
% sudo pacman -S syslog-ng-openrc
% sudo rc-service syslog-ng start
% sudo rc-update add syslog-ng

 

Re: nm-dispatcher spam

Reply #2
Did a few reboots, the messages are gone. Thank you for your help.

Re: [SOLVED] nm-dispatcher spam

Reply #3
Hello everybody,
I have the same problem, but your solution does not really fix it.
After all, it does not bother more in the loginscreen, this is now delayed but two minutes until it appears.
If I add xdm to the default runlevel, nothing happens after the error message:
nm-dispatcher: req:5 'dhcp6-change' [enp0s25]: start runnig ordered skripts... .

Re: [SOLVED] nm-dispatcher spam

Reply #4
Please, post some more info. What's your init, activated/running services etc. Use code tags for readability.

Re: [SOLVED] nm-dispatcher spam

Reply #5
Please, post some more info. What's your init, activated/running services etc. Use code tags for readability.
Thank you for your response.
I'm running GNU/Linux with OpenRC as initsystem.
My main problem is that booting to the XFCE desktop is not possible. The boot process hangs on the place with nm-dispatcher and does nothing more
Code: [Select]
 <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supportet by any plugin
nm-dispatcher: req:3 'up' [enp0s25]: new request (1 scripts)
nm-dispatcher: req:3 'up' [enp0s25]: start running ordered skripts...
nm-dispatcher: req:4 'connectivity-change' : new request (1 skripts)
nm-dispatcher: req:4 'connectivity-change' : start running ordered sktipts...
nm-dispatcher: req:5 'dhcp6-change' [enp0s25]: new request (1 skripts)
nm-dispatcher: req:5 'dhcp6-change' [enp0s25]: start running ordered sktipts...
(if I add xdm as default runlevel). If I don't add xdm it is possible to log into the terminal (after two minutes waiting the message will leave). then i logged in with user+pw and put xfce4start and it works, but this is not usable. :D
Here is my dmesg output:
https://bin.disroot.org/?41ea8a9acfcdeb8e#2tfDJcXN7LWd1rSqvOdFBanCEVn63Yeo7nV3mCKgHVg=

Here is my rc-status --all:
https://bin.disroot.org/?ee41d8c20950f98a#7LPjG/04vai30YLjMdN1ZvU5cqZhLZmZTO7m+rGw/48=


Re: [SOLVED] nm-dispatcher spam

Reply #7
What's your display manager? xdm itself doesn't do much.
I've installed lightdm (best with XFCE4) and changed in /etc/conf.d/xdm xdm to lightdm.

After
Quote
sudo rc-service xdm start
same as when xdm on default runlevel, black screen an flashing cursor, nothing more.
I suspect it's two independent errors. On the one hand that the NetworkManager delays the system start so much (2min), on the other hand that lightdm does not start.
Desktop screenshot:
https://framapic.org/gallery#jJA5kiHNNncc/vZuml7CdyLvY.jpg
After the last output, it takes two minutes for the login terminal to appear (without x-server only console).

/var/log/Xorg.0.log output:
https://bin.disroot.org/?4d5f1eb5b27577ad#w4gmBnVKBiVJr6ZlAoNQhq3/WZRi+0PxGoGo+BZzhpo=

Re: [SOLVED] nm-dispatcher spam

Reply #8
I see nothing special in the logs (except for the parabola kernel). Do other display managers exhibit the same failure? Try lxdm just to narrow things down. If it works, we'll blame lightdm; if it doesn't, we'll blame parabola's kernel.

Re: [SOLVED] nm-dispatcher spam

Reply #9
I had an identical system already running. The nm-dispatcher problems did not occur until I moved my system from an HDD to an SSD (https://wiki.archlinux.de/title/Installation_umziehen#selektives_Kopieren_der_einzelnen_Partitionen). Since then, the error always appears nm-dispatcher and delays the system start immensely. Then I decided to rebuild the system again, but without success. The error remains, in addition the error comes that xfce does not start automatically.

With lxdm
Quote
sudo rc-service xdm start
works fine. O.o  :o  :o  :o Why the hell? :D

Re: [SOLVED] nm-dispatcher spam

Reply #10
My main problem (the topic) with nm-dispatcher still exists.
At the beginning the commands disturbed the login field, this could be solved by the solution of this topic.
However, the message now appears before the login field and delays the appearance by about two minutes, it could relate to the last three lines of my dmesg:
Quote
[    7.551828] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s25: link becomes ready
[  154.276342] random: crng init done
146 seconds could be the delay of about two minutes


Re: [SOLVED] nm-dispatcher spam

Reply #12
Unfortunately the same...  :'(
Since openrc starts NetworkManager the screen looks very chaotic.

Re: [SOLVED] nm-dispatcher spam

Reply #13
Could it be that the router blocks or is not capable of ipv6, hence the delay?  If this is the case disabling ipv6 may help.

Re: [SOLVED] nm-dispatcher spam

Reply #14
Could it be that the router blocks or is not capable of ipv6, hence the delay?  If this is the case disabling ipv6 may help.

Nope, on my previous system i've disabled IPv6 so the line where it delay was like the  topic creator req:4. In addition, I will be shown a public IPv6 address.

Switched to new topic: https://forum.artixlinux.org/index.php/topic,805.new.html#new