Firestarter system log will not open.

Bug #799279 reported by kureyamu on 2011-06-18
This bug report is a duplicate of:  Bug #776361: Firestarter fails to open system log. Edit Remove
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linux Mint
Confirmed
Undecided
Unassigned
firestarter (Ubuntu)
Undecided
Unassigned

Bug Description

The firewall application Firestarter which was compatible with all previous Linux Mint distributions, does not fully function with Mint 11 Katya. The error message that pops up is:
Firestarter error.
Failed to open system log.
No event information will be available. OK.

Well, really it' s not OK. The system event log is an integral part of the firewall, one of the main reasons why users use it - to have displayed what attacks are in progress and to whom the applications are sending messages. Perhaps the system log was moved by Ubuntu to a new location, and Firestarter can no longer find it?

(1) Linux Mint Katya 11
(2) The error happens upon installation. Requests for help are in the forums. You can reproduce it by installing Firestarter, I guess.
(3) Firestarter works but can no longer display events at the port interface. It is unable to use its log file.
(4) I should expects all events at the firewall interface to be displayed as they happen, so that the user can take action if necessary.
(5) The firewall is broken - it happens all the time. I have re-installed Linux Mint 11 three times, actually because of another bug/problem I am working to solve, and the firewall is broken upon fresh installation.

Good luck with it. I If Firestarter uses /var/log/ufw.log as a shared log, maybe the permissions are wrong or maybe the file has been renamed by Ubuntu. I shall leave it to you to investigate. I haven't got the knowledge. Thank you.

Thanks for your recommendation.

Actually, I already edited that file some months back using the information from from the Keith Taylor post.

The workaround does work but my own impression is that I am receiving less Firestarter Event logs (attempted access to ports blocked) than before.  This is a subjective impression which I cannot confirm and may well be unfounded, but because of this impression, I am still waiting for the debugging team to officially close the question. For all I know, another tweak may yet be required.

Having said that, there seems to be no problems with Firestarter now.

Thanks again, szable.  Cheers.

________________________________
From: szabie <email address hidden>
To: <email address hidden>
Sent: Wednesday, 5 October 2011, 22:38
Subject: [Bug 799279] Re: Firestarter system log will not open.

Hi,

try this:
https://bugs.launchpad.net/ubuntu/+source/firestarter/+bug/776361/comments/2

hope this helps

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/799279

Title:
  Firestarter system log will not open.

Status in The Linux Mint Distribution:
  New
Status in Ubuntu:
  New

Bug description:
  The firewall application Firestarter which was compatible with all previous Linux Mint distributions, does not fully function with Mint 11 Katya.  The error message that pops up is:
  Firestarter error.
  Failed to open system log.
  No event information will be available. OK.

  Well, really it' s not OK. The system event log is an integral part of
  the firewall,  one of the main reasons why users use it - to have
  displayed what attacks are in progress and to whom the applications
  are sending messages.  Perhaps the system log was moved by Ubuntu to a
  new location, and Firestarter can no longer find it?

  (1) Linux Mint Katya 11
  (2)  The error happens upon installation. Requests for help are in the forums.  You can reproduce it by installing Firestarter, I guess.
  (3) Firestarter works but can no longer display events at the port interface.  It is unable to use its log file.
  (4) I should expects all events at the firewall interface to be displayed as they happen, so that the user can take action if necessary.
  (5) The firewall is broken - it happens all the time.  I have re-installed Linux Mint 11 three times, actually because of another bug/problem I am working to solve, and the firewall is broken upon fresh installation.

  Good luck with it.  I If Firestarter uses /var/log/ufw.log as a shared
  log, maybe the permissions are wrong or maybe the file has been
  renamed by Ubuntu.  I shall leave it to you to investigate. I haven't
  got the knowledge.  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/799279/+subscriptions

kureyamu (geecee4u7) wrote :

= ================= =

(1) Bugs 799279

https://bugs.launchpad.net/bugs/799279

Firestarter has a loyal following of Linux users who are grateful to Tomas Junnonen for all the work he has done in creating the best free Linux firewall. However, the Firestarter Events log did not work with Linux Mint 11 Katya so this bug was reported. So far there has been no feedback from the Mint team.

= ================= =

(2) Keith Taylor on launchpad suggests the following workaround.

Open a terminal and type:

sudo gedit /etc/rsyslog.d/50-default.conf

(if your text editor is not Gedit but Midori or Jedit or Foobar, substitute that editor name for “gedit”)

Comment out (delete the hash sign #) in front of the following lines:

#*.=info;*.=notice;*.=warn;\
# auth,authpriv.none;\
# cron,daemon.none;\
# mail,news.none -/var/log/messages

so that you now have:

*.=info;*.=notice;*.=warn;\
 auth,authpriv.none;\
 cron,daemon.none;\
 mail,news.none -/var/log/messages

Save the file, close down the terminal and reboot your system.

= ================= =

(3) This workaround works.

I have used this patch for a couple of months with no problem.

At first I thought that the patch did not catch as many Events in Firestarter.(Events are attempts to enter through various ports, and all these attempts are logged into an Events file). Having had a rethink and checked Firestarter out with other operating systenms, I now believe that the Events are logged as before and I have (as far as known) had no problems with the stealing of data or wicked scripts, so I would say that the patch solves the Firestarter problem. The bug can be treated as Solved and the issue can be Closed.

= ================= =

(4) Whoever is handling this bug report, can you please confirm that the Mint team has in fact corrected the software so that a new download of the Katya would mean that it now works with Firestarter, as it is no good closing a bug report if new users will continue to experience the bug.

 I shall leave the issue in your capable hands but for me the problem has been Solved.

= ================= =

Thank you for your efforts on our behalf. It is always appreciated. Cheers.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

affects: ubuntu → firestarter (Ubuntu)
Changed in firestarter (Ubuntu):
status: New → Confirmed
Changed in firestarter (Ubuntu):
status: New → Confirmed
Changed in linuxmint:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers