Booting with any initial selection, the last systemd messages are:
Starting Reconfigure the system on administrator request...
Starting netprofile: The default is the current profile.
[ OK ]
Checking for new hardware [ OK ]
[ OK ] Finished Reconfigure the system on administrator request.
You are in emergency mode. After logging in, type ............
So: what is this administrator request? Google finds nothing, and I
didn't edit any part of the grub commands. I can find no mention of a "reconfigure" option in systemd commands.
Booting with any initial selection, the last systemd messages are:
Starting Reconfigure the system on administrator request...
Starting netprofile: The default is the current profile.
[ OK ]
Checking for new hardware [ OK ]
[ OK ] Finished Reconfigure the system on administrator request.
You are in emergency mode. After logging in, type ............
So: what is this administrator request? Google finds nothing, and I
didn't edit any part of the grub commands. I can find no mention of a "reconfigure" option in systemd commands.
On Wed, 05 Jan 2022 08:01:57 -0500, Grimble <grimble@nomail.afraid.org> wrote:
Booting with any initial selection, the last systemd messages are:
Starting Reconfigure the system on administrator request...
Starting netprofile: The default is the current profile.
[ OK ]
Checking for new hardware [ OK ]
[ OK ] Finished Reconfigure the system on administrator request.
You are in emergency mode. After logging in, type ............
So: what is this administrator request? Google finds nothing, and I
didn't edit any part of the grub commands. I can find no mention of a
"reconfigure" option in systemd commands.
# grep -Iir reconfigure /lib/systemd/* /lib/systemd/system/mandriva-everytime.service:Description=Reconfigure
the system on administrator request
As that finished ok, that is not the problem.
What dm (display manager) is being used? Check /etc/sysconfig/desktop.Xorg.0.log contains an error messge:
I'd try installing a different one such as lxdm, then either use "mcc/Boot/Setup Display Manger" to make it active, or just edit the
desktop file
to have ...
# cat /etc/sysconfig/desktop
DISPLAYMANAGER=lxdm
Regards, Dave Hodginsssdm was the DM; changed it to lxdm with no effect.
Xorg.0.log contains an error messge:
(EE) dbus-core: error connecting to system bus:......(Failed to connect
to socket /run/dbus/system_bus_socket: No such file or directory)
followed by Open PCI failed (var/run/acpid.socket) (No such file or directory).
The last entry on the log is the same dbus-core message, which is being added to every 10 seconds.
I notice no log message has been added to syslog since 3 January! Does
syslog need dbus?
On Tue, 11 Jan 2022 08:34:33 -0500, Grimble <grimble@nomail.afraid.org> wrote:
Xorg.0.log contains an error messge:
(EE) dbus-core: error connecting to system bus:......(Failed to connect
to socket /run/dbus/system_bus_socket: No such file or directory)
followed by Open PCI failed (var/run/acpid.socket) (No such file or
directory).
The last entry on the log is the same dbus-core message, which is being
added to every 10 seconds.
I notice no log message has been added to syslog since 3 January! Does
syslog need dbus?
The dbus program is used by various daemons to talk to each other, as
well as by
desktop environments such as kde plasma and gnome. I have no idea why it might be
failing on that system. It is a critical service.
Try booting to run level 3. Is dbus running ok then?No difference:
Regards, Dave Hodgins
On 11/01/2022 21:51, David W. Hodgins wrote:
Try booting to run level 3. Is dbus running ok then?No difference:
Regards, Dave Hodgins
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: inactive (dead)
It seems such a bizarre error that I have little option but to
re-install, but I'm worried that, without a solution, since the problem arose on the first reboot after a kernel update on a new installation, something else nasty might happen that'll waste hours more of my time.
Regards,
No difference:
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: inactive (dead)
It seems such a bizarre error that I have little option but to
re-install, but I'm worried that, without a solution, since the problem
arose on the first reboot after a kernel update on a new installation, something else nasty might happen that'll waste hours more of my time.
On Wed, 12 Jan 2022 10:26:03 -0500, Grimble <grimble@nomail.afraid.org> wrote:Thanks, William, David. I've chosen to re-install. As I said, nothing
No difference:
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: inactive (dead)
It seems such a bizarre error that I have little option but to
re-install, but I'm worried that, without a solution, since the problem
arose on the first reboot after a kernel update on a new installation,
something else nasty might happen that'll waste hours more of my time.
Either a reinstall, or open a bug report, and attach the output of "journalctl -b --no-hostname |xz >journal.xz".
Regards, Dave Hodgins
On 12/01/2022 17:58, David W. Hodgins wrote:
On Wed, 12 Jan 2022 10:26:03 -0500, Grimble <grimble@nomail.afraid.org>Thanks, William, David. I've chosen to re-install. As I said, nothing
wrote:
No difference:
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: inactive (dead)
It seems such a bizarre error that I have little option but to
re-install, but I'm worried that, without a solution, since the problem
arose on the first reboot after a kernel update on a new installation,
something else nasty might happen that'll waste hours more of my time.
Either a reinstall, or open a bug report, and attach the output of
"journalctl -b --no-hostname |xz >journal.xz".
Regards, Dave Hodgins
gets written to syslog, so there's little to put in a bug report.
The first steps of re-install have gone OK, so for the next day or so,
I'll be recreating my personal work space.
systemd does not write to syslog. It writes to journal, and you see via journalctl
You can get the old style syslog by installing and running rsyslogd.
Then you will get the files like /var/log/syslog, /var/log/messages, ...
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 242:24:44 |
Calls: | 6,624 |
Files: | 12,175 |
Messages: | 5,320,202 |