Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Here we go again

swsnyderswsnyder Member
edited March 2013 in General

The system time on node Wolve is inaccurate by about 4 hours, and that inaccuracy is inherited by all the OpenVZ containers being hosted.

>

Please correct the system time on node Wolve.

>

Thanks.

>


>

$ ntpdate -q 0.us.pool.ntp.org
server 50.28.8.224, stratum 3, offset 14453.030644, delay 0.05405
server 66.162.15.65, stratum 2, offset 14453.022481, delay 0.07492
server 173.230.145.53, stratum 3, offset 14453.026014, delay 0.10904
server 64.62.190.177, stratum 3, offset 14453.021969, delay 0.10876
27 Mar 14:36:21 ntpdate[23589]: step time server 66.162.15.65 offset 14453.022481 sec

>

The node wolve using EDT time due the location in new york

I must be even more crabby than usual tonight, because this casual ignorance is really irritating me.

Comments

Sign In or Register to comment.