Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Dave reported hundreds of listener-thread error -25571 'Cannot create a user thread' messages that stopped all connections until the engine was restarted. Fernando Nunes asked about the dbssodir/seccfg group file, OS resource limits and GLS, then about NETTYPE; Dave found none applied. Nunes advised capturing onstats and calling support. Unresolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Today we saw hundreds of lines in our message log with the following
error. The database pretty much came to a halt and nobody could
connect or do any work. Only bouncing the engine cleared up this
issue.
17:15:47 listener-thread: err = -25571: oserr = 0: errstr = : Cannotcreate a user thread.
17:15:48 listener-thread: err = -25571: oserr = 0: errstr = : Cannotcreate a user thread.
17:15:49 listener-thread: err = -25571: oserr = 0: errstr = : Cannotcreate a user thread.
17:15:50 listener-thread: err = -25571: oserr = 0: errstr = : Cannotcreate a user thread.
Does anyone have any idea what this might be attributed to or what
would have caused the issue?
Any help would be great,
--David
in4mixdba@gmail.com
↪ replying to Dave
Fernando Nunes — — source: Usenet: comp.databases.informix
Dave wrote:
> Today we saw hundreds of lines in our message log with the following
> error. The database pretty much came to a halt and nobody could
> connect or do any work. Only bouncing the engine cleared up this
> issue.
>
> 17:15:47 listener-thread: err = -25571: oserr = 0: errstr = : Cannot> create a user thread.
>
> 17:15:48 listener-thread: err = -25571: oserr = 0: errstr = : Cannot> create a user thread.
>
> 17:15:49 listener-thread: err = -25571: oserr = 0: errstr = : Cannot> create a user thread.
>
> 17:15:50 listener-thread: err = -25571: oserr = 0: errstr = : Cannot> create a user thread.
>
>
> Does anyone have any idea what this might be attributed to or what
> would have caused the issue?
>
> Any help would be great,
>
> --David
> in4mixdba@gmail.com
>
The only time I remember seeing this error was when I used the
$INFORMIXDIR/dbssodir/seccfg file to configure the group that is allowed to
connect to the instance... Are you using it? If yes, could it be that someone
changed the group users?
The other reasons mentioned in the finderr message for this error are lack of
resources (it should give an OS error or you should have something in
/var/adm/messges or /var/log/messages) and some GLS related stuff...
Do any of these make sense in your system?
Regards
--
Fernando Nunes
Portugal
http://informix-technology.blogspot.com
My email works... but I don't check it frequently...
Fernando,
Thanx for your help. We are not using the $INFORMIXDIR/dbssodir/
seccfg
Also, we did check the message/log files you pointed to and there was
nothing there unusual..
Any other ideas?
--David
in4mixdba@gmail.com
On Nov 13, 6:46 pm, Fernando Nunes <s...@onlinedomus.net> wrote:
> Dave wrote:
> > Today we saw hundreds of lines in our message log with the following
> > error. The database pretty much came to a halt and nobody could
> > connect or do any work. Only bouncing the engine cleared up this
> > issue.
>
> > 17:15:47 listener-thread: err = -25571: oserr = 0: errstr = : Cannot> > create a user thread.
>
> > 17:15:48 listener-thread: err = -25571: oserr = 0: errstr = : Cannot> > create a user thread.
>
> > 17:15:49 listener-thread: err = -25571: oserr = 0: errstr = : Cannot> > create a user thread.
>
> > 17:15:50 listener-thread: err = -25571: oserr = 0: errstr = : Cannot> > create a user thread.
>
> > Does anyone have any idea what this might be attributed to or what
> > would have caused the issue?
>
> > Any help would be great,
>
> > --David
> > in4mix...@gmail.com
>
> The only time I remember seeing this error was when I used the
> $INFORMIXDIR/dbssodir/seccfg file to configure the group that is allowed to
> connect to the instance... Are you using it? If yes, could it be that someone
> changed the group users?
>
> The other reasons mentioned in the finderr message for this error are lack of
> resources (it should give an OS error or you should have something in
> /var/adm/messges or /var/log/messages) and some GLS related stuff...
>
> Do any of these make sense in your system?
>
> Regards
>
> --
> Fernando Nunes
> Portugal
>
> http://informix-technology.blogspot.com
> My email works... but I don't check it frequently...- Hide quoted text -
>
> - Show quoted text -
↪ replying to Dave
Fernando Nunes — — source: Usenet: comp.databases.informix
Dave wrote:
> Fernando,
>
> Thanx for your help. We are not using the $INFORMIXDIR/dbssodir/
> seccfg
>
> Also, we did check the message/log files you pointed to and there was
> nothing there unusual..
>
> Any other ideas?
>
What is your nettype configuration?
I'm running out of ideas...
If this happens again try to grab some onstats and contact tech support...
Regards.
--
Fernando Nunes
Portugal
http://informix-technology.blogspot.com
My email works... but I don't check it frequently...
↪ replying to Dave
John Carlson — — source: Usenet: comp.databases.informix
Dave wrote:
> Fernando,
>
> Thanx for your help. We are not using the $INFORMIXDIR/dbssodir/
> seccfg
>
> Also, we did check the message/log files you pointed to and there was
> nothing there unusual..
>
> Any other ideas?
>
Anything in the OS logs??
JWC
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.