[RISOLTO] Il PC sembra disconnesso dall'aggiornamento alla versione 2.2

[Alex]

Ciao,

versione WAPT: 2.2
Server: Debian 11
Client: Windows 10

Ciao,
ho recentemente effettuato la migrazione dalla versione 1.8.1 alla 2.2.
I client ora risultano disconnessi ma con stato OK e la versione del client WAPT si è aggiornata automaticamente sui client.

Ho controllato l'ora come indicato sul forum >> OK.
Non ho modificato nulla riguardo al mio firewall.

Ho aggiornato nuovamente il server e ricreato un certificato, ma niente funziona. Sono un po' perso.

Avete qualche suggerimento per aiutarmi?

Grazie.

[dcardon]

Ciao,

il metodo di firma è cambiato tra le versioni 1.8.1 e 2.0. Devi prima aggiornare alla versione 1.8.2 per garantire la compatibilità tra i due metodi (vedi documentazione).

Pertanto, devi reinstallare gli agenti 2.2 tramite GPO o un altro metodo.

Cordiali saluti,

Denis

[Alex]

Mi dispiace, ma non sono sicuro di aver capito.
Devo effettuare il downgrade della versione del mio server dalla 2.2 alla 1.8.1, poi aggiornarla alla 1.8.2 e infine aggiornarla nuovamente alla 2.2?

[dcardon]

Le workstation che eseguono WAPT 1.8.1 non possono convalidare la firma di un pacchetto waptupgrade generato da WAPT 2.2.

Pertanto, è possibile posticipare l'aggiornamento dell'agente alla versione 2.2 utilizzando waptsetup.exe tramite Criteri di gruppo se si dispone di Active Directory (o qualsiasi altro metodo).

In alternativa, è possibile eseguire il downgrade alla versione 1.8.2 (e aggiornare tutti gli agenti alla versione 1.8.2) e quindi eseguire l'aggiornamento alla versione 2.2.

Tuttavia, la soluzione più semplice è posticipare l'aggiornamento dell'agente tramite Criteri di gruppo se si dispone di Active Directory.

Cordiali saluti,

Denis

[Alex]

Ho distribuito il mio agente 2.2 su una workstation eseguendo l'installazione manuale per testare, ma la workstation continua a non essere visualizzata come OK (raggiungibile).

[sfontenau]

Puoi provare a eseguire il seguente comando:

Codice: Seleziona tutto

"c:\Program Files (x86)\wapt\runwaptservice.bat" -ldebug

su un computer acceso per vedere in tempo reale i messaggi di errore visualizzati dall'agente

[Alex]

Ecco il risultato:

Codice: Seleziona tutto

