2.2.0: CRON Error

Discussions about RaZberry - Z-Wave board for Raspberry computer
cyberhofi
Posts: 26
Joined: 31 Oct 2015 13:48

2.2.0: CRON Error

Post by cyberhofi » 19 Dec 2015 01:56

Last night my sceduled scenes stopped working. I figured out, the Cron does not work anymore, if i try to open the Cron App in the UI i get a 404 Error - Not Found.

Any suggestions to solve this?

Unitone
Posts: 11
Joined: 21 Dec 2015 01:32

Re: 2.2.0: CRON Error

Post by Unitone » 21 Dec 2015 01:35

Same thing here. Removed CRON and now i cannot add it back. "404 Not Found. Requested data does not exists" is all I've got. Please help!

islipfd19
Posts: 126
Joined: 07 Jul 2014 03:35

Re: 2.2.0: CRON Error

Post by islipfd19 » 21 Dec 2015 04:27

I can confirm the same. Cron module giving the same errors as stated above, I can find nothing in the logs.

[Edit]
Created issue #311 on git for this project.

islipfd19
Posts: 126
Joined: 07 Jul 2014 03:35

Re: 2.2.0: CRON Error

Post by islipfd19 » 21 Dec 2015 15:18

I've performed additional tests, if the cron module was installed prior to v2.2.0 and then zway updated to 2.2.0; cron events work as expected. Obviously, removing Cron and attempting to re-add it will not work. Suggestion for current users that did remove the module after updating to v2.2.0 is to revert back to previous stable build (which is automatically backed up in '/opt' when upgrading to x2.2.0) add the cron module then upgrade using the normal method.

Unitone
Posts: 11
Joined: 21 Dec 2015 01:32

Re: 2.2.0: CRON Error

Post by Unitone » 21 Dec 2015 19:23

islipfd19 wrote:Suggestion for current users that did remove the module after updating to v2.2.0 is to revert back to previous stable build (which is automatically backed up in '/opt' when upgrading to x2.2.0)
How do I do that?

[Edit]

Rolled back to v2.1.1 through Configuration Interface, no luck. Still can't add CRON. " 404 Not Found. Requested data does not exists"

islipfd19
Posts: 126
Joined: 07 Jul 2014 03:35

Re: 2.2.0: CRON Error

Post by islipfd19 » 22 Dec 2015 03:38

Are you positive you are now running 2.1.1? Does the interface look the same as the new one? Be sure you stopped z-way-server; it may be beneficial to reboot the RPi. It may also be easier to move the 2.1.1 folder back. Each upgrade saves the previous version. The previous version you have would be in the '/opt' directory with the date and time you upgraded to 2.2.0. Be sure the z-way-server service is stopped. Rename the /opt/z-way-server directory to something like /opt/z-way-server.old and then rename your previous version to /opt/z-way-server and reboot. It should start up with version 2.1.1. You will of course lose any changes you made in version 2.2.0 after the upgrade.

Unitone
Posts: 11
Joined: 21 Dec 2015 01:32

Re: 2.2.0: CRON Error

Post by Unitone » 22 Dec 2015 04:45

Positive. Interface looks different. Is there any logs that can point to why it's happening?

pz1
Posts: 2053
Joined: 08 Apr 2012 13:44

Re: 2.2.0: CRON Error

Post by pz1 » 22 Dec 2015 10:53

islipfd19 wrote:Created issue #311 on git for this project.
Did you intentionally close this issue? My understanding of your further messages is that you found a work-around for the problem, but that the problem still is there for other users. What did I miss?

islipfd19
Posts: 126
Joined: 07 Jul 2014 03:35

Re: 2.2.0: CRON Error

Post by islipfd19 » 22 Dec 2015 14:12

Yes, I intentionally closed the issue. The description of the issue was not correct. Cron still works but you are unable to view the settings of it under Apps and you are not able to load it in 2.2.0. I provided a work around for those that removed it and tried re-adding it. Something is still broken but I'm not sure what.

islipfd19
Posts: 126
Joined: 07 Jul 2014 03:35

Re: 2.2.0: CRON Error

Post by islipfd19 » 22 Dec 2015 14:35

pz1 wrote:
islipfd19 wrote:Created issue #311 on git for this project.
Did you intentionally close this issue? My understanding of your further messages is that you found a work-around for the problem, but that the problem still is there for other users. What did I miss?
Issue reopened on git hub.

Locked