Author Topic: Firewall log says "There are no logs for this domain". No data is being logged  (Read 4067 times)

cyberstudio

  • Zen Monk
  • **
  • Posts: 61
  • Karma: +1/-0
    • View Profile
Right now, im in "Maintenance -> Logs -> Firewall -> Full Report

But, there's nothing logged, from any date to any date... nothing. And on the botton it says "There are no logs for this domain "

Other modules are logging data just fine.

A forum search didn't show anything related.

bendersky

  • Zen Apprentice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
I have the same issue. Zentyal  not produce reports for firewall. And I don't see any error in zentyal log file.
Is any way troubleshoot the issue ?

I have installed last version of zentyal.

c4rdinal

  • Zen Samurai
  • ****
  • Posts: 341
  • Karma: +4/-0
    • View Profile
You have to Enable Firewall Logs before getting anything.

Go to Maintenance > Logs > Configure Logs Tab > Firewall (Enable)

HTH

bendersky

  • Zen Apprentice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
This is the point that logs for firewall enabled and when trying the Full Report it give the message which I attached in screen shot.

andrew_seacap

  • Zen Apprentice
  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
I have exactly the same problem, only the message at the bottom is different. See screenshot.

I have just tested a brand new installation of Zentyal 3 in a virtual machine and the same problem does not occur there. I can see the Firewall and Proxy logs etc.

What can we do to fix the issue in existing installations? I don't want to have to reinstall Zentyal just to fix a bug like this.

Regards

andrew_seacap

  • Zen Apprentice
  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
Aha, looking in the syslog I see lots of the following:

Code: [Select]
Sep 20 14:49:13 zentyal kernel: [171376.751775] init: ebox.loggerd main process (52828) terminated with status 9
Sep 20 14:49:13 zentyal kernel: [171376.751795] init: ebox.loggerd main process ended, respawning
Sep 20 14:49:25 zentyal kernel: [171389.199573] init: ebox.loggerd main process (52846) terminated with status 9
Sep 20 14:49:25 zentyal kernel: [171389.199593] init: ebox.loggerd main process ended, respawning
Sep 20 14:49:38 zentyal kernel: [171401.677225] init: ebox.loggerd main process (52954) terminated with status 9
Sep 20 14:49:38 zentyal kernel: [171401.677246] init: ebox.loggerd main process ended, respawning
Sep 20 14:49:50 zentyal kernel: [171414.103164] init: ebox.loggerd main process (52987) terminated with status 9
Sep 20 14:49:50 zentyal kernel: [171414.103189] init: ebox.loggerd main process ended, respawning
Sep 20 14:50:03 zentyal kernel: [171426.587614] init: ebox.loggerd main process (53008) terminated with status 9
Sep 20 14:50:03 zentyal kernel: [171426.587637] init: ebox.loggerd main process ended, respawning
Sep 20 14:50:15 zentyal kernel: [171439.099930] init: ebox.loggerd main process (53118) terminated with status 9
Sep 20 14:50:15 zentyal kernel: [171439.099958] init: ebox.loggerd main process ended, respawning
Sep 20 14:50:28 zentyal kernel: [171451.576796] init: ebox.loggerd main process (53372) terminated with status 9
Sep 20 14:50:28 zentyal kernel: [171451.576825] init: ebox.loggerd main process ended, respawning
Sep 20 14:50:40 zentyal kernel: [171464.030033] init: ebox.loggerd main process (53454) terminated with status 9
Sep 20 14:50:40 zentyal kernel: [171464.030054] init: ebox.loggerd main process ended, respawning
Sep 20 14:50:53 zentyal kernel: [171476.522623] init: ebox.loggerd main process (53499) terminated with status 9
Sep 20 14:50:53 zentyal kernel: [171476.522643] init: ebox.loggerd main process ended, respawning
Sep 20 14:51:05 zentyal kernel: [171488.980299] init: ebox.loggerd main process (53516) terminated with status 9
Sep 20 14:51:05 zentyal kernel: [171488.980321] init: ebox.loggerd main process ended, respawning
Sep 20 14:51:18 zentyal kernel: [171501.407468] init: ebox.loggerd main process (53597) terminated with status 9
Sep 20 14:51:18 zentyal kernel: [171501.407489] init: ebox.loggerd main process ended, respawning
Sep 20 14:51:30 zentyal kernel: [171513.916003] init: ebox.loggerd main process (53616) terminated with status 9
Sep 20 14:51:30 zentyal kernel: [171513.916024] init: ebox.loggerd main process ended, respawning
Sep 20 14:51:43 zentyal kernel: [171526.343189] init: ebox.loggerd main process (53702) terminated with status 9
Sep 20 14:51:43 zentyal kernel: [171526.343210] init: ebox.loggerd main process ended, respawning
Sep 20 14:51:55 zentyal kernel: [171538.805120] init: ebox.loggerd main process (53734) terminated with status 9
Sep 20 14:51:55 zentyal kernel: [171538.805144] init: ebox.loggerd main process ended, respawning
Sep 20 14:52:08 zentyal kernel: [171551.268769] init: ebox.loggerd main process (53758) terminated with status 9
Sep 20 14:52:08 zentyal kernel: [171551.268792] init: ebox.loggerd main process ended, respawning
Sep 20 14:52:20 zentyal kernel: [171563.730357] init: ebox.loggerd main process (53841) terminated with status 9
Sep 20 14:52:20 zentyal kernel: [171563.730378] init: ebox.loggerd main process ended, respawning
Sep 20 14:52:33 zentyal kernel: [171576.327033] init: ebox.loggerd main process (53900) terminated with status 9
Sep 20 14:52:33 zentyal kernel: [171576.327052] init: ebox.loggerd main process ended, respawning

Any clues as to what 'status 9' means?

andrew_seacap

  • Zen Apprentice
  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
Hmm,

So I enabled the query log in MySQL, and I can see the queries generating the inserts to the squid_access table, but there are none for for the firewall table. What could cause this? The last entry in the firewall table has the timestamp '2012-09-18 23:58:16'. Was there some update this week that could have broken something?

andrew_seacap

  • Zen Apprentice
  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
Interesting, I just rebooted after upgrading to Zentyal 3 and now I have firewall logs...

Oh well, looks like the stable version works!


Sam Graf

  • Guest
I'd be interested to know if the logs stay visible. I've been testing 3.0 on hardware and the logs seem to come and go. I'm watching only DHCP and events for my testing purposes, and I haven't actually tried to see what's going on, but I am keeping on eye on how the logs behave.

andrew_seacap

  • Zen Apprentice
  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
Yes, you're right. I checked this morning and I have no logs from today. They stopped yesterday at 23:59:07. Seems like something is happening around midnight that is interfering with the logger daemon. I checked the syslog and there is no mention of loggerd around that time. I also checked the process and it is still running, having been started some time yesterday.