WAE 512 - ver 4.1.5b.7 - nodemgr: The device_mgr service has been disabled.

[Tomasz Mowinski]

Hi

I have restarted the WAE and now I've this message:

The device_mgr service has been disabled.

here is message from CLI:

ASERVER-53#sh alarms

Critical Alarms:
----------------
     Alarm ID             Module/Submodule     Instance
     -------------------- -------------------- --------------------
   1 svcdisabled          nodemgr              device_mgr

Major Alarms:
-------------
None

Minor Alarms:
-------------
None

Is it possible to try manualy enable this service ? (After next restart I have the same message).

If you need any additional logs please let me know.

Thanks you in advance for your help.

James

[Marcin Latosiewicz]

James,

Is the device manageble (CM, GUI?)

It looks quite similar to:

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtb88170

Marcin

[Tomasz Mowinski]

Hi

Thanks Marcin for your answer.

I can manage it via CM but GUI on  this WAE doesn't work.

I did upgrade to 4.1.5c (Version: oe512-4.1.5c.17) but still doesn't work

Critical Alarms:
----------------
     Alarm ID             Module/Submodule     Instance
     -------------------- -------------------- --------------------
   1 svcdisabled          nodemgr              device_mgr

Any other idea ?

Thanks in advance

James

[Marcin Latosiewicz]

James,

Can you open a TAC SR? This is a question of matching an exception thrown to a particular bug - in most cases anyway.

You can check

local1/errorlog/actona/Manager.stdout
potentially it's there. 

But TAC engineer will be more suited to find this (several locations of exception possible) and it will be all in sysreport.

Marcin

[Tomasz Mowinski]

Hi

In the Manager.stdout file regarding my problem I've found only this:

nodemgr] stopping service Manager: Thu Jan 13 09:38:17 UTC 2011
[nodemgr] sending SIG_TERM to pid 7115

Unfortuanatenly our contract with TAC access has expired few weeks ago

It looks that one thing which I can do is reinstall/repair WAE from rescue CD.

PS. Marcin, is is possibille to save and recover whole configuration for a reinstalled WAE ? I've tried to do this in the past but I had problem with adding it to CM with previously used name. CM told me that the name is registered already  (even I've removed the WAE from CM I couldn't add previously used name) and I had to change the name and do again whole configuration.

thank you in advance

James

[Marcin Latosiewicz]

James,

The log you indicated could be related... but we need more detail.

Regarding reimage - the whole config is stored on CM (especially if you're using groups) , so in practice what you can do is to safely remove the device instance from CM (if you don't the identity will clash), and register after reimage. The CM will push config when you register anew.

Not sure if this answers your question.

Marcin

[Tomasz Mowinski]

Hi

Please find attached whole Manager.stdout file.

If you need more information plese let me know.

Regarding reimage - if I remove WAE from CM, reinstall it, configure the same name and then register in CM - whole configuration will be restored ? CM is recognizing the WAE only using device names ?

ps. is some document which descibes this step by step ?

thanks you very mauch Marcin

best

[Marcin Latosiewicz]

James,

I found following exception thrown:

com.actona.services.configuration.MgException: TimePeriod is not time because it doesn't consist of 'time' element
    at com.actona.services.configuration.MBeanConfigAttribute.objectFromXML(MBeanConfigAttribute.java:158)
    at com.actona.services.configuration.MBeanConfigAttribute.(MBeanConfigAttribute.java:52)
    at com.actona.services.configuration.MBeanConfig.getAttributesFromXML(MBeanConfig.java:118)
    at com.actona.services.configuration.MBeanConfig.(MBeanConfig.java:39)
    at com.actona.services.configuration.ApplicationConfig.loadConfiguration(ApplicationConfig.java:182)
    at com.actona.services.configuration.ApplicationConfig.(ApplicationConfig.java:55)
    at com.actona.services.configuration.Configurator.(Configurator.java:47)
    at com.actona.services.Loader.(Loader.java:82)
    at com.actona.services.Server.(Server.java:65)
    at com.actona.services.Server.init(Server.java:170)
    at com.actona.services.Server.main(Server.java:231)
[FATAL] 2011-01-12 14:05:52 UTC - Server: Caught MgException - com.actona.services.configuration.MgException: TimePeriod is not time because it doesn't consist of 'time' element
Nested exception: TimePeriod is not time because it doesn't consist of 'time' element
com.actona.services.configuration.MBeanConfigAttribute.objectFromXML(MBeanConfigAttribute.java:158)
com.actona.services.configuration.MBeanConfigAttribute.(MBeanConfigAttribute.java:52)
com.actona.services.configuration.MBeanConfig.getAttributesFromXML(MBeanConfig.java:118)
com.actona.services.configuration.MBeanConfig.(MBeanConfig.java:39)
com.actona.services.configuration.ApplicationConfig.loadConfiguration(ApplicationConfig.java:182)
com.actona.services.configuration.ApplicationConfig.(ApplicationConfig.java:55)
com.actona.services.configuration.Configurator.(Configurator.java:47)
com.actona.services.Loader.(Loader.java:82)
com.actona.services.Server.(Server.java:65)
com.actona.services.Server.init(Server.java:170)
com.actona.services.Server.main(Server.java:231)

A quick look in our database and I THINK I found the answer for you.

I found a previous case where under rare circumstances an XML would become corrupted and solution was to run a script.

I'm actually not sure if I'm supposed to provide you with the script (there's always quite a few concerns with this), but I'm going to risk it.

However you can only run the script at your own risk and if it goes wrong please reimage the device.

Regarding CM and how devices are recongnized, forgive my inoreance but I believe it was in part mac address (or something else imprinted into device) of device, but can't remember for sure, nor have the time to look for it.

HTH,

Marcin

[Tomasz Mowinski]

Thanks a lot Marcin.

This WAE is in remote Office so before I'll use this script I have to orginize remote access to it and prepare rescue CD just in case.

When I'll do this I let you know about results and rate your answer.

In the meantime I've upgraded few WAE from 4.1.5(b) to 4.1.5(c) and I've found some major alarm. But I'll describe this in new post.

Thanks a lot for your assistance.

Best

James

[Marcin Latosiewicz]

James,

Did you have a chance to check this out?

Marcin

[Tomasz Mowinski]

Hi

I'm starting to do this. I'll keep you updated.

best

Tomek

[Tomasz Mowinski]

Hi

I have run this script and it didn't help

regards

Tomek

[Marcin Latosiewicz]

Tomek,

Sorry for late reply I was out of office for some days.

At this stage I would say it's best to open a TAC case so we can inspect full sysreport.

Marcin

[Tomasz Mowinski]

OK. I'll do this.

Thank you very much for your time

best

Tomek