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.
A 9.40.FC7 server showed "connection rejected - no calls allowed for sqlexec" every few seconds in online.log while onstat reported the instance as On-Line (CKPT REQ) / Blocked:CKPT. Art Kagel explained such messages are normal when apps (or INFORMIXCONNTIME/CONNRETRY retry loops) hammer the server before it is fully online, suggesting delaying app startup until 'onstat -' returns 5. Others pointed out uptime was actually 56 days, so the real issue was likely a long blocking checkpoint, and asked for 'onstat -l' and more context. The poster never replied, so no resolution is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Dear expert i feel confuse when a got error like this below. I would
appreciate for every one can guide me to solve this error,
IBM Informix Dynamic Server Version 9.40.FC7 -- On-Line (CKPT REQ) -- Up 56
days 00:30:02 -- 5237760 KbytesBlocked:CKPT
informix@DBSERVER> onstat -mIBM Informix Dynamic Server Version 9.40.FC7 -- On-Line (CKPT REQ) -- Up 56
days 00:27:33 -- 5237760 KbytesBlocked:CKPT
Message Log File: /export/home/informix/IDS0/log/online.log
13:07:54 (245670) connection rejected - no calls allowed for sqlexec
13:07:59 (245671) connection rejected - no calls allowed for sqlexec
13:08:05 (245672) connection rejected - no calls allowed for sqlexec
13:08:10 (245673) connection rejected - no calls allowed for sqlexec
13:08:15 (245674) connection rejected - no calls allowed for sqlexec
Regards,
TPX
Not an expert but,
you didn't provide enough context. What did you do before you got into this
state?
Your IDS is blocked on checkpoint and probably in fast recovery.
Did you just do physical restore?
More info would be helpful.
Cheers
Davorin
Nothing to worry about. I see that the engine's been online less than half
an hour at the point you ran this. These messages are typical during engine
startup when you have many users or applications that aggressively try to
connect to the engine while it is still coming online and cannot yet accept
connection requests. I note the regularity of the messages - every 5
seconds plus a bit. This can be caused by an app that was coded to retry
its connection to the database server in a loop until it succeeds or one
that is running under the INFORMIXCONNTIME and INFORMIXCONNRETRY environment
variables which can configure the client library to internally retry the
connections every N seconds over the course of M seconds before returning an
error to the application. This is all normal. However, if this is
happening during a system restart and the applications are local, you may
want to move the engine startup earlier in the startup process or delay the
automatic startup of middleware and other persistent applications that
connect to the engine until the engine is online (if you run 'onstat -' the
return code will be '5' when the engine is finally fully online, so you can
test that in a loop in startup scripts).
Art
On Wed, Nov 5, 2008 at 1:12 AM, TAUFIK FUADI <taufik_zf@gratika.co.id>wrote:
> Dear expert i feel confuse when a got error like this below. I would
> appreciate for every one can guide me to solve this error,
>
> IBM Informix Dynamic Server Version 9.40.FC7 -- On-Line (CKPT REQ) -- Up 56
> days 00:30:02 -- 5237760 Kbytes> Blocked:CKPT
>
> informix@DBSERVER> onstat -m
>
> IBM Informix Dynamic Server Version 9.40.FC7 -- On-Line (CKPT REQ) -- Up 56
> days 00:27:33 -- 5237760 Kbytes> Blocked:CKPT
>
> Message Log File: /export/home/informix/IDS0/log/online.log
> 13:07:54 (245670) connection rejected - no calls allowed for sqlexec
> 13:07:59 (245671) connection rejected - no calls allowed for sqlexec
> 13:08:05 (245672) connection rejected - no calls allowed for sqlexec
> 13:08:10 (245673) connection rejected - no calls allowed for sqlexec
> 13:08:15 (245674) connection rejected - no calls allowed for sqlexec
>
> Regards,
>
> TPX
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Art S. Kagel
Oninit (www.oninit.com)
IIUG Board of Directors (art@iiug.org)
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Oninit, the IIUG, nor any other organization
with which I am associated either explicitly or implicitly. Neither do
those opinions reflect those of other individuals affiliated with any entity
with which I am affiliated nor those of the entities themselves.
↪ replying to TAUFIK FUADI
MIKE MAGIE — — source: IIUG Forums & Mailing Lists
I dunno if there is a problem per se - from the info you sent your engine has
been in a checkpoint for 3 minutes (or am I missing something?) - that may be
excessive - but you need to let us know what is happening, i.e. post some
onstats.
Mike
↪ replying to TAUFIK FUADI
MIKE MAGIE — — source: IIUG Forums & Mailing Lists
I dunno if there is a problem per se - from the info you sent your engine has
been in a checkpoint for 3 minutes (or am I missing something?) - that may be
excessive - but you need to let us know what is happening, i.e. post some
onstats for us to look at.
Mike
Hi Art,
are you sure?
That's what I thought at the first glance. But check it again, it says "Up 56
days 00:27:33"!
So, since the original author didn't reply, I guess either the problem is now
solved or they all ran away quickly...:o)
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.