Installation Calaos_OS sur VM puis sur NUC

[pitixorms]

Il faut regarder ce que dit le log de calaos-server....

root@intel-corei7-64:~# vi calaos-server.log
-- Logs begin at Sun 2020-11-08 12:30:11 UTC, end at Sun 2020-11-08 12:38:05 UTC. --
Nov 08 12:30:13 intel-corei7-64 systemd[1]: Starting Calaos home automation server service...
Nov 08 12:30:13 intel-corei7-64 systemd[1]: Started Calaos home automation server service.
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]:  ╔═══════════════════════════════════════════════╗
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]:  ║                                               ║
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]:  ║  Calaos Server Daemon - http://www.calaos.fr  ║
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]:  ║    v3.0-rc1-93-g81b6f0e6                      ║
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]:  ╚═══════════════════════════════════════════════╝
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]: Using config path: /etc/calaos/
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]: Using cache path: /home/root/.cache/calaos/
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]: [INF] server (Prefix.cpp:26) Binaries directory is: /usr/bin
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]: [INF] server (Prefix.cpp:27) Libraries directory is: /usr/lib
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]: [INF] server (Prefix.cpp:28) Data directory is: /usr/share/calaos
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]: [INF] history (HistLogger.cpp:189) History logger, setup database to /home/root/.cache/calaos/events.db
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]: [INF] server (CalaosConfig.cpp:246) States cache read successfully.
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]: [ERR] server (CalaosConfig.cpp:54) There was a parse error
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]: [ERR] server (CalaosConfig.cpp:55) Error document empty.
Nov 08 12:30:13 intel-corei7-64 calaos_server[548]: [ERR] server (CalaosConfig.cpp:56) In file /etc/calaos/io.xml At line 0
Nov 08 12:30:13 intel-corei7-64 systemd[1]: calaos-server.service: Main process exited, code=exited, status=255/EXCEPTION
Nov 08 12:30:13 intel-corei7-64 systemd[1]: calaos-server.service: Failed with result 'exit-code'.
Nov 08 12:30:13 intel-corei7-64 systemd[1]: calaos-server.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 12:30:13 intel-corei7-64 systemd[1]: calaos-server.service: Scheduled restart job, restart counter is at 1.
Nov 08 12:30:13 intel-corei7-64 systemd[1]: Stopped Calaos home automation server service.
Nov 08 12:30:13 intel-corei7-64 systemd[1]: Starting Calaos home automation server service...
Nov 08 12:30:13 intel-corei7-64 systemd[1]: Started Calaos home automation server service.
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]:  ╔═══════════════════════════════════════════════╗
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]:  ║                                               ║
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]:  ║  Calaos Server Daemon - http://www.calaos.fr  ║
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]:  ║    v3.0-rc1-93-g81b6f0e6                      ║
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]:  ╚═══════════════════════════════════════════════╝
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]: Using config path: /etc/calaos/
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]: Using cache path: /home/root/.cache/calaos/
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]: [INF] server (Prefix.cpp:26) Binaries directory is: /usr/bin
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]: [INF] server (Prefix.cpp:27) Libraries directory is: /usr/lib
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]: [INF] server (Prefix.cpp:28) Data directory is: /usr/share/calaos
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]: [INF] server (CalaosConfig.cpp:246) States cache read successfully.
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]: [ERR] server (CalaosConfig.cpp:54) There was a parse error
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]: [ERR] server (CalaosConfig.cpp:55) Error document empty.
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]: [ERR] server (CalaosConfig.cpp:56) In file /etc/calaos/io.xml At line 0
Nov 08 12:30:13 intel-corei7-64 calaos_server[631]: [INF] history (HistLogger.cpp:189) History logger, setup database to /home/root/.cache/calaos/events.db
Nov 08 12:30:13 intel-corei7-64 systemd[1]: calaos-server.service: Main process exited, code=exited, status=255/EXCEPTION
Nov 08 12:30:13 intel-corei7-64 systemd[1]: calaos-server.service: Failed with result 'exit-code'.
Nov 08 12:30:13 intel-corei7-64 systemd[1]: calaos-server.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 12:30:13 intel-corei7-64 systemd[1]: calaos-server.service: Scheduled restart job, restart counter is at 2.
Nov 08 12:30:13 intel-corei7-64 systemd[1]: Stopped Calaos home automation server service.
Nov 08 12:30:13 intel-corei7-64 systemd[1]: Starting Calaos home automation server service...
Nov 08 12:30:13 intel-corei7-64 systemd[1]: Started Calaos home automation server service.
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]:  ╔═══════════════════════════════════════════════╗
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]:  ║                                               ║
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]:  ║  Calaos Server Daemon - http://www.calaos.fr  ║
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]:  ║    v3.0-rc1-93-g81b6f0e6                      ║
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]:  ╚═══════════════════════════════════════════════╝
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]: Using config path: /etc/calaos/
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]: Using cache path: /home/root/.cache/calaos/
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]: [INF] server (Prefix.cpp:26) Binaries directory is: /usr/bin
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]: [INF] server (Prefix.cpp:27) Libraries directory is: /usr/lib
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]: [INF] server (Prefix.cpp:28) Data directory is: /usr/share/calaos
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]: [INF] server (CalaosConfig.cpp:246) States cache read successfully.
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]: [ERR] server (CalaosConfig.cpp:54) There was a parse error
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]: [ERR] server (CalaosConfig.cpp:55) Error document empty.
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]: [ERR] server (CalaosConfig.cpp:56) In file /etc/calaos/io.xml At line 0
Nov 08 12:30:13 intel-corei7-64 calaos_server[634]: [INF] history (HistLogger.cpp:189) History logger, setup database to /home/root/.cache/calaos/events.db
Nov 08 12:30:13 intel-corei7-64 systemd[1]: calaos-server.service: Main process exited, code=exited, status=255/EXCEPTION
Nov 08 12:30:13 intel-corei7-64 systemd[1]: calaos-server.service: Failed with result 'exit-code'.
Nov 08 12:30:13 intel-corei7-64 systemd[1]: calaos-server.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 12:30:13 intel-corei7-64 systemd[1]: calaos-server.service: Scheduled restart job, restart counter is at 3.
- calaos-server.log 1/114 0%


