Re: F24: no rsyslog forwarding

2015-11-09 Thread Reindl Harald 



Am 07.11.2015 um 17:20 schrieb Zbigniew Jędrzejewski-Szmek:

On Sat, Nov 07, 2015 at 01:31:11PM +0100, Reindl Harald wrote:



Am 07.11.2015 um 12:59 schrieb Zbigniew Jędrzejewski-Szmek:

On Fri, Nov 06, 2015 at 06:20:39PM +0100, Reindl Harald wrote:



Am 06.11.2015 um 18:15 schrieb Subhendu Ghosh:


On Nov 6, 2015 9:52 AM, "Reindl Harald" mailto:h.rei...@thelounge.net>> wrote:


who is responsible that nothing is forwarded to the traditional syslog?
systemd or rsyslog?



Journald is probably hold the log socket and not forwarding to syslog


it does not need to Forward the old way hence "ForwardToSyslog=no"
and instead "$ModLoad imjournal" which is nothing new but don't work
at Rawhide currecntly while it dooes on F20/F21/F22/f23

http://www.rsyslog.com/doc/v8-stable/configuration/modules/imjournal.html

to say it in other words: i did not ask for "probably", just pointed
out that Rawhide is currently broken, that probably systemd or
probably rsyslog is broken in the one or other direction is clear


I looks like a problem on the rsyslog side, from what you describe.
A permission issue seems the most likely


permission to what?

since rsyslog with "imjournal" reads data from journald than it
sounds more like an systemd regression if it's a permission issue
(no SELinux is part of the game here)

Privileges are needed to read the journal. Please file a bug against
rsyslog, include the output of getfacl /var/log/journal /run/log/journal,
and other useful info, and I'm sure rsyslog maintainers will be able
to figure it out or redirect it back to systemd if necessary.
We're not going to solve it on the mailing list


well, i started to create a bugreport - interesting - now it started to 
work and according to the logs i have no idea which update may have 
fixed that and why


Nov 06 15:41:20 INFO Upgraded: rpm-python3-4.13.0-0.rc1.10.fc24.x86_64
Nov 06 15:41:20 INFO Upgraded: rpm-python3-4.13.0-0.rc1.10.fc24.x86_64
Nov 06 15:41:20 INFO Upgraded: rpm-python-4.13.0-0.rc1.10.fc24.x86_64
Nov 06 15:41:20 INFO Upgraded: rpm-python-4.13.0-0.rc1.10.fc24.x86_64
Nov 06 15:41:20 INFO Upgraded: file-5.25-1.fc24.x86_64
Nov 06 15:41:20 INFO Upgraded: file-5.25-1.fc24.x86_64
Nov 06 15:41:20 INFO Upgraded: 
rpm-plugin-systemd-inhibit-4.13.0-0.rc1.10.fc24.x86_64
Nov 06 15:41:20 INFO Upgraded: 
rpm-plugin-systemd-inhibit-4.13.0-0.rc1.10.fc24.x86_64

Nov 06 15:41:20 INFO Upgraded: shadow-utils-2:4.2.1-4.fc24.x86_64
Nov 06 15:41:20 INFO Upgraded: shadow-utils-2:4.2.1-4.fc24.x86_64
Nov 06 15:41:20 INFO Upgraded: make-1:4.1-4.fc24.x86_64
Nov 06 15:41:20 INFO Upgraded: make-1:4.1-4.fc24.x86_64
Nov 06 15:41:20 INFO Upgraded: libtool-ltdl-2.4.6-6.fc24.x86_64
Nov 06 15:41:20 INFO Upgraded: libtool-ltdl-2.4.6-6.fc24.x86_64
Nov 06 15:41:20 INFO Upgraded: libgomp-5.2.1-4.fc24.x86_64
Nov 06 15:41:20 INFO Upgraded: libgomp-5.2.1-4.fc24.x86_64
Nov 06 15:41:21 INFO Upgraded: binutils-2.25.1-9.fc24.x86_64
Nov 06 15:41:21 INFO Upgraded: binutils-2.25.1-9.fc24.x86_64
Nov 06 15:41:23 INFO Installed: kernel-core-4.4.0-0.rc0.git2.1.fc24.x86_64
Nov 06 15:41:23 INFO Installed: kernel-core-4.4.0-0.rc0.git2.1.fc24.x86_64
Nov 06 15:53:20 INFO --- logging initialized ---
Nov 06 15:53:30 INFO Installed: libpipeline-1.4.1-1.fc24.x86_64
Nov 06 15:53:30 INFO Installed: libpipeline-1.4.1-1.fc24.x86_64
Nov 06 15:53:30 INFO Installed: man-db-2.7.4-2.fc24.x86_64
Nov 06 15:53:30 INFO Installed: man-db-2.7.4-2.fc24.x86_64
Nov 06 15:53:30 INFO Installed: less-481-1.fc24.x86_64
Nov 06 15:53:30 INFO Installed: less-481-1.fc24.x86_64
Nov 07 13:33:33 INFO --- logging initialized ---
Nov 07 13:33:34 INFO --- logging initialized ---
Nov 07 13:41:03 INFO Upgraded: 
rpm-plugin-selinux-4.13.0-0.rc1.11.fc24.x86_64
Nov 07 13:41:03 INFO Upgraded: 
rpm-plugin-selinux-4.13.0-0.rc1.11.fc24.x86_64

Nov 07 13:41:03 INFO Upgraded: rpm-libs-4.13.0-0.rc1.11.fc24.x86_64
Nov 07 13:41:03 INFO Upgraded: rpm-libs-4.13.0-0.rc1.11.fc24.x86_64
Nov 07 13:41:03 INFO Upgraded: rpm-4.13.0-0.rc1.11.fc24.x86_64
Nov 07 13:41:03 INFO Upgraded: rpm-4.13.0-0.rc1.11.fc24.x86_64
Nov 07 13:41:03 INFO Upgraded: rpm-build-libs-4.13.0-0.rc1.11.fc24.x86_64
Nov 07 13:41:03 INFO Upgraded: rpm-build-libs-4.13.0-0.rc1.11.fc24.x86_64
Nov 07 13:41:03 INFO Upgraded: libgcc-5.2.1-5.fc24.x86_64
Nov 07 13:41:03 INFO Upgraded: libgcc-5.2.1-5.fc24.x86_64
Nov 07 13:41:03 INFO Upgraded: libstdc++-5.2.1-5.fc24.x86_64
Nov 07 13:41:03 INFO Upgraded: libstdc++-5.2.1-5.fc24.x86_64
Nov 07 13:41:04 INFO Upgraded: rpm-python3-4.13.0-0.rc1.11.fc24.x86_64
Nov 07 13:41:04 INFO Upgraded: rpm-python3-4.13.0-0.rc1.11.fc24.x86_64
Nov 07 13:41:04 INFO Upgraded: rpm-python-4.13.0-0.rc1.11.fc24.x86_64
Nov 07 13:41:04 INFO Upgraded: rpm-python-4.13.0-0.rc1.11.fc24.x86_64
Nov 07 13:41:04 INFO Upgraded: 
rpm-plugin-systemd-inhibit-4.13.0-0.rc1.11.fc24.x86_64
Nov 07 13:41:04 INFO Upgraded: 
rpm-plugin-systemd-inhibit-4.13.0-0.rc1.11.fc24.x86_64

Nov 07 13:41:04 INFO Upgraded: libgomp-5.2.1-5.fc24.x86_64
Nov 07 13:41:04 INFO Upgraded: lib

Re: F24: no rsyslog forwarding

2015-11-07 Thread Zbigniew Jędrzejewski-Szmek 
On Sat, Nov 07, 2015 at 01:31:11PM +0100, Reindl Harald wrote:
> 
> 
> Am 07.11.2015 um 12:59 schrieb Zbigniew Jędrzejewski-Szmek:
> >On Fri, Nov 06, 2015 at 06:20:39PM +0100, Reindl Harald wrote:
> >>
> >>
> >>Am 06.11.2015 um 18:15 schrieb Subhendu Ghosh:
> >>>
> >>>On Nov 6, 2015 9:52 AM, "Reindl Harald"  >>>> wrote:
> 
> who is responsible that nothing is forwarded to the traditional syslog?
> systemd or rsyslog?
> 
> >>>
> >>>Journald is probably hold the log socket and not forwarding to syslog
> >>
> >>it does not need to Forward the old way hence "ForwardToSyslog=no"
> >>and instead "$ModLoad imjournal" which is nothing new but don't work
> >>at Rawhide currecntly while it dooes on F20/F21/F22/f23
> >>
> >>http://www.rsyslog.com/doc/v8-stable/configuration/modules/imjournal.html
> >>
> >>to say it in other words: i did not ask for "probably", just pointed
> >>out that Rawhide is currently broken, that probably systemd or
> >>probably rsyslog is broken in the one or other direction is clear
> >
> >I looks like a problem on the rsyslog side, from what you describe.
> >A permission issue seems the most likely
> 
> permission to what?
> 
> since rsyslog with "imjournal" reads data from journald than it
> sounds more like an systemd regression if it's a permission issue
> (no SELinux is part of the game here)
Privileges are needed to read the journal. Please file a bug against
rsyslog, include the output of getfacl /var/log/journal /run/log/journal,
and other useful info, and I'm sure rsyslog maintainers will be able
to figure it out or redirect it back to systemd if necessary.
We're not going to solve it on the mailing list.

Zbyszek

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F24: no rsyslog forwarding

2015-11-07 Thread Reindl Harald 



Am 07.11.2015 um 12:59 schrieb Zbigniew Jędrzejewski-Szmek:

On Fri, Nov 06, 2015 at 06:20:39PM +0100, Reindl Harald wrote:



Am 06.11.2015 um 18:15 schrieb Subhendu Ghosh:


On Nov 6, 2015 9:52 AM, "Reindl Harald" mailto:h.rei...@thelounge.net>> wrote:


who is responsible that nothing is forwarded to the traditional syslog?
systemd or rsyslog?



Journald is probably hold the log socket and not forwarding to syslog


it does not need to Forward the old way hence "ForwardToSyslog=no"
and instead "$ModLoad imjournal" which is nothing new but don't work
at Rawhide currecntly while it dooes on F20/F21/F22/f23

http://www.rsyslog.com/doc/v8-stable/configuration/modules/imjournal.html

to say it in other words: i did not ask for "probably", just pointed
out that Rawhide is currently broken, that probably systemd or
probably rsyslog is broken in the one or other direction is clear


I looks like a problem on the rsyslog side, from what you describe.
A permission issue seems the most likely


permission to what?

since rsyslog with "imjournal" reads data from journald than it sounds 
more like an systemd regression if it's a permission issue (no SELinux 
is part of the game here)






signature.asc
Description: OpenPGP digital signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F24: no rsyslog forwarding

2015-11-07 Thread Zbigniew Jędrzejewski-Szmek 
On Fri, Nov 06, 2015 at 06:20:39PM +0100, Reindl Harald wrote:
> 
> 
> Am 06.11.2015 um 18:15 schrieb Subhendu Ghosh:
> >
> >On Nov 6, 2015 9:52 AM, "Reindl Harald"  >> wrote:
> > >
> > > who is responsible that nothing is forwarded to the traditional syslog?
> > > systemd or rsyslog?
> > >
> >
> >Journald is probably hold the log socket and not forwarding to syslog
> 
> it does not need to Forward the old way hence "ForwardToSyslog=no"
> and instead "$ModLoad imjournal" which is nothing new but don't work
> at Rawhide currecntly while it dooes on F20/F21/F22/f23
> 
> http://www.rsyslog.com/doc/v8-stable/configuration/modules/imjournal.html
> 
> to say it in other words: i did not ask for "probably", just pointed
> out that Rawhide is currently broken, that probably systemd or
> probably rsyslog is broken in the one or other direction is clear

I looks like a problem on the rsyslog side, from what you describe.
A permission issue seems the most likely.

Zbyszek
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F24: no rsyslog forwarding

2015-11-06 Thread Rahul Sundaram 
Hi

On Fri, Nov 6, 2015 at 12:20 PM, Reindl Harald  wrote:

> to say it in other words: i did not ask for "probably", just pointed out
> that Rawhide is currently broken, that probably systemd or probably rsyslog
> is broken in the one or other direction is clear


Can you file a bug report?

Rahul
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F24: no rsyslog forwarding

