MIDN still running

[dabble]

I have a CS1000M at 7.5
This morning when I logged into the switch the midnight routine appeared to be running still

rocomm Plus Ready!

TTY 01 SCH MTC OSN 8:56
OVL111 MIDN 137
>
TTY 01 SCH MTC OSN 8:56
OVL111 MIDN 137
>login
USERID? userID
PASS?
.
TTY #01 LOGGED IN USERID 08:56 18/3/2013



I was able to go into LD 20 to do an inquiry, but when I tried to go into LD 95 to change a name, it took me back to the > prompt with an OVL000.

OVL0000
This is the Program identifier which indicates that the user has
already logged into the system.

Severity: Info

I am not logged in anywhere else.

Does anyone know what may be wrong?

Thanks.

 

[janaya]

We had this issue on a 7.5 Multigroup many times. We had an issue with the database corrupting. Avaya eventually wrote some patches for the system to keep it from doing this, but to get out of this, we first tried an INI and if that didn't help we Sysloaded the system. I know this is not what you want to hear on a Monday morning.

You could try to go into the LD using the susp command


.ld 95 susp

but if you keep doing this too many times, the system will INI or Sysload on its own.

You will want to check your CPU's (.ld 135 / stat cpu) to see if RDUN is active). If not then you may be running into the same issues we did. We also had to reload the database too many times to mention just to keep them alive. Eventually they went to a full CS1000E, MG1010 cabinets and all IP and we don't have those issues any longer.

Maybe someone else can shed some light on your issue. I just know ours always happened on weekends where I wanted to go out of town and do something.

John Anaya
Signet6 Network Sciences
ACSS/ACIS - CS1000 Rls 7.5/Call Pilot 5
ACSS/ACIS - SME - IP Office 8.0
APSS/APDS - Avaya UC Services

Public Profile

http://www.linkedin.com/pub/john-anaya/25/1b9/a9b/Edit

 

[RickyPone]

You might be able to go to ld 17 and take 137 out of midnight. Possible could unstick it? Have you looked at the history? Might bee some clues there.

 

[dabble]

Tried going into LD 135 and LD 17 and received this


>ld 135
BACKGROUND SESSION 0 CANNOT BE ABORTED.
>ld 17
>

So, I guess it is an ini!

Thanks.

 

[GHTROUT]

I think is is just HALT at the > prompt

Then you take everything out of DROL

Then you log out and let the empty midnights run.

Log in, and add all the DROLs back.

~~
Gene at GHTROUT.com

 

[KCFLHRC]

You could also try the HALT command right after you log in and see if that will stop it.

 

[dabble]

It didn't like HALT

OVL000
>halt
NO HALT-CRITICAL OVERLAY RUNNING
>

 

[KCFLHRC]

Sounds like an INI or SYSLOAD is your next step.

 

[dabble]

I did an ini this morning and all is good.
I can now access the change loads.
thanks.

 

[janaya]

When you are done, check your CPU's. See if you have an issue that would not allow it to finish the Midnight Routine. This could be an indicator of an issue about to come down.

John Anaya
Signet6 Network Sciences
ACSS/ACIS - CS1000 Rls 7.5/Call Pilot 5
ACSS/ACIS - SME - IP Office 8.0
APSS/APDS - Avaya UC Services

Public Profile

http://www.linkedin.com/pub/john-anaya/25/1b9/a9b/Edit