SimpleBackup worked fine for months in Vector 5.8 but now that I have switched to Vector 5.9 it doesn't work at all, in root or in my user account, nor does it create any log or do anything. It is installed according to the directions. I have JRE 1.6, I believe.
Steve: Any frigging clue? I have also written the Vector linux forum. If it is producing a log, I can't find it. For a while I got a log, but no more. Should I go back to an earlier version? I can't recall which version I was using. About 8 months old.
John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have Java Version 6 update 5, and all the other required programs including the pdk gimp tools. It just doesn't run. Either as root or non-root. Nothing happens. I have downloaded it several times with no better result. Vector 5.9 uses slackware 12. I have apm disabled (using acpi). Its a IBM t42 laptop. Perhaps I just have to wait for the clock to turn. I have a full backup scheduled for 2:30 am tomorrow (Monday) morning. Unless I post otherwise, you can assume that this upcoming backup will fail, like all the others since switching to a) Vector 5.9 and b) the IBM t42.
I remember I had install problems when first putting simplebackup on my vector 5.8 machine and we eventually worked that out (5.8 uses slackware 11). However, I don't know how to get to that forum again and think it has been deleted.
John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you were looking for the forum on the SLB's web site, I had to delete it ... it was getting way too many junk postings in the last few months.
So what exactly isn't working? Does the user interface work correctly, or does it not come up? Do the backups not run? If it's the latter, perhaps the upgrade to Vector 5.9 somehow wiped out your cron jobs? You can check by running KCron or simply "crontab -l" from the command line.
If the user interface doesn't work, try running from the command line. Change to the SimpleBackup directory and run "./simplebackupconfig". Tell me what error messages you get, if any. Good luck!
Steve
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the reply. All that works fine (./simplebackupconfig," etc. I go through the complete program. Set the backup time. Etc. All that works as before. However, it won't backup. When the time to run the backup comes around, it does nothing. I tried to the hard drive (Desktop) and to the USB port (where I used to back up). Just blank. Nothing happens at backup time.
John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Steve, with the kind help of the folks at Vector, I figured it out: I did not have cron set to run automatically on boot. As I could not figure out a way to start SimpleBackup without setting a time and waiting for that time to roll around, this error was fatal. I am not sure I am out of the woods yet however as, I think, I was able to run SimpleBackup as user in 5.8 and must run it in root on 5.9.
While I am thinking of it, I wanted to zero out the user SimpleBackup since I was needing to run it in root. Hard to zero it out, i.e. remove all files and directories. However, I thought I should do that rather than potentially having one run in user and the other in boot.
John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It worked for a while, then quit for about a month. I thought is was probably that somehow I wasn't getting cron to load on bootup, though it appeared to be loaded. Did all sorts of silly things, fixed all kinds of things that weren't broke. Then on reviewing your email re crontab -l I decided to learn a bit about crontab. Turned out that the crontab line for some reason referenced a directory that no longer existed. I had unsuccessfully used that directory while trying to get SimpleBackup to run in root and had deleted it. So I concluded that something must be wrong with cron. So I deleted the crontab and reconfigured simplebackup a few days ago and now it works again. I think you need to explain a bit more about dcron on the SimpleBackup Help page. I also think there ought to be an easy way to run Simplebackup without cron, not that anyone would do that, but it would allow easier error tracking.
John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
SimpleBackup worked fine for months in Vector 5.8 but now that I have switched to Vector 5.9 it doesn't work at all, in root or in my user account, nor does it create any log or do anything. It is installed according to the directions. I have JRE 1.6, I believe.
Steve: Any frigging clue? I have also written the Vector linux forum. If it is producing a log, I can't find it. For a while I got a log, but no more. Should I go back to an earlier version? I can't recall which version I was using. About 8 months old.
John
I have Java Version 6 update 5, and all the other required programs including the pdk gimp tools. It just doesn't run. Either as root or non-root. Nothing happens. I have downloaded it several times with no better result. Vector 5.9 uses slackware 12. I have apm disabled (using acpi). Its a IBM t42 laptop. Perhaps I just have to wait for the clock to turn. I have a full backup scheduled for 2:30 am tomorrow (Monday) morning. Unless I post otherwise, you can assume that this upcoming backup will fail, like all the others since switching to a) Vector 5.9 and b) the IBM t42.
I remember I had install problems when first putting simplebackup on my vector 5.8 machine and we eventually worked that out (5.8 uses slackware 11). However, I don't know how to get to that forum again and think it has been deleted.
John
Hi John,
If you were looking for the forum on the SLB's web site, I had to delete it ... it was getting way too many junk postings in the last few months.
So what exactly isn't working? Does the user interface work correctly, or does it not come up? Do the backups not run? If it's the latter, perhaps the upgrade to Vector 5.9 somehow wiped out your cron jobs? You can check by running KCron or simply "crontab -l" from the command line.
If the user interface doesn't work, try running from the command line. Change to the SimpleBackup directory and run "./simplebackupconfig". Tell me what error messages you get, if any. Good luck!
Steve
Steve,
Thanks for the reply. All that works fine (./simplebackupconfig," etc. I go through the complete program. Set the backup time. Etc. All that works as before. However, it won't backup. When the time to run the backup comes around, it does nothing. I tried to the hard drive (Desktop) and to the USB port (where I used to back up). Just blank. Nothing happens at backup time.
John
Steve, with the kind help of the folks at Vector, I figured it out: I did not have cron set to run automatically on boot. As I could not figure out a way to start SimpleBackup without setting a time and waiting for that time to roll around, this error was fatal. I am not sure I am out of the woods yet however as, I think, I was able to run SimpleBackup as user in 5.8 and must run it in root on 5.9.
While I am thinking of it, I wanted to zero out the user SimpleBackup since I was needing to run it in root. Hard to zero it out, i.e. remove all files and directories. However, I thought I should do that rather than potentially having one run in user and the other in boot.
John
It worked for a while, then quit for about a month. I thought is was probably that somehow I wasn't getting cron to load on bootup, though it appeared to be loaded. Did all sorts of silly things, fixed all kinds of things that weren't broke. Then on reviewing your email re crontab -l I decided to learn a bit about crontab. Turned out that the crontab line for some reason referenced a directory that no longer existed. I had unsuccessfully used that directory while trying to get SimpleBackup to run in root and had deleted it. So I concluded that something must be wrong with cron. So I deleted the crontab and reconfigured simplebackup a few days ago and now it works again. I think you need to explain a bit more about dcron on the SimpleBackup Help page. I also think there ought to be an easy way to run Simplebackup without cron, not that anyone would do that, but it would allow easier error tracking.
John