Bug 11103 - shorewall start fails - no LOG target in kernel
Summary: shorewall start fails - no LOG target in kernel
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 10947
Blocks:
  Show dependency tree / graph
 
Reported: 2013-08-28 20:45 CEST by Frank Griffin
Modified: 2019-02-19 22:55 CET (History)
2 users (show)

See Also:
Source RPM: kernel
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Frank Griffin 2013-08-28 20:45:47 CEST 
The shorewall service in current cauldron fails to start throwing the error:

ERROR: Log level INFO requires LOG Target in your kernel and iptables

There are several reports of this error on the net, e. g. http://sourceforge.net/mailarchive/forum.php?thread_name=4FBCEE09.2060704%40lncsa.com&forum_name=shorewall-users and http://forums.gentoo.org/viewtopic-t-948400-start-0.html , our kernel config seems to have all the bases covered.

In any case, shorewall seems to think something's missing

Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-08-28 21:17:21 CEST

Depends on: (none) => 10947
Assignee: bugsquad => tmb

Comment 1 Stéphane Pontier 2014-01-02 07:48:32 CET 
I dont know if it's the same problem, but I got this error when I start my computer. But if I restart the shorewall service by hand with "sudo systemctl restart shorewall", it works fine.

CC: (none) => stephane.pontier

Comment 2 Nic Baxter 2015-12-24 03:25:40 CET 
Almost 2 years since last comment. Resolution?

CC: (none) => nic

Comment 3 Marja Van Waes 2016-08-26 11:43:15 CEST 
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.

Assignee: tmb => kernel

Comment 4 Frank Griffin 2019-02-19 22:55:55 CET 
Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.