rcmd error on fbackup

[Nicky_5]

Hi all,
I am backing up one HP machine remotely, using another machines tapedrive with the fbackup command.(i have pasted the command below)

this has been working fine all this while until we changed the IP address of the other machine (the one with the tape drive).
now it gives me the following error:

fbackup(1421): no history is available for graph file /var/adm/fbackupfiles/graphdb (below level 0)
fbackup(1004): session begins on Tue Mar 15 13:33:32 2005
rcmd: socket: Protocol failure in circuit setup
fbackup(3004): writer aborting
fbackup(1002): Backup did not complete : Reader or Writer process exit

I have checked to see that my machine delta (the one without the tape dirve) can recognise titan and ping / telnet/ rlogin to it without any problem and the other way round (titan to delta) is also possible.

The command i run is:

fbackup -u -v -g /var/adm/fbackupfiles/graphdb -I /var/adm/fbackupfiles/index.db -c /etc/sam/br/fbackup_config -d /var/adm/fbackupfi
les/dates -f titan:/dev/rmt/0m > output 2>&1

[Robert Bennett_3]

Nicky -

This is just a stab in the dark -

Try running the command without the -u after the fbackup. You may not have anything to update after the name change. If this works then add the -u back in for susequent backups.

Hope this helps

B

[Bill Hassell]

fbackup uses remsh to talk to other system so start with: remsh titan pwd

My guess is that it will fail. Whenever an IP address (or hostname) gets changed, a lot of things break, in this case DNS on your local system. Start by verifying that nslookup $(hostname) actually returns a valid IP address. Then reverse the process with nslookup 12.34.56.78 (use your local IP address). Now do the same for titan from delta. If all is well, go onto titan and repeat the 4 nslookups (self and remote).

Finally, try a traceroute to titan from delta to make sure the routing is correct. And also make sure that titan's .rhosts file is 600 (NO read or wirte by anyone except the owner)

[Nicky_5]

hi all,
Thankyou for yourresponse, but the problem is not yet solved.
i have taken care of the following:
1) i can do forward and reverse lookup for both machines on both machines.
2) the permissions of the .rhosts file is 600 on both machines and it contains entry for both machines with host name, ip address, and hostname.domain format.
3) i created /etc/hosts.equiv file with permission 600 on both machine containing the hostsname of both machine


i can do rlogin / remsh from delta
(remsh titan pwd) sucessfully, but when i try the other way round (form titan to delta) it fails

Also when i do rlogin titan (on delta) it is sucessful. But when i do rlogin delta (from titan) it asks for a passwors and let me in only when i give the password.

Could this be the problem?

[Bill Hassell]

The 'r' commands (rlogin, rcp and remsh) are designed to run commands on remote systems without a password. When rlogin asks for a password, it has failed. That's why you use remsh for testing (which will also fail). Now if the tape drive is on titan and from delta, the command: remsh titan pwd works OK, then check that rmt (the remote mt program) is available (ll /usr/sbin/rmt, should be 555 permissions, owned by bin). Make sure that the remote system (titan) has not had upper level permissions messed up (/ must be 755, owned by root, /usr and /usr/sbin must be 555, owned by bin).

[Nicky_5]

hi,

I have checked and confirmed that all the permissions are just as you mentioned. I am trying the rmt command right now, but it seems to be taking alog time to gat a response. I am not sure if i am using it correctly. but after readng the man pages, heres what i am running on delta

rmt -s titan:/dev/rmt/0m

Is this correct?

[Bill Hassell]

No, ther man page for rmt defines it's usage. There are no command line parameters, only a stdin message which would look like this:

O/dev/rmt/0m

which was sent from fbackup to titan using remsh. rmt then responds with either A### or E###\nerror-message where ### are numbers. The actual protocol is not very well documented but since it used to work until you changed IP addresses, I would make sure your /etc/hosts has both delta and titan listed, then change /etc/nsswitch.conf host resolution to:

hosts: files[NOTFOUND=continue UNAVAIL=continue] dns

This insures that hosts will be used first to eliminate any issues with DNS.