"Cannot query interpreter state" in Scene

[pos 22]

Hi

 

I have had a scene running for 6 month without issues. Now it gives an error "[ERROR] 06:43:01: Cannot query interpreter state". This must be due to changes from 4.140 to any of the betas (I only updated to a beta to "eventually solve locking issued with Popp thermostat). No row references of the issue in the LUA... Couldn't be to hard to track this down when I have some spare time. But in the meantime... Anyone with knowledge of where to start looking and what could have caused it?

 

 

/Peo

[speedy 64]

On 5.12.2017 at 2:38 PM, I.Srodka said:

Could you tell whether this error appears also in scenes and cases without:

Please login or register to see this code.

 in the scene header?

 

Yes it does.

 

(Update from V4.140 to V4.150 (no betas))

 

Here is a simple scene i tried for testing.

I also get a 10 sec (exactly) delay in debug response window when executing several scenes at once.

The HC2 also "freezes", like the CPU is locked and no CPU usage is displayed. 

*Video attached of what is happening.

CPU freeze:

Please login or register to see this attachment.

 

Look at debug times.

Please login or register to see this attachment.

 

Here is the code:

Please login or register to see this code.

 

Here is the video:

Please login or register to see this attachment.

 

[petergebruers 1,261]

Thread hijack.

 

Can we talk a bit about "killotherinstances"?

 

I saw it was introduced by Fibaro some ti|e ago, but I think it never got an official explanation. So I started using it sparingly. But I think I never published code based on it.

 

I think it is not a panacea, but I can express certain logic with it in a cleaner way than counting instances and looping.  But I know it can introduce a new problem: if your scene changes something which triggers your script, you kill your running script. You have to handle that.

 

Can you please share your thougts? Especially, what are the downsides? And does it bear any relationship to this topic?

[pos 22]

 > And does it bear any relationship to this topic?

No. This happens without this feature used anywhere.

 

And...

 

Probably better to start a new thread with this

 

/Peo

Edited December 8, 2017 by pos

[petergebruers 1,261]

14 minutes ago, pos said:

 > And does it bear any relationship to this topic?

No. This happens without this feature used anywhere.

 

And...

 

Probably better to start a new thread with this

 

/Peo

 

Thanks. I won't start another topic because it is an "unsupported" feature anyway.

 

On topic: I had one scene crashed again (due to "interpreter state") a few days ago. Now I've upgraded my HC to the latest beta, 4.151, but it is not mentioned in the release notes. I'll post here if it happens again.

[I.Srodka 4]

29 minutes ago, petergebruers said:

On topic: I had one scene crashed again (due to "interpreter state") a few days ago. Now I've upgraded my HC to the latest beta, 4.151, but it is not mentioned in the release notes. I'll post here if it happens again.

 

Guys, @petergebruers, @pos, @speedy!

 

Could you check whether it still exists on 4.151?

 

If you don't want to update to beta I will understand, no pressure ; )

[Jacek Stark 44]

After update for ver 4.151 ( HC2 ) is ok for now.

[speedy 64]

@I.Srodka

 

I have just updated to 4.151 beta to try this again.

First reboot after update resulted in 503 but 2nd reboot was fine.

 

Side note, thank you for the updated scalable LUA windows! 

Thats great!

 

Now on to the problem.

There is no error message in RED now but the problem is still there.

The CPU freeze and scene/HC2  becomes unresponsive for exactly 10 seconds.  

 

*After testing the HC2 goes in a complete freeze, you can not use the HC2!

When the CPU is released the HC2 goes back to "normal" so this i a big deal.

 

Please login or register to see this attachment.

 

*Edit 2

After more testing i got the message back.

Same 10 sec freeze, but multiple this time.

If i execute a scene during the freeze, the freeze extends another 10 seconds.

So if i execute 5 scenes thats a 50 seconds freeze.

 

Please login or register to see this attachment.

 

 

Attached is a video of CPU usage and Scene debug windows.

I used the same code as before.

Please login or register to see this attachment.

 

 

 

Edited December 8, 2017 by speedy

[Jacek Stark 44]

Error "Cannot query interpreter state" is come back in ver 4.151

 

[morpheus75 75]

hi

just seen this topic and i have also seen this happening on a couple of HC2. mine and a few clients which have all been updated to 4.150 will get this error randomly.

would be interested to find out the cause and of course the solution.....

[Acho 2]

Im facing the same issue anfter update to 4.150 on some of the scenes which have worked well so far...

[Acho 2]

Now it happened again in my scenes ("Cannot query interpreter state" in Scene)  4 days after reboot of the HC2. Ive checked HC2 when I realised that some of my scenes are not running, Ive see the mentioned message in the debug windows + none of my motion sensors (fibaro+few others) stopped reporting their state to HC - so moving did not trigger the "breached" status  in the HC2. If I for instance switched on a light via HC2 it worked, but was not shown as "ON" in the HC2, the same when I switched the light manually ON, the state in HC2 did not change - can that be a problem related also to the "BUG" of "Cannot query interpeter..." ?

 

After reboot of course everything running well..

 

Thanks

[henri-allauch 4]

 

Please login or register to see this code.

************************* Log HC2 On 12/12/2017 at 05:00:00 ********
Scene: Hc2 Control Hre (21)
2017-12-11 21:11:30: Main: G_Starting ON Reboot Current Cut
-------------------------------------------------- ---
************************* Log HC2 On 12/12/2017 at 17:00:00 ********
Scene: Mvt Garden Av (80)
2017-12-12 07:28:00: Can not query interpreter state
-------------------------------------------------- ---
Scene: Lighting Kitchen (81)
2017-12-12 14:58:00: Can not query interpreter state
-------------------------------------------------- ---
Scene: Alarm Actions (93)
2017-12-12 14:58:00: Can not query interpreter state
--------------------------------------------------

********************* Log HC2 On 15/12/2017 at 05:00:00 *******

Scene: Sign. Fum. Mans. (127)

2017-12-14 18:51:00:  Can not query interpreter state  
--------------------------------------------------

[Thomasn 77]

I have the same error showing up in some of my lua programs. I run the latest stable firmware and when I get the error, it can be up to three times in a row. Some of the programs seems to freeze for a short while but then starts again.

Please login or register to see this attachment.

Edited January 10, 2018 by Thomasn
Added a picture

[henri-allauch 4]

Please login or register to see this code.

 

[I.Srodka 4]

35 minutes ago, henri-allauch said:

Did anyone who pointed out this problem find a solution or an explanation? What does fibaro support mean?

We do investigate the issue and as it saddens me very much, I wouldn't expect any solutions this year.

[shingoo 0]

Any news?

[I.Srodka 4]

8 hours ago, shingoo said:

Any news?

Have you experienced it on the latest beta?

[henri-allauch 4]

@ 

Please login or register to see this link.

 Sorry but i do not Install Beta ... but Have you found problem and try update for in Beta ? 

 

Please login or register to see this link.

Said

Please login or register to see this link.

 : Error is come back in ver 4.151
 

Among the users concerned have there been tests in 4.152 or 4.153 ?

 

 

[shingoo 0]

1 hour ago, I.Srodka said:

Have you experienced it on the latest beta?

 

 I never installed any beta as well. So this is a problem in the current production release and I can't check if it's still happening in the beta release... Sorry.

Edited January 10, 2018 by shingoo

[petergebruers 1,261]

I run the 4.153 release, I have not seen this error, but this does not prove a lot.  For me the problem was very, very rare, it happened maybe once in a month (and it happened maybe twice, in total!). So it is too soon for me to tell if it is solved in this beta! But I can say...the problem did not get worse, so this is good.