Forum IT Tranquillo

- Installed WAPT version: 1.5.1.23
- Server OS: Debian 9
- Administration/package creation machine OS: Windows 10

Hello,

For some time now, our WAPT server has stopped reporting the availability of certain machines (actually, most of them). What's incomprehensible is that some of them have no problems at all.

I just upgraded the server from version 1.5.1.21 to 1.5.1.23, and I get the same message when I try to upload the new agent.

Avviando il server in modalità debug ecco cosa ottengo:

2018-04-17 15:20:18,691 INFO d573fcb8089e434bb28238dda1e624d3: Pacchetto ricevuto MESSAGGIO dati 2["wapt_pong"]
2018-04-17 15:20:18,691 INFO evento ricevuto "wapt_pong" da d573fcb8089e434bb28238dda1e624d3 [/]
2018-04-17 15:20:18,693 DEBUG Socket.IO pong dal client wapt sid d573fcb8089e434bb28238dda1e624d3 (uuid: 7578a06b-0dfb-4631-bd3f-5ad668abff9c)
2018-04-17 15:20:18,695 DEBUG ('UPDATE "hosts" SET "reachable" = %s, "server_uuid" = %s, "listening_protocol" = %s, "listening_address" = %s, "listening_timestamp" = %s WHERE ("hosts".."uuid" = %s)', [u'OK', u'ccbe3738-7c13-11e7-9353-001422b37596', u'websockets', u'd573fcb8089e434bb28238dda1e624d3', u'2018-04-17T15:20:18.693571', u'7578a06b-0dfb-4631-bd3f-5ad668abff9c'])
2018-04-17 15:20:18,705 DEBUG Restituzione di 139838076834184 al pool.
2018-04-17 15:20:18,717 INFO d573fcb8089e434bb28238dda1e624d3: Pacchetto PING ricevuto dati Nessuno
2018-04-17 15:20:18,717 INFO d573fcb8089e434bb28238dda1e624d3: Invio pacchetto PONG dati Nessuno
2018-04-17 15:20:18,923 DEBUG (1865) accettato ('127.0.0.1', 36760)
2018-04-17 15:20:18,926 INFO f520a971bf9c4b7e962a6f97292ee0a7: Invio pacchetto OPEN data {'pingInterval': 25000, 'pingTimeout': 60000, 'upgrades': ['websocket'], 'sid': 'f520a971bf9c4b7e962a6f97292ee0a7'}
2018-04-17 15:20:18,928 DEBUG ('SELECT "t1".."host_certificate" FROM "hosts" AS t1 WHERE ("t1".."uuid" = %s) LIMIT 1', [u'1E442148-659D-11E4-B810-0F11F5150E00'])
2018-04-17 15:20:18,931 WARNING SocketIO connection refused for uuid 1E442148-659D-11E4-B810-0F11F5150E00, sid f520a971bf9c4b7e962a6f97292ee0a7: Dati troppo vecchi o in età futura: 514s...
2018-04-17 15:20:18,932 DEBUG Restituzione di 139838076834184 al pool.
2018-04-17 15:20:18,934 DEBUG Restituzione di 139838076834184 al pool.
2018-04-17 15:20:18,935 INFO f520a971bf9c4b7e962a6f97292ee0a7: Invio pacchetto MESSAGGIO dati 4
2018-04-17 15:20:18,935 AVVISO L'applicazione ha rifiutato la connessione
2018-04-17 15:20:18,936 INFO 127.0.0.1 - - [17/Apr/2018 15:20:18] "GET /socket.io/?login=%7B%22uuid%22%3A+%221E442148-659D-11E4-B810-0F11F5150E00%22%2C+ %22firma%22%3A+%22iWhnZYSYdNxwP7Xx4FzZUglasWtXEY6NqW4pn%2BCVdMm2H2NM8OG5z1UB2 Fq8AEjIQ55jTWlw%2FBG7W5rGaNT%2Bks5%2BN647M3E0LApRYSXmvW7x85%2BPz%2B%2BJnyRfqcKf4P ujofC8QejzuXYaijA01F2TDzA%2BDiAuIR0SjlOOPl3xlr8a%2Bs8nw%2FcQ%2BJb0A9%2Ft3Assgfse6s qUTbN2PaYxFBKcjrxc3%2FyzdaNUtVenNFVfIbP0LdlgnxRTwgGRPGKLJ5haY3UzMuJaajusB2CAaOHr6 YQ%2BzT6yLlEz%2Bn3jivvoQyw4UQFPmXEo9FXS95y09nqUpmCREsa6cFRkkXjmMLP3oQ%3D%3D%22%2C+ %22signed_attributes%22%3A+%5B%22uuid%22%2C+%22signed_attributes%22%2C+%22signer%22%2C+%22signature_date%22%2C+%22signer_certificate%22%5D%2C+%22signer_certificate [...]

