SoftdPac - Coud not flush state contents to disk

[DP-JYC]

I'm having an issue with the softdPac not able to run on my docker of my Raspberry Pi 4.

I’m on v21.1.21139.10 and I recorded a quick video to show my issue.

Basically, I can log, I can deploy but when I run, I have a message "Deploy Timed Out".
And when I check logs, I have: "Coud not flush state contents to disk for file /var/lib/nxtSRT61499N/data/config/LastDevState.tmp"

I hope that someone is able to help me ASAP.

Hopefully, it will help others later as well.

[KarimBenameur]

I asked our expert & this error is not related to your issue. 

We encountered similar issue in the past that were linked to problems in Docker Network settings & more precisely the gateway connectivity .

You can try to do some test to check it.

If softdpac_1 is the name of your container  and EAEHost is the windows PC where the EAE BT is installed.

Check connectivity of your Soft dPAC

> docker exec -it Softdpac_1 ping EAEHostIp

On EAE Host 

ping  the Soft dPAC

> ping Softdpac_1

Please keep us updated.

[DP-JYC · Accepted solution]

Thank you @KarimBenameur for your help.

I have a bigger issue now... it's working this morning without any changes! 😮

(Note: I stopped my laptop & Raspberry Pi during the night)

My Laptop is on: 192.168.0.7

My Rasp host is on: 192.168.0.11

My Docker hosting Soft_dPac is on 192.168.0.110

My command to have a Soft_dPac on my docker is: 

./startSoftdPAC.sh --image-name softdpac:armhf-v21.1-21125-1703 --ipbase 192.168.0.110/24 --gateway 192.168.0.11 --network macvlan

From my laptop:

   ✅ I can ping the rasp host

   ✅ I can ping the docker image

From my rasp host:

   ✅ I can ping my laptop

   ❌ I can't ping the docker image

From my docker image:

   ✅ I can ping my laptop

   ❌ I can't ping the docker host

And in this setup, I can deploy without the issue of yesterday.

If it happens again, I will look at the gateway config state as you suggested.

[KarimBenameur]

You are welcome. I did nothing.

Your command to create your Soft dPAC looks perfectly fine.

Coming  next release you will be able to manage Soft dPAC controllers directly from EcoStruxure Automation Expert Physical view. You will not need anymore scripts to create & remove Soft dPAC controllers !!!

[DP-JYC]

I knew that I shouldn't have left it like that!

I'm 2 hours unfront my demo at the customer location... And I can't load my project >> For the same reason <<

Here is the message:

• I checked IPs as you suggested, and it's the same as I wrote before.
• I did ./uninstall everything on the raspberry Pi and re ./install to have a fresh volume... But nothing changed.

I'm pretty sure it's possible to know more about this issue quite fast. Especially that it starts with "Coud" and not "Could", so I hope it's easy to find the root cause.

I need help, could you call me to find a solution?

[Anonymous user]

Hello Jean-Yves,

This Error message is ugly but this is most probably not the root cause of your problem because I have already seen it many times without any funcitonal consequence.

The logs you show on the video are quite limited but I suspect that running your application makes the SoftdPAC crash.

On the Raspberry terminal or using portainer, could you get the logs of the container itself ?

In the terminal, just run the command 'docker logs <softdpac_container_name>

We should see if the runtime restarted.

Don't hesitate to call me.

Conerning the fact that you can't ping softdpac containers from the raspberry itself, this is normal because softdpac containers are running on a macvlan network which is isolated from host network. You can ping them only from the outside or from another container attached to the same macvlan network.

[DP-JYC]

Thank you all for your help.

I confirm that the (ugly) Error message is not the root cause of my problem.

It just led me to the wrong direction.

I think that I'm having an infinit loop somewhere, I will find out.

Thx