Bonjour,

Ça y est, le serveur est de nouveau tombé.

Voici la fin du syslog :

...

Oct 24 09:35:01 wapt2 CRON[32194]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Oct 24 09:36:01 wapt2 python[1527]: 2019-10-24 09:36:01,806 WARNING SocketIO connection refused for uuid 4C4C4544-0036-4710-804D-C7C04F425832, sid d7dd626b8b1a4d00a164d4b8f130cd4b: SocketIO connection not authorized, invalid token: 400 Bad Request: The browser (or proxy) sent a request that this server could not understand., instance
Oct 24 09:37:00 wapt2 python[1527]: 2019-10-24 09:37:00,858 WARNING SocketIO connection refused for uuid 4C4C4544-004E-5710-8053-B5C04F354B32, sid 7fef72636b294b999db9bc9dd045ab4d: SocketIO connection not authorized, invalid token: 400 Bad Request: The browser (or proxy) sent a request that this server could not understand., instance
Oct 24 09:39:11 wapt2 python[1527]: 2019-10-24 09:39:11,128 WARNING SocketIO connection refused for uuid 4C4C4544-0054-3210-804D-CAC04F465931, sid a9ee20f9518645f596057db6c332d6a1: SocketIO connection not authorized, invalid token: 400 Bad Request: The browser (or proxy) sent a request that this server could not understand., instance
Oct 24 09:42:50 wapt2 python[1527]: 2019-10-24 09:42:50,226 WARNING SocketIO connection refused for uuid 4C4C4544-0050-3310-8057-B5C04F354B32, sid 1ed4b0741b224f869961b1d3e88c8702: SocketIO connection not authorized, invalid token: 400 Bad Request: The browser (or proxy) sent a request that this server could not understand., instance
Oct 24 09:42:56 wapt2 python[1527]: 2019-10-24 09:42:56,099 WARNING SocketIO connection refused for uuid 4C4C4544-0050-3210-8053-B5C04F354B32, sid bc178e93e17f4062b4fcc8fa77628242: SocketIO connection not authorized, invalid token: 400 Bad Request: The browser (or proxy) sent a request that this server could not understand., instance
Oct 24 09:45:01 wapt2 CRON[32251]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Oct 24 09:47:00 wapt2 systemd[1]: Created slice User Slice of root.
Oct 24 09:47:00 wapt2 systemd[1]: Starting User Manager for UID 0...
Oct 24 09:47:00 wapt2 systemd[1]: Started Session 341 of user root.
Oct 24 09:47:00 wapt2 systemd[1]: Started Session 342 of user root.
Oct 24 09:47:00 wapt2 systemd[1]: Started Session 344 of user root.
Oct 24 09:47:00 wapt2 systemd[32266]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Oct 24 09:47:00 wapt2 systemd[32266]: Reached target Paths.
Oct 24 09:47:00 wapt2 systemd[32266]: Listening on GnuPG cryptographic agent (access for web browsers).
Oct 24 09:47:00 wapt2 systemd[32266]: Listening on GnuPG cryptographic agent and passphrase cache.
Oct 24 09:47:00 wapt2 systemd[32266]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Oct 24 09:47:00 wapt2 systemd[32266]: Reached target Timers.
Oct 24 09:47:00 wapt2 systemd[32266]: Listening on GnuPG network certificate management daemon.
Oct 24 09:47:00 wapt2 systemd[32266]: Starting D-Bus User Message Bus Socket.
Oct 24 09:47:00 wapt2 systemd[32266]: Listening on D-Bus User Message Bus Socket.
Oct 24 09:47:00 wapt2 systemd[32266]: Reached target Sockets.
Oct 24 09:47:00 wapt2 systemd[32266]: Reached target Basic System.
Oct 24 09:47:00 wapt2 systemd[32266]: Reached target Default.
Oct 24 09:47:00 wapt2 systemd[32266]: Startup finished in 16ms.
Oct 24 09:47:00 wapt2 systemd[1]: Started User Manager for UID 0.

La commande pids=$(pgrep -f "server.py"); for f in /proc/$pids/fdinfo/*; do cat $f | grep flags | grep -q -v 400[0,1,2] && ls -al /proc/$pids/fd/$(basename $f); done; donne :

lr-x------ 1 wapt www-data 64 oct.  22 12:28 /proc/1527/fd/0 -> /dev/null
lrwx------ 1 wapt www-data 64 oct.  22 12:28 /proc/1527/fd/1 -> socket:[15786]
lr-x------ 1 wapt www-data 64 oct.  22 12:28 /proc/1527/fd/15 -> /dev/urandom
lrwx------ 1 wapt www-data 64 oct.  22 12:28 /proc/1527/fd/2 -> socket:[15786]
lrwx------ 1 wapt www-data 64 oct.  22 12:28 /proc/1527/fd/3 -> anon_inode:[eventpoll]
lr-x------ 1 wapt www-data 64 oct.  22 12:28 /proc/1527/fd/8 -> /dev/urandom

Cordialement,

Frédéric GARESCHÉ

Équipe Assistance et Exploitation

Direction du Système d'Information (D.S.I)

Correspondant Département EII et laboratoire IETR
Tél. : +33 (0)2 23 23 82 81

20 avenue des Buttes de Coësmes
CS 70839 - 35 708 RENNES Cedex 7

---

De: "Frederic Garesche" <frederic.garesche@insa-rennes.fr>
À: "Hubert TOUVET" <htouvet@tranquil.it>
Cc: "wapt" <wapt@lists.tranquil.it>
Envoyé: Mardi 22 Octobre 2019 15:53:08
Objet: Re: [Wapt] Arrêt aléatoire du serveur wapt

Ok, la commande fonctionne.

pids=$(pgrep -f "server.py"); for f in /proc/$pids/fdinfo/*; do cat $f | grep flags | grep -q -v 400[0,1,2] && ls -al /proc/$pids/fd/$(basename $f); done;
lr-x------ 1 wapt www-data 64 oct.  22 12:28 /proc/1527/fd/0 -> /dev/null
lrwx------ 1 wapt www-data 64 oct.  22 12:28 /proc/1527/fd/1 -> socket:[15786]
lr-x------ 1 wapt www-data 64 oct.  22 12:28 /proc/1527/fd/15 -> /dev/urandom
lrwx------ 1 wapt www-data 64 oct.  22 12:28 /proc/1527/fd/2 -> socket:[15786]
lrwx------ 1 wapt www-data 64 oct.  22 12:28 /proc/1527/fd/3 -> anon_inode:[eventpoll]
lr-x------ 1 wapt www-data 64 oct.  22 12:28 /proc/1527/fd/8 -> /dev/urandom

Je n'ai plus qu'à attendre une panne...

Frédéric GARESCHÉ

Équipe Assistance et Exploitation

Direction du Système d'Information (D.S.I)

Correspondant Département EII et laboratoire IETR
Tél. : +33 (0)2 23 23 82 81

20 avenue des Buttes de Coësmes
CS 70839 - 35 708 RENNES Cedex 7