Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 586546 - app-admin/syslog-ng-3.7.3: Error parsing source, source plugin system not found
Summary: app-admin/syslog-ng-3.7.3: Error parsing source, source plugin system not found
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal major (vote)
Assignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-21 06:19 UTC by Markus Hauschild
Modified: 2017-12-10 04:07 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge-info.txt,4.73 KB, text/plain)
2016-07-01 06:07 UTC, Markus Hauschild
Details
app-admin:syslog-ng-3.7.3:20160701-060350.log (app-admin:syslog-ng-3.7.3:20160701-060350.log,424.05 KB, text/plain)
2016-07-01 06:08 UTC, Markus Hauschild
Details
emerge --info (file_586546.txt,6.00 KB, text/plain)
2017-05-30 15:37 UTC, José Pekkarinen
Details
Fix patch. (0001-Fix-bug-586546-app-admin-syslog-ng-3.7.3-Error-parsi.patch,964 bytes, patch)
2017-05-31 07:10 UTC, José Pekkarinen
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Hauschild 2016-06-21 06:19:04 UTC
syslog-ng with default config cannot be started:
Error parsing source, source plugin system not found in /etc/syslog-ng/syslog-ng.conf at line 25, column 14:

source src { system(); internal(); };
             ^^^^^^

syslog-ng documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
mailing list: https://lists.balabit.hu/mailman/listinfo/syslog-ng

Reproducible: Always

Steps to Reproduce:
1. emerge --depclean syslog-ng
2. emerge syslog-ng
3. service syslog-ng restart
Actual Results:  
 * Caching service dependencies ...                                                                                                               [ ok ]
 * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...
Error parsing source, source plugin system not found in /etc/syslog-ng/syslog-ng.conf at line 25, column 14:

source src { system(); internal(); };
             ^^^^^^

syslog-ng documentation: http://www.balabit.com/support/documentation/?product=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

Expected Results:  
It should have started without errors
Comment 1 Mr. Bones. (RETIRED) gentoo-dev 2016-06-30 14:16:12 UTC
Please attach the output from emerge --info and the build log from building the package.
Comment 2 Markus Hauschild 2016-07-01 06:07:11 UTC
Created attachment 439274 [details]
emerge --info
Comment 3 Markus Hauschild 2016-07-01 06:08:23 UTC
Created attachment 439276 [details]
app-admin:syslog-ng-3.7.3:20160701-060350.log
Comment 4 Markus Hauschild 2016-07-01 06:09:09 UTC
Fresh emerge --info, and build log from another build run have been added. (Problem still persists on this machine)
Comment 5 Le Baron d'Merde 2016-11-20 04:13:12 UTC
Does not this line

source src { system(); internal(); };

should be

OpenRC - source src { unix-stream("/dev/log"); internal(); };
Systemd - source src { systemd-journal(); internal(); };

As per WIKI?

https://wiki.gentoo.org/wiki/Syslog-ng#Files
Comment 6 kfm 2017-02-25 03:43:26 UTC
(In reply to lebarondemerde from comment #5)
> Does not this line
> 
> source src { system(); internal(); };
> 
> should be
> 
> OpenRC - source src { unix-stream("/dev/log"); internal(); };
> Systemd - source src { systemd-journal(); internal(); };
> 
> As per WIKI?
> 
> https://wiki.gentoo.org/wiki/Syslog-ng#Files

No, it should not. People should always use system() unless they know exactly what they are doing. This is how it works:

https://www.balabit.com/documents/syslog-ng-ose-latest-guides/en/syslog-ng-ose-guide-admin/html/configuring-source-system.html

Further, the use of system() results in a sufficiently large receive buffer to avoid the problem described in bug 406623.

Markus, please run syslog-ng -V and confirm that "system-source" is among the list of available modules. Assuming that it is, your error could be caused by failing to include scl.conf. Therefore, please also double-check that syslog-ng.conf is exactly the same as the Gentoo-provided default by running:

# emerge --noconfmem syslog-ng
# dispatch-conf
Comment 7 José Pekkarinen 2017-05-30 15:37:30 UTC
Created attachment 474696 [details]
emerge --info
Comment 8 José Pekkarinen 2017-05-30 15:37:52 UTC
Hi,

I hit the same bug, doing the suggested operations didn't help.

This is the output after the emerge from my laptop:

ant 64bit # dispatch-conf
ant 64bit # service syslog-ng restart
 * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...
Error parsing source, source plugin system not found in /etc/syslog-ng/syslog-ng.conf at line 24, column 14:

source src { system(); internal(); };
             ^^^^^^

syslog-ng documentation: http://www.balabit.com/support/documentation/?product=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

Thanks!

José.
Comment 9 José Pekkarinen 2017-05-31 06:36:07 UTC
Just for completeness, the module is there:

Available-Modules: dbparser,afprog,afstomp,csvparser,afsocket,afuser,affile,confgen,linux-kmsg-format,graphite,basicfuncs,system-source,pseudofile,syslogformat,cryptofuncs,kvformat

Thanks!

José.
Comment 10 José Pekkarinen 2017-05-31 07:10:33 UTC
Created attachment 474728 [details, diff]
Fix patch.
Comment 11 Tomáš Mózes 2017-12-10 04:07:48 UTC
I cannot reproduce on version 3.12.1, if so, please reopen, thank you.