[OpenAFS] pts modifications suddenly fail

[Christian]

Hi all,

since this morning, PTS updates are failing for us (I rebooteded the 
servers yesterday). Here is the symptom:

/usr/bin/pts createuser -name XXX -id YYY
/usr/bin/pts: not synchronization site (should work on sync site) ; 
unable to create user XXX with id YYY

udebug output looks good to me (see below). Time seems ok. The server 
NetInfo has the primary network interface of the respective server on 
it. I am lost. Maybe one of you can spot something...

Thanks and best wishes,

Christian


Host's addresses are: 130.75.103.1
Host's 130.75.103.1 time is Wed Aug 20 12:10:27 2025
Local time is Wed Aug 20 12:10:27 2025 (time differential 0 secs)
Last yes vote for 130.75.103.1 was 1 secs ago (sync site);
Last vote started 1 secs ago (at Wed Aug 20 12:10:26 2025)
Local db version is 1754523762.21
I am sync site until 59 secs from now (at Wed Aug 20 12:11:26 2025) (5 
servers)
Recovery state 1f
The last trans I handled was 1755682660.1636
Sync site's db version is 1754523762.21
0 locked pages, 0 of them for write
Last time a new db version was labelled was:
          1967 secs ago (at Wed Aug 20 11:37:40 2025)

Server (130.75.103.223): (db 1754523762.21)
     last vote rcvd 1 secs ago (at Wed Aug 20 12:10:26 2025),
     last beacon sent 1 secs ago (at Wed Aug 20 12:10:26 2025), last 
vote was yes
     dbcurrent=1, up=1 beaconSince=1

Server (130.75.103.221): (db 1754523762.21)
     last vote rcvd 1 secs ago (at Wed Aug 20 12:10:26 2025),
     last beacon sent 1 secs ago (at Wed Aug 20 12:10:26 2025), last 
vote was yes
     dbcurrent=1, up=1 beaconSince=1

Server (130.75.103.3): (db 1754523762.21)
     last vote rcvd 1 secs ago (at Wed Aug 20 12:10:26 2025),
     last beacon sent 1 secs ago (at Wed Aug 20 12:10:26 2025), last 
vote was yes
     dbcurrent=1, up=1 beaconSince=1

Server (130.75.103.2): (db 1754523762.21)
     last vote rcvd 1 secs ago (at Wed Aug 20 12:10:26 2025),
     last beacon sent 1 secs ago (at Wed Aug 20 12:10:26 2025), last 
vote was yes
     dbcurrent=1, up=1 beaconSince=1