I have any Autobahn Python server that I’m trying to start on boot using Ubuntu 16.04 systemd. I start crossbar.io as a service also.
When my server starts on boot it logs that everything is going well until it calls reactor.run(), then it just goes silent. Once I log in I can simply do systemctl restart my-service and it works correctly.
I have logging in all my onJoin calls and so I know that none of them are getting called when it starts on boot.
One more detail. The start on boot works fine in a VM on a relatively new computer but fails on older, less powerful computers.
All this points to some timing-related issue that Autobahn is getting started before crossbar is ready. In fact, symptomatically, my service is acting just like it does if I start it without starting crossbar at all.
I have tried just delaying the start of my service with a long sleep. I believe I have dependencies properly set up between my service and crossbar.
Any ideas on how to debug this would be appreciated.