no backups when running koha-run-backups
Hi, The scenario - Koha 19.11.11, MariaDB 10.5 on Debian 10. The problem - no backups are being generated under the default backupdir either via cron or when running koha-run-backups manually. It exists without any output or error shown on STDOUT. Interestingly, a regular mysqldump using the koha db user and pass from koha-conf.xml works flawlessly. Anyone else facing this issue? thanks in advance -- Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg
just in case... Isn't the instance named "demo"? 58 for name in $(koha-list --enabled | grep -Fxv demo) Le mar. 17 nov. 2020 à 06:56, Indranil Das Gupta <indradg@l2c2.co.in> a écrit :
Hi,
The scenario - Koha 19.11.11, MariaDB 10.5 on Debian 10.
The problem - no backups are being generated under the default backupdir either via cron or when running koha-run-backups manually. It exists without any output or error shown on STDOUT.
Interestingly, a regular mysqldump using the koha db user and pass from koha-conf.xml works flawlessly.
Anyone else facing this issue?
thanks in advance -- Indranil Das Gupta L2C2 Technologies
Phone : +91-98300-20971 WWW : http://www.l2c2.co.in Blog : http://blog.l2c2.co.in IRC : indradg on irc://irc.freenode.net Twitter : indradg _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Sorry then, no idea what's happening. I can only confirm it works for me on master! I'd try to remove the /dev/null redirection 60 koha-dump "$name" > /dev/null Maybe you will have info about what's going on. Le mar. 17 nov. 2020 à 11:27, Indranil Das Gupta <indradg@l2c2.co.in> a écrit :
On Tue, 17 Nov 2020 at 15:43, Jonathan Druart <jonathan.druart@bugs.koha-community.org> wrote:
just in case... Isn't the instance named "demo"?
58 for name in $(koha-list --enabled | grep -Fxv demo)
Currently only a single instance name medica on the box.
-indranil
On Tue, 17 Nov 2020 at 16:07, Jonathan Druart < jonathan.druart@bugs.koha-community.org> wrote:
Sorry then, no idea what's happening. I can only confirm it works for me on master!
I'd try to remove the /dev/null redirection 60 koha-dump "$name" > /dev/null
I had done that earlier it was showing the following text and immediately exiting the script Dumping Koha site medica: thanks to @Joubu's pointer, it made me look more closely at the dump_instance() function in the koha-dump. apparently the following line was the reason behind the script's sudden termination: mysqlhost="$( xmlstarlet sel -t -v 'yazgfs/config/hostname' $kohaconfig )" In the end it was the given instance's empty 'yazgfs/config/hostname' node. Filling it with 'localhost' sorted out the issue. cheers -Indranil
participants (2)
-
Indranil Das Gupta -
Jonathan Druart