Thanks. It ended up that I needed to make the SQL user default to that database, even though I already have the database specified in the config file. No big deal, just annoying that it seems to ignore the database setting. Shawn Cannon IT Professional http://www.shawncannon.com Contact Me <http://www.linkedin.com/pub/shawn-cannon/5/84/81a> LinkedIn<http://www.linkedin.com/pub/shawn-cannon/5/84/81a> <http://www.facebook.com/rolltidega72> Facebook<http://www.facebook.com/rolltidega72> <http://twitter.com/rolltidega> Twitter <http://twitter.com/rolltidega> On Thu, Jan 20, 2011 at 1:35 PM, Matthew Hall <mhall@mhcomputing.net> wrote:
On Thu, Jan 20, 2011 at 12:39:37PM -0500, Shawn Cannon wrote:
I am trying to setup a second syslog-ng server that will be part of a load balanced cluster. When the 2nd server tries to connect to my mssql database, it tries to run the CREATE TABLE commands which fails because the table already exists since the first syslog-ng server already created them. How do I tell the 2nd server not to try the CREATE TABLE stuff so it will start working?
Shawn Cannon
IT Professional
There is a dont-create-tables option in newer syslog-ngs which will fix this one.
dont-create-tables: Enable this flag to prevent syslog-ng OSE from creating non-existing database tables automatically. The syslog-ng OSE application typically has to create tables if you use macros in the table names. Available in syslog-ng OSE version 3.2 and later.
http://www.balabit.com/sites/default/files/documents/syslog-ng-ose-v3.2-guid...
HTH, Matthew.
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html