Problems connecting to the DIY client #207
Comments
|
Hi @Sineos , sorry for the late reply. I was a bit under stress the last days.
This is the IP of the DIY client?
Ending with "ready for setup"? :-)
That look weird, I've never seen that 🤔 . Maybe it doesn't matter though since the server seems to be running. |
|
Hi @fquirin, thanks for coming back to this.
DIY client and control hub are both running on the same physical machine, a Asus Tinkerboard 2S with 4GB RAM.
Ending with "I'll be right there" |
That indicates that the client runs into an error and doesn't actually start. If that's the case you should see something in the mentioned log file |
I cannot see anything wrong in the logs. From the hub I can connect to the clexi instance (green LED / After reboot, I just get the message "I'll be right there". |
|
The logs look good indeed, I can't see any problems. Actually I'm a little bit surprised, are you using a pre-release build of v2.7.0? 😁 There is one thing that the logs don't show and that is if Chromium itself crashed after this line: What you can try to get more info is to activate the experimental Chromium log. Open the If you restart the client and check the |
|
Thanks for supporting this. Appreciated.
I started off with the release version and ran into the same problem as we are discussing now. Switching to dev was an attempt to see if it changes anything
Following the first message, I did
Where do I set this? |
Did you build it with the included scripts? It's nice to see that people actually build their own versions 😀 .
The EGL error looks familiar, it might actually be the reason for the RPI4 flag below, if I remember correctly.
It is the right play, but you need to comment out the line below as well or it will be reset: |
|
It changes something but still no luck. With With: If I add the |
I think this flag is running Chromium in the background and because of that the run-script jumps to the end immediately. Unfortunately we can't use the integrated 'headless' mode because of limited or missing features (that's why the script uses xvfb).
The Tinkerboard might have a GPU driver problem or the driver has some conflict with Chromium. Can you try the Chromium flag: |
It seems to start. In the Control-Hub I can connect but no reaction to ping etc |
|
Did you hear the "ready for setup" message this time? |
|
No, only "I'll be right there" |
|
yields: |
Looking at your logs I think this only happens without Do you have any chance to connect a display to your Tinkerboard?
These messages are very weird, why would Chromium try to access things like |
The really strange thing is that these message only appear when booting up with auto-login. When started via
Armbian (Ubuntu based)
Ok, now it gets really wired. It works in pseudo headless. I get the message "ready for setup" and can work with the o1 client. There is one error message at start.
Otherwise it looks good:
|
Maybe some OS related things, idk 🤷♂️, let's just ignore it for now 😅
Maybe it was still waiting for the reboot after first successful start. You can try to switch back to "real" 'headless' and observe what happens :-). Maybe it has some issues with 'xvfb', but I would expect error messages visible inside the log in this case. |
|
Ok, not yet there:
Does it make any difference to run the client headless or pseudo display? |
There are subtile difference, the biggest one being performance since the "pure" headless version emulates a very small display internally. Sometimes services are optimized for display as well and might mention something like "I need to show you the result on a display" in headless, but you can manipulate that behavior with the settings.js I think (environment varaible).
Good question. Maybe something went wrong during installation. Did you check the
When you hear the "ready for setup" you can login via the remote terminal of your SEPIA Control-HUB (client connections page) or you can use the display to enter your credentials. Are you using v0.25.0 right now? (if so you have ~8s to abort the automatic-setup at load-up of the client). |
I would like to setup SEPIA (framework and DIY client) on a Tinkerboard 2 and a Jabra Speak 510 as audio device.
It seems to be working "half way":
CLEXI server says welcome. Info: {"version":"CLEXI Node.js server v0.9.2","xtensions":{"clexi-broadcaster":{"active":true},"clexi-http-events":{"active":true},"runtime-commands":{"active":true},"gpio-interface":{"active":true}}}What is not working:
ping alldoes not return theo1clientOnly indication in the logs:
I also tried to build the
devbranches but ended up the same. Any pointer would be appreciated.The text was updated successfully, but these errors were encountered: