ERROR: Ticket authentication failed - invalid ticket

  • Thread starter Thread starter sub3xt1
  • Start date Start date
S

sub3xt1

Guest
master : PVE 1.4
slave : PVE 1.4

vhost2:~# pveca -l
CID----IPADDRESS----ROLE-STATE--------UPTIME---LOAD----MEM---DISK
1 : 192.168.8.33 M ERROR: Ticket authentication failed - invalid ticket 'root::root::1254151041::a40187d323ce4b1adf9""""""""XYZ'

2 : 192.168.8.32 N S 00:13 0.11 3% 1%
 
vhost1:~# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
19.168.8.253 .LOCL. 1 u 2 64 377 0.194 -293419 10.219
19.168.8.255 .BCST. 16 u - 64 0 0.000 0.000 0.001

vhost2:~# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
19.168.8.253 .LOCL. 1 u 39 64 377 0.156 -252816 13.226
19.168.8.255 .BCST. 16 u - 64 0 0.000 0.000 0.001

both of the server is different about 2 hour(s). there is no command like : ntpdate, rdate, etc to correct the date/time.
 
yes, the file is same on both.
i use 192.168.8.253 as NTP server for other linux server and it is works.
but, no luck on both of PVE 1.4

# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help
driftfile /var/lib/ntp/ntp.drift


# Enable this if you want statistics to be logged.
statsdir /var/log/ntpstats/

statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable


# You do need to talk to an NTP server or two (or three).
#server ntp.your-provider.example
server 192.168.8.253

# pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will
# pick a different set every time it starts up. Please consider joining the
# pool: <http://www.pool.ntp.org/join.html>
#server 0.debian.pool.ntp.org iburst dynamic
#server 1.debian.pool.ntp.org iburst dynamic
#server 2.debian.pool.ntp.org iburst dynamic
#server 3.debian.pool.ntp.org iburst dynamic

# Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for
# details. The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions>
# might also be helpful.
#
# Note that "restrict" applies to both servers and clients, so a configuration
# that might be intended to block requests from certain clients could also end
# up blocking replies from your own upstream servers.

# By default, exchange time with everybody, but don't allow configuration.
restrict -4 default kod notrap nomodify nopeer noquery
restrict -6 default kod notrap nomodify nopeer noquery

# Local users may interrogate the ntp server more closely.
restrict 127.0.0.1
restrict ::1

# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
#restrict 192.168.123.0 mask 255.255.255.0 notrust


# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
#broadcast 192.168.123.255
broadcast 192.168.8.255

# If you want to listen to time broadcasts on your local subnet, de-comment the
# next lines. Please do this only if you trust everybody on the network!
disable auth
broadcastclient
 
i even try to set up:
a. vhost1 as NTP server
b. vhost2 as NTP server
c. 192.168.8.253 as NTP server (for other linux box, it is OK)

and restart NTP service
# /etc/init.d/ntp restart
Stopping NTP server: ntpd.
Starting NTP server: ntpd.

now, my question is, how can i correct this date/time service (ntp service) ??
 
Dietmar,
what do you mean "what..."?

i have time problem between two server (about 2 hours different), and i want to synchronyze this time between them. how can i do that??
 
Dietmar,
what do you mean "what..."?

You did not gave any info - for example what the output ot 'ntpq -p'

i have time problem between two server (about 2 hours different), and i want to synchronyze this time between them. how can i do that??

Normaly, just spezify the servers int ntp.conf - then restart the ntp service (as you have already done).
 
i have print output : ntpq -p
vhost1:~# ntpq -p
remote refid st t when poll reach delay offset jitter
================================================== ============================
19.168.8.253 .LOCL. 1 u 2 64 377 0.194 -293419 10.219
19.168.8.255 .BCST. 16 u - 64 0 0.000 0.000 0.001

vhost2:~# ntpq -p
remote refid st t when poll reach delay offset jitter
================================================== ============================
19.168.8.253 .LOCL. 1 u 39 64 377 0.156 -252816 13.226
19.168.8.255 .BCST. 16 u - 64 0 0.000 0.000 0.001

both of the server is different about 2 hour(s). there is no command like : ntpdate, rdate, etc to correct the date/time.

please see above.

for timezone, i have reconfigure for Asia/Jakarta.
# dpkg-reconfigure tzdata

Current default timezone: 'Asia/Jakarta'
Local time is now: Tue Sep 29 21:51:14 WIT 2009.
Universal Time is now: Tue Sep 29 14:51:14 UTC 2009.
 
You said you added 3 server to ntp.conf, but 'ntpq -p' does not show them - this is quite confusing?
 
You said you added 3 server to ntp.conf, but 'ntpq -p' does not show them - this is quite confusing?

actually, i just add one server.
which is one of IP :
a. 192.168.8.253, or
b. vhost1, or
c. vhost2.

none of the configuration give result just like what i want.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!