Fail to upgrade from DCE 7.2.7 to 7.3.1

[DCIM_Support]

So trying to upgrade a VM DCE.  Initially it had the standard HDD which did not have enough spare space to allow upload of the update file.  An additional HDD was added to avoid this issue.

The first attempt to upload resulted in hang of the DCE client and no change in the operation of DCE.

Second attempt allowed ht upload of the file and seemed start the update process but then bombed out to "Cannot retrieve data from DCE") about 13 seconds into "installing update stage 1".  The only way to get the server back up is to shut it down and restart it from the VM client

The DCE upgrade file was downloaded again and MD5 checked , but each attempt to update had the same result. 

The server was configured with 1GB RAM and  1x CPU, The RAM was increased to 4GB to see if that helped but no change.

The log files show at the end of each attempt...

Restarting software to launch product upgrade Restarting ISXC software RMS Device API Engine shutting down 1 unposted events RMS Device API shutdown complete Received shutdown complete notify shutdown() returning SOCKS Proxy is already stopped! Batch Dispatcher - 3 has been interrupted and will terminate. Batch Dispatcher - 4 is no longer accepting events. Newly pushed events will be dropped. Batch Dispatcher - 5 has been interrupted and will terminate. Batch Dispatcher - 6 is no longer accepting events. Newly pushed events will be dropped.

As far as I can see it is not

• Corrupt update files
• Lack of disk space
• Lack of RAM

I guess it could be lack of CPU but there seems to be no indication of this and the 3 items above are the only things that have stopped me doing updates in the past.

There are a lot of post error which appear to be from netbotz devices with expired certificates, I don't think this would cause the update to fail

Any assistance in what else it could be stopping the update please?

Regards

(CID:133368099)

[DCIM_Support]

Dear Garry Priestland,

Have you tried making a full backup of the DCE-server and deploying it to a cleanly installed DCE-7.2.7? And then upgrade to DCE-7.3.1.

With respect.

(CID:133368437)

[DCIM_Support]

Thanks - that was my next move, but wanted to avoid that effort if I could.

Also, although that may well cure the problem and allow an upgrade I would like to know what has caused the problem.

(CID:133368443)

[DCIM_Support]

From your question:

...Initially it had the standard HDD which did not have enough spare space to allow upload of the update file.  An additional HDD was added to avoid this issue.

After this step please, check the free space on your DCE server's hard drive: http://DCE_address/nbc/compress/repository/status . How much free space?

With respect.

(CID:133368449)

[DCIM_Support]

I can't get onto the server right now - it is not mine and it is remote.  The DCE client was showing about 50.2GB of free disk space 

(CID:133368481)

[DCIM_Support]

I would be grateful if you show the screenshot.

With respect.

(CID:133368491)

[DCIM_Support]

Unfortunately I did not take a screenshot - next chance to get on the server is in a few weeks time...

Was there something in particular you were thinking the issue could be?

(CID:133368495)

[DCIM_Support]

It's best to check everything. Try and report the result, please.

With respect.

(CID:133368498)

[DCIM_Support]

Hi Garry,

Is there any chance we can get the latest capturelogs from the server?
This should give us more information about why the upgrade is failing.

Thanks & Regards

(CID:133368507)

[DCIM_Support]

I do have the capturelogs - where can I upload them?  Prefer not to do it on a public forum.

Thanks

(CID:133368512)

[DCIM_Support]

Hi Garry,

I have sent you a link to a Box folder. Can you upload the capturelogs onto that, and I will have a look at them soon.

Thanks & Regards

(CID:133368818)

[DCIM_Support]

Thanks John. Out of the office at the moment but will upload them soon...

(CID:133369242)

[DCIM_Support]

Hi - the file has now been uploaded

(CID:133369883)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.