Re: [arch-general] systemd 214, journal problem

2014-07-03 Thread Stefan Tatschner
Am Mittwoch, den 25.06.2014, 13:07 +0200 schrieb Davor Rotim: > I have reported this to the bug tracker: https://bugs.archlinux.org/task/40970 - Update to systemd 214 - reboot - rebuild the initramdisk (mkinitcpio -p linux-lts, mkinitcpio -p linux) - reboot -> my problem was fixed I always have r

Re: [arch-general] systemd 214, journal problem

2014-06-25 Thread Stefan Tatschner
Am Mittwoch, den 25.06.2014, 12:40 +0200 schrieb Davor Rotim: > Yes, same issue here. All services start normally just no logging to the > journal. For example, journalctl -u systemd-networkd will only show logs > until the systemd 214 upgrade after that as if it never existed (but > strangely ever

Re: [arch-general] systemd 214, journal problem

2014-06-25 Thread Davor Rotim
I have reported this to the bug tracker: https://bugs.archlinux.org/task/40970

Re: [arch-general] systemd 214, journal problem

2014-06-25 Thread Davor Rotim
Yes, same issue here. All services start normally just no logging to the journal. For example, journalctl -u systemd-networkd will only show logs until the systemd 214 upgrade after that as if it never existed (but strangely everything works normally). This is on 3.15.1-1-ARCH i686.

Re: [arch-general] systemd 214, journal problem

2014-06-25 Thread Martti Kühne
This is not correct. :-) Fail2ban needs to somehow get those messages from journald. Did you try disabling it for a boot? When you update today, maybe trying to log the clogging of your services (eg. strace) would be a good idea. cheers! mar77i

Re: [arch-general] systemd 214, journal problem

2014-06-25 Thread Stefan Tatschner
Am Mittwoch, den 25.06.2014, 11:01 +0200 schrieb Martti Kühne: > On Wed, Jun 25, 2014 at 9:04 AM, Stefan Tatschner > > The lack of journal messages also mean that fail2ban does not work; > > that's really bad. I will try updating once again later this day and > > I'll let you know. > > I'm not sur

Re: [arch-general] systemd 214, journal problem

2014-06-25 Thread Martti Kühne
On Wed, Jun 25, 2014 at 9:04 AM, Stefan Tatschner wrote: > I dont't get *ANY* message after booting the machine. After every > service has been started (my last one is always fail2ban) I do not get > any more messages. This includes e.g. postfix, amavis, ssh, dovecot, > cron, sudo things, ... > >

Re: [arch-general] systemd 214, journal problem

2014-06-25 Thread Stefan Tatschner
Am Mittwoch, den 25.06.2014, 08:58 +0200 schrieb Ralf Mardorf: > [rocketmouse@archlinux ~]$ uname -rm > 3.8.13-rt14-1-rt x86_64 > [rocketmouse@archlinux ~]$ pacman -Si linux-lts | grep Version > Version: 3.10.44-1 > > I still don't know what messages you don't get, however, I get messages

Re: [arch-general] systemd 214, journal problem

2014-06-24 Thread Ralf Mardorf
On Wed, 2014-06-25 at 06:40 +0200, Stefan Tatschner wrote: > Am Mittwoch, den 25.06.2014, 04:57 +0200 schrieb Ralf Mardorf: > > On Tue, 2014-06-24 at 12:29 +0200, Stefan Tatschner wrote: > > > today I have run pacman -Syu on my arch server. Systemd was updated from > > > 213 to 214 and now I don't

Re: [arch-general] systemd 214, journal problem

2014-06-24 Thread Stefan Tatschner
Am Mittwoch, den 25.06.2014, 04:57 +0200 schrieb Ralf Mardorf: > On Tue, 2014-06-24 at 12:29 +0200, Stefan Tatschner wrote: > > today I have run pacman -Syu on my arch server. Systemd was updated from > > 213 to 214 and now I don't get any new journal entries. I just get the > > messages from the b

Re: [arch-general] systemd 214, journal problem

2014-06-24 Thread Ralf Mardorf
On Tue, 2014-06-24 at 12:29 +0200, Stefan Tatschner wrote: > today I have run pacman -Syu on my arch server. Systemd was updated from > 213 to 214 and now I don't get any new journal entries. I just get the > messages from the boot process and that's all. You got this messages when installing it:

Re: [arch-general] systemd 214, journal problem

2014-06-24 Thread Stefan Tatschner
Am Dienstag, den 24.06.2014, 13:31 -0400 schrieb Genes Lists: > I had same issue with systemd 214 and kernel 3.15. For me,it was > resolved with 3.15.1 kernel (which had some capabilities and audit fixes > - not sure they were cause, but 3.15.1 fixed it for me). I can try this. I use the arch

