OpenScape 400 v7: Process dbwrite not found. (2217)

[majimomi]

Hi there,

have a couple of OS4kv7 and this morning on one of them error: Process dbwrite not found. (2217), please see attached screen shot. This error appear when I try to change something with OS Assistant Configuration Manager. Also I cannot access it over ComWin, it gives me: Could not initialize ComWin for host .... (ses attach)
I have also tried over ssh connection to assistant and than running dipas_batch to access amo mml but there is also the error (please see the attach).

This is happening only on one of machines we have. What could be the reason and how to overcome it?

Thank you

 

[adibv]

Hi.

Restart daemon, restart cm processes, and restart Assistant.
Try to stop the cm then stop/start the procm.

OR

group cm_subadm stop / start
Then reset UW7

OR

rm /etc/etaeq/SecM.RMX_Data
/opt/secm/bin/harm init

Hard restart of A1.

And check:

# ps -ef => process -every -full
# ps aux => process shows all users x status:

root 31120 0.0 2.1 21772 16472 ? Ss 2012 0:13 /opt/cm/sad/bin/dbwrite

 

[majimomi]

Do this restarts affect the telephony? Will my users lost telephony service?

 

[adibv]

Restarting of Assistant will not affect basic telephony service, but it will affect connectivity with other applications/servers connected to sys (if is the case): e.g XPR,CTI/UC,OSCC,ACWin,Voice mail etc.

 

[majimomi]

I have just restarted Assistant over Webmin and the situation is the same. Same errors.

 

[donb01]

Is the system Simplex or Duplex?

If it's duplex and you flip to the standby processor you might lose ringing calls and calls in the process of dialing, but "should not" drop calls in progress.... ... should not....

If it's simplex (one processor) and you hard start the system/platform you could lose telephony for up to 5 minutes depending on how many shelves and STMI/NCUI boards you have.

If telephony is up and you are having possible disk errors I might not immediately jump to a hard restart, because there is a possibility the system won't come back up.

You can get into the portal, which is customarily 1 IP less than the assistant (so if Assistant is 1.2.3.4 the portal might be 1.2.3.3) and you have to use https:// - The creds are the same as assistant if you have full admin rights. There are different system status things you can see in there (disk, lan, etc), you could restart assistant from there (or even re-install it if necessary), and if you are still V7R1 all of the system documentation is in there as well (They broke that in V7R2).




Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[adibv]

After doing all steps mentioned above, check also if CM configuration is done from SysM.

 

[majimomi]

There is no dropping calls when I restart Assistant.

This is capture from Platform Portal status:

It looks like there is no disk errors.

 

[majimomi]

Solved. If there is anyone with this problem, here is my fix:

Restarting Assistant multiple times didn't help. So I did this: Went to Platform Portal -> System -> DSCXL Frontpanel. And I hit the Reset buttons on CCA and ADP

According to some docs Ihave it is equivalent to executing

EXEC-REST: UNIT, BP or bpA/B or bpS, soft/hard/reload, EXEC-REST: UNIT, A1, soft/hard/reload

in ComWin. After that I have restarted Assistant once more.

 

[donb01]

So from the sound of it you just rebooted the whole system, which I wouldn't necessarily think is a bad idea after running 11,000+ days - as one of my vendor techs likes to say, "sometimes the system just needs a good enema"

Looks like you only have a simplex system so I would assume it was down maybe 5 minutes - unless pushing that reset button does a soft restart or reload instead of a hard restart.

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA