Project

General

Profile

Actions

Bug #10059

closed

An agent upgraded from 3.1 to 4.1 cannot fetch its promises

Added by Nicolas CHARLES about 7 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
N/A
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

I upgraded my agent Centos5 from 3.1.18 to 4.1beta, and it cannot get its new promises
Error is

rudder  verbose: Obtained IP address of '192.168.41.4' on socket 7 from accept
rudder  verbose: New connection (from 192.168.41.4, sd 7), spawning new thread...
rudder     info: 192.168.41.4> Accepting connection
rudder  verbose: 192.168.41.4> Setting socket timeout to 600 seconds.
rudder  verbose: 192.168.41.4> Peeked CAUTH in TCP stream, considering the protocol as Classic
rudder     info: 192.168.41.4> Connection is not using latest protocol, denying
rudder  verbose: Obtained IP address of '192.168.41.4' on socket 7 from accept
rudder  verbose: New connection (from 192.168.41.4, sd 7), spawning new thread...
rudder     info: 192.168.41.4> Accepting connection
rudder  verbose: 192.168.41.4> Setting socket timeout to 600 seconds.
rudder  verbose: 192.168.41.4> Peeked CAUTH in TCP stream, considering the protocol as Classic
rudder     info: 192.168.41.4> Connection is not using latest protocol, denying

Agent kept the promises distributed by the server, as expected

Actions #1

Updated by Nicolas CHARLES about 7 years ago

  • Status changed from New to Rejected

it was because promises were not regenerated on the server side

Actions #2

Updated by Florian Heigl over 6 years ago

  • Priority set to 0

Just managed to run into this (dont ask)

Advice for anyone affected is to (temporarily!) add a valid allowlegacyconnects section in cf-served.st (plus commit and technique reload)

Actions

Also available in: Atom PDF