drizzled starts without logging enabled in RHEL5 build

Update:

I've added 'syslog.logging-enable' to /etc/drizzle/drizzled.cnf, and still dont' see any log messages.

I've also cleaned out /var/lib/drizzle to see if it was some issue with me directly running 'sudo drizzled', didn't help.

Sorry if this is obvious, but is syslog set up for Drizzle and vice-versa?
It's been a while since I played with the plugin, but I do recall needing to
do some setup:
http://machinesplusminds.blogspot.com/2010/06/setting-up-drizzle-and-syslog-for-each.html

I assumed that there would be some of that handled automatically (like every other RPM), especially since the drizzle7 rpm went through the trouble of creating a /var/log/drizzle directory. I also though (and could be wrong) that /var/log/messages and /var/log/all typically catches every syslog entry not otherwise handled, and I see nothing in there.

If this is the "expected" way to handle drizzle logging (i.e., set it all up yourself), then I'd argue that it's pretty non-intuitive and there should be some basic pre-configured on most/all linux systems to get some of this basic stuff working, especially if you're assuming you can just use the /etc/init.d/drizzled script that comes in the package.

You'll get no argument from me on these points.

Logging is pluggable, so it is possible to do other things. I'm not sure
syslog is our by-default option more than it is our "it is there and
working" option ; ) As I said, things may have changed since I played
around with things, but those instructions should be able to get you up and
running.

On Mon, Apr 25, 2011 at 12:17 PM, Jay Janssen <email address hidden>wrote:

> I assumed that there would be some of that handled automatically (like
> every other RPM), especially since the drizzle7 rpm went through the
> trouble of creating a /var/log/drizzle directory. I also though (and
> could be wrong) that /var/log/messages and /var/log/all typically
> catches every syslog entry not otherwise handled, and I see nothing in
> there.
>
> If this is the "expected" way to handle drizzle logging (i.e., set it
> all up yourself), then I'd argue that it's pretty non-intuitive and
> there should be some basic pre-configured on most/all linux systems to
> get some of this basic stuff working, especially if you're assuming you
> can just use the /etc/init.d/drizzled script that comes in the package.
>
> --
> You received this bug notification because you are a member of Drizzle-
> developers, which is subscribed to Drizzle.
> https://bugs.launchpad.net/bugs/769008
>
> Title:
> drizzled starts without logging enabled in RHEL5 build
>
> Status in A Lightweight SQL Database for Cloud Infrastructure and Web
> Applications:
> New
>
> Bug description:
> Using drizzle7-server-2011.03.11-1.el5 from
> http://rpm.drizzle.org/7-dev/redhat/5/x86_64/
>
> Starting up with /etc/init.d/drizzled start fails, but there I can't
> find any error in /var/log (or /var/log/drizzle)
>
>
> jayj@/var/log [680]$ /etc/init.d/drizzled start
> Starting Drizzle: [FAILED]
>
> jayj@/var/log [681]$ ls -l drizzle/
> total 0
>
> nothing in system logs in /var/log either.
>

Is there an alternative plugin/place/way for me to see server error messages? I'm happy to use the "preferred" way. Seems like that way might not be using the init.d script?