Обсуждение: Npgsql Exception
Hi all, this is really a NHibernate issue I believe, but I emailed their DL and all I got was crickets.. Lots and lots of crickets.. I get this error every time I start my app. It also appears in my SQL log files. I'm running Postgres 8.3.x. The exception occurs on this line of code: ISession session = holder.CreateSession(typeof(DB.User)); Whatever is throwing the exception is catching it and ignoring it, so it isn't anything the breaks my program; however, sometimes I like to have "Break on all exceptions thrown" enabled and this gets kinda annoying. Is there any way to prevent whatever this configuration parameter is from being set? Thanks!
Sorry, when I had emailed the NHibernate DL the exception was in the subject line. I forgot to copy the subject this time. The exception is: ERROR: 42704: unrecognized configuration parameter "ssl_renegotiation_limit" On Sun, Aug 22, 2010 at 8:54 PM, Mike Christensen <mike@kitchenpc.com> wrote: > Hi all, this is really a NHibernate issue I believe, but I emailed > their DL and all I got was crickets.. Lots and lots of crickets.. > > I get this error every time I start my app. It also appears in my SQL > log files. I'm running Postgres 8.3.x. The exception occurs on this > line of code: > > ISession session = holder.CreateSession(typeof(DB.User)); > > Whatever is throwing the exception is catching it and ignoring it, so > it isn't anything the breaks my program; however, sometimes I like to > have "Break on all exceptions thrown" enabled and this gets kinda > annoying. Is there any way to prevent whatever this configuration > parameter is from being set? Thanks! >
Mike Christensen <mike@kitchenpc.com> writes:
> Sorry, when I had emailed the NHibernate DL the exception was in the
> subject line. I forgot to copy the subject this time. The exception
> is:
> ERROR: 42704: unrecognized configuration parameter
> "ssl_renegotiation_limit"
ssl_renegotiation_limit is a server parameter that was added to all
active PG branches in a security patch last February. Apparently you
have a postgresql.conf file that tries to set that parameter, and have
reverted to a server version that doesn't include it. Best fix is to
update your PG to latest minor release. Alternatively you could take
out the setting but that would imply you don't have the security fix,
and also probably the problem that led you to put in the setting would
come back.
regards, tom lane
Are you using Npgsql with NHibernate? We added an option to send this command when starting a connection. But the setting is inside a try catch error handler, so you aren't supposed to receive it. On my tests I couldn't reproduce the error. The only error we got about that was a user who had a breakpoint set in VS.net to trigger an exception whenever there was an error from server. But this was only while debugging his app, obviously. On Mon, Aug 23, 2010 at 10:49, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Mike Christensen <mike@kitchenpc.com> writes: >> Sorry, when I had emailed the NHibernate DL the exception was in the >> subject line. I forgot to copy the subject this time. The exception >> is: > >> ERROR: 42704: unrecognized configuration parameter >> "ssl_renegotiation_limit" > > ssl_renegotiation_limit is a server parameter that was added to all > active PG branches in a security patch last February. Apparently you > have a postgresql.conf file that tries to set that parameter, and have > reverted to a server version that doesn't include it. Best fix is to > update your PG to latest minor release. Alternatively you could take > out the setting but that would imply you don't have the security fix, > and also probably the problem that led you to put in the setting would > come back. > > regards, tom lane > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general > -- Regards, Francisco Figueiredo Jr. Npgsql Lead Developer http://www.npgsql.org http://fxjr.blogspot.com http://twitter.com/franciscojunior
Whooops, I didn't check the message header... You can ignore my first question :) On Mon, Aug 23, 2010 at 15:56, Francisco Figueiredo Jr. <francisco@npgsql.org> wrote: > Are you using Npgsql with NHibernate? > > We added an option to send this command when starting a connection. > > But the setting is inside a try catch error handler, so you aren't > supposed to receive it. > > On my tests I couldn't reproduce the error. The only error we got > about that was a user who had a breakpoint set in VS.net to trigger an > exception whenever there was an error from server. But this was only > while debugging his app, obviously. > > > On Mon, Aug 23, 2010 at 10:49, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Mike Christensen <mike@kitchenpc.com> writes: >>> Sorry, when I had emailed the NHibernate DL the exception was in the >>> subject line. I forgot to copy the subject this time. The exception >>> is: >> >>> ERROR: 42704: unrecognized configuration parameter >>> "ssl_renegotiation_limit" >> >> ssl_renegotiation_limit is a server parameter that was added to all >> active PG branches in a security patch last February. Apparently you >> have a postgresql.conf file that tries to set that parameter, and have >> reverted to a server version that doesn't include it. Best fix is to >> update your PG to latest minor release. Alternatively you could take >> out the setting but that would imply you don't have the security fix, >> and also probably the problem that led you to put in the setting would >> come back. >> >> regards, tom lane >> >> -- >> Sent via pgsql-general mailing list (pgsql-general@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-general >> > > > > -- > Regards, > > Francisco Figueiredo Jr. > Npgsql Lead Developer > http://www.npgsql.org > http://fxjr.blogspot.com > http://twitter.com/franciscojunior > -- Regards, Francisco Figueiredo Jr. Npgsql Lead Developer http://www.npgsql.org http://fxjr.blogspot.com http://twitter.com/franciscojunior
Sounds good, I think I'll take Tom's advice.. Actually I'm planning on waiting for the 9.0 release to upgrade, so in theory that should just fix everything.. This only happens if I break on all exceptions, which I usually have turned off.. Thanks! Mike On Mon, Aug 23, 2010 at 11:56 AM, Francisco Figueiredo Jr. <francisco@npgsql.org> wrote: > Are you using Npgsql with NHibernate? > > We added an option to send this command when starting a connection. > > But the setting is inside a try catch error handler, so you aren't > supposed to receive it. > > On my tests I couldn't reproduce the error. The only error we got > about that was a user who had a breakpoint set in VS.net to trigger an > exception whenever there was an error from server. But this was only > while debugging his app, obviously. > > > On Mon, Aug 23, 2010 at 10:49, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Mike Christensen <mike@kitchenpc.com> writes: >>> Sorry, when I had emailed the NHibernate DL the exception was in the >>> subject line. I forgot to copy the subject this time. The exception >>> is: >> >>> ERROR: 42704: unrecognized configuration parameter >>> "ssl_renegotiation_limit" >> >> ssl_renegotiation_limit is a server parameter that was added to all >> active PG branches in a security patch last February. Apparently you >> have a postgresql.conf file that tries to set that parameter, and have >> reverted to a server version that doesn't include it. Best fix is to >> update your PG to latest minor release. Alternatively you could take >> out the setting but that would imply you don't have the security fix, >> and also probably the problem that led you to put in the setting would >> come back. >> >> regards, tom lane >> >> -- >> Sent via pgsql-general mailing list (pgsql-general@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-general >> > > > > -- > Regards, > > Francisco Figueiredo Jr. > Npgsql Lead Developer > http://www.npgsql.org > http://fxjr.blogspot.com > http://twitter.com/franciscojunior >
BTW, version is: 'PostgreSQL 8.3.4, compiled by Visual C++ build 1400' I don't have any such setting referenced in any .conf file. So I guess NHibernate tries to set this setting, assuming I have a more recent version of PG. If that's the case, it'll go away when I upgrade.. Mike On Mon, Aug 23, 2010 at 6:49 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Mike Christensen <mike@kitchenpc.com> writes: >> Sorry, when I had emailed the NHibernate DL the exception was in the >> subject line. I forgot to copy the subject this time. The exception >> is: > >> ERROR: 42704: unrecognized configuration parameter >> "ssl_renegotiation_limit" > > ssl_renegotiation_limit is a server parameter that was added to all > active PG branches in a security patch last February. Apparently you > have a postgresql.conf file that tries to set that parameter, and have > reverted to a server version that doesn't include it. Best fix is to > update your PG to latest minor release. Alternatively you could take > out the setting but that would imply you don't have the security fix, > and also probably the problem that led you to put in the setting would > come back. > > regards, tom lane >