This package has been removed from Ubuntu. Closing all related bugs.
** Changed in: firestarter (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/132039
** Branch linked: lp:ubuntu/karmic/firestarter
--
[gutsy] /etc/network/if-up.d/50firestarter exited with return code 2
https://bugs.launchpad.net/bugs/132039
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I think I've been hited by this bug, too. Firestarter do not start
automatically on startup the system, supposedly it should starts when eth0 is
brought up. Also when I try
- sudo ifup eth0
or
- sudo ifdown eth0
I can see the return code 2 message and firestarter does not start.
On the other
Firestarter aren't supported by Ubuntu devs anymore so I doub't that it will be
resolved or gain high priority.
UFW is right now supported and recommended by Ubuntu devs and it have no such
trouble.
--
[gutsy] /etc/network/if-up.d/50firestarter exited with return code 2
There is clearly a massive misconception as to what this bug is and what the
effects are.
If either external or internal interface is down Firestarter does not start or
discontinues operating.
The firewall shuts down leaving the box exposed on the Internet or local lan
depending on the
** Description changed:
Binary package hint: firestarter
-
Architecture: i386
Version: 1.0.3-5ubuntu1
During boot, firestarter daemon is started twice and first of the
invocations fails with message:
invoke-rc.d: initscript firestarter, action restart failed
run-parts:
I have the same issue on my Dell Latitude D620 with Ubuntu Intrepid 8.10
all patches applied.
I modified
/etc/network/if-down.d/50firestarter
/etc/network/if-up.d/50firestarter
(no 'S' before 50 in the filenames on my system)
as suggested by Johan.
The error:
run-parts:
Hi again,
This is what I did- Let Firestarter start under my runlevel 2 to start
on boot, but changed the code in /etc/if-up.d/Sxfirestarter to only
start if there is a runlevel available. Thus, it doesn't start here on
boot up, but it still starts when bringing the network up on a running
In Hardy is ufw already (ufw is a middleman between IPTABLES and user -
like Firestarter, but it's shell command tool) and with gufw (GUI -
Gnome ufw) it's really nice. I've tested it on 8.10 thought, but it
should be gufw for Hardy too (I've seen it with Polish edition 8.04.1 so
search for gufw
Ok, seems that I have the same problem in Ubuntu Hardy Heron.
Firestarter hangs up in the system boot, and when X starts reports me an
error no wireless interface found, so... I have to remove firestarter
to do a normal start.
I have the files S40networking and S65 Firestarter... so firestarter
I agree with John, whenever the network interface name is not available,
Firestarter fails. There is a dialogue under Settings - Auto started
applications in the GUI of XUbuntu. If Firestarter is only enabled
there, it might work, as the networking interfaces should be available
by the time the
I am likewise experiencing this bug on my home PC, which is running
Ubuntu 8.04. Upon reading the post by Sanyam located just above this
post, I decided to insert the 'dirty hack' that Sanyam described into
the 50firestarter file on my home PC.
To open the 50firestarter file for the purpose of
Hi guys..
I am ubuntu newbie ...and I was facing same problem of firestarter exited with
return code 2 during bootup...
I tried a couple of things and realized that it happens only when 50firestarter
is launched for interface 'lo' which is for loopback.
so I did this in the 50firestarter file:
[gutsy] /etc/network/if-up.d/50firestarter exited with return code 2
I still have this annoying problem on all my production gutsy servers,
on one of them I can't get my nx session until a session is opened and
firestarter started (?!)...
Waiting a real fix, what is the best dirty hack to apply
So... the problem is that networking is starting before filesystem is up
and running (and Firestarter with it).
--
[gutsy] /etc/network/if-up.d/50firestarter exited with return code 2
https://bugs.launchpad.net/bugs/132039
You received this bug notification because you are a member of Ubuntu
yes and no
yes:
I have made it impossible for firestarter to get called twice during bootup and
still got the error
no:
that wouldn't explain, why someone gets it also when installing firstarter
(since then all partitions are mounted allready - supposedly)
--
[gutsy]
after various tests i don't think this has anything to do with
/etc/init.d/firestarter being run twice
rather with with partitions not mounted yet.
In my case it is /var where /etc/firestarter/firestarter.sh stores e.g.
/var/lock/firestarter (see e.g. line 180)
what ever i do the first run of
I like dk75s , i would have done it very similar, but i will wait for
the update now.
--
[gutsy] /etc/network/if-up.d/50firestarter exited with return code 2
https://bugs.launchpad.net/bugs/132039
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
OK. So I will write what's happening.
Everybody, look inside yours /etc/rcS.d directory - which priority have
networking and which firestarter? At my system it is respectively 40 and 65.
It means that first /etc/init.d/networking is running and with that
/etc/network/if-up.d/50firestarter which
** Changed in: firestarter (Ubuntu)
Assignee: Lionel Le Folgoc (mrpouit) = (unassigned)
--
[gutsy] /etc/network/if-up.d/50firestarter exited with return code 2
https://bugs.launchpad.net/bugs/132039
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Or, it will be better to edit /etc/network/if-up.d/50firestarter form this:
[code]
#! /bin/sh
/etc/init.d/firestarter restart
[/code]
to this:
[code]
#! /bin/sh
if [ $(/etc/init.d/firestarter status | grep running) ]; then
/etc/init.d/firestarter restart;
else /etc/init.d/firestarter start; fi
I can confirm too...it's interesting that this is assigned to low
priority when a normal user wants to know they have a running firewall
and this might be one of those a and runs from linux for newbs. :
( It doesn't appear this would be too hard to fix either. But heah, it's
free and once the
I have the same problem. One thing to note, if I understand firestarter
correctly, it is simply an interface to view and change the rules that
the ipchains firewall uses - and if it is not running, it does not mean
your firewall is not running - it just means that you cannot use the
firestarter
I confirm this too:
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2
I keep having this error in the official gutsy release.
Firestarter works ok though when I start it.
--
[gutsy] /etc/network/if-up.d/50firestarter exited with return code 2
I can confirm this, though my firewall seems to be working as usual, I
see this message on boot. Using Gutsy beta.
** Changed in: firestarter (Ubuntu)
Status: New = Confirmed
--
[gutsy] /etc/network/if-up.d/50firestarter exited with return code 2
https://bugs.launchpad.net/bugs/132039
I can confirm This. I'm having the same problem. The error message
occurs at boot time and the firewall does not start for me at all. I've
had to shut down my test server because there is no firewall running,
leaving all the open ports are left vulnerable. This error started
occuring after
I still seem to get this problem, though it's happening when I try and
install firestarter. This is on a Tribe 5? gutsy straight install,
updated by update manager to stay current.
sudo apt-get install firestarter
Reading package lists... Done
Building dependency tree
Reading state
** Changed in: firestarter (Debian)
Status: Unknown = Fix Released
--
[gutsy] /etc/network/if-up.d/50firestarter exited with return code 2
https://bugs.launchpad.net/bugs/132039
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Problem is the same on Debian Sid :)
Stopping the Firestarter firewall
Starting the Firestarter firewall... failed!
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2
--
[gutsy] /etc/network/if-up.d/50firestarter exited with return code 2
This is supposed to be fixed in Debian unstable now
** Bug watch added: Debian Bug tracker #438732
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438732
** Also affects: firestarter (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438732
Importance: Unknown
Status:
** Changed in: firestarter (Ubuntu)
Assignee: (unassigned) = Lionel Le Folgoc
Status: Confirmed = In Progress
--
[gutsy] /etc/network/if-up.d/50firestarter exited with return code 2
https://bugs.launchpad.net/bugs/132039
You received this bug notification because you are a member of
firestarter (1.0.3-6ubuntu1) gutsy; urgency=low
* Merge from Debian Unstable, Ubuntu remaining changes: (LP: #132039)
+ Adhere to DebianMaintainerField
+ debian/rules: call [ ! -f Makefile ] || $(MAKE) distclean instead of
-$(MAKE) distclean
+ 11_desktop_file.dpatch:
32 matches
Mail list logo
