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
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 fixed the problem.
Stefan
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 old feature.
Cheers
On Tue, Jun 24, 2014 at 7:39 AM, Stefan Tatschner rumpelsepp@sevenbyte.org 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 process and that's all.
Downgrading systemd to 213 fixed the problem.
Stefan
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-coredump %p %u %g %s %t %e"
===
I guess this command will re-enable the old feature.
He spoke of any messages, not coredumps.
On Tue, Jun 24, 2014 at 2:11 PM, Bjoern Franke bjo@nord-west.org 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-coredump.conf \ "kernel.core_pattern=|/usr/lib/systemd/systemd-coredump %p %u %g %s %t
%e"
===
I guess this command will re-enable the old feature.
He spoke of any messages, not coredumps.
It's true. My mistake, sorry.
cheers
--
xmpp bjo@schafweide.org bjo.nord-west.org | nord-west.org
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 process and that's all.
Downgrading systemd to 213 fixed the problem.
Stefan
What seems to be a similar problem occurred about 3 months ago. It was fixed when systemd was upgraded. See:
https://bbs.archlinux.org/viewtopic.php?id=178450
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 entries. I just get the messages from the boot process and that's all.
Downgrading systemd to 213 fixed the problem.
Stefan
What seems to be a similar problem occurred about 3 months ago. It was fixed when systemd was upgraded. See:
Sorry - replied to wrong thread - please ignore/
AC
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 be working fine here, the output of 'journalctl -b' includes output from dbus, polkitd, NetworkManager, etc.
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...
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 as I had.
gene
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 lts-kernel on my server. Maybe it is not yet fixed in the lts kernel?
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:
:: 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"
OT: But while I get rid of the forced fsck, now the forced fsck happens again.
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 boot process and that's all.
You got this messages when installing it:
:: 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"
We already had this here:
https://mailman.archlinux.org/pipermail/arch-general/2014-June/036672.html
Stefan
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 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:
:: 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"
We already had this here:
https://mailman.archlinux.org/pipermail/arch-general/2014-June/036672.html
I read it a while after my reply.
On Tue, 2014-06-24 at 19:33 +0200, Stefan Tatschner wrote: 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 lts-kernel on my server. Maybe it is not yet fixed in the lts kernel?
JFTR
[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 without editing /etc/sysctl.d/50-coredump.conf for e.g. pppd and the graphics etc..
Currently the only issue on my machine is that at startup fsck is forced again and sure, as always using journalctl is a PITA, but at least it works even with an older kernel, than the linux-lts.
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 without editing /etc/sysctl.d/50-coredump.conf for e.g. pppd and the graphics etc..
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, ...
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.
Stefan
On Wed, Jun 25, 2014 at 9:04 AM, Stefan Tatschner rumpelsepp@sevenbyte.org 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, ...
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 sure how you configured fail2ban, but since it's not working for you and a quick research reveals it does things with logs... This clearly points to some incompatibility between systemd-214 and fail2ban. Did you contact devs of either? They might be able to point something out you have overlooked up to now.
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 sure how you configured fail2ban, but since it's not working for you and a quick research reveals it does things with logs... This clearly points to some incompatibility between systemd-214 and fail2ban. Did you contact devs of either? They might be able to point something out you have overlooked up to now.
This is not correct. Fail2ban works fine here, but with no journal messages (which might be a systemd problem) it does not work as it evaluates the messages from the journal. But that's not actually my problem; it's just a messy side effect. :)
I will try updating to systemd-214 again later this day and I'll let you know what happens.
Stefan
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
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.
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 rebuilt my initramdisk before rebooting; so my udev version was 213...
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 everything works normally). This is on 3.15.1-1-ARCH i686.
I was afraid I'm alone with this problem...
arch-general@lists.archlinux.org