Logging stops after some time

[ap1821]

Hi. I had a problem like this in 2.2. It seems that after a day of usage, the logging stops, but Zentyal log service seems to be started. After restarting log service, it starts to work, but the period between that time is lost in the logs. It usually happens in somewhere between ~8 o'clock in the morning. Then no more logs are shown in the log section for any module.
Anyone getting this?
I'm using 3.0.25 as a gateway

[ap1821]

Looks like this.

Again ~8:00 today it stopped working. HTTP Proxy log stops, Samba access log stops, only VPN log, Antivirus update log or maybe some other logs seems to work.
After I restart Logs module:


edit: I also noticed that I cannot search trough the logs, only the time period searches work.

[ap1821]

Sorry for lots of bumping up, but this is really important to me, because in production I use logs a lot, especially for samba and squid.
Maybe this output helps:

Code: [Select]

admins@server:/var/log/zentyal$ sudo cat error.log | grep logs | less
Use of uninitialized value $content in pattern match (m//) at /usr/share/zentyal/templates/logs/dbtable.mas line 41.
Use of uninitialized value $tooltip in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in substitution (s///) at /usr/share/zentyal/templates/logs/dbtable.mas line 36.
Use of uninitialized value $content in numeric gt (>) at /usr/share/zentyal/templates/logs/dbtable.mas line 38.
Use of uninitialized value $content in pattern match (m//) at /usr/share/zentyal/templates/logs/dbtable.mas line 41.
Use of uninitialized value $tooltip in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in substitution (s///) at /usr/share/zentyal/templates/logs/dbtable.mas line 36.
Use of uninitialized value $content in numeric gt (>) at /usr/share/zentyal/templates/logs/dbtable.mas line 38.
Use of uninitialized value $content in pattern match (m//) at /usr/share/zentyal/templates/logs/dbtable.mas line 41.
Use of uninitialized value $tooltip in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in substitution (s///) at /usr/share/zentyal/templates/logs/dbtable.mas line 36.
Use of uninitialized value $content in numeric gt (>) at /usr/share/zentyal/templates/logs/dbtable.mas line 38.
Use of uninitialized value $content in pattern match (m//) at /usr/share/zentyal/templates/logs/dbtable.mas line 41.
Use of uninitialized value $tooltip in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in substitution (s///) at /usr/share/zentyal/templates/logs/dbtable.mas line 36.
Use of uninitialized value $content in numeric gt (>) at /usr/share/zentyal/templates/logs/dbtable.mas line 38.
Use of uninitialized value $content in pattern match (m//) at /usr/share/zentyal/templates/logs/dbtable.mas line 41.
Use of uninitialized value $tooltip in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in substitution (s///) at /usr/share/zentyal/templates/logs/dbtable.mas line 36.
Use of uninitialized value $content in numeric gt (>) at /usr/share/zentyal/templates/logs/dbtable.mas line 38.
Use of uninitialized value $content in pattern match (m//) at /usr/share/zentyal/templates/logs/dbtable.mas line 41.
Use of uninitialized value $tooltip in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in substitution (s///) at /usr/share/zentyal/templates/logs/dbtable.mas line 36.
Use of uninitialized value $content in numeric gt (>) at /usr/share/zentyal/templates/logs/dbtable.mas line 38.
Use of uninitialized value $content in pattern match (m//) at /usr/share/zentyal/templates/logs/dbtable.mas line 41.
Use of uninitialized value $tooltip in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in substitution (s///) at /usr/share/zentyal/templates/logs/dbtable.mas line 36.
Use of uninitialized value $content in numeric gt (>) at /usr/share/zentyal/templates/logs/dbtable.mas line 38.
Use of uninitialized value $content in pattern match (m//) at /usr/share/zentyal/templates/logs/dbtable.mas line 41.
Use of uninitialized value $tooltip in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in substitution (s///) at /usr/share/zentyal/templates/logs/dbtable.mas line 36.
Use of uninitialized value $content in numeric gt (>) at /usr/share/zentyal/templates/logs/dbtable.mas line 38.
Use of uninitialized value $content in pattern match (m//) at /usr/share/zentyal/templates/logs/dbtable.mas line 41.
Use of uninitialized value $tooltip in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
Use of uninitialized value $content in join or string at /usr/share/zentyal/templates/logs/dbtable.mas line 49.
(END)
One solution would be to add a cron job to restart zentyal logs at 8:00 AM. And again I'm not quite sure how to properly do that in Zentyal.
I will appreciate all comments. Thanks!

[christian]

Not clear to me:
what is "stopping" ? Squid log or Zentyal log ?
If I understand correctly, Zentyal log and Squid log are 2 different processes isn't it?

[ap1821]

Sorry not to mention. Zentyal log is stopping. When restarting Zentyal log service at 8:01AM, the next day now it seems to log properly, but still I can filter logs only by time period. For example if I'll try to filter HTTP Proxy log by the connected host, url, filter result, it will still show all results instead of filtered results. The same with Samba logs.
Of course if I take a look into MySQL DB of zentyal, then I can select anything I want, but still in the web interface it fails to filter properly, so something is a bit wrong there, altrough anything else in the server seems to work very well.

[christian]

Am I correct thinking that Zentyal log is based on Zentyal DB ?
If yes, then you could perhaps look there in case there is something wrong.

I can't help that much as I don't really use Zentyal logs module: for my own purpose, this is redundant with log at system level. ssh is much faster when you look for something specific.

[ap1821]

Yes, Zentyal log is definitely based on whats going on in Zentyal DB. And these logs are somehow squeezed out of original logs in /var/log.
Okay, the tables squid_traffic_daily, squid_traffic_monthly, squid_traffic_hourly, squid_traffic_weekly contain old info, no matter I purged the logs via Zentyal UI. Is it safe to delete the info in them?
It might be related of bad info in DB, maybe because I managed to get the server time a bit back when resetting server bios (It messed up monitoring, but I managed to get that back working).

Ehh, maybe I should turn the Zentyal logs better off? Would I gain any performance?