Summary: | app-admin/syslog-ng-3.2.4: init script fails to start with ethernet bonding | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Remco Overdijk <remco> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mr_bones_ |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Remco Overdijk
2011-09-17 12:05:10 UTC
Doesn't sound like a syslog-ng problem so much as the service getting started too soon. Agree, syslog-ng as a program works fine, but being started too soon causes the error. After some more research I actually found out that syslog-ng being pulled early is due to the fact that ip6tables is in the default runlevel. (Which would be the issue described in https://bugs.gentoo.org/show_bug.cgi?id=228973 instead of a separate bug). The fact remains however that this configuration used to work without ethernet bonding, but fails after enabling. Could it be filed under 'dumb luck' that the original configuration worked, looking at 228973? In the meantime I have removed ip6tables from the runlevel as shorewall is starting to provide firewall, which also sets ip6tables state during init. As shorewall doesn't need the logger, syslog-ng now starts after net, which eliminates the problem. try it with syslog-ng-3.4.1 please use syslog-ng 3.4.x |