PDA

View Full Version : boot message: Couldn't write '"1 1 1 1"' to 'kernel/printk': Invalid argument



garymeer
30th November 2017, 02:03 PM
I am getting an error message while starting Fedora 27.

systemctl status network.service
● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network; generated; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2017-11-30 07:42:49 EST; 2min 55s ago
Docs: man:systemd-sysv-generator(8)
Process: 1482 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

Nov 30 07:42:48 system1 systemd-sysctl[1516]: Couldn't write '"1 1 1 1"' to 'kernel/printk': Invalid argument
Nov 30 07:42:49 system1 systemd-sysctl[1721]: Couldn't write '"1 1 1 1"' to 'kernel/printk': Invalid argument
Nov 30 07:42:49 system1 systemd[1]: Failed to start LSB: Bring up/down networking.
Nov 30 07:42:49 system1 systemd[1]: network.service: Failed with result 'exit-code'.

ifconfig -a reports:
ifconfig -a
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet 192.168.1.101 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::d250:99ff:fea7:c078 prefixlen 64 scopeid 0x20<link>
inet6 2602:306:3815:7990:d250:99ff:fea7:c078 prefixlen 64 scopeid 0x0<global>
ether d0:50:99:a7:c0:78 txqueuelen 1000 (Ethernet)
RX packets 24968 bytes 20393212 (19.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 14670 bytes 2777955 (2.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether d0:50:99:a7:c0:78 txqueuelen 1000 (Ethernet)
RX packets 3777 bytes 1094374 (1.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 546 bytes 394085 (384.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xefc00000-efc20000

eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether d0:50:99:a7:c0:78 txqueuelen 1000 (Ethernet)
RX packets 21203 bytes 19299582 (18.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 14124 bytes 2383870 (2.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 21879 bytes 1267883 (1.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 21879 bytes 1267883 (1.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Everything seems to be working properly. Can I safely discard this message? Is there something I can do to prevent it?

nsnbm
30th November 2017, 10:01 PM
Oddly, I have also had "Active: failed" on a system that uses network.service (not NetworkManager), and yet networking seemed to function. I found errors in my config files: /etc/sysconfig/network-scripts/... and also in /etc/xinetd.d/... which I was also running, and fixing either one or the other (can't remember which) fixed that "systemctl status network" command ouput to "Active: active (running)". As for the "1 1 1 1", they refer to logging levels, and may also relate to config variables in the config files. Some basic info on that is: https://unix.stackexchange.com/questions/13019/description-of-kernel-printk-values