Nextcloud, disparition après mise à jour puis 502

Support apps
1

Après avoir déjà posté dans un sujet existant sur ce problème, je me rends compte que je n’ai pas forcément la même chose.

Voici un descriptif du problème dans son ensemble et chronologique, suivi des logs.

Yunohost 3;2;2

Dans un premier temps, j’ai lancé via l’interface web une mise à jour de yunohost. A priori cette mise à jour à provoqué des problèmes avec php7, chose que je n’ai pas immédiatement vu. Dans la foulée, j’ai tenté de mettre à jour Nextcloud. J’ai eu ce log d’erreur :

2018-10-02 10:55:48,874: WARNING - Data dir will not be saved, because backup_core_only is set.
2018-10-02 10:57:22,067: WARNING - php7.0-fpm.service is not active, cannot reload.
2018-10-02 10:57:22,068: WARNING - !!
2018-10-02 10:57:22,068: WARNING - nextcloud’s script has encountered an error. Its execution was cancelled.
2018-10-02 10:57:22,068: WARNING - !!
2018-10-02 10:57:22,068: WARNING - Upgrade failed.
2018-10-02 10:57:25,176: WARNING - E: dpkg a été interrompu. Il est nécessaire d’utiliser « sudo dpkg --configure -a » pour corriger le problème.
2018-10-02 10:57:25,377: WARNING - Removing database nextcloud
2018-10-02 10:57:30,690: WARNING - php7.0-fpm.service is not active, cannot reload.
2018-10-02 10:57:30,790: WARNING - Remove the user nextcloud

Suite à cela, je me suis rendu compte du probleme de php7 que j’ai corrigé. J’ai ensuite remarqué que mon domaine associé à Nextcloud a redirigé vers le portail utilisateur de yunohost. J’ai alors retenté une mise à jour :

2018-10-02 11:20:23,143: WARNING - Source path ‘/etc/logrotate.d/nextcloud’ does not exist
2018-10-02 11:20:23,144: WARNING - !!
2018-10-02 11:20:23,144: WARNING - nextcloud’s script has encountered an error. Its execution was cancelled.
2018-10-02 11:20:23,145: WARNING - !!
2018-10-02 11:20:23,145: WARNING -
2018-10-02 11:20:23,246: WARNING - Impossible de sauvegarder l’application « nextcloud »
2018-10-02 11:20:23,247: WARNING - Il n’y a rien à sauvegarder
2018-10-02 11:20:23,247: WARNING - Backup failed, the upgrade process was aborted.
2018-10-02 11:20:23,400: ERROR - Impossible de mettre à jour nextcloud

Le domaine à continuer à rediriger vers le portail yunohost… Bizarrement ensuite, impossible d’accèder à mon serveur, que ce soit en ssh ou en web avec mon adresse ip de chez moi. Obligé d’utiliser un VPN sinon j’ai une déconnexion forcé par le software au bout de quelques secondes, voir minutes (et impossible de trouver pourquoi mais c’est un autre probleme).

Et là, du jour au lendemain j’ai désormais une erreur 502 bad gateway. Mon php7 fonctionne correctement à priori. Je ne sais pas ou me diriger pour solutionner ce problème . Mes différentes recherches sur le forum ne m’ont mené à rien, et malheureusement, je ne suis pas assez doué en serveur pour trouver tout seul (mais j’essaie d’apprendre).

Pensez vous pouvoir m’aider (si il manque certains logs n’hésitez pas à me demander.)

2

Salut !

Si tu arrives à te connecter en ssh, est-ce que tu peux indiquer ce que retourne la commande:

# systemctl list-dependencies

Pour voir s’il y a des services failed (en rouge)

3

En failed (rouge) j’ai networking.service

EN gris j’ai : display-manager.service, systemd-update-runlevel.service, yunoprompt.service, grafana-server.service, nscd.service, rmilter.service, rsync.service, tmp.mount

4

Pas bon signe ça veut dire qu’il y a un problème avec le routage.

Peux tu regarder ce qui s’ajoute dans le fichier /var/log/syslog quand tu exécutes la commande:
systemd start networking.service

5

J’ai ça

Oct 12 14:54:22 ns384042 mysqld[1017]: 2018-10-12 14:54:22 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:22 ns384042 mysqld[1017]: 2018-10-12 14:54:22 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:55 ns384042 mysqld[1017]: 2018-10-12 14:54:55 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:55 ns384042 mysqld[1017]: 2018-10-12 14:54:55 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:55 ns384042 mysqld[1017]: 2018-10-12 14:54:55 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e0384700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e0384700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e0384700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e0384700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e0384700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e0384700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e0384700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:54:56 ns384042 mysqld[1017]: 2018-10-12 14:54:56 6358e03b0700 InnoDB: Error: Column last_update in table “mysql”.“innodb_table_stats” is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Oct 12 14:55:01 ns384042 CRON[17684]: (root) CMD (/usr/local/rtm/bin/rtm 44 > /dev/null 2> /dev/null)
Oct 12 14:55:08 ns384042 dovecot: imap-login: Disconnected (auth failed, 1 attempts in 6 secs): user=, method=PLAIN, rip=91.98.111.100, lip=46.105.121.58, TLS, session=

Je n’ai pas tout mis du fichier, je n’y comprends pas grand chose en soit

1 Like
6

J’ai fait un systemctl start networking.service au lieu de systemd

J’ai eu plus d’info dans le log du coup :slight_smile:
Oct 12 15:06:01 ns384042 CRON[18582]: (root) CMD (/usr/local/rtm/bin/rtm 44 > /dev/null 2> /dev/null)
Oct 12 15:06:06 ns384042 named[767]: REFUSED unexpected RCODE resolving ‘ns4.highsecure.ru/AAAA/IN’: 208.79.240.3#53
Oct 12 15:06:06 ns384042 named[767]: REFUSED unexpected RCODE resolving ‘ns4.highsecure.ru/A/IN’: 208.79.240.3#53
Oct 12 15:06:07 ns384042 named[767]: REFUSED unexpected RCODE resolving ‘ns1.highsecure.ru/AAAA/IN’: 2607:fe70:0:3::b#53
Oct 12 15:06:07 ns384042 named[767]: REFUSED unexpected RCODE resolving ‘ns1.highsecure.ru/AAAA/IN’: 208.79.240.3#53
Oct 12 15:06:21 ns384042 systemd[1]: Starting Raise network interfaces…
Oct 12 15:06:21 ns384042 ifup[18657]: RTNETLINK answers: File exists
Oct 12 15:06:21 ns384042 ifup[18657]: ifup: failed to bring up eth0
Oct 12 15:06:21 ns384042 named[767]: received control channel command ‘reconfig’
Oct 12 15:06:21 ns384042 named[767]: loading configuration from ‘/etc/bind/named.conf’
Oct 12 15:06:21 ns384042 named[767]: reading built-in trusted keys from file ‘/etc/bind/bind.keys’
Oct 12 15:06:21 ns384042 named[767]: GeoIP Country (IPv4) (type 1) DB not available
Oct 12 15:06:21 ns384042 named[767]: GeoIP Country (IPv6) (type 12) DB not available
Oct 12 15:06:21 ns384042 named[767]: GeoIP City (IPv4) (type 2) DB not available
Oct 12 15:06:21 ns384042 named[767]: GeoIP City (IPv4) (type 6) DB not available
Oct 12 15:06:21 ns384042 named[767]: GeoIP City (IPv6) (type 30) DB not available
Oct 12 15:06:21 ns384042 named[767]: GeoIP City (IPv6) (type 31) DB not available
Oct 12 15:06:21 ns384042 named[767]: GeoIP Region (type 3) DB not available
Oct 12 15:06:21 ns384042 named[767]: GeoIP Region (type 7) DB not available
Oct 12 15:06:21 ns384042 named[767]: GeoIP ISP (type 4) DB not available
Oct 12 15:06:21 ns384042 named[767]: GeoIP Org (type 5) DB not available
Oct 12 15:06:21 ns384042 named[767]: GeoIP AS (type 9) DB not available
Oct 12 15:06:21 ns384042 named[767]: GeoIP Domain (type 11) DB not available
Oct 12 15:06:21 ns384042 named[767]: GeoIP NetSpeed (type 10) DB not available
Oct 12 15:06:21 ns384042 named[767]: using default UDP/IPv4 port range: [32768, 61000]
Oct 12 15:06:21 ns384042 named[767]: using default UDP/IPv6 port range: [32768, 61000]
Oct 12 15:06:21 ns384042 named[767]: sizing zone task pool based on 5 zones
Oct 12 15:06:21 ns384042 named[767]: using built-in root key for view _default
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 10.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 16.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 17.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 18.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 19.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 20.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 21.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 22.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 23.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 24.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 25.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 26.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 27.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 28.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 29.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 30.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 31.172.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 168.192.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 64.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 65.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 66.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 67.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 68.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 69.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 70.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 71.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 72.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 73.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 74.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 75.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 76.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 77.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 78.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 79.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 80.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 81.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 82.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 83.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 84.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 85.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 86.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 87.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 88.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 89.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 90.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 91.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 92.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 93.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 94.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 95.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 96.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 97.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 98.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 99.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 100.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 101.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 102.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 103.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 104.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 105.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 106.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 107.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 108.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 109.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 110.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 111.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 112.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 113.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 114.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 115.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 116.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 117.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 118.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 119.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 120.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 121.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 122.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 123.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 124.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 125.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 126.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 127.100.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 254.169.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: D.F.IP6.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 8.E.F.IP6.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 9.E.F.IP6.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: A.E.F.IP6.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: B.E.F.IP6.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Oct 12 15:06:21 ns384042 named[767]: automatic empty zone: EMPTY.AS112.ARPA
Oct 12 15:06:21 ns384042 named[767]: configuring command channel from ‘/etc/bind/rndc.key’
Oct 12 15:06:21 ns384042 named[767]: configuring command channel from ‘/etc/bind/rndc.key’
Oct 12 15:06:21 ns384042 named[767]: reloading configuration succeeded
Oct 12 15:06:21 ns384042 named[767]: any newly configured zones are now loaded
Oct 12 15:06:26 ns384042 systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Oct 12 15:06:26 ns384042 systemd[1]: Failed to start Raise network interfaces.
Oct 12 15:06:26 ns384042 systemd[1]: networking.service: Unit entered failed state.
Oct 12 15:06:26 ns384042 systemd[1]: networking.service: Failed with result ‘exit-code’.
Oct 12 15:06:30 ns384042 dovecot: imap-login: Disconnected (auth failed, 1 attempts in 6 secs): user=, method=PLAIN, rip=110.136.205.216, lip=46.105.121.58, TLS, session=