Ciao seb-aprolis,

seb-aprolis ha scritto: ↑17 aprile 2018 - 15:27 ...
Da un po' di tempo ormai, il nostro server WAPT ha smesso di segnalare la disponibilità di alcune macchine (in realtà, la maggior parte). La cosa incomprensibile è che alcune di esse non hanno alcun problema.

Ho appena aggiornato il server dalla versione 1.5.1.21 alla 1.5.1.23 e ricevo lo stesso messaggio quando provo a caricare il nuovo agente.

Quando eseguo il server in modalità debug, ecco cosa ottengo:
B810-0F11F5150E00, sid f520a971bf9c4b7e962a6f97292ee0a7: Dati troppo vecchi o in età futura: 514s
...

Potresti controllare l'ora sul server e sui computer client? Per impostazione predefinita, WAPT accetta una differenza oraria massima di 5 minuti tra il server e il client. Questa tolleranza può essere aumentata con il parametro `signature_clockskew` nel file `waptserver.ini`:

https://www.wapt.fr/en/doc-1.5/Configur ... tie-option

Sinceramente,

Denis

Thanks for your reply, Denis.

I changed the relevant setting, but it doesn't make much difference. However, I have a question: does SocketIO use CEST or UTC time?

As far as I know, clients are sending CEST time (so, in my case, the Paris time zone). Even though I've set the `signature_clockskew` value to 72,000 (20 minutes), I'm still getting an error message for smaller discrepancies (713 seconds).

Here is an excerpt from the log:
2018-04-18 09:26:05,075 WARNING SocketIO connection refused for uuid 5E56B0BC-659C-11E4-B666-D54C01160E00, sid 9bbed422a96647b09e7012ac3ba53bb3: Data too old or in the future age: 713s...


However, on the PING/PONG requests, I observe that the clients are not sending back anything...

