2.10.0BETA Doesn't create new partitions

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install 2.10.0BETA
2. Wait until midnight
3. See that no new logs are being entered into database

What is the expected output? What do you see instead?

New logs are expected to be entered into database, instead there are none

What version of the product are you using? On what operating system?

2.10.0BETA on Ubuntu 8.04

Please provide any additional information below.

I tried to manually enter a log entry using db_insert.pl and got the
following error message

printf "host\tlocal7\terr\terr\ttest\t2009-12-07\t14:00:00\t6409431\t6409431:
: : 6407848: Sep 10 04:11:02.491 UTC :
%%CCM_CALLMANAGER-CALLMANAGER-3-TspError: Error in TSP\n" | ./db_insert.pl 

DBD::mysql::st execute failed: Table has no partition for value 734115 at
./db_insert.pl line 367, <> line 1.
FATAL: Can't execute SQL insert statement (Table has no partition for value
734115)

running this command in mysql to add a partition alleviated the issue, but
it will occur again at midnight.

mysql> ALTER TABLE logs ADD PARTITION (PARTITION p20091210 VALUES LESS THAN
(734116));

Original issue reported on code.google.com by gur...@gmail.com on 9 Dec 2009 at 6:23

[GoogleCodeExporter]

I was able to find the part in install.pl that is supposed to add MYSQL events 
for
adding partitions, and executed just that part and it appears to have added them
successfully, not sure why they did not install originally, or perhaps they 
became
removed somehow (same on 2 separate installs). I will see if they are still 
there
tomorrow and if the event succeeds

Original comment by gur...@gmail.com on 9 Dec 2009 at 7:36

[GoogleCodeExporter]

events are still in the events table, but they did not execute because the event
scheduler defaults to off. I had to enable it by adding event_schedule=on under
[mysqld] in my.cnf
we'll see if it works tomorrow :)

Original comment by gur...@gmail.com on 10 Dec 2009 at 8:00

[GoogleCodeExporter]

Please do not use the 2.10 Beta.
It wasn't meant for public use.

Original comment by cdu...@gmail.com on 23 Dec 2009 at 2:09

• Changed state: WontFix
• Added labels: Type-Other

[GoogleCodeExporter]

I got the "DBD::mysql::st execute failed:...<snip>" errors when installing
logzilla_v3.0Beta16.

I have Edited /etc/mysql/my.cnf, and added this line to the [mysqld] section:

event_schedule=on

After deleting the syslog database, there are now no errors when running the 
logzilla
installation script - particular to the database setup process.

This comes after having to pull in mysql-server-5.1 into Debian Lenny (5.0) from
Backports - it is otherwise not available. Whether that has something to do 
with it
or not, who knows. It would be interesting to see if Ubuntu has the same issue, 
or
whether event_schedule is already set in Ubuntu installs. It's not present in 
Debian
my.cnf configs.

Cheers,
Michael

Original comment by mhutchin...@Manux.co.nz on 12 Apr 2010 at 1:57

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi Michael,
The event scheduler not being on by default is a known issue, please see the 
forum
post here:
http://forum.logzilla.info/index.php/topic,71.0.html

(it's also noted during install in the new version (not released yet).
But thanks :-)

Original comment by cdu...@gmail.com on 12 Apr 2010 at 2:30