On 5/7/2014 11:41 AM, Brian Burch wrote: > On 07/05/14 18:07, Tom Eastep wrote: >> On 5/7/2014 9:28 AM, Bill Shirley wrote: >>> [0:root@jabba shorewall]$ rpm -q shorewall >>> shorewall-4.5.15-1.fc19.noarch >>> >>> I'm running Fedora 19 on this server and everyone plays nice with >>> kernel-3.12.11-201.fc19.x86_64. However, all versions >>> of 3.13.9 crash during reboot. >>> >>> If I disable Shorewall I can boot the new kernel. But then the kernel >>> dumps when I do a 'shorewall start'. >>> >>> Anyone have any ideas on how to begin to diagnose this? I have the partial >>> console output of 'shorewall trace start' >>> from the 3.13 kernel and the full output of that command from the 3.12 >>> kernel. I would prefer not to post these >>> publicly since they have my public IP addresses in them. >>> >>> Any help is appreciated. >>> >> >> I would submit a bug report against the Fedora Kernel. Include any AI >> you have and follow the Fedora Kernel's suggestions for isolating the >> problem. This is always a hazard when running Fedora -- you don't know >> if a newly-installed kernel will even boot on your system... > > Hi Tom, > > Sorry to butt in and I hope my comment is relevant to this thread. > > My shorewall 4.5.21.3 was working fine with ubuntu 13.10 running the > 3.11 lowlatency kernel. > > Last weekend I upgraded to ubuntu 14.04 with the 3.13 lowlatency kernel. > Every time shorewall started, the system completely froze. > > Since then I've been trying to unpick the symptoms. All I need to do is > "shorewall show compatibilities" and the system dies completely - the > console listing shows most of the capabilities, but the mouse and > keyboard are dead. I can't even ping the system and have to do a hard > power-off. > > Currently, I have shorewall stopped and the system works fine until I > ask shorewall to go near the kernel. > > I have the same symptoms with the 3.13 generic kernel. I also did an > update of shorewall to 4.5.21.9 from the tar.bz's, but nothing seems to > have changed. > > Unfortunately "shorewall dump" freezes the system as well!!!! > > I intended to spend more time on problem determination before I bothered > you, but I decided a quick heads up might save us all some time.
Sounds like Netfilter is badly broken on your system. 'shorewall dump' does nothing but run iptables and iproute2 query commands. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
