CUDPSender::Send failed with: 'Permission denied' about ecal HOT 3 CLOSED

And another note:
Please don't start eCAL applications with sudo permissions, or if you do, please be aware that tasks started with sudo cannot communicate with started without sudo on the same machine using shared memory.
The memory files are created in user space (which is root for those applications started with sudo) and then non sudo applications won't be able to access them (and vice versa).

from ecal.

It seems that the output of "permission denied" is correlated with publisher sleep time inside the loop. If I let the publisher wait for 3 seconds per sending message, it will print 6 times "permission denied". I don't know why they are connected and how I can fix the issue.

from ecal.

So we have never before worked with CRIU.
eCAL programs have a lot of resources (e.g. shared memory files, mutexes) which are shared between a publisher and a subscriber. Both entities negotiate where and how data will be exchanged and keep file handles to these resources.
There are other resources like open sockets for multicast udp traffic.

If you now just halt the program of the subscriber and dump it, and try to restore it later, I honestly have no idea what will happen to all these resources.
The publisher might clean them up, because to him there are no more active subscribers.
The OS might clean them up, if nobody is using them.

I assume that there is some problem with a UDP socket, since you get CUDPSender::Send failed.

And apart from this as mentioned previously:
for eCAL communication to work, you need negotiations between publishers and subscribers. If you just freeze them and spin them up at a later random point, I highly doubt that things will go well...

Maybe this helps somehow: https://criu.org/External_UNIX_socket

from ecal.