Some info about the ompgsql threads:
in tryExec(uchar *pszCmd, instanceData *pData:
modified code:
if(execState != PGRES_COMMAND_OK && execState != PGRES_TUPLES_OK) {
dbgprintf("postgres query execution failed: %s , %s \n",
PQresStatus(PQresultStatus(pgRet)),PQerrorMessage(pData->f_hpgsql));
bHadError = 1;
}
result:
postgres query execution failed: PGRES_FATAL_ERROR , could not receive data
from server: Transport endpoint is not connected
So after the first connection, the connection is closed for an unkown
reason...
Alain
ecze wrote
> Hi,
>
> I open a new thread for ompgsql.
>
> After three days of testing, I finally point that if rsyslogd is forked (
> running background ) , each thread of ompgsql will fail to connect at
> first time.
>
> All connection are opened , closed and reopened....
>
> But this mechanism seems to block rsyslogd... other threads are blocked
> without a clear reason for the moment.
>
> I'm still looking why... Any ideas are welcome....
>
> Alain Degreffe
--
View this message in context:
http://rsyslog-users.1305293.n2.nabble.com/rsyslog-7-4-9-ompgsql-libpq-threads-problem-tp7584204p7584206.html
Sent from the rsyslog-users mailing list archive at Nabble.com.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
