Some configuration file errors not logged

Bug #702577 reported by Andrew Hutchings
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Drizzle
Triaged
Medium
Unassigned
7.0
Won't Fix
Medium
Unassigned

Bug Description

Rackspace bug.

In some cases errors caused by problems in configuration files are not logged

Revision history for this message
Monty Taylor (mordred) wrote :

This one, it turns out - is gonna be slightly tricky. I will get to it - but not today.

Revision history for this message
Walter Heck (walterheck) wrote :
Download full text (3.4 KiB)

Here's an example:

root@walterheck-tecra:/etc/drizzle# cat drizzled.cnf
mysql-protocol.port = 3307
root@walterheck-tecra:/etc/drizzle# service drizzle stop
drizzle stop/waiting
root@walterheck-tecra:/etc/drizzle# ps aux | grep drizzled.cnf
root 21749 0.0 0.0 8952 880 pts/8 S+ 00:47 0:00 grep --color=auto drizzled.cnf
root@walterheck-tecra:/etc/drizzle# ps aux | grep drizz
root 21761 0.0 0.0 8952 876 pts/8 S+ 00:47 0:00 grep --color=auto drizz
root@walterheck-tecra:/etc/drizzle# service drizzle start
drizzle start/running, process 21770
root@walterheck-tecra:/etc/drizzle# ps aux | grep drizz
root 21782 0.0 0.0 8952 876 pts/8 S+ 00:47 0:00 grep --color=auto drizz
root@walterheck-tecra:/etc/drizzle# tail /var/log/syslog -n30
Mar 12 00:43:31 walterheck-tecra postfix/smtpd[21236]: connect from walterheck-tecra[127.0.0.1]
Mar 12 00:43:31 walterheck-tecra postfix/smtpd[21236]: disconnect from walterheck-tecra[127.0.0.1]
Mar 12 00:44:31 walterheck-tecra postfix/smtpd[21236]: connect from walterheck-tecra[127.0.0.1]
Mar 12 00:44:31 walterheck-tecra postfix/smtpd[21236]: disconnect from walterheck-tecra[127.0.0.1]
Mar 12 00:45:31 walterheck-tecra postfix/smtpd[21236]: connect from walterheck-tecra[127.0.0.1]
Mar 12 00:45:31 walterheck-tecra postfix/smtpd[21236]: disconnect from walterheck-tecra[127.0.0.1]
Mar 12 00:46:31 walterheck-tecra postfix/smtpd[21236]: connect from walterheck-tecra[127.0.0.1]
Mar 12 00:46:31 walterheck-tecra postfix/smtpd[21236]: disconnect from walterheck-tecra[127.0.0.1]
Mar 12 00:47:11 walterheck-tecra init: drizzle main process (21770) terminated with status 1
Mar 12 00:47:11 walterheck-tecra init: drizzle main process ended, respawning
Mar 12 00:47:11 walterheck-tecra init: drizzle main process (21771) terminated with status 1
Mar 12 00:47:11 walterheck-tecra init: drizzle main process ended, respawning
Mar 12 00:47:11 walterheck-tecra init: drizzle main process (21772) terminated with status 1
Mar 12 00:47:11 walterheck-tecra init: drizzle main process ended, respawning
Mar 12 00:47:11 walterheck-tecra init: drizzle main process (21773) terminated with status 1
Mar 12 00:47:11 walterheck-tecra init: drizzle main process ended, respawning
Mar 12 00:47:12 walterheck-tecra init: drizzle main process (21774) terminated with status 1
Mar 12 00:47:12 walterheck-tecra init: drizzle main process ended, respawning
Mar 12 00:47:12 walterheck-tecra init: drizzle main process (21775) terminated with status 1
Mar 12 00:47:12 walterheck-tecra init: drizzle main process ended, respawning
Mar 12 00:47:12 walterheck-tecra init: drizzle main process (21776) terminated with status 1
Mar 12 00:47:12 walterheck-tecra init: drizzle main process ended, respawning
Mar 12 00:47:12 walterheck-tecra init: drizzle main process (21777) terminated with status 1
Mar 12 00:47:12 walterheck-tecra init: drizzle main process ended, respawning
Mar 12 00:47:12 walterheck-tecra init: drizzle main process (21778) terminated with status 1
Mar 12 00:47:12 walterheck-tecra init: drizzle main process ended, respawning
Mar 12 00:47:12 walterheck-tecra init: drizzle main process (21779) terminated with status 1
Ma...

Read more...

Revision history for this message
Walter Heck (walterheck) wrote :

Just to clarify, I was on Ubuntu Meerkat, and it turns out that doesn't have the mysql-protocol for drizzle installed by default.

Changed in drizzle:
milestone: 2011-03-14 → none
Monty Taylor (mordred)
Changed in drizzle:
assignee: Monty Taylor (mordred) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.