case study - journalctl - where is logger output

Balint Szigeti balint.szgt at gmail.com
Thu Sep 11 18:04:45 UTC 2014


hello

today I installed the rsyslog and enable it then disabled (then masked)
systemd-journal-flush, systemd-journald services. Plus I disabled
systemd-journald.socket as well.
It broke my system. After I closed the sudo session I could gain root
access plus I couldn't start any program only forks for the existed ones
(like gnome terminal).
The reboot didn't work. The box just didn't start up. :( (just remark -
systemd is not depends on itself........)

I booted into runlevel 1 (yeeeah - runlevel doesn't exist on systemd - I
wanted to say rescue.target) and redo the mask and enable everything. 

I've noticed the rsyslog doesn't listen to the system logging.

I've run logger command but I don't find it in the log. I've checked the
journalctl and /var/log/messages file as well.

# logger -t AAAA hello
# journalctl |grep hello
# grep hello /var/log/messages 
#

Does anyone have a clue?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20140911/9158897e/attachment.html>


More information about the users mailing list