ControlBlock service won't start with v1.6 board
-
Also, you can call controlblock service from within the build directory directly. That should also give you an error output.
-
OK, those are great suggestions. The commands "make", "sudo make install", "sudo make installservice" all run just fine with zero errors or warnings of any type.
The I2C interface was not enabled (at least according to raspi-config), so I enabled it, and then rebooted. Still "service --status-all" showed that controlblockservice was not started. So that didn't work. (Note that "sudo make installservice" reported : "Making sure that the ARM I2C Interface is enabled via /boot/config.txt . . ." even though the I2C interface was not turned on when I ran it.
When I ran "sudo controlblock" from the build directory I got no error messages of any type. I just got the following:
[ControlBlock] Gamepadtype = ARCADE gamepads
[ControlBlock] Single gamepade mode DEACTIVATED
[ControlBlock] Shutdown is ACTIVATEDAny other ideas?
-
@EmbeddedMan @petrockblog Any other ideas for what things to check? I'm an embedded C guy, and Linux isn't my primary environment so I'm not exactly sure what to check next.
-
Sorry for this delayed reply.
I would start and step-by-step go through the non-quick installation steps that are described at https://github.com/petrockblog/ControlBlockService/blob/master/README.md
it would be interesting to see at which of the step something goes wrong.
-
Thinking about it — if you can start the controlblock service manually with ‘controlblockservice &’, you should be able to see test the controlblock with the jstest tool as described at https://github.com/petrockblog/ControlBlockService2/blob/master/README.md#troubleshooting (that also works works with the ControlBlock 1.x).
-
@petrockblog said in ControlBlock service won't start with v1.6 board:
Sorry for this delayed reply.
I would start and step-by-step go through the non-quick installation steps that are described at https://github.com/petrockblog/ControlBlockService/blob/master/README.md
it would be interesting to see at which of the step something goes wrong.
And, unfortunately, when I do this, I get the exact same result as what I've listed above and in the GH issue. There are no error messages until the very end when I get
[ERROR] The ControlBlock service is not running
That's it.
*Brian
-
@petrockblog When I type "controlblockservice &" on the command line, I get "-bash: controlblockservice: command not found" error. Is there some specific directory I need to be in to run the service that way?
-
@petrockblog I found the controlblockservice script : in /etc/init.d/controlblockservice. When I do "sudo /etc/init.d/controlblockservice &", I don't get any error message (just "[1] 690") but then the next command that I type (no matter what it is) I get "[1]+ Done sudo /etc/init.d/controlblockservice" which I think means that the service started but then immediately exited?
-
@petrockblog Well, I think I've found something : /usr/local/bin is completely empty. The service script (controlblockservice) exits immediately after executing this line:
[ -x "$DAEMON" ] || exit 0
And since $DAEMON is /usr/local/bin/controlblockservice, it exits.
So why does the 'install' process not generate any errors for me (either using the install.sh script, or doing it all manually) but yet it doesn't copy anything over into /user/local/bin?
-
@petrockblog It appears that I can get the service running by commenting out the line "[ -x "$DAEMON" ] || exit 0" and then starting the service. This also allows the service to run on boot.
So, why does this line need to be commented out? I'm confused why this would work for everyone else and not my setup (even though I started from a completely fresh RetroPi 4.5).
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.