Firestarter fails at networking restart

Bug #228995 reported by Alejandro Bokser
2
Affects Status Importance Assigned to Milestone
firestarter (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi:

I've installed Kubuntu 8.04

Please look at this:

~$ sudo /etc/init.d/networking restart

* Reconfiguring network interfaces...
 * Stopping the Firestarter firewall...
   ...done.
 * Starting the Firestarter firewall...
   ...fail! <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<Here
run-parts: /etc/network/if-down.d/50firestarter exited with return code 2
There is already a pid file /var/run/dhclient.eth0.pid with pid 4260
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:10:b5:c1:d7:dc
Sending on LPF/eth0/00:10:b5:c1:d7:dc
Sending on Socket/fallback
DHCPRELEASE on eth0 to 172.20.2.102 port 67
 * Stopping the Firestarter firewall...
   ...done.
 * Starting the Firestarter firewall...
   ...fail! <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<Here
run-parts: /etc/network/if-down.d/50firestarter exited with return code 2
There is already a pid file /var/run/dhclient.eth0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:10:b5:c1:d7:dc
Sending on LPF/eth0/00:10:b5:c1:d7:dc
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 201.231.228.237 from 201.241.226.1
DHCPREQUEST of 201.231.228.237 on eth0 to 255.255.255.255 port 67
DHCPACK of 201.231.228.237 from 201.241.226.1
bound to 201.231.228.237 -- renewal in 13923 seconds.
 * Stopping the Firestarter firewall...
   ...done.
 * Starting the Firestarter firewall...
   ...fail! <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<Here
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2
 * Stopping the Firestarter firewall...
   ...done.
 * Starting the Firestarter firewall...
   ...fail! <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<and Here
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2
                                                                         [ OK ]

Firestarter created one entry in if-up.d and other in if-down.d both nemed 50firestarter, you can see them following:

~$ cat /etc/network/if-up.d/50firestarter
#! /bin/sh

/etc/init.d/firestarter restart

~$ cat /etc/network/if-down.d/50firestarter
#! /bin/sh

/etc/init.d/firestarter restart

I think in the case of if-down.d /etc/init.d/firestarter stop would suffice being the nework stopped.

In the case of if-up.d it's OK, but I don know why it fails, because when I restart Firestarter manually or by means of GUI it works OK.

That's the proof:

 ~$ sudo /etc/init.d/firestarter restart
* Stopping the Firestarter firewall... [ OK ]
 * Starting the Firestarter firewall... [ OK ]

Thanks

Revision history for this message
Alejandro Bokser (abokser) wrote :

It's seems to be the same that
Bug #132039 in firestarter (Ubuntu)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.