Il me remonte une erreur avec le WAGO :


root@intel-corei7-64:~#  systemctl status calaos-server
● calaos-server.service - Calaos home automation server service
   Loaded: loaded (/lib/systemd/system/calaos-server.service; enabled; vendor p>
   Active: active (running) since Sun 2020-11-08 12:50:09 UTC; 1min 2s ago
  Process: 560 ExecStartPre=/bin/mkdir -p /home/root/.cache/calaos /etc/calaos >
 Main PID: 562 (calaos_server)
    Tasks: 3 (limit: 4915)
   Memory: 11.2M
   CGroup: /system.slice/calaos-server.service
           ├─562 /usr/bin/calaos_server --config /etc/calaos --cache /home/root>
           └─633 /usr/bin/calaos_wago --socket /tmp/calaos_proc_cc04920b-9cd8-f>

Nov 08 12:51:01 intel-corei7-64 calaos_server[562]: [ERR] wago (WagoExternProc_>
Nov 08 12:51:01 intel-corei7-64 calaos_server[562]: [ERR] wago (WagoMap.cpp:140>
Nov 08 12:51:02 intel-corei7-64 calaos_server[562]: [INF] wago (WagoExternProc_>
Nov 08 12:51:04 intel-corei7-64 calaos_server[562]: [ERR] wago (WagoCtrl.cpp:67>
Nov 08 12:51:05 intel-corei7-64 calaos_server[562]: [INF] wago (WagoExternProc_>
Nov 08 12:51:07 intel-corei7-64 calaos_server[562]: [ERR] wago (WagoCtrl.cpp:67>
Nov 08 12:51:08 intel-corei7-64 calaos_server[562]: [INF] wago (WagoExternProc_>
Nov 08 12:51:09 intel-corei7-64 calaos_server[562]: [INF] server (CalaosConfig.>
Nov 08 12:51:10 intel-corei7-64 calaos_server[562]: [ERR] wago (WagoCtrl.cpp:67>
Nov 08 12:51:10 intel-corei7-64 calaos_server[562]: [WRN] wago (WagoExternProc_>

[raoulh]

Met le fichier de log en entier sur le forum (en fichier attaché au post) car la tu n'as qu'une tout petite partie qui ne nous interesse pas...

[pitixorms]

Met le fichier de log en entier sur le forum (en fichier attaché au post) car la tu n'as qu'une tout petite partie qui ne nous interesse pas...

Le problème c'est que pour ca il faudrait que le serveur me laisse entrer avec un FTP... et ni Winscp ni Filezilla ne me laisse entrer...

[raoulh]

il n'y pas de ftp sur calaos-os...
Il y a juste SSH, et winscp fait du SCP. Il faut se connecter avec "root" et mot de passe vide.

Et sinon avec la commande journalctl, tu dois descendre tout en bas avec les fleches du clavier, car la, a chaque fois tu nous donne le debut du log qui est un vieux log, il nous faut la fin...

[pitixorms]

il n'y pas de ftp sur calaos-os...
Il y a juste SSH, et winscp fait du SCP. Il faut se connecter avec "root" et mot de passe vide.

Et sinon avec la commande journalctl, tu dois descendre tout en bas avec les fleches du clavier, car la, a chaque fois tu nous donne le debut du log qui est un vieux log, il nous faut la fin...

A ben voilà... c'était ca... j'essayais en FTP et SFTP....

Voilà le fichier  ==> ICI

Le serveur est bien "active"

[raoulh]

Pour le SCP je l'ai deja dit dans un post plus haut et c'est ecrit sur la doc du wiki que j'ai aussi mis dans un post plus haut

Ton lien ne marche pas, acces refusé.......

[pitixorms]

Pour le SCP je l'ai deja dit dans un post plus haut et c'est ecrit sur la doc du wiki que j'ai aussi mis dans un post plus haut

Ton lien ne marche pas, acces refusé.......

Arf... désolé.

Je repose ==> ICI


En parallèle, un extrait du journal sur 1 minute :

Nov 08 13:35:00 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:01 intel-corei7-64 calaos_server[553]: [INF] wago (WagoExternProc_main.cpp:50) Connecting to 192.168.75.240
Nov 08 13:35:02 intel-corei7-64 calaos_server[553]: [INF] websocket (WebSocket.cpp:446) Received a PONG back in 00:00
Nov 08 13:35:03 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:03 intel-corei7-64 calaos_server[553]: [WRN] wago (WagoExternProc_main.cpp:92) Wago MBUS, Reconnecting to host 192.168.75.240
Nov 08 13:35:07 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:07 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoExternProc_main.cpp:96) Wago MBUS, failed to send request
Nov 08 13:35:07 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoMap.cpp:140) failed to read !
Nov 08 13:35:07 intel-corei7-64 systemd-journald[434]: Forwarding to syslog missed 72 messages.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Succeeded.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Succeeded.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Succeeded.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Scheduled restart job, restart counter is at 143.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Scheduled restart job, restart counter is at 143.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Scheduled restart job, restart counter is at 143.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS1.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS1.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS2.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS2.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS0.
Nov 08 13:35:07 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS0.
Nov 08 13:35:08 intel-corei7-64 calaos_server[553]: [INF] wago (WagoExternProc_main.cpp:50) Connecting to 192.168.75.240
Nov 08 13:35:10 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:11 intel-corei7-64 calaos_server[553]: [INF] wago (WagoExternProc_main.cpp:50) Connecting to 192.168.75.240
Nov 08 13:35:12 intel-corei7-64 calaos_server[553]: [INF] server (CalaosConfig.cpp:276) State cache file written successfully (/home/root/.cache/calaos/iostates.cache)
Nov 08 13:35:13 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:13 intel-corei7-64 calaos_server[553]: [WRN] wago (WagoExternProc_main.cpp:92) Wago MBUS, Reconnecting to host 192.168.75.240
Nov 08 13:35:16 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:16 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoExternProc_main.cpp:96) Wago MBUS, failed to send request
Nov 08 13:35:16 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoMap.cpp:140) failed to read !
Nov 08 13:35:17 intel-corei7-64 calaos_server[553]: [INF] wago (WagoExternProc_main.cpp:50) Connecting to 192.168.75.240
Nov 08 13:35:17 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Succeeded.
Nov 08 13:35:17 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Succeeded.
Nov 08 13:35:17 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Succeeded.
Nov 08 13:35:17 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:17 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Scheduled restart job, restart counter is at 144.
Nov 08 13:35:17 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:17 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Scheduled restart job, restart counter is at 144.
Nov 08 13:35:17 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:17 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Scheduled restart job, restart counter is at 144.
Nov 08 13:35:17 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS0.
Nov 08 13:35:17 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS0.
Nov 08 13:35:17 intel-corei7-64 calaos_server[553]: [INF] websocket (WebSocket.cpp:446) Received a PONG back in 00:00
Nov 08 13:35:17 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS1.
Nov 08 13:35:17 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS1.
Nov 08 13:35:17 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS2.
Nov 08 13:35:17 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS2.
Nov 08 13:35:19 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:20 intel-corei7-64 calaos_server[553]: [INF] wago (WagoExternProc_main.cpp:50) Connecting to 192.168.75.240
Nov 08 13:35:22 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:23 intel-corei7-64 calaos_server[553]: [WRN] wago (WagoExternProc_main.cpp:92) Wago MBUS, Reconnecting to host 192.168.75.240
Nov 08 13:35:25 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:25 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoExternProc_main.cpp:96) Wago MBUS, failed to send request
Nov 08 13:35:25 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoMap.cpp:140) failed to read !
Nov 08 13:35:26 intel-corei7-64 calaos_server[553]: [INF] wago (WagoExternProc_main.cpp:50) Connecting to 192.168.75.240
Nov 08 13:35:27 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Succeeded.
Nov 08 13:35:27 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:27 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Scheduled restart job, restart counter is at 145.
Nov 08 13:35:27 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS0.
Nov 08 13:35:27 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS0.
Nov 08 13:35:27 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Succeeded.
Nov 08 13:35:27 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:27 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Scheduled restart job, restart counter is at 145.
Nov 08 13:35:27 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Succeeded.
Nov 08 13:35:27 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:27 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Scheduled restart job, restart counter is at 145.
Nov 08 13:35:27 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS1.
Nov 08 13:35:27 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS1.
Nov 08 13:35:27 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS2.
Nov 08 13:35:27 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS2.
Nov 08 13:35:28 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:29 intel-corei7-64 calaos_server[553]: [INF] wago (WagoExternProc_main.cpp:50) Connecting to 192.168.75.240
Nov 08 13:35:31 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:32 intel-corei7-64 calaos_server[553]: [INF] wago (WagoExternProc_main.cpp:50) Connecting to 192.168.75.240
Nov 08 13:35:32 intel-corei7-64 calaos_server[553]: [INF] websocket (WebSocket.cpp:446) Received a PONG back in 00:00
Nov 08 13:35:34 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:34 intel-corei7-64 calaos_server[553]: [WRN] wago (WagoExternProc_main.cpp:92) Wago MBUS, Reconnecting to host 192.168.75.240
Nov 08 13:35:37 intel-corei7-64 systemd-journald[434]: Forwarding to syslog missed 71 messages.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Succeeded.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Scheduled restart job, restart counter is at 146.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Succeeded.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Succeeded.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Scheduled restart job, restart counter is at 146.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Scheduled restart job, restart counter is at 146.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS2.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS2.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS1.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS1.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS0.
Nov 08 13:35:37 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS0.
Nov 08 13:35:37 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:37 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoExternProc_main.cpp:96) Wago MBUS, failed to send request
Nov 08 13:35:37 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoMap.cpp:140) failed to read !
Nov 08 13:35:38 intel-corei7-64 calaos_server[553]: [INF] wago (WagoExternProc_main.cpp:50) Connecting to 192.168.75.240
Nov 08 13:35:40 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:41 intel-corei7-64 calaos_server[553]: [INF] wago (WagoExternProc_main.cpp:50) Connecting to 192.168.75.240
Nov 08 13:35:43 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:43 intel-corei7-64 calaos_server[553]: [WRN] wago (WagoExternProc_main.cpp:92) Wago MBUS, Reconnecting to host 192.168.75.240
Nov 08 13:35:47 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:47 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoExternProc_main.cpp:96) Wago MBUS, failed to send request
Nov 08 13:35:47 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoMap.cpp:140) failed to read !
Nov 08 13:35:47 intel-corei7-64 calaos_server[553]: [INF] websocket (WebSocket.cpp:446) Received a PONG back in 00:00
Nov 08 13:35:47 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Succeeded.
Nov 08 13:35:47 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Succeeded.
Nov 08 13:35:47 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Succeeded.
Nov 08 13:35:47 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:47 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Scheduled restart job, restart counter is at 147.
Nov 08 13:35:47 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:47 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Scheduled restart job, restart counter is at 147.
Nov 08 13:35:47 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:47 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Scheduled restart job, restart counter is at 147.
Nov 08 13:35:47 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS0.
Nov 08 13:35:47 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS0.
Nov 08 13:35:47 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS1.
Nov 08 13:35:47 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS1.
Nov 08 13:35:47 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS2.
Nov 08 13:35:47 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS2.
Nov 08 13:35:48 intel-corei7-64 calaos_server[553]: [INF] wago (WagoExternProc_main.cpp:50) Connecting to 192.168.75.240
Nov 08 13:35:50 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:51 intel-corei7-64 calaos_server[553]: [INF] wago (WagoExternProc_main.cpp:50) Connecting to 192.168.75.240
Nov 08 13:35:53 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:53 intel-corei7-64 calaos_server[553]: [WRN] wago (WagoExternProc_main.cpp:92) Wago MBUS, Reconnecting to host 192.168.75.240
Nov 08 13:35:56 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:35:56 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoExternProc_main.cpp:96) Wago MBUS, failed to send request
Nov 08 13:35:56 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoMap.cpp:140) failed to read !
Nov 08 13:35:57 intel-corei7-64 calaos_server[553]: [INF] wago (WagoExternProc_main.cpp:50) Connecting to 192.168.75.240
Nov 08 13:35:57 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Succeeded.
Nov 08 13:35:57 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Succeeded.
Nov 08 13:35:57 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Succeeded.
Nov 08 13:35:57 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:57 intel-corei7-64 systemd[1]: serial-getty@ttyS0.service: Scheduled restart job, restart counter is at 148.
Nov 08 13:35:57 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:57 intel-corei7-64 systemd[1]: serial-getty@ttyS1.service: Scheduled restart job, restart counter is at 148.
Nov 08 13:35:57 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Nov 08 13:35:57 intel-corei7-64 systemd[1]: serial-getty@ttyS2.service: Scheduled restart job, restart counter is at 148.
Nov 08 13:35:57 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS2.
Nov 08 13:35:57 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS2.
Nov 08 13:35:57 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS1.
Nov 08 13:35:57 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS1.
Nov 08 13:35:57 intel-corei7-64 systemd[1]: Stopped Serial Getty on ttyS0.
Nov 08 13:35:57 intel-corei7-64 systemd[1]: Started Serial Getty on ttyS0.
Nov 08 13:35:59 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:36:00 intel-corei7-64 calaos_server[553]: [INF] wago (WagoExternProc_main.cpp:50) Connecting to 192.168.75.240
Nov 08 13:36:02 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:36:02 intel-corei7-64 calaos_server[553]: [INF] websocket (WebSocket.cpp:446) Received a PONG back in 00:00
Nov 08 13:36:03 intel-corei7-64 calaos_server[553]: [WRN] wago (WagoExternProc_main.cpp:92) Wago MBUS, Reconnecting to host 192.168.75.240
Nov 08 13:36:05 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoCtrl.cpp:67) WagoCtrl::Connect(): Can't connect...
Nov 08 13:36:05 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoExternProc_main.cpp:96) Wago MBUS, failed to send request
Nov 08 13:36:05 intel-corei7-64 calaos_server[553]: [ERR] wago (WagoMap.cpp:140) failed to read !

