Re: [Xenomai] Xenomai/cobalt: low_init(): binding failed: Function not implemented error issued when trting to run latency app on xeno 3.x-rc3

[Philippe Gerum <rpm@xenomai.org>]

On 03/03/2015 09:38 PM, Helder Daniel wrote:
> Done that:
> 
> $> sudo pkill sysregd
> 
> $> sudo ps aux | grep sysregd
> user      4045  0.0  0.1   3796   800 pts/1    S+   20:30   0:00 grep
> sysregd
> 
> all instances killed.
> 
> Now launch:
> 
> $> sudo /usr/xenomai/sbin/sysregd --linger --daemonize
> 
> $> sudo ps aux | grep sysregd
> root      4022  0.0  0.3   3776  1888 ?        Ssl  20:28   0:00
> /usr/xenomai/sbin/sysregd --linger --daemonize
> user      4045  0.0  0.1   3796   800 pts/1    S+   20:30   0:00 grep
> sysregd
> 
> Daemon running.
> 
> Now tried to run app and receive the same error:
> 
> ./hello
> sysregd: create_directory_recursive("/var/run/xenomai/anon/system"):
> Transport endpoint is not connected
> sysregd: create_directory_recursive("/var/run/xenomai/anon/system"):
> Transport endpoint is not connected
> sysregd: create_directory_recursive("/var/run/xenomai/anon/system"):
> Transport endpoint is not connected
>    3"006.383| WARNING: [main] cannot connect to registry daemon
>    3"006.574| BUG: [main] initialization failed, EAGAIN
> 

The only plausible scenario for this issue is that sysregd got killed
(e.g. SIGKILL or SIGHUP, not SIGTERM which currently leads to a graceful
exit) while it was running, which caused the FUSE-based anon/system
mountpoint to be left over.

To fix this, you can unmount the system mount point manually before
starting sysregd again:

# fusermount -u /var/run/xenomai/anon/system

We can probably do better with graceful exit and cleaning up left overs.
I'll look at this.

-- 
Philippe.