CPPIV Release 6 Syncing after JOIN

[hippster2001]

Have a hospital with CPPIV release 6. It was in SPLIT mode. I checked both sides and found both were release 6 and both had PEPs loaded. The Active Core was 0. I typed JOIN in LD 135. The Cores joined without any harmful error codes. The system is not redundant and is still SYNCING after 28 hours. Midnights run fine and backups run okay. How do I fix this?

ld 135
CCED000
.stat cpu

cp 0 16 PASS -- ENBL

SYSTEM STATE = SYNCING
DISK STATE = NOT REDUNDANT
HEALTH = 24
VERSION = Jun 2 2009, 17:46:52
Side = 0, DRAM SIZE = 512 MBytes

cp 1 16 PASS -- STDBY

SYSTEM STATE = SYNCING
DISK STATE = NOT REDUNDANT
HEALTH = 24
VERSION = Jun 2 2009, 17:46:52
Side = 1, DRAM SIZE = 512 MBytes

=========================================
Summary of Local System Resource (side 0)
=========================================
File Descriptors
-----------------
alloc 63
free 1985
total 2048

Unprotected Heap (bytes)
------------------------
alloc 50384544
free 195381808
total 245766352

Protected Heap (bytes)
----------------------
alloc 959388
free 3234916
total 4194304

 

[biv343]

When I've had this issue a couple times, I found that disconnecting the HSP cable from the offline side, performing an INI on the offline side, then connecting the HSP after the INI starts on the offline side resolved the issue. It makes no sense to me, but it worked.

 

[RickyPone]

I had the exact trouble. Had to reload software on both cores. I hope pulling the cable works. It is much easier.

 

[hippster2001]

Pulling the cable and plugging it back in during the INI of off line core worked!

Thanks.

 

[curtismo]

I think there is a patch that finally fixed this for us; we have CPPM processors in an HA configuration.

I determined by watching the TTY of the inactive CPPM it would "bomb out" in a disk sync portion of the boot. By manually INI the inactive processor again they would get back into a normal state.

I'll try to find my e-mail correspondence with my vendor to see if I can find the MPLR that fixed this.

 

[curtismo]

See thread798-1617433 for more information on similar issues on my CPPM version 6 system. I just checked my ISSP and I don't have that particular patch in the system any longer, so it may be depreciated by now, but AFAIK I no longer have the problem.