John Nagle schreef:
> Axel Schwenke wrote:
>> Hi John,
>>
>> John Nagle <nagle@animats.com> wrote:
>>> Luuk wrote:
>>
>>>>> I have a Python application which seems to lose its connection
>>>>> to the database exactly once per week. It's not an idle time issue;
>>>>> there's a transaction every few seconds, continuously. Is there
>>>>> a 1-week timeout somewhere in MySQL or MySQLdb?
>>
>>> It happens every Sunday morning, when the first new transaction
>>> comes in after 5 AM or so.
>>>
>>> The Linux server and mysqld instance have been up without a crash
>>> for
>>> months. It's not a database engine restart.
>>
>> I guess you checked this in the MySQL error log? No other messages
>> for this time?
>
> Nothing. This is the MySQL daemon log for all of 2008:
>
> 080120 22:34:17 mysqld started
> 080120 22:34:17 InnoDB: Started; log sequence number 1 192541792
> 080120 22:34:17 [Note] /usr/libexec/mysqld: ready for connections.
> Version: '5.0.27' socket: '/var/lib/mysql/mysql.sock' port: 3306
> Source distribution
>
> > You should add log_warnings=2 to my.cnf. This will
>> enable some additional messages in the MySQL error log.
>
> OK, let me see how I can do that without making the Plesk control
> panel system unhappy. This is on a dedicated server, but it's maintained
> in a way that doesn't allow too many changes to the configuration.
>
> Is it "log_warnings" or "log-warnings"?
>
> John Nagle

http://dev.mysql.com/doc/refman/5.0/en/error-log.html

(so its, 'log_warnings' in your config file..)

--
Luuk