Technical article 104748

OpenServer 5, Root gets "permission denied" error message on network backups.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6OpenServer 5.0.7

Written · Last revised

Problem

I am logged in as the Superuser: root on system A.  I have
created the /.rhosts file on System A, giving System B user
equivalency for the root account.

I then telnet/rlogin into System B and create the file /.rhosts on System B, establishing user equivalency for System A.

Next, I start the SCOAdmin Backup Manager on System B and choose the Menu options:

(S)chedule --> (N)ew Remote Filesystem

I open System A as the remote filesystem host and add selected filesystems from System A to the list of known filesystems on System B.

Then I choose the following Menu options:

(B)ackup --> Run (U)nscheduled --> (S)elected Filesystems

After setting the media options, I get the dialog box message which tells me:

Filesystem system.a.com /dev/bootsystem
This may take a while.

After a few seconds, I get an error message in another message box:

Backup of filesystem system.a.com /dev/boot failed
Under the details option, I see:

"General failure occurred in processing the request. Error occurred reading or writing the backup archive: Process terminated with exit status 1. cpio: I/O error on write() : Broken pipe (error 32)

Error occurred while accessing the media device: Permission denied."

Why did root get a "permission denied" error message for the backup operation when I have established user equivalency for the root account?

Cause

Backup requests that are issued across the network are done under the ownership of the user, backup.

Regardless of which user account initiates the remote backup request (root, backup, or another user) the actual requests are submitted as the account, backup.

Solution

You must establish user equivalency for the backup
account between the two systems.  The following is
an excerpt from the System Administration Guide:
----------------------------------------------------
System Administration Guide
Chapter 3, Backing up filesystems
Establishing backup user equivalence

Before you use the Backup Manager to back up a filesystem on a remote host, you must establish user equivalence for the backup user account on both the remote and local hosts. To do this, use the User Equivalence Manager. On the local system:

1. Select Open from the File menu.

2. Enter or select the backup user and click on OK.

3. Select Add Equivalence from the User menu.

4. Enter the name of the remote host and enter
   backup in the ``Remote user'' field.

5. Select Save from the File menu.

Repeat steps 1 through 5 on the remote system.

Make sure that the /usr/backup/.rhosts files on both the local and remote systems are owned by the backup user:

-rw------- 1 backup  backup  878 Oct 21 15:57 .rhosts

To verify that backup user equivalence is established, check the contents of the /usr/backup/.rhosts files. For example, the .rhosts file on pdxbox contains:

hawthorne            backup
The .rhosts file on hawthorne contains:
pdxbox               backup
----------------------------------------------------

Once you have established user equivalence for the backup account between two systems, you will be able to successfully complete remote backups between those two systems, as long as the user who is invoking the Backup Manager has the proper System Authorizations.

See also

`Adding user equivalence' in the Networking Guide.

From the Xinuos technical article database, record 104748. Reproduced with permission. The original is at www.sco.com/ta/104748, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.