[opensuse-factory] 12.3M1 looses rsyslog shortly after system generation
After generating a standard system in a VM from the DVD iso of 12.3 M1 I do get some messages in /var/log/messages and a last message telling: 2012-11-15T23:53:01.950045+01:00 linux rsyslogd: [origin software="rsyslogd" swVersion="7.2.1" x-pid="1497" x-info="http://www.rsyslog.com"] exiting on signal 15. After that nothing appears in that file and the command # systemctl start rsyslog.service Failed to issue method call: Unit rsyslog.service failed to load: No such file or directory. See system logs and 'systemctl status rsyslog.service' for details. This is an ironic message because the system log is not working and the status command returns: # systemctl status rsyslog.service rsyslog.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) How to proceed? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
How to proceed? systemctl status syslog.service
-- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 16.11.2012 01:20, schrieb Freek de Kruijf:
After generating a standard system in a VM from the DVD iso of 12.3 M1 I do get some messages in /var/log/messages and a last message telling:
2012-11-15T23:53:01.950045+01:00 linux rsyslogd: [origin software="rsyslogd" swVersion="7.2.1" x-pid="1497" x-info="http://www.rsyslog.com"] exiting on signal 15.
After that nothing appears in that file and the command
# systemctl start rsyslog.service Failed to issue method call: Unit rsyslog.service failed to load: No such file or directory. See system logs and 'systemctl status rsyslog.service' for details.
https://bugzilla.novell.com/show_bug.cgi?id=789059 which got marked as a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=788330
This is an ironic message because the system log is not working and the status command returns: # systemctl status rsyslog.service rsyslog.service Loaded: error (Reason: No such file or directory) Active: inactive (dead)
How to proceed?
journalctl -b -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op vrijdag 16 november 2012 06:43:48 schreef Stefan Seyfried:
Am 16.11.2012 01:20, schrieb Freek de Kruijf:
After generating a standard system in a VM from the DVD iso of 12.3 M1 I do get some messages in /var/log/messages and a last message telling:
2012-11-15T23:53:01.950045+01:00 linux rsyslogd: [origin software="rsyslogd" swVersion="7.2.1" x-pid="1497" x-info="http://www.rsyslog.com"] exiting on signal 15.
After that nothing appears in that file and the command
# systemctl start rsyslog.service Failed to issue method call: Unit rsyslog.service failed to load: No such file or directory. See system logs and 'systemctl status rsyslog.service' for details.
https://bugzilla.novell.com/show_bug.cgi?id=789059 which got marked as a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=788330
This is an ironic message because the system log is not working and the status command returns: # systemctl status rsyslog.service rsyslog.service
Loaded: error (Reason: No such file or directory) Active: inactive (dead)
How to proceed?
journalctl -b
I checked the journal log with the above command and found an error message telling that the file /run/systemd/syslog.core does not exist. However after giving the commands "systemctl start {r|}syslog.service" nothing appears in the journal. The error message from these commands reports a missing file, but without a name. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 16.11.2012 11:33, schrieb Freek de Kruijf:
I checked the journal log with the above command and found an error message telling that the file /run/systemd/syslog.core does not exist. However after
Yes, see the bug reports I linkes. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Alin M Elena -
Freek de Kruijf -
Stefan Seyfried