[psamman]

Hello,

Trying to connect to XFB Gateway 6.9.1 running on HP UX 11i from Windows XP (Windows Client), I get the message : System busy, retry later.

Does any one know what could possibly be keeping the Gateway busy so it won't accept client connections ?
Gateway is up and listening on port number 6390

[Mario128]

Hello,
Are you using Sentinel ?
The message "system busy retry later" can be observed when Sentinel doesn't receive anymore the notification.
The process Sup doesn't answer anymore and client connection are refused.
To solve your problem
- Check the sentinel server status
- Diseable Sentinel from gateway and restart the server to have your gateway up and running while you restart sentinel
- Change the sentinel_congestion_strategy to 2 -> gateway will focus on his own transfers instead of sending notifications
- You can refer the to file tracker.txt into run_time/etc folder
- When you will have Sentinel up and running again enable Sentinel into Gateway and restart your server

Hope that it will help you

[psamman]

Wow ! That's a quick answer !
I do have Sentinel running, but its admin left for today.
I'll try disabling Sentinel Option & restart.

I don't know how to change sentinel_congestion_strategy though. run_time/etc/qtracker says :

"As long as the fill-up ratio of the file tracker.pmq is lower than 50 %,
the XFB product behaves normally. When this ratio reaches 50 %, XFB may
suspend or refuse some activities in order to avoid as possible to
run out of space of the file tracker.pmq"

Which worries me a little. As soon as tracker.pmq is half filled, I can expect trouble

- Rather then enlarging it with pmqctl as suggested, can I purge it ? (I'm on a test system)
- How to determine the fill-up ratio

Thank you for your help.

[psamman]

Disable Sentinel option & restart didn't help.
And "peldconf update -scstr 2" too says: system busy !

[Mario128]

Hi

Try to :

- Stop your gateway

- Check and kill all persistant processes

- Diseable sentinel manually from the dconfsave.ini and pelsetup.def files into run_time/etc and run gatesetup / apply changes

- backup the actual tracker.pmq a new one will be created during the startup

- Run a pelmon check_base -ra command - that will clean up context - and restart

- If despite these steps you still have the error message a deeper analyse is needed and you should open a ticket support.

- if the message doesn't appears anymore configure the congestion strategy and wait for you sentinel admin to check what's going wrong

Raphael

[psamman]

Thank you Raphael.
I'll carry out your instructions first thing off tomorrow as I get back to office, and I'll report back here.
I guess there is no way of finding out the fill-up ratio of tracker.pmq?

[psamman]

Manually changing the configuration worked. No mention of Sentinel in pelsetup.def.
I confirm Sentinel was no longer monitoring my Gateway, so the buffer got filled up (I was not informed, so that should get me a free coffee this morning!).
I didn't turn Sentinel Option back on, so no new tracker.pmq file. I have some urgent tests to do first with XSR 2.1.0, so I'm happy having a working Gateway for now.

Raphael, you're the boss!

[Mario128]

You are welcome !
I am glad to make you win a free coffee from your sentinel co-worker