fbackup fails for remote machine

[Dave Chamberlin]

Hello,

I am using fbackup to write to a DLT on another machine, and the last time I did this there were no problems. Now, the backup fails with:
fbackup(3301): could not open output file saturn:/dev/rmt/0m
I can of course connect and resolve the remote machine. On the remote machine, fbackup works correctly. Any ideas on what is happening?

Thanks

[Sridhar Bhaskarla]

Hi,

You will need to have .rhosts setup for root's account on the machine saturn.

DId you try rlogin saturn -l root and see if you can login without prompting for a password?.

-Sri

[Dave Chamberlin]

Hi Sridhar,

Yes the remote server has a .rhosts file and rlogin does work.

Thanks

[Jeff Schussele]

Hi Dave,

Do you know for a fact that

1) That's the proper drive device file(not 1m or 0mn?)
2) There's a tape in the drive
3) It's a good tape

Telnet or rlogin to saturn & try a local (to it) tar or fbackup to rule all above out.

Rgds,
Jeff

[Sridhar Bhaskarla]

Hmmm... if it works and fbackup is running correctly on the remote host, then I would check for the file /usr/sbin/rmt on the remote host and see if it has correct permissions bin:bin with execute permissions.

-Sri

[S.K. Chan]

What about hostname resolution on both machines ? Are they consistent ? Try putting both "short name" and full domain name in the .rhosts file and see if it helps.

[Dave Chamberlin]

Hi Jeff,

Yep - I know it is correct - On the remote machine I did an ioscan to verify the device and successfully backed up a directory using the same command that I tried on the other machine (but without the host part of the file name).

thanks

[Dave Chamberlin]

The file /usr/sbin/rmt is set to 555 bin:bin so that is ok. The rhosts files had long names, but I added short names as well. Same behavior.

[Dave Chamberlin]

I fixed it. I checked inetd.conf on saturn and noted that the line for shell was commented out. Uncommented, ran inetd -c and the backup now runs. Learn something new every day...
Thanks for the help though.

[Jeff Schussele]

Hi (again) Dave,

Sorry, I missed that next to last sentence in your org post that you'd already done that.

Next thing to consider might be patch level. Although I don't see any mention of this particular problem in these you may wish to try:

1) PHCO_25424 (fbackup cumulative)
2) PHNE_23003 (r-commands cumulative)

Neither requires reboot. These are both 11.0 patches.

Rgds,
Jeff