7

Pour ce problème là j’avais le même, pas sûr que ce soit grave, mais ça pollue le log,

J’ai regardé ici:

C’est un problème à priori dû à une migration de mysql qui s’est mal passée.
Il ‘suffit’ de refaire un export de la table mysql et la réimporter.

On l’exporte (user=root, le mot de passe à utiliser est indiqué dans le fichier /etc/yunohost/mysql)
mysqldump --events --quick --single-transaction --password mysql > mysql-dump.sql

ensuite:

mysql --password < mysql-dump.sql

puis on redémarre le service mysql:

service mysql restart
1 Like
8

Oui c’est mieux :smile: j’ai confondu les 2

La command ifup n’arrive pas à monter l’interface réseau eth0, il faudrait savoir pourquoi

D’après networking - Solving “RTNETLINK answers: File exists” when running ifup - Raspberry Pi Stack Exchange il est possible qu’il y ait 2 gateways de configurées.

Peux-tu copier/coller le contenu de /etc/network/interfaces ?

9

This file describes the network interfaces available on your system

and how to activate them. For more information, see interfaces(5).

The loopback network interface

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 46.105.121.58
netmask 255.255.255.0
network 46.105.121.0
broadcast 46.105.121.255
gateway 46.105.121.254

iface eth0 inet6 static
address 2001:41d0:0002:e83a::
netmask 64
dns-nameservers 2001:41d0:3:163::1
post-up sleep 5; /sbin/ip -family inet6 route add 2001:41d0:0002:e8ff:ff:ff:ff:ff dev eth0
post-up sleep 5; /sbin/ip -family inet6 route add default via 2001:41d0:0002:e8ff:ff:ff:ff:ff
pre-down /sbin/ip -family inet6 route del default via 2001:41d0:0002:e8ff:ff:ff:ff:ff
pre-down /sbin/ip -family inet6 route del 2001:41d0:0002:e8ff:ff:ff:ff:ff dev eth0

10

Je ne vois rien qui saute aux yeux dans ce fichier.

Est-ce que tu peux essayer:

ifup eth0 -vvv

voir si on a un message d’erreur explicite

11

Voila :
root@ns384042:~# ifup eth0 -vvv

ifup: configuring interface eth0=eth0 (inet)
/bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/ethtool
run-parts: executing /etc/network/if-pre-up.d/vlan
/bin/ip addr add 46.105.121.58/255.255.255.0 broadcast 46.105.121.255 dev eth0 label eth0
RTNETLINK answers: File exists
ifup: failed to bring up eth0

12

Pas d’erreur évidente.

Que donne la commande?

ifconfig

Pour voir l’état des interfaces réseaux déjà montées

13

Ca donne ça :

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 46.105.121.58 netmask 255.255.255.0 broadcast 46.105.121.255
inet6 fe80::225:90ff:fe23:12b8 prefixlen 64 scopeid 0x20
inet6 2001:41d0:2:e83a:: prefixlen 64 scopeid 0x0
ether 00:25:90:23:12:b8 txqueuelen 1000 (Ethernet)
RX packets 322541 bytes 54354262 (51.8 MiB)
RX errors 0 dropped 288 overruns 0 frame 0
TX packets 388066 bytes 274775105 (262.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xfbce0000-fbd00000

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 0 (Boucle locale)
RX packets 376062 bytes 247010334 (235.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 376062 bytes 247010334 (235.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

14

Cela prouve que l’interface eth0 est déjà UP RUNNING.

Donc c’est normal qu’on ait une erreur si on essaie de refaire un ifup.

Il faut que je regarde ce que j’ai sur ma brique dans le fichier interface.
J’ai l’impression que sur ta carte on essaie de monter 2 fois les interfaces réseaux.

15

Chez moi les IP sont dynamiques

auto eth0
allow-hotplug eth0
iface eth0 inet dhcp

Là je suis sec pour chercher quoi investiguer dasn ta configuration :frowning:

16

Mince, je sais vraiment pas comment je vais pouvoir résoudre ce problème et recupérer mon nextcloud :’(

Merci pour tes tentatives d’aide en tout cas