Arch Linux

4on6

Member

Registered: 2011-10-05

Posts: 172

[SOLVED] Starting Syslog-NG [FAIL]

After an upgrade yesterday, I have the following error message in the boot logs:

Thu Nov 29 12:19:59 2012: :: Starting Syslog-NG    [BUSY] Error binding socket; addr='AF_UNIX(/run/systemd/journal/syslog)', error='No such file or directory (2)'
Thu Nov 29 12:19:59 2012: Error initializing source driver; source='src', id='src#0'
Thu Nov 29 12:19:59 2012: Error initializing message pipeline;
Thu Nov 29 12:19:59 2012:    [FAIL] 

This causes that my configurations for the console (font, keyboardlayout) are not loaded. When I start X, then everything is fine and all my configuration are as usual.

There is a thread from 2011 with regards to a syslog-ng bug, but this shouldn't be relevant anymore. Have I missed something in this "change to systemd process"? Or isn't the error sitting in front of the computer?

Last edited by 4on6 (2012-12-19 11:33:28)

Leonid.I

Member

From: Aethyr

Registered: 2009-03-22

Posts: 999

Re: [SOLVED] Starting Syslog-NG [FAIL]

After an upgrade yesterday, I have the following error message in the boot logs:

Thu Nov 29 12:19:59 2012: :: Starting Syslog-NG    [BUSY] Error binding socket; addr='AF_UNIX(/run/systemd/journal/syslog)', error='No such file or directory (2)'
Thu Nov 29 12:19:59 2012: Error initializing source driver; source='src', id='src#0'
Thu Nov 29 12:19:59 2012: Error initializing message pipeline;
Thu Nov 29 12:19:59 2012:    [FAIL] 

This causes that my configurations for the console (font, keyboardlayout) are not loaded. When I start X, then everything is fine and all my configuration are as usual.

There is a thread from 2011 with regards to a syslog-ng bug, but this shouldn't be relevant anymore. Have I missed something in this "change to systemd process"? Or isn't the error sitting in front of the computer?

The error is on the screen. Change "/run/systemd/journal/syslog" to "/dev/log" in /etc/syslog-ng/syslog-ng.conf. The former socket location is only available when booring with systemd.  Since systemd is the default now, syslog-ng.conf has been adjusted accordingly.

On another note, assuming syslog-ng worked before, you should have gotten a syslog-ng.conf.pacnew on update... did you blindly moved it into syslog-ng.conf?

---

Arch Linux is more than just GNU/Linux -- it's an adventure
pkill -9 systemd

4on6

Member

Registered: 2011-10-05

Posts: 172

Re: [SOLVED] Starting Syslog-NG [FAIL]

After an upgrade yesterday, I have the following error message in the boot logs:

Thu Nov 29 12:19:59 2012: :: Starting Syslog-NG    [BUSY] Error binding socket; addr='AF_UNIX(/run/systemd/journal/syslog)', error='No such file or directory (2)'
Thu Nov 29 12:19:59 2012: Error initializing source driver; source='src', id='src#0'
Thu Nov 29 12:19:59 2012: Error initializing message pipeline;
Thu Nov 29 12:19:59 2012:    [FAIL] 

The error is on the screen. Change "/run/systemd/journal/syslog" to "/dev/log" in /etc/syslog-ng/syslog-ng.conf. The former socket location is only available when booring with systemd.  Since systemd is the default now, syslog-ng.conf has been adjusted accordingly.

On another note, assuming syslog-ng worked before, you should have gotten a syslog-ng.conf.pacnew on update... did you blindly moved it into syslog-ng.conf?

Thanks for the tip. I started to inform myself a bit about systemd and will probably try to switch soon. However, your tip did not work for me, the system still boots without my configurations. (And I never got a syslog-ng.conf.pacnew on update either.)

root

Member

From: 127.0.0.1

Registered: 2012-04-13

Posts: 297

Re: [SOLVED] Starting Syslog-NG [FAIL]

I don't remember if there was an actual pacnew file as Leonid.I states but there was indeed a notification concerning the change in the syslog-ng.conf file. There are even forum threads concerning this issue.
As far as I can tell from my pacman log the notification was featured when upgrading to the 3.3.6-3 version.

Remember that you have to pay attention to the pacman log as it may include info for additional steps besides the mere system upgrade.

---

\(o_X)/
                        'Cause I wanna be an Archy - An Archy in the UK // Sex Pistols

cfr

Member

From: Cymru

Registered: 2011-11-27

Posts: 7,132

Re: [SOLVED] Starting Syslog-NG [FAIL]

I don't think you'd get a .pacnew file unless you'd made changes to syslog-ng.conf so you probably needed to watch the messages from pacman.

However, your tip did not work for me, the system still boots without my configurations.

I'm not sure what you mean here. Do you mean that even after correcting the path, you get the same FAIL message on boot? If so, post the contents of /etc/syslog-ng/syslog-ng.conf.

---

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

4on6

Member

Registered: 2011-10-05

Posts: 172

Re: [SOLVED] Starting Syslog-NG [FAIL]

I don't think you'd get a .pacnew file unless you'd made changes to syslog-ng.conf so you probably needed to watch the messages from pacman.

However, your tip did not work for me, the system still boots without my configurations.

I'm not sure what you mean here. Do you mean that even after correcting the path, you get the same FAIL message on boot? If so, post the contents of /etc/syslog-ng/syslog-ng.conf.

No, sorry for being imprecise, this FAIL message is gone, now I get another one:

Sun Dec  2 01:10:02 2012: ln: failed to create symbolic link '/dev/cdrom': File exists

which is true, the symlink '/dev/cdrom' exists - shall I delete it?

But the problem I associated with the syslog FAIL message is not gone, that is my system still boots without loading my configurations (keyboard, font etc). Only when I switch to X11, then everything works fine.

I did not make the switch to systemd yet, but the old config is supposed to still work, right?

Gusar

Member

Registered: 2009-08-25

Posts: 3,605

Re: [SOLVED] Starting Syslog-NG [FAIL]

I did not make the switch to systemd yet, but the old config is supposed to still work, right?

Nope. Even if you still use initscripts, you need to use the same config files as systemd (/etc/vconsole.conf and others). Except one thing - DAEMONS. That's still in /etc/rc.conf. To learn how to configure the rest:

man archlinux

You won't be able to use the *ctl commands though, they're for systemd. So you'll need to manually do the stuff that these commands do - for example, manually create the /etc/localtime symlink instead of using timedatectl.

Last edited by Gusar (2012-12-02 20:22:53)