Bug 128648

Summary: ntp segfaults at startup if firewall enabled
Product: [Fedora] Fedora Reporter: Christopher Aillon <caillon>
Component: iptablesAssignee: Thomas Woerner <twoerner>
Status: CLOSED DUPLICATE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:04:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Christopher Aillon 2004-07-27 17:56:34 UTC
Description of problem:
ntpd: Opening firewall for input from 66.187.233.4 port 123[  OK  ]
ntpd: Opening firewall for input from clock.redhat.com port
123/etc/init.d/ntpd:  line 169:  9481 Segmentation fault      iptables
-I $FWCHAIN -m udp -p udp -s $ server/32 --sport 123 -d 0/0 --dport
123 -j ACCEPT
                                                           [FAILED]
ntpd: Synchronizing with time server:                      [  OK  ]
Starting ntpd:                                             [  OK  ]


Version-Release number of selected component (if applicable):
# rpm -q ntp
ntp-4.2.0.a.20040616-1


How reproducible:
always


Steps to Reproduce:
1. service ntp start
2. 
3.
  
Actual results: Segfault.

Expected results: Not a segfault :-)

Additional info:

I noticed that system-config-securitylevel had the firewall enabled. 
Disabling the firewall causes ntp to load normally.

Comment 1 Harald Hoyer 2004-07-28 07:19:11 UTC
this is iptables, which segfaults

Comment 2 Thomas Woerner 2004-08-02 14:55:33 UTC
Can you give me the glibc and iptables version by 'rpm -q <rpm>' and
your fireall configuration (/etc/sysconfig/iptables*).

Comment 3 Thomas Woerner 2004-08-02 15:13:44 UTC

*** This bug has been marked as a duplicate of 128322 ***

Comment 4 Red Hat Bugzilla 2006-02-21 19:04:43 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.