Hi Stephen!
> Some things to check. Is irexec running?
>
> sudo ps -ef | grep irexec
pi 2095 852 0 13:55 pts/0 00:00:00 grep –color=auto irexec
Quite frankly not all that conclusive to me, though that H:M:S of all
zeros is a little suspicious. So ran *service irexec status* and got an
‘inactive (dead)’ result. Seems to confirm my suspicion.
> What log output do you get from irexec? I am not sure exactly where
> the irexec service will be logging things, but it should show up
> somewhere. What do these commands show?
>
> sudo systemctl status irexec
> sudo journalctl --unit=irexec
> sudo journalctl -b0 /usr/bin/irexec
pi@RPi-MythFE:~ $ sudo systemctl status irexec
? irexec.service - Handle events from IR remotes decoded by lircd(8)
Loaded: loaded (/lib/systemd/system/irexec.service; disabled; vendor
preset: enabled)
Active: inactive (dead)
Docs: man:irexec(1)
http://lirc.org/html/configure.html http://lirc.org/html/configure.html#lircrc_format pi@RPi-MythFE:~ $ sudo journalctl --unit=irexec
-- Logs begin at Mon 2020-05-18 18:36:22 CDT, end at Tue 2020-05-19
14:06:30 CDT. --
-- No entries --
pi@RPi-MythFE:~ $
pi@RPi-MythFE:~ $ sudo journalctl -b0 /usr/bin/irexec
-- Logs begin at Mon 2020-05-18 18:36:22 CDT, end at Tue 2020-05-19
14:07:14 CDT. --
-- No entries --
pi@RPi-MythFE:~ $
OK, so those results weren’t unexpected as we had found out irexec
wasn’t running. Reading ahead a bit found /sudo systemctl restart
irexec/ so let’s see what /sudo systemctrl start irexec/does:
Now /service status irexec/says is active (running). (Good!) rerun the
above tests….
pi@RPi-MythFE:~ $ sudo systemctl status irexec
? irexec.service - Handle events from IR remotes decoded by lircd(8)
Loaded: loaded (/lib/systemd/system/irexec.service; disabled; vendor
preset: enabled)
Active: active (running) since Tue 2020-05-19 14:12:12 CDT; 3min 52s ago
Docs: man:irexec(1)
http://lirc.org/html/configure.html http://lirc.org/html/configure.html#lircrc_format Main PID: 2235 (irexec)
Tasks: 1 (limit: 4915)
Memory: 300.0K
CGroup: /system.slice/irexec.service
??2235 /usr/bin/irexec /etc/lirc/irexec.lircrc
May 19 14:12:12 RPi-MythFE systemd[1]: Started Handle events from IR
remotes decoded by lircd(8).
pi@RPi-MythFE:~ $
pi@RPi-MythFE:~ $ sudo journalctl --unit=irexec
-- Logs begin at Mon 2020-05-18 18:36:22 CDT, end at Tue 2020-05-19
14:16:47 CDT. --
May 19 14:12:12 RPi-MythFE systemd[1]: Started Handle events from IR
remotes decoded by lircd(8).
pi@RPi-MythFE:~ $
pi@RPi-MythFE:~ $ sudo journalctl -b0 /usr/bin/irexec
-- Logs begin at Mon 2020-05-18 18:36:22 CDT, end at Tue 2020-05-19
14:17:13 CDT. --
-- No entries --
pi@RPi-MythFE:~ $
So that appears to be good news! Test the remote…. Well, I would have
loved to have said the thing now worked but no.
> Getting irexec to work as well is just icing on the cake. But it too
> should work, with the right config. So for testing purposes, I would
> suggest:
>
> config = echo "irexec test" >/tmp/irexec.txt
Huh: I just switched SD cards to test on a ‘temporary system’ – the
irexec service is up and running – I was not expecting that. /sudo
systemctl status irexec/says it has been running for 20 hours, which I
find odd as that card removed last night and I just installed it.
Other two look the same except for the timestamps
Probably insignificant, just saying something if it is.
Back to testing: /config = echo "irexec test" >/tmp/irexec.txt/
Again to be nitpicky, mainly because you mentioned permissions, I had to
/mkdir tmp/as wasn’t present. Properties: owner = pi, group = pi, view
content = anyone, change content = only owner (so pi), access content =
anyone.
> sudo systemctl restart irexec
Well that wasn’t impressive – /tmp is empty.
Reboot, check irexec status, test; nope.
> begin
> prog = irexec
> button = KEY_SELECT
> config = echo "irexec test"
> end
I left in as /echo "irexec test" >/tmp/irexec.txt/so see if would now
write to the file. Darn. :(
Edit out my test….
and restarted irexec again. Pressing Home three times gave this from
a "journalctl --unit=irexec" command:
My results:
pi@RPi-MythFE:~/tmp $ sudo journalctl --unit=irexec
-- Logs begin at Tue 2020-05-19 15:00:47 CDT, end at Tue 2020-05-19
15:11:35 CDT
May 19 15:00:50 RPi-MythFE systemd[1]: Started Handle events from IR
remotes dec
May 19 15:08:40 RPi-MythFE systemd[1]: Stopping Handle events from IR
remotes de
May 19 15:08:40 RPi-MythFE systemd[1]: irexec.service: Main process
exited, code
May 19 15:08:40 RPi-MythFE systemd[1]: irexec.service: Succeeded.
May 19 15:08:40 RPi-MythFE systemd[1]: Stopped Handle events from IR
remotes dec
May 19 15:08:40 RPi-MythFE systemd[1]: Started Handle events from IR
remotes dec
May 19 15:10:17 RPi-MythFE systemd[1]: Stopping Handle events from IR
remotes de
May 19 15:10:17 RPi-MythFE systemd[1]: irexec.service: Main process
exited, code
May 19 15:10:17 RPi-MythFE systemd[1]: irexec.service: Succeeded.
May 19 15:10:17 RPi-MythFE systemd[1]: Stopped Handle events from IR
remotes dec
May 19 15:10:17 RPi-MythFE systemd[1]: Started Handle events from IR
remotes dec
May 19 15:11:07 RPi-MythFE irexec[945]: irexec test
May 19 15:11:08 RPi-MythFE irexec[945]: irexec test
May 19 15:11:09 RPi-MythFE irexec[945]: irexec test
lines 1-15/15 (END)
pi@RPi-MythFE:~/tmp $ sudo journalctl -b0 /usr/bin/irexec
-- Logs begin at Tue 2020-05-19 15:00:47 CDT, end at Tue 2020-05-19
15:14:11 CDT
May 19 15:11:07 RPi-MythFE irexec[945]: irexec test
May 19 15:11:08 RPi-MythFE irexec[945]: irexec test
May 19 15:11:09 RPi-MythFE irexec[945]: irexec test
lines 1-4/4 (END)
OK, you know me well enough you probably guessed what I did! Yes, tried
to see if the old config to load Myth would work. Nothing; did put in a
new line to journalctl -b0… still “irexec test” though. Ah! restart
irexec ==> nope but journalctl -b0’s message was:
May 19 15:21:03 RPi-MythFE irexec[945]: irexec test /<== the old test/
May 19 15:25:52 RPi-MythFE irexec[1109]: /bin/sh: 1: echo <mypassword> |
su -l pi -c /home/pi/Load_MythFE.sh: not found
My config line starts at “echo”; no idea where “/bin/sh :1:” originates.
OK, tried without the quote marks (config = echo pswd blah-blah-blah).
Nothing, nothing... about to check journalctl and MythTV pops up!!
Woohoo!!!!
Shutdown, power switch off, … power up – at Desktop, push button – still
works! Yea!!!!
Thank you!! Barry