Hello !
It seems that the weekly and monthly backups do not work, even if they are activated in WHM. Does anyone have an and ideea what could be the cause ? Is it possible to be the OS (FreeBSD 6.2) ?
Hello !
It seems that the weekly and monthly backups do not work, even if they are activated in WHM. Does anyone have an and ideea what could be the cause ? Is it possible to be the OS (FreeBSD 6.2) ?
"A dog has raised it’s hind leg on the age of nevermore !"
-- Rolf
The problem is (hopefuly) solved. I opened a ticket it seems that they know about it, only that the issue is fixed only on EDGE. The one who answered me was kind enough to fix it for me without upgrading cPanel to EDGE.
The fix is rather straight foward. When executed via cron, if no PATH is setup by the system admin, or script writer, then a default PATH is used, which on FreeBSD is:
cpbackup was, for quite a while, simply calling the system tools, such as rsync, without specifying the full path to the binary. On FreeBSD, these are often in /usr/local/bin.Code:/bin:/usr/bin
The simple fix is to add /usr/local/bin to the $ENV{'PATH'} statement near the top of the script, like:
Code:$ENV{'PATH'} .= ":/sbin:/usr/local/bin";
The fixed version that is in EDGE doesn't do that, rather it looks up the actual path to the binary and uses the full path when calling it. There are also a number of other fixes in the EDGE version which make it non-portable to non-EDGE setups.
Due to the path issues, the script works fine when called manually, but would never perform the rsync to weekly and monthly when called via cron.
By the way, please feel free to open support tickets specific to FreeBSD as we are striving to improve our support of that platform. Our primary target platform is Linux, which uses SysV semantics and doesn't always translate well to a BSD platform.
I am glad to see this finally fixed. I had been hunting for the solution to this problem for years without any success. Hopefully this will fix the backup issues on FreeBSD once and for all.![]()