ourdelta-developers team mailing list archive

[Arjen Lentz <arjen@xxxxxxxxxxxxxxxx>]

Hi

On 18/12/2008, at 3:00 PM, Gena01 wrote:
> It took me a while to narrow down why I didn't see any logs or  
> activity
> in the logs after upgrading to the OurDelta MySQL build. I didn't have
> log_error set and the default wasn't working.
>
> Once I set log_error = /var/log/mysql.log then I started seeing  
> messages
> showing up when restarting mysqld.
>
> I did check both the /var/log and the mysql data directory.


Did you check syslog? Depending on the syslog settings of your distro,  
this can be /var/log/messages or /var/log/syslog or something else.


Cheers,
Arjen.
-- 
Arjen Lentz, Director @ Open Query (http://openquery.com.au)
MySQL Training from $475/day, DBA/Support from $249/month

My blog is at http://arjen-lentz.livejournal.com
OurDelta: free enhanced builds for MySQL @ http://ourdelta.org

-- 
No log file created when log_error is not set
https://bugs.launchpad.net/bugs/309250
You received this bug notification because you are a member of OurDelta-
developers, which is the registrant for OurDelta.

Status in OurDelta - Builds for MySQL: New

Bug description:
It took me a while to narrow down why I didn't see any logs or activity in the logs after upgrading to the OurDelta MySQL build. I didn't have log_error set and the default wasn't working.

Once I set log_error = /var/log/mysql.log then I started seeing messages showing up when restarting mysqld.

I did check both the /var/log and the mysql data directory.