Welcome to our community

Dear Friends,

yesterday, i try to invoked asemgr, but it hangs, all my services on ASE hang even the service which located on the other member i cann't access the mounted point of it. when i check my logs i found these lines in the day before yesterday daemond log file, as folloing:

Apr 9 01:01:12 kuora3 os_mibs[879]: os_mibs WARNING esnmp_lib.c line 1366: o_oid; Null oid or oid->elements, or, oid->nelem == 0

then


Apr 9 01:01:12 kuora3 last message repeated 5 times

Apr 9 17:38:22 kuora3 ASE: local AseMgr Error: can't find director in portmap,
retrying...

then
Apr 9 18:42:47 kuora3 ASE: local AseMgr Error: can't connect to the director, giving up.
Apr 9 18:42:47 kuora3 cnxmibd[354]: cnxmibd **ERROR cnxmib_mthd.c line 942: beginEvent() can't connect
Apr 9 18:43:33 kuora3 cnxmibd[354]: local AseMgr Error: can't find director in
portmap, retrying...
Apr 9 18:43:53 kuora3 cnxmibd[354]: local AseMgr Error: can't find director in
portmap, retrying...

then, ASE shutdown my database properly!

please, what is causing this problem?
and, how can i save myself from this problem later?
because when i rebooted the system, everything return as it is good!!

Best Regards,
Amr

Hi Amr,
I don't think the os_mibs warning is too significant since it precedes the problem by 17 hours, nor the fact that it is cnxmibd that is complaining. The issue is what is it complaining about and that is that it cannot "find the director in portmap".
On your ASE if you do
# rpcinfo -p kuora3 | grep ase
and then
# rpcinfo -p other_member_name | grep ase
you should see that the ase daemons have registered with the portmapper with there being an entry on each member for the aseagent, and asehsm as well as one entry on one member for the director.
When you run the asemgr command it attempts to talk to the asedirector but first must ask the portmapper which port/programs have been registered. If it cannot contact the portmapper then either the portmapper has died or more likely asemgr and the asedirector are running on different members and there is a network problem . Where the network problem is depends on your configuration. As far as ASE is concerned the network problem is with the subnet that ASE uses for inter node communication.

Are you using Production Server, which uses memory channel for inter ASE member comms?
If not you are using ASE and so do you have a dedicated network link between members for ASE heartbeat eg a crossover cable?

Since you say that your services were also hanging I'm inclined to think that you are using the same subnet for both ASE comms and service access.
I think that asemgr -d -C will dump out the full ase database and show the network configuration plus everything else otherwise you'll have to go through several menus to find the network config.


Either way, check the network connections especially on kuora3. netstat -i will give a summary for each interface and
netstat -is -I tu0
say will give more info for interface tu0 say.

Hope this helps, it is 5 years since I have had anything to do with ASE so this is coming from memory.

Regards Tom