2015-11-06 Thread Reindl Harald 



Am 06.11.2015 um 18:15 schrieb Subhendu Ghosh:


On Nov 6, 2015 9:52 AM, "Reindl Harald" mailto:h.rei...@thelounge.net>> wrote:
 >
 > who is responsible that nothing is forwarded to the traditional syslog?
 > systemd or rsyslog?
 >

Journald is probably hold the log socket and not forwarding to syslog


it does not need to Forward the old way hence "ForwardToSyslog=no" and 
instead "$ModLoad imjournal" which is nothing new but don't work at 
Rawhide currecntly while it dooes on F20/F21/F22/f23


http://www.rsyslog.com/doc/v8-stable/configuration/modules/imjournal.html

to say it in other words: i did not ask for "probably", just pointed out 
that Rawhide is currently broken, that probably systemd or probably 
rsyslog is broken in the one or other direction is clear



 > /var/lib/rsyslog/imjournal.state exists and get re-created when it is
deleted
 > __
 >
 > imjournal is configured
 >
 > $ModLoad imjournal
 > $MainMsgQueueSize 10
 > $WorkDirectory /var/lib/rsyslog
 > $IMJournalStateFile imjournal.state
 > __
 >
 > [root@rawhide ~]# cat /var/lib/rsyslog/imjournal.state
 >
s=fd7c18c2f779473fa1b001f7c110f006;i=3b0;b=d7cb147743824c819a33714632f29e16;m=112d9776;t=523e0539c0a26;x=3ff5b07833c8f9c
 >
 >
 > [root@rawhide ~]# rpm -q rsyslog
 > rsyslog-8.12.0-2.fc24.x86_64
 >
 > [root@rawhide ~]# rpm -qa | grep systemd
 > systemd-227-3.fc24.x86_64
 > systemd-libs-227-3.fc24.x86_64




signature.asc
Description: OpenPGP digital signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F24: no rsyslog forwarding

2015-11-06 Thread Subhendu Ghosh 
On Nov 6, 2015 9:52 AM, "Reindl Harald"  wrote:
>
> who is responsible that nothing is forwarded to the traditional syslog?
> systemd or rsyslog?
>

Journald is probably hold the log socket and not forwarding to syslog

> /var/lib/rsyslog/imjournal.state exists and get re-created when it is
deleted
> __
>
> imjournal is configured
>
> $ModLoad imjournal
> $MainMsgQueueSize 10
> $WorkDirectory /var/lib/rsyslog
> $IMJournalStateFile imjournal.state
> __
>
> [root@rawhide ~]# cat /var/lib/rsyslog/imjournal.state
>
s=fd7c18c2f779473fa1b001f7c110f006;i=3b0;b=d7cb147743824c819a33714632f29e16;m=112d9776;t=523e0539c0a26;x=3ff5b07833c8f9c
>
>
> [root@rawhide ~]# rpm -q rsyslog
> rsyslog-8.12.0-2.fc24.x86_64
>
> [root@rawhide ~]# rpm -qa | grep systemd
> systemd-227-3.fc24.x86_64
> systemd-libs-227-3.fc24.x86_64
>
>
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

F24: no rsyslog forwarding

2015-11-06 Thread Reindl Harald 

who is responsible that nothing is forwarded to the traditional syslog?
systemd or rsyslog?

/var/lib/rsyslog/imjournal.state exists and get re-created when it is 
deleted

__

imjournal is configured

$ModLoad imjournal
$MainMsgQueueSize 10
$WorkDirectory /var/lib/rsyslog
$IMJournalStateFile imjournal.state
__

[root@rawhide ~]# cat /var/lib/rsyslog/imjournal.state
s=fd7c18c2f779473fa1b001f7c110f006;i=3b0;b=d7cb147743824c819a33714632f29e16;m=112d9776;t=523e0539c0a26;x=3ff5b07833c8f9c


[root@rawhide ~]# rpm -q rsyslog
rsyslog-8.12.0-2.fc24.x86_64

[root@rawhide ~]# rpm -qa | grep systemd
systemd-227-3.fc24.x86_64
systemd-libs-227-3.fc24.x86_64




signature.asc
Description: OpenPGP digital signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct