DCO upgrade to 8.2.7

[DCIM_Support]

Hello

I try upgrade the stand alone DCO server from version 8.2.2 to 8.2.7 .

Unfortunately the  upgrade is failed .

 After a few attempts the upgrade finished successfully if I choose the following option into upgrade sections :

No thirdparty RPMs

Do not download packages from the Internet

What the meaning of those options ?

Can I upgrade production DCO with (or right without )  those  options ?  

(CID:133367745)

[DCIM_Support]

Hello Boris.

Does your DCO server have access to the public internet? The upgrade will try to connect to public repositories which contain updates to the OS and other modules used by DCO.

If you're DCO server does not have access to the public internet the "do not download packages from the internet" option should be checked at which point the OS updates contained in the upgrade iso will be used instead.

The no thirdparty rpms option is more common on redhat installations where customers manage/control the redhat image which is deployed. This option prevents download/upgrade of 3rd party software (like java) where the customer themselves might manage which specific versions are deployed.

Regards

Greg Sterling

(CID:133367946)

[DCIM_Support]

Hello Greg

The customer DCO has been installed on CentOS (not on RedHat) like is part of the build in installationfrom iso file . 

The server not have access to Internet.

Regarding to thirdparty rpms we didn't configure any repositorysand customer don't manage the 3rd party software deploy on this server .

How I can find log file of the upgrade for investagationof the problem?

(CID:133368177)

[DCIM_Support]

Hello Boris. I will reach out to you directly to avoid getting too customer specific in this post.

GregS

(CID:133368183)

[DCIM_Support · Accepted solution]

Updating this post. Received the following update through a direct email response after sending the customer the webmin patch for upgrading to newer DCO releases.

Hello Gregory

Firstly thanks on cooperation .

I provide the result of the upgrade into customer that include installation of the patch , that you sent .

1. Install webmin module patch and check that operation module version is 1.7 .
2. Restart server .
3. Check that dco has been started .
4. Upgrade

Unfortunately after upgrade the dco hasn't started . The error that I see into log file is same that , was when I opened topic in forum .

I think that not belong to operation's module version .
The user jbos doesn't exist at server . The Jboss application is running as dcojboss

I copy part of the log file for to your  interest (unfortunately I can't transfer log file) :

[info] - Remove old lock files for lucene
[err] - STDERRR: chown:invalid user: 'jboss:jboss'
[info] - Cleaning temprary jboss data
[info] - Clening temp file in Jboss instance ;standalone' at : /opt/jboss-as/standalone
[info] - starting 'StructureWare Data Center Operation' . . .
[err] - STDERR : chown: invalid user: 'jboss'
Bla bla bla
[err] - STDERR: su: user jboss does not exit
[info] 11111 Operations::OperationsLib::changeOwner Non-recursively changing owner of /data/heapdump to 888:889

End log file

At this point if user accounts like "jboss" are missing from the DCO server, I suggested Boris download the most recent copy of the customers backup off the dco server, re-install the DCO server using the dco 8.2.7 iso and restore the backup file. 

(CID:134023492)

[DCIM_Support]

Hello Greg,

According with your suggestion to re-intall or create a new DCO server in version 8.2.7 or 8.2.12 and after that restore the backup file, I want to know what happen with all the licenses belong to this server? Is it necessary to migrate the licenses from the original server to the new one? Please confirm. Regards

(CID:137104867)

[DCIM_Support]

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