I have a strange behavior when I modify a group by sql via crontab
if i do this in my terminal:
sudo sqlite3 /etc/pihole/gravity.db "update 'group' set 'enabled' = 0 where name = 'basmala_internet';" ; pihole -g
I can see that the flows are going well => it's good
however when i do this in the crontab
30 18 * * 1-5 sudo sqlite3 /etc/pihole/gravity.db "update 'group' set 'enabled' = 0 where name = 'basmala_internet';" ; pihole -g
flows are still blocked. => it's not good
what is even stranger is that visually on the group management GUI I see that it is disabled. => it's ok
that's why I added "pihole -g" because I said to myself that maybe it's not only the value in base to change but something else.
the problem with crontab as root is that I will not be able to do the command pihole with the non-root user or else I will have to do something like su pi ...?
I need these two commands to be chained
i will try your command and update my post if it's ok
Sorry, I don't understand what you try to say. If you create a crontab for the root user there is no need for sudo within the commands. Both will be executed as root (who has sudo-power).
It should work like this
sqlite3 /etc/pihole/gravity.db "update 'group' set 'enabled' = 0 where name = 'basmala_internet';" ; pihole restartdns reload-list
Please try, bu I think it is better not to update but create a new reply.
Is there a specific reason you have the FTL branch on a dev version (and not the master)? For example, troubleshooting with a specfic build? FTL crash resolution?
*** [ DIAGNOSING ]: FTL version
[✓] FTL: vDev-5ad55e8 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
Edit - in fact you have quite the mismatch, including a branch that we haven't released:
2020-06-10 15:00:26: (mod_fastcgi.c.421) FastCGI-stderr: PHP Warning: SQLite3::query(): Unable to prepare statement: 5, database is locked in /var/www/html/admin/api_speedtest.php on line 115
concerning the management of the branches how to return to the standard version? without reinstalling
it's true that with the release of V5 I no longer have a reason to be on the other branch