Log is always empty

23 views
Skip to first unread message

Konzertheld

unread,
Jul 2, 2012, 1:59:35 PM7/2/12
to habari...@googlegroups.com
Hi there,

I'm having empty Habari logs for a while now... database (MySQL) seems ok... I've been using Habari 0.8 Stable and now updated to trunk (problem existed before and still exists). Any ideas why Habari could stop logging anything?

In addition, scheduled posts do not work anymore (do not get published).

I had both problems before but can't remember if there was a real fix or if it just disappeared...

Regards
Konzertheld

mikelietz

unread,
Jul 3, 2012, 3:39:03 PM7/3/12
to habari...@googlegroups.com
What is the Minimum Severity set to on your Options page?

Does anything show up in the server error logs? Are you using a database prefix (like 'habari__')?

Konzertheld

unread,
Jul 4, 2012, 11:25:45 AM7/4/12
to habari...@googlegroups.com
Minimum severity is information.

I think I don't have access to the error logs. At least there is nothing named "apache" or "error" in the logs directory, only access and ftp logs.

Yes, my database tables are all named habari__XX.

Colin

unread,
Jul 4, 2012, 11:30:20 AM7/4/12
to habari...@googlegroups.com
Are you getting any entries in your habari__log table when you perform "loggable" actions like creating a new post or moderating a comment?


--
To post to this group, send email to habari...@googlegroups.com
To unsubscribe from this group, send email to habari-users...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/habari-users



--
Colin Seymour
Blog: http://colinseymour.co.uk
Tech Stuff: http://lildude.co.uk
Barefoot Running: http://barefootrunner.co.uk
IRC: lildude #habari

Konzertheld

unread,
Jul 4, 2012, 11:37:54 AM7/4/12
to habari...@googlegroups.com
No, the database log table is empty. Sorry, checked that, should have mentioned it.


Am Mittwoch, 4. Juli 2012 17:30:20 UTC+2 schrieb lildude:
Are you getting any entries in your habari__log table when you perform "loggable" actions like creating a new post or moderating a comment?
On Wed, Jul 4, 2012 at 4:25 PM, Konzertheld <konze...@konzertheld.de> wrote:
Minimum severity is information.

I think I don't have access to the error logs. At least there is nothing named "apache" or "error" in the logs directory, only access and ftp logs.

Yes, my database tables are all named habari__XX.

Am Dienstag, 3. Juli 2012 21:39:03 UTC+2 schrieb mikelietz:
What is the Minimum Severity set to on your Options page?

Does anything show up in the server error logs? Are you using a database prefix (like 'habari__')?

On Monday, July 2, 2012 1:59:35 PM UTC-4, Konzertheld wrote:
Hi there,

I'm having empty Habari logs for a while now... database (MySQL) seems ok... I've been using Habari 0.8 Stable and now updated to trunk (problem existed before and still exists). Any ideas why Habari could stop logging anything?

In addition, scheduled posts do not work anymore (do not get published).

I had both problems before but can't remember if there was a real fix or if it just disappeared...

Regards
Konzertheld

--
To post to this group, send email to habari...@googlegroups.com
To unsubscribe from this group, send email to habari-users-unsubscribe@googlegroups.com

For more options, visit this group at http://groups.google.com/group/habari-users

mikelietz

unread,
Jul 5, 2012, 8:41:58 AM7/5/12
to habari...@googlegroups.com
Have you checked the habari__logs table for corruption or REPAIRed it? http://dev.mysql.com/doc/refman/5.1/en/repair-table.html


On Monday, July 2, 2012 1:59:35 PM UTC-4, Konzertheld wrote:

Konzertheld

unread,
Jul 6, 2012, 7:59:11 PM7/6/12
to habari...@googlegroups.com
Yep, already did that (no effect).

Konzertheld

unread,
Jul 12, 2012, 10:51:51 AM7/12/12
to habari...@googlegroups.com
Thanks to ringmaster I fixed it. There's a bug in Habari where log entries do not get severity levels when using translation. So I either have to disable translation or set log minimum severity to "all" (0). http://drunkenmonkey.org/irc/habari/2012-07-12#T14-49-59

Oh and about the scheduling... no idea what happened but I truncated the cronjob table and a bit later the problem fixed itself.
Reply all
Reply to author
Forward
0 new messages