MonitorWare Knowledge Base

I have 2 installations of rsyslog (thanks for the excellent piece of software, btw). One on a Debian Sarge box, and the other on a RedHat ES3 box, both with local MySQL DBs. The Debian box works perfectly, but the RedHat box has a problem logging to MySQL. I see the following in my syslogs when rsyslog tries to talk to the DB (rsyslog setup to log to a log and MySQL):

Oct 28 10:29:33 <munged> rsyslogd: db error (1045): Access denied for user: 'root@localhost' (Using password: NO)
Oct 28 10:29:33 <munged> rsyslogd: db error (2006): MySQL server has gone away

This is strange since I have specified the user and pass it should be using to log to MySQL.

My rsyslogd.conf file contains the following line to specify logging to MySQL with the default format:

*.* >127.0.0.1,Syslog,rsysloger,<munged>

I have granted the user rsysloger all privileges on the database Syslog, created by createDB.sql.

I am seeing the same error with 1.0.2 and 1.11.1 on the RH machine. It's running MySQL 4.0.16, rsyslog compiled under gcc 3.4.3.

Rsyslogd -v output:
rsyslogd 1.11.1, compiled with:
FEATURE_DB
FEATURE_LARGEFILE
SYSLOG_INET (Internet/remote support)

Thank you all in advance for any insight this community can offer on this issue.

• Custom written rsyslog.conf?
• Maintenance Contract?
• Installation support?

That's puzzling me, too. One thing that comes to my mind is that the mysql-dev package might be too old. But it looks like I need to talk to my MySQL buddies, that is not the best part of my knowledge It might take a little while...

Rainer

I've been banging my head against it for a week or two, so if you happen to come up with a suggestion anytime, it would be greatly appreciated.

In the mean time, I'll go see if I can't make sure my mysql-devel stuff is at least as new as my version of MySQL. (Should be, but I'll double check, it might still be playing with ES3's old 3.23.58 libraries).

Thanks again.

Sounds strange. Can you please enable debug and forward us the output? To do so, start rsyslog with the options -d -n.

Michael

The debug output is hiding at the link below. The forum would not allow me to feed it such a long text file (Browser timeouts):

http://showcase.netins.net/web/freksho/rsyslog.txt

Really strange. Unfortunately I have no RedHat ES3 box for testing at hand. rsyslog gets the right username and password, but for whatever reason, the MySql API seems to use root account instead of the configured user. I have to admit that I have no idea what causing this.

Michael

I'll do some poking around with the MySQL service, probably try kicking the whole shebang up to 4.1 (all source and all development libraries.) If it takes, I'll let you all know. Thanks for the help.