Excerpt from the log:
2018-04-18 09:26:07,944 INFO a4363b4915254ffeb9b8bb2985b6dfc4: Received packet PING data None
2018-04-18 09:26:07,945 INFO a4363b4915254ffeb9b8bb2985b6dfc4: Invio pacchetto dati PONG Nessuno
2018-04-18 09:26:08,998 INFO 46271366851944f8aa9c2bf7a03549fa: Pacchetto PING ricevuto dati Nessuno
2018-04-18 09:26:08,999 INFO 46271366851944f8aa9c2bf7a03549fa: Invio pacchetto dati PONG Nessuno
2018-04-18 09:26:09,176 INFO 16d467efc7384eefb02d5be7283d6b8f: Pacchetto PING ricevuto dati Nessuno
2018-04-18 09:26:09,177 INFO 16d467efc7384eefb02d5be7283d6b8f: Sending packet PONG data None
2018-04-18 09:26:09,873 INFO 59494df967ab428fa7c668f3cef3a805: Received packet PING data None
2018-04-18 09:26:09,874 INFO 59494df967ab428fa7c668f3cef3a805: Sending packet PONG data None
2018-04-18 09:26:11,227 INFO 8d1463c48dce43588d62eb62658f9077: Received packet PING data None
2018-04-18 09:26:11,228 INFO 8d1463c48dce43588d62eb62658f9077: Sending packet PONG data None
2018-04-18 09:26:13,243 INFO ccec047c606943efb23b004f2f3a4eed: Received packet PING data None
2018-04-18 09:26:13,243 INFO ccec047c606943efb23b004f2f3a4eed: Sending packet PONG data None
2018-04-18 09:26:15,097 INFO 20a2baf55f5d4892a9939b223e090e37: Received packet PING data None
2018-04-18 09:26:15,097 INFO 20a2baf55f5d4892a9939b223e090e37: Sending packet PONG data None
2018-04-18 09:26:15,700 INFO 6906fbbacc504f3eb7d71a3091128b79: Received packet PING data None
2018-04-18 09:26:15,700 INFO 6906fbbacc504f3eb7d71a3091128b79: Invio pacchetto dati PONG Nessuno
2018-04-18 09:26:16,791 INFO 314b59759c4344119b33773a5fded716: Pacchetto PING ricevuto dati Nessuno
2018-04-18 09:26:16,791 INFO 314b59759c4344119b33773a5fded716: Invio pacchetto dati PONG Nessuno
2018-04-18 09:26:18,345 INFO e1158c58a76643fdb58d749ae5067186: Pacchetto PING ricevuto dati Nessuno
2018-04-18 09:26:18,346 INFO e1158c58a76643fdb58d749ae5067186: Sending packet PONG data None
2018-04-18 09:26:19,745 INFO 1d93e6ed3ba249ee853515e4cf3ab09b: Received packet PING data None
2018-04-18 09:26:19,746 INFO 1d93e6ed3ba249ee853515e4cf3ab09b: Sending packet PONG data None
2018-04-18 09:26:21,657 INFO 337ee328bde54513b049f980c36111ea: Received packet PING data None
2018-04-18 09:26:21,657 INFO 337ee328bde54513b049f980c36111ea: Sending packet PONG data None
2018-04-18 09:26:22,377 INFO 070ccfd6869a4e1db4a237427cc36087: Received packet PING data None
2018-04-18 09:26:22,377 INFO 070ccfd6869a4e1db4a237427cc36087: Sending packet PONG data None
2018-04-18 09:26:22,406 INFO 7cd8939bfcce47c2a91fcc1803439780: Received packet Dati PING Nessuno
2018-04-18 09:26:22,407 INFO 7cd8939bfcce47c2a91fcc1803439780: Invio pacchetto Dati PONG Nessuno

Ciao seb-aprolis,

seb-aprolis ha scritto: ↑18 apr 2018 - 09:37 Ho modificato il parametro rilevante, ma non cambia molto. Tuttavia, ho una domanda: SocketIO utilizza l'ora CEST o UTC?

Per me, i client inviano l'ora CEST (quindi, nel mio caso, il fuso orario di Parigi). Nonostante abbia impostato il valore di signature_clockskew a 72.000 (ovvero 20 minuti), ricevo ancora un messaggio per discrepanze minori (713 secondi).

Ecco un estratto dal log:
2018-04-18 09:26:05,075 WARNING Connessione SocketIO rifiutata per uuid 5E56B0BC-659C-11E4-B666-D54C01160E00, sid 9bbed422a96647b09e7012ac3ba53bb3: Dati troppo vecchi o in età futura: 713s...

Tuttavia, sulle richieste PING/PONG, osservo che i client non stanno inviando nulla in risposta...

Estratto dal log:
2018-04-18 09:26:07,944 INFO a4363b4915254ffeb9b8bb2985b6dfc4: Dati PING del pacchetto ricevuto Nessuno
2018-04-18 09:26:07,945 INFO a4363b4915254ffeb9b8bb2985b6dfc4: Invio pacchetto dati PONG Nessuno
2018-04-18 09:26:08,998 INFO 46271366851944f8aa9c2bf7a03549fa: Pacchetto PING ricevuto dati Nessuno
....
2018-04-18 09:26:22,407 INFO 7cd8939bfcce47c2a91fcc1803439780: Invio pacchetto dati PONG Nessuno

In passato abbiamo riscontrato problemi con il client Socket.io che non ripristinava la connessione in caso di perdita. Un modo per forzare il ripristino del client Socket.io è riavviare Nginx. Potresti provare a fermare Nginx, attendere qualche secondo e poi riavviarlo?

Sinceramente,

Denis