[Bug 107] New: when trying to log to postgres database if port is not specified it gets defaulted to 0
https://bugzilla.balabit.com/show_bug.cgi?id=107 Summary: when trying to log to postgres database if port is not specified it gets defaulted to 0 Product: syslog-ng Version: 3.2.x Platform: PC OS/Version: Linux Status: NEW Severity: minor Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: jhnsmth64@gmail.com Type of the Report: bug Estimated Hours: 0.0 syslog-ng.conf ... destination d_pgsql { sql(type(pgsql) host("localhost") username("user") password("pass") ... }; ... If destination stays defined like above, without port specified explicitly, syslog sends log messages to port 0 instead defaulting port to the Postgres port (5432). Destination settings below works: ... destination d_pgsql { sql(type(pgsql) host("localhost") port(5432) username("user") password("pass") ... }; ... -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
On Thu, Jan 06, 2011 at 01:14:49AM +0100, bugzilla@bugzilla.balabit.com wrote:
https://bugzilla.balabit.com/show_bug.cgi?id=107
Summary: when trying to log to postgres database if port is not specified it gets defaulted to 0 ReportedBy: jhnsmth64@gmail.com
Thanks for filing this one. It will help improve the product. Matthew.
https://bugzilla.balabit.com/show_bug.cgi?id=107 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |algernon@balabit.hu --- Comment #1 from Gergely Nagy <algernon@balabit.hu> 2011-01-06 19:26:05 --- I tried a postgres destination without explicitly specifying the port, and it just worked. On localhost, it just worked, when I specified a remote host (which had no postgres listening), it figured out the correct port, and tried to connect there. I'd assume the problem lies within libdbi, as when no port is specified, syslog-ng sets the port option on the DBI object to 0. My version of DBI (Debian Squeeze) treats the zero port as "use the default" (verified, just had a look at the libdbi-drivers source). Judging by the libdbi-drivers CVS tree, every other version of libdbi should behave in a similar manner. Why it still tries to connect to port 0 though, is beyond me, but the ball's in libdbi's court, in my opinion. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=107 --- Comment #2 from Balazs Scheidler <bazsi@balabit.hu> 2011-01-11 17:41:01 --- hmm can you tell us which syslog-ng/libdbi versions you were using? that might help somewhat. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=107 Balazs Scheidler <bazsi@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution| |INVALID Status|NEW |RESOLVED --- Comment #3 from Balazs Scheidler <bazsi@balabit.hu> 2011-10-23 09:18:46 --- in case if this exists, it is probably a libdbi-drivers issue. closing it here. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (2)
-
bugzilla＠bugzilla.balabit.com
-
Matthew Hall