bobs 0.6.0 - new installation fails, previous install worked - was Re: [Bobs-devel] new installation question

[Bishop <bi...@pl...>]

James,

Your previous installation - was it also 73 backed onto 9?  There may be 
differences in the two that can help.

How'd you get the source to that bobs install?  Any chance that some cvs 
code may have sneaked into this new install package where the old 
package definitely had no chance?  Also, the old installation definitely 
had no key, right, and we're sure that it couldn't have just been doing 
ssh before and had a key neatly left there by someone before?  I think 
you told me this already, and no, I haven't looked into fixing the spec 
file yet - too much (paid/regular) work getting in the way (bug me this 
weekend when I get back home so I get onto the right project and stay 
there).

When it's all said and done, did the key fix it?  (a question I'm only 
asking for those who may later read the archive and Just Want It to Work).

- - -

Jochen,

Has there been any config changes around 060 where it may have defaulted 
into some ssh kind of connection where a previous version would have 
been some kind of clear rsync instead?

  - bishop

James W. Beauchamp wrote:
> Jochen
> I didn't think that method was implemented in 0.6.0?  That it was only 
> in CVS.  I'm just using the .tar 0.6.0.  plus rsync_ssh is not one of 
> the selections in the drop down box when you set up the share in BOBS, 
> plus the admin help page still says "Help function is not yet implemented."
> 
> Any other ideas?
> (BTW this is on RH9 if that matters - the server being backed up is 
> running RH73)
> James
> 
> 
> Jochen Metzger wrote:
> 
>> Hi,
>>
>>
>>  
>>
>>> This was in the logwatch:
>>> Finished /backup/bobsdata/current/process/cmd/cmd.1074617726.php
>>> Starting /backup/bobsdata/current/process/cmd/cmd.1074617727.bash
>>> Host key verification failed.
>>> rsync: connection unexpectedly closed (0 bytes read so far)
>>> Starting /backup/bobsdata/current/process/cmd/cmd.1074617741.bash
>>> Permission denied, please try again.
>>> Permission denied, please try again.
>>> Permission denied (publickey,password,keyboard-interactive).
>>> rsync: connection unexpectedly closed (0 bytes read so far)
>>> rsync error: error in rsync protocol data stream (code 12) at io.c(165
>>>
>>>
>>>   
>>
>> it seems to be that you are using rsync_ssh as backup method
>>
>>  
>>
>>> Here's the straight output from running cmdloop from the command line:
>>>
>>> [root@basalt process]# ./cmdloop
>>> Starting ./cmd/cmd.1074617761.bash
>>> root@10.0.1.128's password:
>>>
>>> Sorry for the lack of detail the first time!
>>>
>>> James
>>>
>>>
>>>   
>>>
>>>> Please give us some more detail.
>>>>
>>>>
>>>> If you use cvs bobs and "rsync_ssh" as backup method, then please 
>>>> take a
>>>> look at the admin help page to proceed with the setup.
>>>>     
>>
>> Please check the admin help page and create a public / private key pair
>> on your backuped server / bobs server.