2022-07-06 10:26:36,855 [waptcore MainThread 912] DEBUG Thread 912 is connecting to wapt db
2022-07-06 10:26:41,647 [waptcore MainThread 912] DEBUG DB Start transaction
2022-07-06 10:26:41,656 [waptcore MainThread 912] DEBUG DB commit
2022-07-06 10:26:41,692 [waptservice MainThread 912] INFO Setting hiberboot_enabled to 0
2022-07-06 10:26:41,694 [waptcore MainThread 912] DEBUG Thread 912 is connecting to wapt db
2022-07-06 10:26:41,695 [waptcore MainThread 912] DEBUG DB Start transaction
2022-07-06 10:26:41,696 [waptcore MainThread 912] DEBUG DB commit
2022-07-06 10:26:41,869 [waptcore MainThread 912] DEBUG Using host certificate c:\Program Files (x86)\wapt\private\4C4C4544-0047-3410-8047-B7C04F593633.pem for repo global auth
2022-07-06 10:26:41,870 [waptcore MainThread 912] DEBUG Loading ssl context with cert c:\Program Files (x86)\wapt\private\4C4C4544-0047-3410-8047-B7C04F593633.crt and key c:\Program Files (x86)\wapt\private\4C4C4544-0047-3410-8047-B7C04F593633.pem
2022-07-06 10:26:41,872 [urllib3.connectionpool MainThread 912] DEBUG Starting new HTTPS connection (1): 192.168.10.15:443
2022-07-06 10:26:41,893 [urllib3.connectionpool MainThread 912] DEBUG https://192.168.10.15:443 "GET /licences.json HTTP/1.1" 200 0
2022-07-06 10:26:41,894 [wapttasks MainThread 912] INFO Service Configuration: {'config_filename': 'c:\\Program Files (x86)\\wapt\\wapt-get.ini', 'waptservice_user': None, 'waptservice_password': None, 'MAX_HISTORY': 30, 'waptservice_port': 8088, 'dbpath': 'c:\\Program Files (x86)\\wapt\\db\\waptdb.sqlite', 'loglevel': 'debug', 'log_directory': 'c:\\Program Files (x86)\\wapt\\log', 'waptserver': <WaptServer https://192.168.10.15>, 'hiberboot_enabled': 0, 'max_gpo_script_wait': 180, 'pre_shutdown_timeout': 180, 'log_to_windows_events': False, 'allow_user_service_restart': False, 'signature_clockskew': 21600, 'notify_user': False, 'waptservice_admin_filter': False, 'enable_remote_repo': False, 'local_repo_path': 'c:\\Program Files (x86)\\wapt\\repository', 'local_repo_sync_task_period': '2h', 'local_repo_time_for_sync_start': None, 'local_repo_time_for_sync_end': None, 'local_repo_limit_bandwidth': None, 'wol_port': '7,9', 'wol_relay': False, 'service_auth_type': 'system', 'verify_cert_ldap': False, 'download_after_update_with_waptupdate_task_period': True, 'forced_installs_task_period': '2m', 'reconfig_on_network_change': False, 'loglevel_waptcore': None, 'loglevel_waptservice': None, 'loglevel_waptws': None, 'loglevel_waptdb': None, 'loglevel_websocket': None, 'loglevel_waitress': None, 'loglevel_wapttasks': None}
2022-07-06 10:26:41,894 [wapttasks MainThread 912] INFO Starting task queue
2022-07-06 10:26:41,895 [wapttasks MainThread 912] INFO Tasks queue running
2022-07-06 10:26:41,895 [wapttasks WaptTaskManager 15356] INFO Wapt tasks management initialized with c:\Program Files (x86)\wapt\wapt-get.ini configuration
2022-07-06 10:26:41,897 [wapttasks MainThread 912] INFO Starting waitress waptservice on port 8088
2022-07-06 10:26:41,900 [waptcore WaptTaskManager 15356] DEBUG Thread 15356 is connecting to wapt db
2022-07-06 10:26:41,900 [waptservice SocketIOClient 13416] INFO No password set for local waptservice, using local computer security
2022-07-06 10:26:41,902 [waptcore WaptTaskManager 15356] DEBUG DB Start transaction
2022-07-06 10:26:41,903 [waptcore SocketIOClient 13416] DEBUG Thread 13416 is connecting to wapt db
2022-07-06 10:26:41,904 [waptcore WaptTaskManager 15356] DEBUG DB commit
2022-07-06 10:26:41,910 [waptcore SocketIOClient 13416] DEBUG DB Start transaction
2022-07-06 10:26:41,910 [waptcore SocketIOClient 13416] DEBUG DB commit
2022-07-06 10:26:41,920 [waitress MainThread 912] INFO Serving on http://127.0.0.1:8088
2022-07-06 10:26:42,018 [wapttasks SocketIOClient 13416] INFO Starting socketio on "https://192.168.10.15:443" Thread id 13416
2022-07-06 10:26:42,018 [waptws SocketIOClient 13416] DEBUG Certificate checking : False
2022-07-06 10:26:42,020 [waptcore WaptTaskManager 15356] DEBUG Using host certificate c:\Program Files (x86)\wapt\private\4C4C4544-0047-3410-8047-B7C04F593633.pem for repo global auth
2022-07-06 10:26:42,026 [waptcore WaptTaskManager 15356] DEBUG Using host certificate c:\Program Files (x86)\wapt\private\4C4C4544-0047-3410-8047-B7C04F593633.pem for repo wapt auth
2022-07-06 10:26:42,027 [waptcore WaptTaskManager 15356] INFO Main repository: https://192.168.10.15/wapt
2022-07-06 10:26:42,029 [waptcore WaptTaskManager 15356] DEBUG Using host certificate c:\Program Files (x86)\wapt\private\4C4C4544-0047-3410-8047-B7C04F593633.pem for repo wapt-host auth
2022-07-06 10:26:42,036 [wapttasks WaptTaskManager 15356] INFO Core Configuration: {'wapt_base_dir': 'c:\\Program Files (x86)\\wapt', 'waptserver': <WaptServer https://192.168.10.15>, 'config_filename': 'c:\\Program Files (x86)\\wapt\\wapt-get.ini', 'proxies': {'http': '', 'https': ''}, 'repositories': [<WaptRepo https://192.168.10.15/wapt>, <WaptHostRepo https://192.168.10.15/wapt-host for host_id 4C4C4544-0047-3410-8047-B7C04F593633 >], 'personal_certificate_path': '', 'public_certs_dir': 'c:\\Program Files (x86)\\wapt\\ssl', 'package_cache_dir': 'c:\\Program Files (x86)\\wapt\\cache', 'dbpath': 'c:\\Program Files (x86)\\wapt\\db\\waptdb.sqlite', 'use_http_proxy_for_repo': False, 'use_http_proxy_for_server': False, 'limit_bandwidth': None, 'locales': ['fr'], 'custom_tags': [], 'packages_whitelist': None, 'packages_blacklist': None, 'maturities': ['PROD'], 'host_uuid': '4C4C4544-0047-3410-8047-B7C04F593633', 'use_fqdn_as_uuid': False, 'use_hostpackages': True, 'use_ad_groups': False, 'use_repo_rules': False, 'host_profiles': [], 'host_organizational_unit_dn': 'CN=Computers,DC=SJB-ADMIN,DC=local', 'host_ad_site': None, 'waptaudit_task_period': '2h', 'hiberboot_enabled': '0', 'max_gpo_script_wait': 180.0, 'pre_shutdown_timeout': 180.0, 'uninstallkey_timeout': 120, 'check_certificates_validity': True, 'token_lifetime': 86400}
2022-07-06 10:26:42,036 [wapttasks WaptTaskManager 15356] INFO Wapt tasks queue started
2022-07-06 10:26:42,041 [waptcore WaptTaskManager 15356] DEBUG Loading ssl context with cert c:\Program Files (x86)\wapt\private\4C4C4544-0047-3410-8047-B7C04F593633.crt and key c:\Program Files (x86)\wapt\private\4C4C4544-0047-3410-8047-B7C04F593633.pem
2022-07-06 10:26:42,045 [urllib3.connectionpool WaptTaskManager 15356] DEBUG Starting new HTTPS connection (1): 192.168.10.15:443
2022-07-06 10:26:42,058 [waptcore SocketIOClient 13416] DEBUG Using host certificate c:\Program Files (x86)\wapt\private\4C4C4544-0047-3410-8047-B7C04F593633.pem for repo global auth
2022-07-06 10:26:42,061 [waptcore SocketIOClient 13416] DEBUG Loading ssl context with cert c:\Program Files (x86)\wapt\private\4C4C4544-0047-3410-8047-B7C04F593633.crt and key c:\Program Files (x86)\wapt\private\4C4C4544-0047-3410-8047-B7C04F593633.pem
2022-07-06 10:26:42,063 [urllib3.connectionpool SocketIOClient 13416] DEBUG Starting new HTTPS connection (1): 192.168.10.15:443
2022-07-06 10:26:42,144 [urllib3.connectionpool WaptTaskManager 15356] DEBUG https://192.168.10.15:443 "GET /licences.json HTTP/1.1" 200 0
2022-07-06 10:26:42,232 [urllib3.connectionpool SocketIOClient 13416] DEBUG https://192.168.10.15:443 "POST /get_websocket_auth_token HTTP/1.1" 200 311
2022-07-06 10:26:42,233 [waptcore SocketIOClient 13416] DEBUG DB Start transaction
2022-07-06 10:26:42,237 [waptcore SocketIOClient 13416] DEBUG DB commit
2022-07-06 10:26:42,256 [waptws SocketIOClient 13416] WARNING Websocket connect params failure, trying registration: Unable to get auth token: Error on server:
ProgrammingError("ERREUR:  erreur de syntaxe sur ou près de « ON »\nLINE 1: ...519b9b0-d697-11e7-8d03-000c2954dc5e', 1657096002) ON CONFLIC...\n                                                             ^\n")
2022-07-06 10:26:42,259 [urllib3.connectionpool SocketIOClient 13416] DEBUG Starting new HTTPS connection (1): 192.168.10.15:443
2022-07-06 10:26:42,278 [urllib3.connectionpool SocketIOClient 13416] DEBUG https://192.168.10.15:443 "HEAD /ping HTTP/1.1" 200 0
2022-07-06 10:26:42,280 [urllib3.connectionpool SocketIOClient 13416] DEBUG Starting new HTTPS connection (1): 192.168.10.15:443
2022-07-06 10:26:42,328 [urllib3.connectionpool SocketIOClient 13416] DEBUG https://192.168.10.15:443 "HEAD /ping HTTP/1.1" 200 0
2022-07-06 10:26:42,329 [waptcore SocketIOClient 13416] DEBUG DB Start transaction
2022-07-06 10:26:42,337 [waptcore SocketIOClient 13416] DEBUG DB commit
2022-07-06 10:26:42,416 [waptcore SocketIOClient 13416] DEBUG DB Start transaction
2022-07-06 10:26:42,419 [waptcore SocketIOClient 13416] DEBUG DB commit
2022-07-06 10:26:42,425 [waptcore SocketIOClient 13416] DEBUG DB Start transaction
2022-07-06 10:26:42,426 [waptcore SocketIOClient 13416] DEBUG DB commit
2022-07-06 10:26:42,433 [urllib3.connectionpool SocketIOClient 13416] DEBUG Starting new HTTPS connection (1): 192.168.10.15:443
2022-07-06 10:26:42,623 [urllib3.connectionpool SocketIOClient 13416] DEBUG https://192.168.10.15:443 "GET /licences.json HTTP/1.1" 200 0
2022-07-06 10:26:43,167 [waptcore SocketIOClient 13416] DEBUG Using host certificate c:\Program Files (x86)\wapt\private\4C4C4544-0047-3410-8047-B7C04F593633.pem for repo wapt auth
2022-07-06 10:26:43,168 [waptcore SocketIOClient 13416] INFO Main repository: https://192.168.10.15/wapt
2022-07-06 10:26:43,171 [waptcore SocketIOClient 13416] DEBUG Using host certificate c:\Program Files (x86)\wapt\private\4C4C4544-0047-3410-8047-B7C04F593633.pem for repo wapt-host auth
2022-07-06 10:26:43,184 [waptcore SocketIOClient 13416] DEBUG host_info timing: 0.5586521625518799 s
2022-07-06 10:26:43,191 [waptcore SocketIOClient 13416] DEBUG Stores cert chain check in cache
2022-07-06 10:26:43,193 [waptcore SocketIOClient 13416] DEBUG Stores cert chain check in cache
2022-07-06 10:26:43,200 [urllib3.connectionpool SocketIOClient 13416] DEBUG Starting new HTTPS connection (1): 192.168.10.15:443
2022-07-06 10:26:43,268 [urllib3.connectionpool SocketIOClient 13416] DEBUG https://192.168.10.15:443 "GET /licences.json HTTP/1.1" 200 0
2022-07-06 10:26:43,270 [urllib3.connectionpool SocketIOClient 13416] DEBUG Starting new HTTPS connection (1): 192.168.10.15:443
2022-07-06 10:26:43,277 [urllib3.connectionpool SocketIOClient 13416] DEBUG https://192.168.10.15:443 "GET /licences.json HTTP/1.1" 200 0
2022-07-06 10:26:43,278 [waptcore SocketIOClient 13416] DEBUG wapt_status timing: 0.09369778633117676 s
2022-07-06 10:26:43,280 [urllib3.connectionpool SocketIOClient 13416] DEBUG Starting new HTTPS connection (1): 192.168.10.15:443
2022-07-06 10:26:43,373 [urllib3.connectionpool SocketIOClient 13416] DEBUG https://192.168.10.15:443 "GET /licences.json HTTP/1.1" 200 0
2022-07-06 10:26:43,379 [waptcore SocketIOClient 13416] DEBUG host_capabilities timing: 0.10073566436767578 s
2022-07-06 10:26:43,540 [waptcore SocketIOClient 13416] DEBUG host_metrics timing: 0.1605672836303711 s
2022-07-06 10:26:43,566 [waptcore SocketIOClient 13416] DEBUG installed_softwares timing: 0.025931119918823242 s
2022-07-06 10:26:43,567 [waptcore SocketIOClient 13416] DEBUG installed_packages timing: 0.000995635986328125 s
2022-07-06 10:26:43,568 [waptcore SocketIOClient 13416] DEBUG last_update_status timing: 0.0 s
2022-07-06 10:26:43,575 [waptcore SocketIOClient 13416] DEBUG authorized_certificates timing: 0.0 s
2022-07-06 10:26:43,576 [waptcore SocketIOClient 13416] DEBUG audit_status timing: 0.0009965896606445312 s
2022-07-06 10:26:43,579 [waptcore SocketIOClient 13416] DEBUG configurations timing: 0.0019636154174804688 s
2022-07-06 10:26:43,581 [waptcore SocketIOClient 13416] INFO Run "dmidecode -q"
2022-07-06 10:26:43,600 [waptcore SocketIOClient 13416] INFO dmidecode -q command returns code 0
2022-07-06 10:26:43,601 [waptcore SocketIOClient 13416] DEBUG dmi timing: 0.019902467727661133 s

[dcardon]

Sembra un problema di aggiornamento schematico.

Puoi effettuare un backup e poi reimpostare il database per verificare se funziona con uno schema di database pulito?.

Codice: Seleziona tutto

systemctl stop waptserver
sudo -u postgres psql -c "DROP DATABASE wapt;"
systemctl start waptserver

Il server era stato aggiornato in passato oppure si trattava di un'installazione di base 1.8.1?

Sinceramente,

Denis

P.S.: Utilizza i tag di codice corretti per i tuoi blocchi di codice; renderà i post più facili da leggere

[dcardon]

Potresti estrarre lo schema del database così possiamo analizzare il problema?

Codice: Seleziona tutto

sudo -u postgres pg_dump --schema-only wapt | gzip - >  /root/waptdb_structure.sql.gz

Esporta solo lo schema, non i dati. Quindi allegalo al messaggio.

Sinceramente,

Denis

[Alex]

In Pg, l'estrazione del database richiesta