Tranquil IT Forum

Published: **July 4, 2022 - 5:56 PM**

Hello,

WAPT version: 2.2
Server: Debian 11
Clients: Windows 10

Hello,
I recently migrated from version 1.8.1 to 2.2.
The clients now appear disconnected but with an OK status, and the WAPT client version updated automatically on the clients.

I checked the time as indicated on the forum >> OK.
I haven't changed anything regarding my firewall.

I re-updated on the server side and recreated a certificate, but nothing works. I'm a bit lost.

Do you have any ideas to guide me?

Thank you.

Published: **July 5, 2022 - 8:58 AM**

Hello,

the signature method changed between versions 1.8.1 and 2.0. You must first upgrade to 1.8.2 to ensure compatibility between the two methods (see documentation).

Therefore, you need to push back the 2.2 agents via GPO or another method.

Regards,

Denis

Published: **July 5, 2022 - 5:11 PM**

I'm sorry, but I'm not sure I understand.
Do I need to downgrade my server version from 2.2 to 1.8.1, then update it to 1.8.2, and then upgrade it to 2.2?

Published: **July 5, 2022 - 5:24 PM**

Workstations running WAPT 1.8.1 cannot validate the signature of a waptupgrade package generated from WAPT 2.2.

Therefore, you can postpone the agent update to version 2.2 using waptsetup.exe via Group Policy if you have Active Directory (or any other method).

Alternatively, you can downgrade to 1.8.2 (and upgrade all agents to 1.8.2) and then upgrade to 2.2.

However, the simplest solution is to postpone the agent update via Group Policy if you have Active Directory.

Sincerely,

Denis

Published: **July 5, 2022 - 5:40 PM**

I deployed my agent 2.2 on a workstation by doing the manual install to test but the workstation still does not appear as OK (reachable).

Published: **July 5, 2022 - 10:12 PM**

You can try running the following command:

Code: Select all

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

on a switched-on computer to see live error messages that the agent displays

Published: **July 6, 2022 - 10:30 AM**

Here is the result:

Code: Select all

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

Published: **July 6, 2022 - 11:25 AM**

This smells like a schematic upgrade problem.

Can you make a backup and then reset the database to see if it works with a clean database schema?.

Code: Select all

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

Had the server been upgraded in the past, or was it a basic 1.8.1 installation?

Sincerely,

Denis

PS: Please use the correct code tags for your code blocks; it makes posts easier to read

Published: **July 6, 2022 - 11:38 AM**

And could you extract the database schema so we can look into the problem?

Code: Select all

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

It only exports the schema, not the data. Then attach it to the message.

Sincerely,

Denis

Published: **July 6, 2022 - 11:48 AM**

In Pg, the requested database extraction

Tranquil IT Forum

[SOLVED] PC appears disconnected since update to 2.2

[SOLVED] PC appears disconnected since update to 2.2

Re: PC appears disconnected since update to 2.2

Re: PC appears disconnected since update to 2.2

Re: PC appears disconnected since update to 2.2

Re: PC appears disconnected since update to 2.2

Re: PC appears disconnected since update to 2.2

Re: PC appears disconnected since update to 2.2

Re: PC appears disconnected since update to 2.2

Re: PC appears disconnected since update to 2.2

Re: PC appears disconnected since update to 2.2