Hello,
I just installed it and waited a day for it to run, and this is the output I'm getting.. not sure what the issue might be, but it didn't backup any files.
/home/SimpleBackup/bkup: line 127: date: command not found
/home/SimpleBackup/bkup: line 128: date: command not found
/home/SimpleBackup/bkup: line 129: date: command not found
/home/SimpleBackup/bkup: line 130: date: command not found
/home/SimpleBackup/bkup: line 182: touch: command not found
Starting backup in directory '/'
/home/SimpleBackup/bkup: line 236: date: command not found
Full backup last performed about 0 day(s) ago.
/home/SimpleBackup/bkup: line 246: [: too many arguments
Performing incremental backup using '/root/.simplebackup/timestamp'
/home/SimpleBackup/bkup: line 253: ls: command not found
Copying files...
/home/SimpleBackup/bkup: line 276: date: command not found
/home/SimpleBackup/bkup: line 294: touch: command not found
Done collecting and compressing files; return code 127.
Done!
Some help deciphering this would be greatly appreciate. Thank you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I changed some things in the config file and ran it manually, now it seems to have picked up the "last time it was run" variable properly. and it is performing a full backup now.
It does however say that it is "starting backup in directory '/'"
Which is unsettling, because I configured it to go to /backup (which is a separate drive).
Is this normal?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, this time I did actually get it figured out.. there was a extraneous path command in the crontab that must have been overriding the default system path setting. Now it runs error free! woohoo! Thanks for this, it's great.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm glad you got it working. The extraneous PATH command must have been in the crontab from something else (other than SLB), right? SLB doesn't write a PATH command to the crontab, though it does add a "SHELL=" line.
Glad you like the program!
- Steve
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I just installed it and waited a day for it to run, and this is the output I'm getting.. not sure what the issue might be, but it didn't backup any files.
/home/SimpleBackup/bkup: line 127: date: command not found
/home/SimpleBackup/bkup: line 128: date: command not found
/home/SimpleBackup/bkup: line 129: date: command not found
/home/SimpleBackup/bkup: line 130: date: command not found
/home/SimpleBackup/bkup: line 182: touch: command not found
Starting backup in directory '/'
/home/SimpleBackup/bkup: line 236: date: command not found
Full backup last performed about 0 day(s) ago.
/home/SimpleBackup/bkup: line 246: [: too many arguments
Performing incremental backup using '/root/.simplebackup/timestamp'
/home/SimpleBackup/bkup: line 253: ls: command not found
Copying files...
/home/SimpleBackup/bkup: line 276: date: command not found
/home/SimpleBackup/bkup: line 294: touch: command not found
Done collecting and compressing files; return code 127.
Done!
Some help deciphering this would be greatly appreciate. Thank you.
I changed some things in the config file and ran it manually, now it seems to have picked up the "last time it was run" variable properly. and it is performing a full backup now.
It does however say that it is "starting backup in directory '/'"
Which is unsettling, because I configured it to go to /backup (which is a separate drive).
Is this normal?
Ok, my first message still holds true, the result was the same error list when the cron tried to run the software.
Ok, this time I did actually get it figured out.. there was a extraneous path command in the crontab that must have been overriding the default system path setting. Now it runs error free! woohoo! Thanks for this, it's great.
Greg,
I'm glad you got it working. The extraneous PATH command must have been in the crontab from something else (other than SLB), right? SLB doesn't write a PATH command to the crontab, though it does add a "SHELL=" line.
Glad you like the program!
- Steve