[Sqlgrey-users] Re: bug in SQLGrey 1.4.x?

[Lionel B. <lio...@bo...>]

Paolo Andretta wrote:

> On Wed, 8 Jun 2005, Lionel Bouton wrote:
>
>>> Thanks for your work.
>>> I am using SQLGrey in a Trustix box (attached rpm -qi report)
>>>
>>> Previous 1.4.x version have problems (in my box) when DB (SQL Lite in
>>> /var/lib/sqlgrey), became about 16MB size.
>>> After upgrade to 1.4.8 I have problems also with smallest DB.
>>> I solve restarting the server and if still having problem, removing
>>> the DB that was recreated on next start.
>>> I have similar problem to 2 different box (but same linux
>>> distro/conf); so I can't understand if it is a sqlgrey's problem or my
>>> perl/conf problem.
>>>
>>> This is what I think is relevant in my log:
>>>
>>> Jun  8 10:56:14 mx7 sqlgrey: fatal: Modification of a read-only value
>>> attempted at
>>> /usr/lib/perl5/5.8.5/i586-linux-thread-multi/Sys/Syslog.pm line 312.
>>
>
>> You may have several problems here. The fact that you get problems when
>> the size of the database grows probably means there is a problem with
>> SQLite or its Perl DBD driver.
>> You didn't tell what problems you had exactly so I don't have any idea
>> of what is happening.
>
>
> Thanks for replay.
> The daemon dead. So mail are refused and users ... ;-)
>

I assume the daemon dies at the time you get the Syslog.pm error. I'm
betting on a pure Perl problem. Which version of Net::Server::Multiplex
do you have ?

>
>> The Syslog.pm errors are puzzling. Did you have them with previous 1.4.x
>> versions or only with 1.4.8?
>
>
> Also with the previous 1.4.x. But very limited compared with current
> problems.
>
>> What was sqlgrey doing at the time (you can use a higher log level
>> and check the postfix logs of the same period)?
>
>
> I have Verbose = 1. Can increase to 2/3/... or is a on/off parameter?
> No more info from postfix.


You can comment "verbose = 1" and uncomment "debug" in sqlgrey.conf.

>
>
> 1.5.x transition can be an option for a production server?


With SQLite, I'm not sure (the point I'm worrying about is the new
asynchronous cleanup, I've made it run a few times on SQLite but not on
an extended period).
1.5.x is well tested with MySQL and PostgreSQL. Unless a new function we
are discussing on the mailing-list is proven useful to me shortly, I'm
planning to release a 1.6.0 stable version based on 1.5.9.

> I can consider using MySQL with 1.4.x or 1.5.x.
>
Then 1.5.9 with MySQL should be fine. If you have Syslog.pm errors
and/or crashes in this configuration, then it's most probably a Perl
problem as many users run MySQL with 1.5.x without trouble.

Lionel.