io.xml et rules.xml sont vides

[mifrey]

Bonjour a tous,

Apres avoir reboote mon Raspberry, Calaos Server ne demarrait plus :

Code:

root@raspberrypi:~# systemctl restart calaos-server
root@raspberrypi:~# systemctl status calaos-server
calaos-server.service - Calaos home automation server service
   Loaded: loaded (/lib/systemd/system/calaos-server.service; enabled)
   Active: failed (Result: start-limit) since Thu 1970-01-01 01:02:02 CET; 46 years 1 months ago
  Process: 267 ExecStart=/usr/bin/calaos_server --config /etc/calaos --cache /home/root/.cache/calaos (code=exited, status=255)
  Process: 264 ExecStartPre=/bin/mkdir -p /home/root/.cache/calaos /etc/calaos (code=exited, status=0/SUCCESS)
 Main PID: 267 (code=exited, status=255)

Jan 01 01:02:02 raspberrypi systemd[1]: calaos-server.service: main process exited, code=exited, status=255/n/a
Jan 01 01:02:02 raspberrypi systemd[1]: calaos-server.service changed running -> failed
Jan 01 01:02:02 raspberrypi systemd[1]: Unit calaos-server.service entered failed state.
Jan 01 01:02:02 raspberrypi systemd[1]: calaos-server.service changed failed -> auto-restart
Jan 01 01:02:02 raspberrypi systemd[1]: calaos-server.service holdoff time over, scheduling restart.
Jan 01 01:02:02 raspberrypi systemd[1]: Trying to enqueue job calaos-server.service/restart/fail
Jan 01 01:02:02 raspberrypi systemd[1]: Starting Calaos home automation server service...
Jan 01 01:02:02 raspberrypi systemd[1]: calaos-server.service start request repeated too quickly, refusing to start.
Jan 01 01:02:02 raspberrypi systemd[1]: Failed to start Calaos home automation server service.
Jan 01 01:02:02 raspberrypi systemd[1]: Unit calaos-server.service entered failed state.

Code:

