Unable to connect

[py_more]

Bonjour,
J’ai tenté de faire un peu de place sur le disque de mon vps, pour faire une mise à jour de nextcloud. J’ai notamment supprimé en ligne de commande des sauvegardes précédement supprimées via l’interface d’administration.
depuis, je n’arrive plus à me connecter via l’interface web utilisateur et administrateur.

J’ai fait un test yunoports
résultat :

puis je me suis connecté en ssh et j’ai regardé le journal de Nginx :
systemctl status nginx.service

● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2021-11-03 17:11:08 CET; 1h 42min ago
Docs: man:nginx(8)
Process: 766 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)

Puis fait un
sudo journalctl -xe

– Logs begin at Wed 2021-11-03 16:51:13 CET, end at Wed 2021-11-03 17:00:57 CET. –
Nov 03 16:56:59 cloud.xdma.fr rabbitmq-server[3707]: 2021-11-03 16:56:59.756092+01:00 [erro] <0.223.0> BOOT FAILED
Nov 03 16:56:59 cloud.xdma.fr rabbitmq-server[3707]: 2021-11-03 16:56:59.756092+01:00 [erro] <0.223.0> ===========
Nov 03 16:56:59 cloud.xndma.fr rabbitmq-server[3707]: 2021-11-03 16:56:59.756092+01:00 [erro] <0.223.0> failed to open log file at ‘/var/log/rabbitmq/rabbit@cloud.log’, reason: permission deni
ed
Nov 03 16:56:59 cloud.xndma.fr rabbitmq-server[3707]: 2021-11-03 16:56:59.756092+01:00 [erro] <0.223.0>
Nov 03 16:56:59 cloud.xdma.fr rabbitmq-server[3707]: ===========
Nov 03 16:56:59 cloud.xndma.fr rabbitmq-server[3707]: failed to open log file at ‘/var/log/rabbitmq/rabbit@cloud.log’, reason: permission denied
Nov 03 16:57:00 cloud.xndma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> crasher:
Nov 03 16:57:00 cloud.xndma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> initial call: application_master:init/4
Nov 03 16:57:00 cloud.xndma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> pid: <0.222.0>
Nov 03 16:57:00 cloud.xndma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> registered_name:
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> exception exit: {{cannot_log_to_file,
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> “/var/log/rabbitmq/rabbit@cloud.log”,eacces},
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> {rabbit,start,[normal,]}}
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> in function application_master:init/4 (application_master.erl, line 142)
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> ancestors: [<0.221.0>]
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> message_queue_len: 1
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> messages: [{‘EXIT’,<0.223.0>,normal}]
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> links: [<0.221.0>,<0.44.0>]
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> dictionary:
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> trap_exit: true
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> status: running
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> heap_size: 610
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> stack_size: 29
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> reductions: 177
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0> neighbours:
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.759302+01:00 [erro] <0.222.0>
Nov 03 16:57:00 cloud.dma.fr rabbitmq-server[3707]: 2021-11-03 16:57:00.764423+01:00 [noti] <0.44.0> Application rabbit exited with reason: {{cannot_log_to_file,“/var/log/rabbitmq/rabbit@clo
ud.log”,eacces},{rabbit,start,[normal,]}}
Nov 03 16:57:01 cloud.dma.fr cron[789]: (systemframaforms) WRONG FILE OWNER (/etc/cron.d/framaforms)
Nov 03 16:57:01 cloud.dma.fr cron[789]: (systemkanboard) WRONG FILE OWNER (/etc/cron.d/kanboard)
Nov 03 16:57:01 cloud.dma.fr CRON[3762]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 03 16:57:01 cloud.dma.fr CRON[3763]: (root) CMD (/var/www/kanboard/plugins/Imap/kanboard_imap_tasks/cron.php /var/www/kanboard/app/Schema/Sql/mysql.sql)
Nov 03 16:57:01 cloud.dma.fr postfix/pickup[1293]: ACC873E8C7: uid=0 from=
Nov 03 16:57:01 cloud.dma.fr postfix/cleanup[1630]: ACC873E8C7: message-id=20211103155701.ACC873E8C7@cloud.dma.fr
Nov 03 16:57:01 cloud.dma.fr CRON[3762]: pam_unix(cron:session): session closed for user root
Nov 03 16:57:01 cloud.dma.fr postfix/qmgr[1294]: ACC873E8C7: from=root@cloud.dma.fr, size=728, nrcpt=1 (queue active)
Nov 03 16:57:01 cloud.dma.fr dovecot[3767]: lda(pierreyves@cloud.dma.fr)<3767>: sieve: msgid=20211103155701.ACC873E8C7@cloud.dma.fr: stored mail int
o mailbox ‘INBOX’
Nov 03 16:57:01 cloud.dma.fr postfix/pipe[1634]: ACC873E8C7: to=pierreyves@cloud.dma.fr, orig_to=, relay=dovecot, delay=0.15, delays=0.05/0/0/0.1, dsn=2.0.0, status=sent (del
ivered via dovecot service (lda(pierreyves@cloud.dma.fr,)Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: ))
Nov 03 16:57:01 cloud.dma.fr postfix/qmgr[1294]: ACC873E8C7: removed
Nov 03 16:57:02 cloud.dma.fr rabbitmq-server[3707]: {“Kernel pid terminated”,application_controller,“{application_start_failure,rabbit,{{cannot_log_to_file,"/var/log/rabbitmq/rabbit@cloud.l
og",eacces},{rabbit,start,[normal,]}}}”}
Nov 03 16:57:02 cloud.dma.fr rabbitmq-server[3707]: Kernel pid terminated (application_controller) ({application_start_failure,rabbit,{{cannot_log_to_file,"/var/log/rabbitmq/rabbit@cloud.log
",eacces},{rabbit,start,[normal,]}}})
Nov 03 16:57:02 cloud.dma.fr rabbitmq-server[3707]: [1B blob data]
Nov 03 16:57:02 cloud.dma.fr rabbitmq-server[3707]: Crash dump is being written to: /var/log/rabbitmq/erl_crash.dump…
Nov 03 16:57:02 cloud.dma.fr systemd[1]: rabbitmq-server.service: Main process exited, code=exited, status=1/FAILURE
– Subject: Unit process exited
– Defined-By: systemd
– Support: Debian -- User Support

– An ExecStart= process belonging to unit rabbitmq-server.service has exited.

– The process’ exit code is ‘exited’ and its exit status is 1.
Nov 03 16:57:02 cloud.dma.fr systemd[1]: rabbitmq-server.service: Failed with result ‘exit-code’.

Je constate que le journal “/var/log/rabbitmq/rabbit@cloud.log" est absent.

Lancé un diagnostique :

admin@cloud:~$ sudo yunohost diagnosis run
Success! Everything looks good for Base system!
Success! Everything looks good for Internet connectivity! (+ 1 ignored issue(s))
Warning: Found 1 item(s) that could be improved for DNS records. (+ 7 ignored issue(s))
Error: Found 2 significant issue(s) related to Ports exposure!
Error: Found 11 significant issue(s) related to Web!
Success! Everything looks good for Email! (+ 1 ignored issue(s))
Error: Found 11 significant issue(s) related to Services status check! (+ 1 ignored issue(s))
Success! Everything looks good for System resources!
Success! Everything looks good for System configurations!
Warning: To see the issues found, you can go to the Diagnosis section of the webadmin, or run ‘yunohost diagnosis show --issues --human-readable’ from the command-line.

Avant de tenter une réinstallation rabbitmq-server, je veux bien un avis.
Merci infiniment.

[Aleks]

et que racontent un nginx -t et journalctl -u nginx -n 100 --no-hostname --no-pager

[py_more]

@Aleks

nginx -t

sudo nginx -t

nginx: [alert] could not open error log file: open() “/var/log/nginx/error.log” failed (2: No such file or directory)
2021/11/03 20:10:36 [info] 13140#13140: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:63
2021/11/03 20:10:36 [warn] 13140#13140: conflicting server name “collabora.snes-bretagne.fr” on 0.0.0.0:443, ignored
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
2021/11/03 20:10:36 [emerg] 13140#13140: open() “/var/log/nginx/access.log” failed (2: No such file or directory)
nginx: configuration file /etc/nginx/nginx.conf test failed

[Aleks]

hmok, could it be that you deleted /var/log/nginx entirely or even /var/log …?

[py_more]

@Aleks

journalctl -u nginx -n 100 --no-hostname --no-pager

admin@cloud:~$ sudo journalctl -u nginx -n 100 --no-hostname --no-pager
– Logs begin at Wed 2021-11-03 17:25:12 CET, end at Wed 2021-11-03 20:11:52 CET. –
– No entries –

[py_more]

@Aleks

could it be that you deleted /var/log/nginx entirely or even /var/log

Je ne sais pas, voici le contenu de “/var/log/”

admin@cloud:/var/log/$ ls -la
total 12660
drwxr-xr-x 6 root root 12288 Nov 3 16:45 .
drwxr-xr-x 13 root root 4096 Sep 23 19:04 …
-rw-r–r-- 1 root root 624 Nov 3 17:11 alternatives.log
-rw-r----- 1 root adm 203337 Nov 3 20:13 auth.log
-rw-rw---- 1 root utmp 131328 Nov 3 20:11 btmp
-rw-r----- 1 root adm 5690548 Nov 3 20:13 daemon.log
-rw-r----- 1 root adm 28884 Nov 3 20:11 debug
-rw-r----- 1 root adm 127721 Nov 3 17:23 kern.log
-rw-rw-r-- 1 root utmp 294336 Nov 3 18:47 lastlog
-rw-r----- 1 root adm 219577 Nov 3 20:13 mail.info
-rw-r----- 1 root adm 219577 Nov 3 20:13 mail.log
-rw-r----- 1 root adm 3485 Nov 3 20:13 mail.warn
-rw-r----- 1 root adm 106500 Nov 3 17:23 messages
-rw------- 1 root root 947 Nov 3 19:45 php7.3-fpm.log
drwxrwxr-t 2 root postgres 4096 Nov 3 16:44 postgresql
drwx------ 2 root root 4096 Nov 3 16:44 private
-rw-r----- 1 root adm 6120065 Nov 3 20:13 syslog
drwxr-xr-x 2 root root 4096 Nov 3 16:44 unattended-upgrades
-rw-rw-r-- 1 root utmp 10368 Nov 3 18:47 wtmp
drwxr-x— 2 root root 4096 Nov 3 16:44 yunohost

[Aleks]

ben du coup oui, pas de /var/log/nginx … Mais si tu n’es pas capable de savoir ce que tu as supprimé ou non c’est relativement problématique pour pouvoir comprendre et réparer les problèmes …

[py_more]

Ok, merci @Aleks. Je n’ai pas le souvenir d’avoir supprimé ce repertoire…
L’essentiel pour moi est de récuperer les données de kanboard. Est-ce que peux le faire en ligne de commande ?

[Aleks]

J’imagine que tu peux faire un mkdir /var/log/nginx et chown nginx:root /var/log/nginx

[py_more]

sudo chown nginx:root /var/log/nginx/

chown: invalid user: ‘nginx:root’

en faisant “cat etc/passwd”, je ne vois pas de user nginx.

[py_more]

Bonjour,
J’ai sauvegardé toutes mes données. Je pense réinstaller complètement le serveur. J’y vois un intérêt : repartir sur une base saine et régler le problème d’espace disque.
Le bilan de ces deux années avec ce serveur est excellent. Le projet Yunohost répond à des valeurs qui me sont chères et techniquement, il met à la portée du plus grand nombre la possibilité d’administrer son propre serveur. Un seul problème pour moi, au fil du temps, le système a pris de plus en plus d’espace disque. Peut-être est ce dû à mes (trop) nombreux tests d’applications.
Un très grand merci à @Aleks, pour sa disponibilité, son aide et ses conseils.