naymar27
Enthusiast
Enthusiast

upgrade 6.5 U1 to 6.5 U2

Jump to solution

Hello,

I'm upgrading vcenter with external psc from 6.5 U1 to 6.5 U2.

The first step of PSC upgrade was OK but i had an issue in step 2. The issue was appeared during the pre-upgrade check.

When i looked into the log files I saw that there was an issue with ntp service.

2019-01-06T23:37:26.510Z INFO service_manager Service vmware-stsd: STARTED

2019-01-06T23:37:26.510Z INFO sdk_utils Appliance has version 6.5.0.0

2019-01-06T23:37:26.517Z ERROR transport Command ['/sbin/chkconfig', 'ntp'] exit-code=1, stdout=, stderr=ntp: unknown service

I ran the command /sbin/chkconfig ntp on the psc server. These were the results.

root@psc [ ~ ]# /sbin/chkconfig ntp

ntp: unknown service

root@psc [ ~ ]# /sbin/chkconfig ntpd

Note: Forwarding request to 'systemctl is-enabled ntpd.service'.

enabled

root@psc [ ~ ]#

You will find attached the log files.

Can someone help me solve this?


Thanks

1 Solution

Accepted Solutions
a_p_
Leadership
Leadership

I'm upgrading vcenter with external psc from 6.5 U1 to 6.5 U2.

Shouldn't this be an update/patch rather than an upgrade?

Unless I'm mistaken the update should be performed from the vCSA's VAMI (5380) interface via Internet, or via a downloaded "fp" ISO image.


André

View solution in original post

12 Replies
daphnissov
Immortal
Immortal

This may be an erroneous warning. There is no daemon for ntp with the name "ntp". Does the upgrade let you continue or not? And do you have NTP setup and configured to point to an internal source?

0 Kudos
nivs
VMware Employee
VMware Employee

Any NTP issue on the esxi host or VC ?

0 Kudos
nivs
VMware Employee
VMware Employee

run ntpq -p command on the PSC appliance and VCSA to see how much drift you have.

Are you using DC as NTP ? if so check DC time.

0 Kudos
naymar27
Enthusiast
Enthusiast

Yes, the daemon for ntp is "ntpd". The upgrade does not  continue.

pastedImage_0.png

That is the error that I get.

0 Kudos
naymar27
Enthusiast
Enthusiast

I'm using DC time. when I run ntpq -p on psc and VCSA i see that the ntp server is the DC server.

0 Kudos
naymar27
Enthusiast
Enthusiast

No there's no NTP issue. but I don't know why in the script the daemon for ntp is "ntp" whereas on the PSC and VCSA it is ntpd

0 Kudos
nivs
VMware Employee
VMware Employee

Are you using Local Time or Is it in UTC?

If you have changed it to your local time zone, please change it back to UTC.

Using the VMware vSphere Appliance Management (https://domain.tld:5480) :Navigator > Time > Time Zone

rm /etc/localtime                                                       Remove Current Time symlink

ln -s /usr/share/zoneinfo/UTC /etc/localtime             Set a new Time

Manually Sync:

service ntpd stop

ntpdate Timeserver

service ntpdate start

Time servers are defined in /etc/ntpd.conf

Note : Take Snapshot before you make any changes.

0 Kudos
naymar27
Enthusiast
Enthusiast

I still get the same error.  When i look in the log is still see that it is checking for the daemon for ntp using "ntp".

0 Kudos
naymar27
Enthusiast
Enthusiast

These are the logs bundle.

0 Kudos
a_p_
Leadership
Leadership

I'm upgrading vcenter with external psc from 6.5 U1 to 6.5 U2.

Shouldn't this be an update/patch rather than an upgrade?

Unless I'm mistaken the update should be performed from the vCSA's VAMI (5380) interface via Internet, or via a downloaded "fp" ISO image.


André

View solution in original post

daphnissov
Immortal
Immortal

André has correctly pointed out that you're getting this error because you're going about this wrong. U1 to U2 is an update (not an upgrade). You do not use the appliance installer wizard for this process but either the VAMI (5480) or manually attaching the update bundle (ISO) and running commands at a CLI.

naymar27
Enthusiast
Enthusiast

Yes André, I did an update and it was OK.

Thanks for your help.

0 Kudos