root@raspberrypi:~# journalctl -lu calaos-server
-- Logs begin at Thu 1970-01-01 01:00:05 CET, end at Wed 2016-02-10 05:22:54 CET. --
Jan 01 01:02:00 raspberrypi systemd[1]: Trying to enqueue job calaos-server.service/restart/replace
Jan 01 01:02:00 raspberrypi systemd[1]: Installed new job calaos-server.service/restart as 477
Jan 01 01:02:00 raspberrypi systemd[1]: Enqueued job calaos-server.service/restart as 477
Jan 01 01:02:00 raspberrypi systemd[1]: Job calaos-server.service/restart finished, result=done
Jan 01 01:02:00 raspberrypi systemd[1]: Converting job calaos-server.service/restart -> calaos-server.service/start
Jan 01 01:02:00 raspberrypi systemd[1]: Starting Calaos home automation server service...
Jan 01 01:02:00 raspberrypi systemd[1]: About to execute: /bin/mkdir -p /home/root/.cache/calaos /etc/calaos
Jan 01 01:02:00 raspberrypi systemd[1]: Forked /bin/mkdir as 244
Jan 01 01:02:00 raspberrypi systemd[1]: calaos-server.service changed failed -> start-pre
Jan 01 01:02:00 raspberrypi systemd[1]: Child 244 belongs to calaos-server.service
Jan 01 01:02:00 raspberrypi systemd[1]: calaos-server.service: control process exited, code=exited status=0
Jan 01 01:02:00 raspberrypi systemd[1]: calaos-server.service got final SIGCHLD for state start-pre
Jan 01 01:02:00 raspberrypi systemd[1]: About to execute: /usr/bin/calaos_server --config /etc/calaos --cache /home/root/.cache/calaos
Jan 01 01:02:00 raspberrypi systemd[1]: Forked /usr/bin/calaos_server as 247
Jan 01 01:02:00 raspberrypi systemd[247]: Executing: /usr/bin/calaos_server --config /etc/calaos --cache /home/root/.cache/calaos
Jan 01 01:02:00 raspberrypi systemd[1]: Started Calaos home automation server service.
Jan 01 01:02:00 raspberrypi systemd[1]: Child 247 belongs to calaos-server.service
Jan 01 01:02:00 raspberrypi systemd[1]: [[1;39mcalaos-server.service: main process exited, code=exited, status=255/n/a[[0m
Jan 01 01:02:00 raspberrypi systemd[1]: calaos-server.service changed running -> failed
Jan 01 01:02:00 raspberrypi systemd[1]: [[1;39mUnit calaos-server.service entered failed state.[[0m
Jan 01 01:02:00 raspberrypi systemd[1]: calaos-server.service changed failed -> auto-restart
Jan 01 01:02:00 raspberrypi systemd[1]: calaos-server.service holdoff time over, scheduling restart.
Jan 01 01:02:00 raspberrypi systemd[1]: Trying to enqueue job calaos-server.service/restart/fail
Jan 01 01:02:00 raspberrypi systemd[1]: Installed new job calaos-server.service/restart as 531
Jan 01 01:02:00 raspberrypi systemd[1]: calaos-server.service scheduled restart job.
Jan 01 01:02:00 raspberrypi systemd[1]: Job calaos-server.service/restart finished, result=done
Jan 01 01:02:00 raspberrypi systemd[1]: Converting job calaos-server.service/restart -> calaos-server.service/start
Jan 01 01:02:00 raspberrypi systemd[1]: calaos-server.service got final SIGCHLD for state start-pre
Jan 01 01:02:00 raspberrypi systemd[1]: About to execute: /usr/bin/calaos_server --config /etc/calaos --cache /home/root/.cache/calaos
Jan 01 01:02:00 raspberrypi systemd[1]: Forked /usr/bin/calaos_server as 252
Jan 01 01:02:00 raspberrypi systemd[252]: Executing: /usr/bin/calaos_server --config /etc/calaos --cache /home/root/.cache/calaos
Jan 01 01:02:00 raspberrypi systemd[1]: calaos-server.service changed start-pre -> running
Jan 01 01:02:00 raspberrypi systemd[1]: Job calaos-server.service/start finished, result=done
Jan 01 01:02:00 raspberrypi systemd[1]: Started Calaos home automation server service.
Jan 01 01:02:01 raspberrypi systemd[1]: Child 252 belongs to calaos-server.service
Jan 01 01:02:01 raspberrypi systemd[1]: [[1;39mcalaos-server.service: main process exited, code=exited, status=255/n/a[[0m
Jan 01 01:02:01 raspberrypi systemd[1]: calaos-server.service changed running -> failed
Jan 01 01:02:01 raspberrypi systemd[1]: [[1;39mUnit calaos-server.service entered failed state.[[0m
Jan 01 01:02:01 raspberrypi systemd[1]: calaos-server.service changed failed -> auto-restart
Jan 01 01:02:01 raspberrypi systemd[1]: calaos-server.service holdoff time over, scheduling restart.
Jan 01 01:02:01 raspberrypi systemd[1]: Trying to enqueue job calaos-server.service/restart/fail
Jan 01 01:02:01 raspberrypi systemd[1]: Installed new job calaos-server.service/restart as 585
Jan 01 01:02:01 raspberrypi systemd[1]: Child 254 belongs to calaos-server.service
Jan 01 01:02:01 raspberrypi systemd[1]: calaos-server.service: control process exited, code=exited status=0
Jan 01 01:02:01 raspberrypi systemd[1]: calaos-server.service got final SIGCHLD for state start-pre
Jan 01 01:02:01 raspberrypi systemd[1]: About to execute: /usr/bin/calaos_server --config /etc/calaos --cache /home/root/.cache/calaos
Jan 01 01:02:01 raspberrypi systemd[1]: calaos-server.service changed start-pre -> running
Jan 01 01:02:01 raspberrypi systemd[1]: Started Calaos home automation server service.
Jan 01 01:02:01 raspberrypi systemd[1]: Child 257 belongs to calaos-server.service
Jan 01 01:02:01 raspberrypi systemd[1]: [[1;39mcalaos-server.service: main process exited, code=exited, status=255/n/a[[0m
Jan 01 01:02:01 raspberrypi systemd[1]: calaos-server.service changed running -> failed
Jan 01 01:02:01 raspberrypi systemd[1]: [[1;39mUnit calaos-server.service entered failed state.[[0m
Jan 01 01:02:01 raspberrypi systemd[1]: calaos-server.service changed failed -> auto-restart
Jan 01 01:02:01 raspberrypi systemd[1]: calaos-server.service holdoff time over, scheduling restart.
Jan 01 01:02:01 raspberrypi systemd[1]: Trying to enqueue job calaos-server.service/restart/fail
Jan 01 01:02:01 raspberrypi systemd[1]: Installed new job calaos-server.service/restart as 639
Jan 01 01:02:01 raspberrypi systemd[1]: calaos-server.service scheduled restart job.
Jan 01 01:02:01 raspberrypi systemd[1]: Stopping Calaos home automation server service...
Jan 01 01:02:01 raspberrypi systemd[1]: calaos-server.service changed auto-restart -> dead
Jan 01 01:02:01 raspberrypi systemd[1]: Job calaos-server.service/restart finished, result=done
Jan 01 01:02:01 raspberrypi systemd[1]: About to execute: /bin/mkdir -p /home/root/.cache/calaos /etc/calaos
Jan 01 01:02:01 raspberrypi systemd[1]: Forked /bin/mkdir as 259
Jan 01 01:02:01 raspberrypi systemd[1]: Child 259 belongs to calaos-server.service
Jan 01 01:02:01 raspberrypi systemd[1]: calaos-server.service: control process exited, code=exited status=0
Jan 01 01:02:01 raspberrypi systemd[1]: Forked /usr/bin/calaos_server as 262
Jan 01 01:02:01 raspberrypi systemd[1]: calaos-server.service changed start-pre -> running
Jan 01 01:02:01 raspberrypi systemd[1]: Job calaos-server.service/start finished, result=done
Jan 01 01:02:01 raspberrypi systemd[1]: Started Calaos home automation server service.
Jan 01 01:02:02 raspberrypi systemd[1]: Child 262 belongs to calaos-server.service
Jan 01 01:02:02 raspberrypi systemd[1]: [[1;39mcalaos-server.service: main process exited, code=exited, status=255/n/a[[0m
Jan 01 01:02:02 raspberrypi systemd[1]: calaos-server.service changed running -> failed
Jan 01 01:02:02 raspberrypi systemd[1]: [[1;39mUnit calaos-server.service entered failed state.[[0m
Jan 01 01:02:02 raspberrypi systemd[1]: calaos-server.service changed failed -> auto-restart
Jan 01 01:02:02 raspberrypi systemd[1]: calaos-server.service holdoff time over, scheduling restart.
Jan 01 01:02:02 raspberrypi systemd[1]: Trying to enqueue job calaos-server.service/restart/fail
Jan 01 01:02:02 raspberrypi systemd[1]: Installed new job calaos-server.service/restart as 693
Jan 01 01:02:02 raspberrypi systemd[1]: Child 264 belongs to calaos-server.service
Jan 01 01:02:02 raspberrypi systemd[1]: calaos-server.service: control process exited, code=exited status=0
Jan 01 01:02:02 raspberrypi systemd[1]: calaos-server.service got final SIGCHLD for state start-pre
Jan 01 01:02:02 raspberrypi systemd[1]: About to execute: /usr/bin/calaos_server --config /etc/calaos --cache /home/root/.cache/calaos
Jan 01 01:02:02 raspberrypi systemd[267]: Executing: /usr/bin/calaos_server --config /etc/calaos --cache /home/root/.cache/calaos
Jan 01 01:02:02 raspberrypi systemd[1]: Job calaos-server.service/start finished, result=done
Jan 01 01:02:02 raspberrypi systemd[1]: Started Calaos home automation server service.
Jan 01 01:02:02 raspberrypi systemd[1]: Child 267 belongs to calaos-server.service
Jan 01 01:02:02 raspberrypi systemd[1]: [[1;39mcalaos-server.service: main process exited, code=exited, status=255/n/a[[0m
Jan 01 01:02:02 raspberrypi systemd[1]: calaos-server.service changed running -> failed
Jan 01 01:02:02 raspberrypi systemd[1]: [[1;39mUnit calaos-server.service entered failed state.[[0m
Jan 01 01:02:02 raspberrypi systemd[1]: calaos-server.service changed failed -> auto-restart
Jan 01 01:02:02 raspberrypi systemd[1]: calaos-server.service holdoff time over, scheduling restart.
Jan 01 01:02:02 raspberrypi systemd[1]: Trying to enqueue job calaos-server.service/restart/fail
Jan 01 01:02:02 raspberrypi systemd[1]: Starting Calaos home automation server service...
Jan 01 01:02:02 raspberrypi systemd[1]: [[1;39mcalaos-server.service start request repeated too quickly, refusing to start.[[0m
Jan 01 01:02:02 raspberrypi systemd[1]: [[1;31mFailed to start Calaos home automation server service.[[0m
Jan 01 01:02:02 raspberrypi systemd[1]: [[1;39mUnit calaos-server.service entered failed state.[[0m

J'ai cherche et remarque que les fichiers io.xml et rules.xml etaient vide. Ils semblent avoir ete modifies au demarrage de Calaos Server (annee 1970) mais j'ai remarque que la date de ces 2 fichiers changait a chaque fois que Calaos Server demarrait.

Code:

root@raspberrypi:~# ls -la  /etc/calaos/
drwxr-xr-x    2 root     root          1024 Jan  1  1970 .
drwxr-xr-x   45 root     root          2048 Feb 10 05:13 ..
-rw-r--r--    1 root     root             0 Jan  1  1970 io.xml
-rw-r--r--    1 root     root          1015 Jan  4 12:52 local_config.xml
-rw-r--r--    1 root     root             0 Jan  1  1970 rules.xml
-rw-r--r--    1 root     root            95 Jan  1  1970 widgets.xml

J'ai recopie les fichiers de mon dernier backup et tout remarche comme avant.

Questions :

1. Qu'est-ce qui a bien pu se passer pour que io.xml et rules.xml deviennent vides ?
   
2. Est-ce normal que la date de io.xml et rules.xml change a chaque fois que Calaos Server demarre ?
   

[raoulh]

Comment as tu rebootéton Rpi? en debranchant le cable ou en tapant reboot en console?

[mifrey]

Il a reboote suite a une coupure de courant.

[raoulh]

Donc les fichiers ont du etre ecrit au moment de la coupure.
Il faut onduler ton serveur pour pas avoir de pb.

[mifrey]

Ok mais est-ce normal que ces fichiers sont ecrits par autre chose que Calaos Installer et si oui par quoi et dans quels cas ?

J'ai remarque que ces fichiers changent de date mais pas de contenu a chaque demarrage de Calaos Server mais plus apres. Est-ce que ces fichiers sont reecrits ? Si oui, il est possible que qu'il y ait eu 2 coupures de courant successives dont la 2e qui s'est produite pendant le redemarrage de Calaos Server apres la 1ere coupure ?

[raoulh]

Oui calaos_server lit la config au demarrage et la reecrit juste apres pour avoir une version valide. Il la reecrit aussi quand il a besoin (quand quelque chose change comme les IO interne qui sont modifiés avec le parametre save=true par ex, ou encore quand tu utilises les scenarios automatiques ou des regles sont crées a la volée, etc...)

Donc oui calaos_server ecrit regulierement les fichiers et au minimum une fois au lancement.

A terme, on va surement faire disparaitre ces fichiers de calaos_installer et uniquement laisser calaos_server toucher a ces fichiers de config.