You are not logged in.
Hi, I am posting this in a separate post so the main openrc thread does not get bloated.
So I am using packages from
[openrc-eudev]
SigLevel=PackageOptional
Server=http://downloads.sourceforge.net/project/archopenrc/$repo/$arch
I have these syslog packages installed
openrc-eudev/syslog-ng-nosystemd
openrc-eudev/syslog-ng-openrc
when issuing the "sudo rc-service syslog-ng start" command, I get:
* Caching service dependencies ... [ ok ]
* Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...
[2015-10-01T15:50:21.648841] Error opening plugin module; module='afsocket-notls', error='libwrap.so.0: cannot open shared object file: No such file or directory'
[2015-10-01T15:50:21.649030] Error opening plugin module; module='json-plugin', error='libjson-c.so.2: cannot open shared object file: No such file or directory'
[2015-10-01T15:50:21.650971] Error opening plugin module; module='afsocket', error='libwrap.so.0: cannot open shared object file: No such file or directory'
[2015-10-01T15:50:21.652767] Error opening plugin module; module='afsocket-tls', error='libwrap.so.0: cannot open shared object file: No such file or directory'
[2015-10-01T15:50:21.652837] Error opening plugin module; module='tfgeoip', error='libGeoIP.so.1: cannot open shared object file: No such file or directory'
Error parsing source, source plugin unix-dgram not found in source confgen system at line 4, column 14:
included from /etc/syslog-ng/syslog-ng.conf line 22, column 10source { unix-dgram
^^^^^^^^^^syslog-ng documentation: http://www.balabit.com/support/document … =syslog-ng
mailing list: https://lists.balabit.hu/mailman/listinfo/syslog-ng
* Configuration error. Please fix your configfile (/etc/syslog-ng/syslog-ng.conf) [ !! ]
* ERROR: syslog-ng failed to start
however there is no "source { unix-dgram" text in the config file.
my syslog-ng.conf:
http://pastebin.com/mz65BS5x
Last edited by zwa (2016-03-23 14:40:53)
Offline
that looks like the default archlinux syslog-ng.conf indeed.
source src {
system();
internal();
};
the system() tells syslog-ng to try and determine the system it's running on, but sometimes fails.
When using openrc as init, syslog-ng does indeed need dgram, so that detection has improved.
I can verify that stock syslog-ng does include the unix-dgram plugin AND runs on my system that boots with openrc (apg) , but has systemd installed .
This is in my syslog-ng.conf file :
source src {
unix-dgram("/dev/log");
internal();
file("/proc/kmsg");
};
If you use that and it still fails, i'd say you have found a bug in eudev/syslog-ng-nosystemd package.
You could try to build syslog-ng-nosystemd from AUR to verify if the problem is with the eudev repo OR in the package.
Last edited by Lone_Wolf (2015-10-01 23:08:10)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
I installed syslog-ng from extra and it started successully and I can confirm it's running. I modified syslog-ng.conf according to your file. I do not have systemd. There are numerous log files in /var/log, does this mean syslog is running fine? Should I make any other modification?
If syslog-ng is working as intended then maybe syslog-ng-nosystemd package is redundant.
Thanks for the input.
Offline
check /var/log/syslog.log , it should show any errors encountered when starting syslog-ng .
Other configuration is optional, but not needed.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
on the /etc/syslog-ng/syslog-ng.conf file, on the header, do you have
@version: 3.6
@include "scl.conf"
i had that error previously and i believe adding the @include solved it. you can search the forums or the web for that error:
Error opening plugin module; module='afsocket-notls', error='libwrap.so.0: cannot open shared object file: No such file or directory'
"I know what you're thinking, 'cause right now I'm thinking the same thing. Actually, I've been thinking it ever since I got here:
Why oh why didn't I take the BLUE pill?"
Offline
For some reason I had to deal with this again. The solution was to install tcp_wrappers. Just for you to know.
Offline
How did you install tcp_wrappers? They are no longer in the repos.
Offline
How did you install tcp_wrappers? They are no longer in the repos.
Offline