[raoulh]

il arrive pas a se connecter a ton wago, donc ca veut dire probleme réseau quelque part. Essaye de faire un ping depuis le ssh de calaos vers ton automate pour voir. Une piste pour toi a creuser: comment as tu configuré le reseau dans VirtualBox? Avec du NAT? avec du Bridge? il faut creuser la...

[pitixorms]

il arrive pas a se connecter a ton wago, donc ca veut dire probleme réseau quelque part. Essaye de faire un ping depuis le ssh de calaos vers ton automate pour voir. Une piste pour toi a creuser: comment as tu configuré le reseau dans VirtualBox? Avec du NAT? avec du Bridge? il faut creuser la...

Je suis en réseau privé hôte, donc ca semble logique, mais comme  j'ai essayé le bridge avec ma connexion wifi ou Ethernet locale puis le NAT, dans un cas comme dans l'autre il prend systématiquement l'adresse 10.0.2.15 malgré une conf via la SSH et putty , que ce soit en changeant l'adressage du réseau, en ajoutant et activant une Vcarte réseau sur virtualbox, etc....

Ca qui semble étrange c'est que même en changeant via putty l'adressage IP par un adressage fixe, il garde cette adresse.

Avec l'adressage de mon réseau (192.168. etc...) il n'y a qu'en réseau privé hôte qu'il prend cette conf...

Avec le réseau privé hôte, j'ai accès au réseau local et à la VM.

Par contre la VM ne voit pas le Wago du coup...

[raoulh]

Normalement pour pas t'embeter tu dois utilise le mode bridge... Et ca connecte l'interface sur ton reseau local comme si c'etait une machine...