Cannot access python3 - restart solved

1

Hello,
I’m running debian LXC, and OH4.2.2 as dedicated machine.
This night I’ve found out this new error (never happened before)

note: manual run in the shell of the “python3 /etc/openhab/scripts/shadow.py” indeed worked fine.

2024-10-22 12:29:22.589 [WARN ] [rg.openhab.core.io.net.exec.ExecUtil] - Error occurred when executing commandLine '[python3, /etc/openhab/scripts/shadow.py, update, 240.4]'
java.io.IOException: Cannot run program "python3": error=0, Failed to exec spawn helper: pid: 1018285, exit value: 1
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:1143) ~[?:?]
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:1073) ~[?:?]
        at org.openhab.core.io.net.exec.ExecUtil.executeCommandLine(ExecUtil.java:59) ~[?:?]
        at org.openhab.core.model.script.actions.Exec.executeCommandLine(Exec.java:39) ~[?:?]
        at jdk.internal.reflect.GeneratedMethodAccessor250.invoke(Unknown Source) ~[?:?]
        at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
        at java.lang.reflect.Method.invoke(Method.java:569) ~[?:?]
        at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.invokeOperation(XbaseInterpreter.java:1192) ~[?:?]
        at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.invokeOperation(XbaseInterpreter.java:1167) ~[?:?]
        at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._invokeFeature(XbaseInterpreter.java:1153) ~[?:?]
        at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.invokeFeature(XbaseInterpreter.java:1098) ~[?:?]
        at org.openhab.core.model.script.interpreter.ScriptInterpreter.invokeFeature(ScriptInterpreter.java:151) ~[?:?]
        at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:1008) ~[?:?]
        at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:971) ~[?:?]
        at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:247) ~[?:?]
        at org.openhab.core.model.script.interpreter.ScriptInterpreter.doEvaluate(ScriptInterpreter.java:226) ~[?:?]
        at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:227) ~[?:?]
        at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter._doEvaluate(XbaseInterpreter.java:475) ~[?:?]
        at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.doEvaluate(XbaseInterpreter.java:251) ~[?:?]
        at org.openhab.core.model.script.interpreter.ScriptInterpreter.doEvaluate(ScriptInterpreter.java:226) ~[?:?]
        at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.internalEvaluate(XbaseInterpreter.java:227) ~[?:?]
        at org.eclipse.xtext.xbase.interpreter.impl.XbaseInterpreter.evaluate(XbaseInterpreter.java:213) ~[?:?]
        at org.openhab.core.model.script.runtime.internal.engine.ScriptImpl.execute(ScriptImpl.java:80) ~[?:?]
        at org.openhab.core.model.script.runtime.internal.engine.DSLScriptEngine.eval(DSLScriptEngine.java:137) ~[?:?]
        at org.openhab.core.automation.module.script.internal.handler.ScriptActionHandler.lambda$0(ScriptActionHandler.java:75) ~[?:?]
        at java.util.Optional.ifPresent(Optional.java:178) [?:?]
        at org.openhab.core.automation.module.script.internal.handler.ScriptActionHandler.execute(ScriptActionHandler.java:72) [bundleFile:?]
        at org.openhab.core.automation.internal.RuleEngineImpl.executeActions(RuleEngineImpl.java:1188) [bundleFile:?]
        at org.openhab.core.automation.internal.RuleEngineImpl.runRule(RuleEngineImpl.java:997) [bundleFile:?]
        at org.openhab.core.automation.internal.TriggerHandlerCallbackImpl$TriggerData.run(TriggerHandlerCallbackImpl.java:86) [bundleFile:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
        at java.lang.Thread.run(Thread.java:840) [?:?]
Caused by: java.io.IOException: error=0, Failed to exec spawn helper: pid: 1018285, exit value: 1
        at java.lang.ProcessImpl.forkAndExec(Native Method) ~[?:?]
        at java.lang.ProcessImpl.<init>(ProcessImpl.java:314) ~[?:?]
        at java.lang.ProcessImpl.start(ProcessImpl.java:244) ~[?:?]
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:1110) ~[?:?]
        ... 35 more

restart of the OH did solve it.
Any idea for reasoning of this issue?

2

Searching the exception shows this could occur if you upgrade Java while OH is running. People who seem to see this the most are running Jenkins.

The solution is to restart the service, so you’ve done the correct step to mitigate the problem. However, if it persists come back and we will continue to explore.

Ultimately this is comming from interanl Java stuff and it’s related to how Java creates child processes.

3

thank you, as always your nailed it!

looks like there was an apt java upgrade last night (running periodic ansible jobs to maintain my rigs)

root@openhab:~# tail -3 /var/log/apt/history.log
Commandline: /usr/bin/apt-get -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold dist-upgrade --auto-remove
Upgrade: zulu17-ca-jre-headless:amd64 (17.0.12-1, 17.0.13-1), zulu17-ca-jdk-headless:amd64 (17.0.12-1, 17.0.13-1), zulu17-jre-headless:amd64 (17.0.12-1, 17.0.13-1), zulu17-jdk-headless:amd64 (17.0.12-1, 17.0.13-1), zulu17-ca-doc:amd64 (17.0.12-1, 17.0.13-1), zulu17-ca-jdk:amd64 (17.0.12-1, 17.0.13-1), zulu17-ca-jre:amd64 (17.0.12-1, 17.0.13-1), zulu17-doc:amd64 (17.0.12-1, 17.0.13-1), zulu17-jdk:amd64 (17.0.12-1, 17.0.13-1), zulu17-jre:amd64 (17.0.12-1, 17.0.13-1)
End-Date: 2024-10-22  03:31:36
root@openhab:~#

It’s not that often, for last 6yrs I’m running OH this is the first occurence, so I guess no need to do some health checking inside OH

4

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.