I see someone asked about getting the console screensaver turned off, but I have the opposite problem. I am dealing with a pair of Vyos 1.2.0-rolling systems that are installed on PCs, one of which is a laptop. I don’t want the screen to burn in, so I set system console powersave, which works fine to blank the screen. However, when the boxes reboot, there is a configuration load error and this console setting is always the cause. Is there another way to do this, or is this a bug I should report?
Hey,
can you provide more infos about the error?
Not sure I have much more information. The configuration commits and saves and works, that is, the screen blanks. But when the router is booted again the configuration fails to load and the powersave configuration is highlighted when configuration mode is entered. Saving the config without the option and then rebooting again gets the config to load successfully (there’s probably a better way to do that, I suppose). I never saw any display that gave more information about why the error happened or pointed to any process that was the cause.
Anything in /var/log/messages visible?
I can’t recreate the problem right now; we’re using the two routers we’ve set up on a field test and they are supporting a remote office. When the test is over I can run the configuration again.
I reproduced the problem again and nothing jumps out at me in the logs. I don’t see any logs indicating a failure. Any idea what I might try looking for?
Hello @tllewell55, can you provide logs?
sudo tail -n 100 /var/log/vyatta/vyatta-config-loader.log
and
sudo tail -n 100 /var/log/vyatta/vyatta-commit.log
I lengthened the listing from the commit loader due to a lot of reconfig stuff going on:
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2019.08.09 14:33:08 =~=~=~=~=~=~=~=~=~=~=~=
sudo tail -n 400 /var/log/vyatta/vyatta-commit.log
e[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[C100 /var/log/vyatta/vyatta-config-loader.log
2019-07-18 19:03:20 == begin boot-config-loader
2019-07-18 19:03:20 – begin load
2019-07-18 19:03:21 – load finished successfully
2019-07-18 19:03:21 – begin commit
2019-07-18 19:03:25 – commit succeeded
2019-07-18 19:03:25 – teardown succeeded
2019-07-18 19:03:25 – exiting
2019-07-18 19:40:44 == begin boot-config-loader
2019-07-18 19:40:44 – begin load
2019-07-18 19:40:44 – load finished successfully
2019-07-18 19:40:44 – begin commit
2019-07-18 19:40:48 – commit failed
2019-07-18 19:40:48 – teardown succeeded
2019-07-18 19:40:48 – exiting
2019-07-18 19:41:47 == begin boot-config-loader
2019-07-18 19:41:47 – begin load
2019-07-18 19:41:47 – load finished successfully
2019-07-18 19:41:47 – begin commit
2019-07-18 19:41:51 – commit succeeded
2019-07-18 19:41:51 – teardown succeeded
2019-07-18 19:41:51 – exiting
2019-07-19 18:52:02 == begin boot-config-loader
2019-07-19 18:52:02 – begin load
2019-07-19 18:52:02 – load finished successfully
2019-07-19 18:52:02 – begin commit
2019-07-19 18:52:06 – commit succeeded
2019-07-19 18:52:06 – teardown succeeded
2019-07-19 18:52:06 – exiting
2019-07-23 17:08:30 == begin boot-config-loader
2019-07-23 17:08:30 – begin load
2019-07-23 17:08:30 – load finished successfully
2019-07-23 17:08:30 – begin commit
2019-07-23 17:08:35 – commit succeeded
2019-07-23 17:08:35 – teardown succeeded
2019-07-23 17:08:35 – exiting
2019-08-09 10:53:09 == begin boot-config-loader
2019-08-09 10:53:09 – begin load
2019-08-09 10:53:09 – load finished successfully
2019-08-09 10:53:09 – begin commit
2019-08-09 10:53:15 – commit succeeded
2019-08-09 10:53:15 – teardown succeeded
2019-08-09 10:53:15 – exiting
2019-08-09 11:00:34 == begin boot-config-loader
2019-08-09 11:00:34 – begin load
2019-08-09 11:00:34 – load finished successfully
2019-08-09 11:00:34 – begin commit
2019-08-09 11:00:38 – commit failed
2019-08-09 11:00:38 – teardown succeeded
2019-08-09 11:00:38 – exiting
2019-08-09 11:08:13 == begin boot-config-loader
2019-08-09 11:08:13 – begin load
2019-08-09 11:08:13 – load finished successfully
2019-08-09 11:08:13 – begin commit
2019-08-09 11:08:17 – commit succeeded
2019-08-09 11:08:17 – teardown succeeded
2019-08-09 11:08:17 – exiting
2019-08-09 14:26:23 == begin boot-config-loader
2019-08-09 14:26:23 – begin load
2019-08-09 14:26:23 – load finished successfully
2019-08-09 14:26:23 – begin commit
2019-08-09 14:26:27 – commit succeeded
2019-08-09 14:26:27 – teardown succeeded
2019-08-09 14:26:27 – exiting
e]0;vyos@vyos: ~avyos@vyos:~$ sudo tail -n 100 /var/log/vyatta/vyatta-config-loader.log
e[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[Ce[7P400 /var/log/vyatta/vyatta-commit.log
[ system time-zone UTC ]
Restarting rsyslog (via systemctl): rsyslog.service.
[ interfaces ethernet eth0 vif 203 bridge-group ]
Adding interface eth0.203 to bridge br203
[ interfaces ethernet eth0 vif 605 bridge-group ]
Adding interface eth0.605 to bridge br605
[ interfaces vxlan vxlan203 bridge-group ]
Adding interface vxlan203 to bridge br203
[ interfaces vxlan vxlan605 bridge-group ]
Adding interface vxlan605 to bridge br605
[ system time-zone UTC ]
Restarting rsyslog (via systemctl): rsyslog.service.
[[system console]] failed
[ interfaces ethernet eth0 vif 203 bridge-group ]
Adding interface eth0.203 to bridge br203
[ interfaces ethernet eth0 vif 605 bridge-group ]
Adding interface eth0.605 to bridge br605
[ interfaces vxlan vxlan203 bridge-group ]
Adding interface vxlan203 to bridge br203
[ interfaces vxlan vxlan605 bridge-group ]
Adding interface vxlan605 to bridge br605
Commit failed
[ system time-zone UTC ]
Restarting rsyslog (via systemctl): rsyslog.service.
[ interfaces ethernet eth0 vif 203 bridge-group ]
Adding interface eth0.203 to bridge br203
[ interfaces ethernet eth0 vif 605 bridge-group ]
Adding interface eth0.605 to bridge br605
[ interfaces vxlan vxlan203 bridge-group ]
Adding interface vxlan203 to bridge br203
[ interfaces vxlan vxlan605 bridge-group ]
Adding interface vxlan605 to bridge br605
[ system time-zone UTC ]
Restarting rsyslog (via systemctl): rsyslog.service.
[ interfaces ethernet eth0 vif 203 bridge-group ]
Adding interface eth0.203 to bridge br203
[ interfaces ethernet eth0 vif 605 bridge-group ]
Adding interface eth0.605 to bridge br605
[ interfaces vxlan vxlan203 bridge-group ]
Adding interface vxlan203 to bridge br203
[ interfaces vxlan vxlan605 bridge-group ]
Adding interface vxlan605 to bridge br605
[ system time-zone UTC ]
Restarting rsyslog (via systemctl): rsyslog.service.
[ interfaces ethernet eth0 vif 691 bridge-group ]
Adding interface eth0.691 to bridge br691
[ interfaces ethernet eth0 vif 281 bridge-group ]
Adding interface eth0.281 to bridge br281
[ interfaces ethernet eth0 vif 249 bridge-group ]
Adding interface eth0.249 to bridge br249
[ interfaces ethernet eth0 vif 910 bridge-group ]
Adding interface eth0.910 to bridge br910
[ interfaces ethernet eth0 vif 900 bridge-group ]
Adding interface eth0.900 to bridge br900
[ interfaces vxlan vxlan910 bridge-group ]
Adding interface vxlan910 to bridge br910
[ interfaces vxlan vxlan691 bridge-group ]
Adding interface vxlan691 to bridge br691
[ interfaces vxlan vxlan281 bridge-group ]
Adding interface vxlan281 to bridge br281
[ interfaces vxlan vxlan249 bridge-group ]
Adding interface vxlan249 to bridge br249
[ interfaces vxlan vxlan900 bridge-group ]
Adding interface vxlan900 to bridge br900
[ system time-zone US/Eastern ]
Restarting rsyslog (via systemctl): rsyslog.service.
[ interfaces ethernet eth0 vif 691 bridge-group ]
Adding interface eth0.691 to bridge br691
[ interfaces ethernet eth0 vif 281 bridge-group ]
Adding interface eth0.281 to bridge br281
[ interfaces ethernet eth0 vif 249 bridge-group ]
Adding interface eth0.249 to bridge br249
[ interfaces ethernet eth0 vif 910 bridge-group ]
Adding interface eth0.910 to bridge br910
[ interfaces ethernet eth0 vif 900 bridge-group ]
Adding interface eth0.900 to bridge br900
[ system name-server 172.16.0.123 ]
Job for rsyslog.service failed. See ‘systemctl status rsyslog.service’ and ‘journalctl -xn’ for details.
[ system name-server 172.16.0.122 ]
Job for rsyslog.service failed. See ‘systemctl status rsyslog.service’ and ‘journalctl -xn’ for details.
[ system syslog ]
Job for rsyslog.service failed. See ‘systemctl status rsyslog.service’ and ‘journalctl -xn’ for details.
[ interfaces vxlan vxlan910 bridge-group ]
Adding interface vxlan910 to bridge br910
[ interfaces vxlan vxlan691 bridge-group ]
Adding interface vxlan691 to bridge br691
[ interfaces vxlan vxlan281 bridge-group ]
Adding interface vxlan281 to bridge br281
[ interfaces vxlan vxlan249 bridge-group ]
Adding interface vxlan249 to bridge br249
[ interfaces vxlan vxlan900 bridge-group ]
Adding interface vxlan900 to bridge br900
[[system console]] failed
[ system time-zone US/Eastern ]
Restarting rsyslog (via systemctl): rsyslog.service.
[ system name-server 172.16.0.123 ]
Job for rsyslog.service failed. See ‘systemctl status rsyslog.service’ and ‘journalctl -xn’ for details.
[ system name-server 172.16.0.122 ]
Job for rsyslog.service failed. See ‘systemctl status rsyslog.service’ and ‘journalctl -xn’ for details.
[ system syslog ]
Job for rsyslog.service failed. See ‘systemctl status rsyslog.service’ and ‘journalctl -xn’ for details.
Commit failed
[ system time-zone US/Eastern ]
Restarting rsyslog (via systemctl): rsyslog.service.
[ system name-server 172.16.0.122 ]
Job for rsyslog.service failed. See ‘systemctl status rsyslog.service’ and ‘journalctl -xn’ for details.
[ system name-server 172.16.0.123 ]
Job for rsyslog.service failed. See ‘systemctl status rsyslog.service’ and ‘journalctl -xn’ for details.
[ system name-server 172.16.0.122 ]
Job for rsyslog.service failed. See ‘systemctl status rsyslog.service’ and ‘journalctl -xn’ for details.
[ system time-zone US/Eastern ]
Restarting rsyslog (via systemctl): rsyslog.service.
[ system name-server 172.16.0.122 ]
Job for rsyslog.service failed. See ‘systemctl status rsyslog.service’ and ‘journalctl -xn’ for details.
[ system name-server 172.16.0.123 ]
Job for rsyslog.service failed. See ‘systemctl status rsyslog.service’ and ‘journalctl -xn’ for details.
[ system name-server 172.16.0.122 ]
Job for rsyslog.service failed. See ‘systemctl status rsyslog.service’ and ‘journalctl -xn’ for details.
e]0;vyos@vyos: ~avyos@vyos:~$ exit
logout
@tllewell55 , I can reproduce this issue and I think I have solution, but need wait for testing on correct device