I just tried upgrading greyhole to 0.6.22-1 and now I get the following messages in the greyhole.log:
Aug 23 23:45:51 6 daemon: Greyhole (version 0.6.22) daemon started.
Aug 23 23:45:51 7 daemon: Loading graveyard backup directories...
Aug 23 23:45:51 7 daemon: Missing some directories. Need 2, currently have 0. Will select more...
Aug 23 23:45:51 7 daemon: Randomly picked /var/hda/files/drives/sdh1/gh/.gh_graveyard_backup
Aug 23 23:45:51 7 daemon: Randomly picked /var/hda/files/drives/sdh1/gh/.gh_graveyard_backup
Aug 23 23:45:51 7 daemon: Randomly picked /var/hda/files/drives/sdd1/gh/.gh_graveyard_backup
Aug 23 23:45:51 2 daemon: Can't insert new settings for graveyard_backup_directory: near "ON": syntax error
The daemon then shuts down and gets restartet again by the watchdog and the same messages appear over and over again.
Any clues what the cause is?
(Posted in this thread because I tried this because of the same problem with the --going command)
Problem With --going Command
Re: Problem With --going Command
My bad! This other change was introduced earlier, and is incompatible with SQLite, which is what Amahi uses for Greyhole.
I fixed it in 0.6.23 (links updated in previous post):
I fixed it in 0.6.23 (links updated in previous post):
Code: Select all
rpm -Uvh http://greyhole.pommepause.com/releases/hda-greyhole-0.6.23-1.x86_64.rpm
rpm -Uvh http://greyhole.pommepause.com/releases/hda-greyhole-0.6.23-1.i386.rpm
- Guillaume Boudreau
Re: Problem With --going Command
Your latest fix did the job. Now my system is up and running again.
Thank you very much
Thank you very much

-
- Posts: 16
- Joined: Sat Aug 21, 2010 9:44 pm
Re: Problem With --going Command
Hi,
I updated greyhole to 0.6.23, unchecked then rechecked my sdb1 drive in amahi, ran --fsck, then ran the --going command but still don't seem to be having much luck. The files on my sdb1 drive have not been moved (as far as I can tell) to the other drives.
I have zipped my log file and sent it through in case it will help.
I updated greyhole to 0.6.23, unchecked then rechecked my sdb1 drive in amahi, ran --fsck, then ran the --going command but still don't seem to be having much luck. The files on my sdb1 drive have not been moved (as far as I can tell) to the other drives.
I have zipped my log file and sent it through in case it will help.
Re: Problem With --going Command
bradwebber: I'd need access to your HDA to help you further.
Create me a user in Amahi, and either forward a random public port to your HDA port 22, or setup the VPN.
You can pm me the details.
I'd also need my user to have sudo access, to be able to restart the Greyhole service.
Create me a user in Amahi, and either forward a random public port to your HDA port 22, or setup the VPN.
You can pm me the details.
I'd also need my user to have sudo access, to be able to restart the Greyhole service.
- Guillaume Boudreau
Re: Problem With --going Command
With access to bradwebber HDA, I was able to resolve the issue.
Fixed RPMs:
Sorry for the mess!
bradwebber: I didn't run --going on your HDA, I'll let you do it and confirm it worked.
Fixed RPMs:
Code: Select all
rpm -Uvh http://greyhole.pommepause.com/releases/hda-greyhole-0.6.24-1.x86_64.rpm
rpm -Uvh http://greyhole.pommepause.com/releases/hda-greyhole-0.6.24-1.i386.rpm
bradwebber: I didn't run --going on your HDA, I'll let you do it and confirm it worked.
- Guillaume Boudreau
-
- Posts: 16
- Joined: Sat Aug 21, 2010 9:44 pm
Re: Problem With --going Command
Hi,
I did a quick --fsck (not sure if it was required or not) then ran --going and it is all looking really good. I took a quick look at the greyhole.log as well and couldn't spot anything out of the ordinary.
It is going to take an hour or two for the operation to complete because there is about 200GB to move off the disk. I'll jump back on tomorrow after work and confirm that everything ran as expected.
A huge thanks Guillaume, you're a legend.
I did a quick --fsck (not sure if it was required or not) then ran --going and it is all looking really good. I took a quick look at the greyhole.log as well and couldn't spot anything out of the ordinary.
It is going to take an hour or two for the operation to complete because there is about 200GB to move off the disk. I'll jump back on tomorrow after work and confirm that everything ran as expected.
A huge thanks Guillaume, you're a legend.
-
- Posts: 16
- Joined: Sat Aug 21, 2010 9:44 pm
Re: Problem With --going Command
Just a quick note to let everyone know that everything seems to be running perfectly with the --going command.
Cheers.
Cheers.
Who is online
Users browsing this forum: No registered users and 13 guests