Page 2 of 2

Re: MxInfo tool collection

Posted: 05 Aug 2019 17:23
by piet66
Ok, I haven't used this app yet and I don't know it.

My tool gets the information from http://IP:8083/ZAutomation/api/v1/instances. There in Cron section all jobs are mentioned which are enabled to fire. This section is build up at start of z-way-server. A restart should remove all old tasks.

But generally an app which stops has to remove all tasks which it has created. If it doesn't it is badly programmed.

There's a garbage collection missing in this system.

Re: MxInfo tool collection

Posted: 05 Aug 2019 17:43
by micky1500
Thanks Piet66

I was hoping for an easy fix !
Thanks for trying to help.

My system has got a bit messy, but too big now to go for a factory reset.
I need to learn a bit more JavaScript programming.
With the info from Mxinfo, I'll try to properly delete the broken Cron Jobs.

Re: MxInfo tool collection

Posted: 05 Aug 2019 18:15
by piet66
I don't mean a factory reset. Only stop and start again the z-way-server service:
On Raspi terminal do:
sudo /etc/init.d/z-way-server stop
sudo /etc/init.d/z-way-server start

Which app were you talking about? From automations page or from the old apps page?
I have no much experience with the new automations functions. But I have the feeling (maybe I'm wrong) that the transformation doesn't always work correctly.

Re: MxInfo tool collection

Posted: 05 Aug 2019 18:44
by micky1500
I have restarted, many times. Occasionally a full power on/off cycle.
The old apps page, App called 'Schedule' I have 20 instances set.
I think I also had this issue with rogue Cron jobs running while on 2.3.8

Think i'm passed the point where it will self fix.
I will be looking into writing a JavaScript to delete the rogue Cron Jobs.

I like to play, so it might be fun to try.

Re: MxInfo tool collection

Posted: 05 Aug 2019 19:19
by piet66
Hm,
when I'm right that the task list is build up at start, there must be anyone who adds these tasks again. So such a script wouldn't be a solution.

Perhaps you can
- detect in Mx tools which app instance has created the tasks,
- make a copy of this instance
- and delete the old one?

You can also have a look in http://<ip>:8083/ZAutomation/api/v1/instances/<instance no> if there are any wrong data.