<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.6.6">
</HEAD>
<BODY>
On Tue, 2014-09-16 at 17:46 -0600, Chris Murphy wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On Sep 16, 2014, at 9:11 AM, Balint Szigeti <<A HREF="mailto:balint.szgt@gmail.com">balint.szgt@gmail.com</A>> wrote:
<FONT COLOR="#737373">> On Tue, 2014-09-16 at 09:52 -0400, Tom H wrote:</FONT>
<FONT COLOR="#737373">>> On Sat, Sep 13, 2014 at 11:47 AM, Balint Szigeti <<A HREF="mailto:balint.szgt@gmail.com">balint.szgt@gmail.com</A></FONT>
<FONT COLOR="#737373">>> > wrote:</FONT>
<FONT COLOR="#737373">>> </FONT>
<FONT COLOR="#737373">>> > On Thu, 2014-09-11 at 16:16 -0400, Tom H wrote:</FONT>
<FONT COLOR="#737373">>> ></FONT>
<FONT COLOR="#737373">>> > On Thu, Sep 11, 2014 at 2:04 PM, Balint Szigeti <<A HREF="mailto:balint.szgt@gmail.com">balint.szgt@gmail.com</A>></FONT>
<FONT COLOR="#737373">>> > wrote:</FONT>
<FONT COLOR="#737373">>> ></FONT>
<FONT COLOR="#737373">>> ></FONT>
<FONT COLOR="#737373">>> >> today I installed the rsyslog and enable it then disabled (then masked)</FONT>
<FONT COLOR="#737373">>> >> systemd-journal-flush, systemd-journald services. Plus I disabled</FONT>
<FONT COLOR="#737373">>> >> systemd-journald.socket as well.</FONT>
<FONT COLOR="#737373">>> >> It broke my system. After I closed the sudo session I could gain root</FONT>
<FONT COLOR="#737373">>> >> access</FONT>
<FONT COLOR="#737373">>> >> plus I couldn't start any program only forks for the existed ones (like</FONT>
<FONT COLOR="#737373">>> >> gnome terminal).</FONT>
<FONT COLOR="#737373">>> >> The reboot didn't work. The box just didn't start up. :( (just remark -</FONT>
<FONT COLOR="#737373">>> >> systemd is not depends on itself........)</FONT>
<FONT COLOR="#737373">>> ></FONT>
<FONT COLOR="#737373">>> > I disabled all of the journal service and socket units and rebooted</FONT>
<FONT COLOR="#737373">>> > without a hitch. It was in an X-less VM though so perhaps things go</FONT>
<FONT COLOR="#737373">>> > awry when booting a DE (I don't see why it whould).</FONT>
<FONT COLOR="#737373">>> ></FONT>
<FONT COLOR="#737373">>> ></FONT>
<FONT COLOR="#737373">>> >> I booted into runlevel 1 (yeeeah - runlevel doesn't exist on systemd - I</FONT>
<FONT COLOR="#737373">>> >> wanted to say rescue.target) and redo the mask and enable everything.</FONT>
<FONT COLOR="#737373">>> ></FONT>
<FONT COLOR="#737373">>> > I boot into runlevel 1 when I use "1" on the kernel cmdline.</FONT>
<FONT COLOR="#737373">>> ></FONT>
<FONT COLOR="#737373">>> ></FONT>
<FONT COLOR="#737373">>> >> I've noticed the rsyslog doesn't listen to the system logging.</FONT>
<FONT COLOR="#737373">>> >></FONT>
<FONT COLOR="#737373">>> >> I've run logger command but I don't find it in the log. I've checked the</FONT>
<FONT COLOR="#737373">>> >> journalctl and /var/log/messages file as well.</FONT>
<FONT COLOR="#737373">>> >></FONT>
<FONT COLOR="#737373">>> >> # logger -t AAAA hello</FONT>
<FONT COLOR="#737373">>> >> # journalctl |grep hello</FONT>
<FONT COLOR="#737373">>> >> # grep hello /var/log/messages</FONT>
<FONT COLOR="#737373">>> >> #</FONT>
<FONT COLOR="#737373">>> ></FONT>
<FONT COLOR="#737373">>> > Same here.</FONT>
<FONT COLOR="#737373">>> ></FONT>
<FONT COLOR="#737373">>> > Is journald supposed to be turned off when using systemd? Why do you</FONT>
<FONT COLOR="#737373">>> > want it off? You can set "Storage=volatile" in</FONT>
<FONT COLOR="#737373">>> > "/etc/systemd/journald.conf" and 1) you'll only have rsyslog logs</FONT>
<FONT COLOR="#737373">>> > across reboots and 2) the journald logs will be written to the</FONT>
<FONT COLOR="#737373">>> > "/run/log/journal/" tmpfs so journald will simply collect logs for</FONT>
<FONT COLOR="#737373">>> > rsyslog.</FONT>
<FONT COLOR="#737373">>> ></FONT>
<FONT COLOR="#737373">>> > I've just tried to set the Storage entry in /etc/systemd/journald.conf to</FONT>
<FONT COLOR="#737373">>> > "none" according to manual page and off course no effect.</FONT>
<FONT COLOR="#737373">>> > Also tried to set LogTarget to "syslog" in /etc/systemd/system.conf and</FONT>
<FONT COLOR="#737373">>> > reboot (funny, hurray we become Windows......)but no effect.</FONT>
<FONT COLOR="#737373">>> ></FONT>
<FONT COLOR="#737373">>> > Needless to say, the logs are being found in journalctl and messages file of</FONT>
<FONT COLOR="#737373">>> > course. I don't think to raise bug because any time when they hear someone</FONT>
<FONT COLOR="#737373">>> > doesn't want to use their 'solutions' they refuse/ignore or set the ticket</FONT>
<FONT COLOR="#737373">>> > to WONTFIX.</FONT>
<FONT COLOR="#737373">>> > Personally that is my bigger problem.</FONT>
<FONT COLOR="#737373">>> ></FONT>
<FONT COLOR="#737373">>> > I finished testing the syslog. I think the only thing that we can do to</FONT>
<FONT COLOR="#737373">>> > accept and shut our mouth :(</FONT>
<FONT COLOR="#737373">>> </FONT>
<FONT COLOR="#737373">>> </FONT>
<FONT COLOR="#737373">>> It's working here. systemd must sense that you don't like it and it's</FONT>
<FONT COLOR="#737373">>> messin' wit' u!</FONT>
<FONT COLOR="#737373">>> </FONT>
<FONT COLOR="#737373">>> </FONT>
<FONT COLOR="#737373">>> </FONT>
<FONT COLOR="#737373">> you are right. I don't like it.</FONT>
<FONT COLOR="#737373">>> # grep Storage /etc/systemd/journald.conf</FONT>
<FONT COLOR="#737373">>> Storage=none</FONT>
<FONT COLOR="#737373">>> </FONT>
<FONT COLOR="#737373">> I've set it and restarted the "systemctl restart systemd-journald.service" journald and the system stopped to logging. :(</FONT>
>From defaults, only changing journald.conf Storage=none, installing and enabling rsyslog, I can't reproduce the problem on either Fedora 20 or 21.
[root@f20v log]# logger biscuit
[root@f20v log]# grep biscuit /var/log/messages
Sep 16 10:33:42 f20v root: biscuit
[root@f20v log]# journalctl | grep biscuit
Sep 16 10:33:42 f20v.localdomain root[786]: biscuit
rsyslog-7.4.8-1.fc20.1.x86_64
systemd-208-21.fc20.x86_64
</PRE>
</BLOCKQUOTE>
Well, I have definitely a problem:<BR>
<BR>
[<A HREF="mailto:root@szigeti-6560b">root@szigeti-6560b</A> ~]# vi /etc/systemd/journald.conf <BR>
[<A HREF="mailto:root@szigeti-6560b">root@szigeti-6560b</A> ~]# grep none $_<BR>
Storage=none<BR>
[<A HREF="mailto:root@szigeti-6560b">root@szigeti-6560b</A> ~]# systemctl restart systemd-journald.service <BR>
[<A HREF="mailto:root@szigeti-6560b">root@szigeti-6560b</A> ~]# logger foo<BR>
[<A HREF="mailto:root@szigeti-6560b">root@szigeti-6560b</A> ~]# grep foo /var/log/messages<BR>
[<A HREF="mailto:root@szigeti-6560b">root@szigeti-6560b</A> ~]# journalctl -n 100 |grep foo<BR>
[<A HREF="mailto:root@szigeti-6560b">root@szigeti-6560b</A> ~]#<BR>
[<A HREF="mailto:root@szigeti-6560b">root@szigeti-6560b</A> ~]# vi /etc/systemd/journald.conf <BR>
[<A HREF="mailto:root@szigeti-6560b">root@szigeti-6560b</A> ~]# systemctl restart systemd-journald.service <BR>
[<A HREF="mailto:root@szigeti-6560b">root@szigeti-6560b</A> ~]# grep Storage /etc/systemd/journald.conf <BR>
#Storage=none<BR>
#Storage=auto<BR>
[<A HREF="mailto:root@szigeti-6560b">root@szigeti-6560b</A> ~]# logger AAAAAAAAAAA<BR>
[<A HREF="mailto:root@szigeti-6560b">root@szigeti-6560b</A> ~]# grep AAAAAA /var/log/messages<BR>
Sep 17 11:38:14 SZIGETI-6560B bszigeti: AAAAAAAAAAA<BR>
[<A HREF="mailto:root@szigeti-6560b">root@szigeti-6560b</A> ~]# journalctl -n 100 |grep AAAA<BR>
Sep 17 11:38:14 szigeti-6560b bszigeti[28839]: AAAAAAAAAAA<BR>
<BR>
rsyslog-7.4.8-1.fc20.1.x86_64<BR>
systemd-208-21.fc20.x86_64<BR>
<BR>
Do you have any clue?<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
Chris Murphy
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>