[Release candidate 0.10.0 - It's Froxlor, but with API :)]

I raised froxlor to 0.10 before the Debian update. Renamed the old folder and restored the config file.
Since then I haven't changed anything in the settings.
After the Debian Update I have removed old cipher and noticed that the cron doesn't work anymore.
When I make the file "froxlor_master_cronjob.php" executable it runs as usual again.

I had installed Froxlor before as a package, that was uninstalled during the update of Debian.

[Release candidate 0.10.0 - It's Froxlor, but with API :)]

ok interesting, only since I made it executable the crons works again.

[Release candidate 0.10.0 - It's Froxlor, but with API :)]

In the package "froxlor-0.10.0-rc2.tar.gz" the "froxlor_master_cronjob.php" is not executable. Couldn't this be stored in tar.gz?

I only came across it because I had to update it manually and the crons didn't run through.

[Release candidate 0.10.0 - It's Froxlor, but with API :)]

ok then we leave that as unresolved

[Release candidate 0.10.0 - It's Froxlor, but with API :)]

I believe you already.

But where does it come from if I didn't execute anything? that wasn't even possible because the problem occurred in the middle of the update process.

[Release candidate 0.10.0 - It's Froxlor, but with API :)]

i had it installed before as a package can there be a problem when the package was uninstalled and i uploaded the data via ftp?

[Release candidate 0.10.0 - It's Froxlor, but with API :)]

but then that would have to been done automatically.

[Release candidate 0.10.0 - It's Froxlor, but with API :)]

No I diddn't

[Release candidate 0.10.0 - It's Froxlor, but with API :)]

I just upgraded my main system to buster and an error occurred with "bind".
In the "named.conf.local" the include of Froxlor was included twice.

//
// Do any local configuration here
//

// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";

include "/etc/bind/froxlor_bind.conf";
include "/etc/bind/froxlor_bind.conf";

 

[Release candidate 0.10.0 - It's Froxlor, but with API :)]

So there were no problems with the update (Debian 9)
I could also create and edit subdomains as well as delete them.
2FA also works

I also installed it on a test server without any problems. (Debian 10)
On the server I'm still testing

[Release candidate 0.10.0 - It's Froxlor, but with API :)]

Are there any points I can test?

 

On 7/7/2019 at 3:20 PM, snoopotic said:

Maybe we can add a hint that it may mean up to a 10-15 minutes "possible outage" on upgrade!? 

After that, your pages went back?