Re: [arch-general] systemd 214, journal problem

2014-06-24 Thread Genes Lists
I had same issue with systemd 214 and kernel 3.15. For me,it was resolved with 3.15.1 kernel (which had some capabilities and audit fixes - not sure they were cause, but 3.15.1 fixed it for me). If you're running 3.15.1 or 3.15.rc2 and still have the issue then it is likely not same issue

Re: [arch-general] systemd 214, journal problem

2014-06-24 Thread Anthony Campbell
On 24 Jun 2014, Anthony Campbell wrote: > On 24 Jun 2014, Stefan Tatschner wrote: > > Am Dienstag, den 24.06.2014, 12:29 +0200 schrieb Stefan Tatschner: > > > Hi, > > > today I have run pacman -Syu on my arch server. Systemd was updated from > > > 213 to 214 and now I don't get any new journal entr

Re: [arch-general] systemd 214, journal problem

2014-06-24 Thread Stefan Tatschner
Am Dienstag, den 24.06.2014, 18:16 +0100 schrieb Mauro Santos: > It seems to be working fine here, the output of 'journalctl -b' includes > output from dbus, polkitd, NetworkManager, etc. > It works on my desktop as well. My server seems to have a problem with systemd 214...

Re: [arch-general] systemd 214, journal problem

2014-06-24 Thread Bruno Yemini
On Tue, Jun 24, 2014 at 2:11 PM, Bjoern Franke wrote: > Am Dienstag, den 24.06.2014, 13:51 -0300 schrieb Bruno Yemini: > > When upgrading to systemd 214-2, Pacman gives this message: > > === > > :: coredumps are no longer sent to the journal by default. To re-enable: > >echo >/etc/sysctl.d/50

Re: [arch-general] systemd 214, journal problem

2014-06-24 Thread Stefan Tatschner
Am Dienstag, den 24.06.2014, 19:11 +0200 schrieb Bjoern Franke: > > I guess this command will re-enable the old feature. > > He spoke of any messages, not coredumps. Yes, I did not mean the coredump thing.

Re: [arch-general] systemd 214, journal problem

2014-06-24 Thread Mauro Santos
On 24-06-2014 11:29, Stefan Tatschner wrote: > Hi, > today I have run pacman -Syu on my arch server. Systemd was updated from > 213 to 214 and now I don't get any new journal entries. I just get the > messages from the boot process and that's all. > > Any ideas? > > Stefan > > . > It seems to

Re: [arch-general] systemd 214, journal problem

2014-06-24 Thread Bjoern Franke
Am Dienstag, den 24.06.2014, 13:51 -0300 schrieb Bruno Yemini: > When upgrading to systemd 214-2, Pacman gives this message: > === > :: coredumps are no longer sent to the journal by default. To re-enable: >echo >/etc/sysctl.d/50-coredump.conf \ > "kernel.core_pattern=|/usr/lib/systemd/systemd-

Re: [arch-general] systemd 214, journal problem

2014-06-24 Thread Anthony Campbell
On 24 Jun 2014, Stefan Tatschner wrote: > Am Dienstag, den 24.06.2014, 12:29 +0200 schrieb Stefan Tatschner: > > Hi, > > today I have run pacman -Syu on my arch server. Systemd was updated from > > 213 to 214 and now I don't get any new journal entries. I just get the > > messages from the boot pro

Re: [arch-general] systemd 214, journal problem

2014-06-24 Thread Bruno Yemini
When upgrading to systemd 214-2, Pacman gives this message: === :: coredumps are no longer sent to the journal by default. To re-enable: echo >/etc/sysctl.d/50-coredump.conf \ "kernel.core_pattern=|/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e" === I guess this command will re-enable the

Re: [arch-general] systemd 214, journal problem

2014-06-24 Thread Stefan Tatschner
Am Dienstag, den 24.06.2014, 12:29 +0200 schrieb Stefan Tatschner: > Hi, > today I have run pacman -Syu on my arch server. Systemd was updated from > 213 to 214 and now I don't get any new journal entries. I just get the > messages from the boot process and that's all. Downgrading systemd to 213 f

[arch-general] systemd 214, journal problem

2014-06-24 Thread Stefan Tatschner
Hi, today I have run pacman -Syu on my arch server. Systemd was updated from 213 to 214 and now I don't get any new journal entries. I just get the messages from the boot process and that's all. Any ideas? Stefan