ITEM: BR1720L

sbfwd: Cannot attach to shared memory for buffer status.

Env:
  AIX 3.2.5
  RISC 590
  Tape 4mm 4gb
  sysback 3.3.3.7

Desc:
  Customer does a full system backup to a remote tape
  drive without getting any error messages.  When
  he tries to run this command to verify it it fails:

  sysrestore -lxf vdev0 -h mars -v datavg

sbfwd: Cannot attach to shared memory for buffer status.
sbfwd: Permission denied

Explained the message is comming from the sbfwd2 command.  
A shared memory segment has been created but is failing 
on the attach.  The shared memory segment is created when 
operating against sysack parallel virtual tape drives.  
This problem will only exist when it is run against a 
remote parallel tape drive.  The problem is that sysback 
will open up the socket as the sbnet user on the server 
side.  It will run the sbfwd2 command as sbnet user.  
Root is the only user who can open up shared memory 
segments.

Workaround (DONE ON THE SEVER MACHINE)
---------------------------------------
chmod ug+s /usr/sbin/sbfwd2

Opened up a problem record with the developer to add
this fix to sysback.3.3.3.11

The problem is how the shared memory segments where
being created for the sbfwd2 command.  It was setting
the wrong permissions on the shared memory segment.

Next Action:
  Sending out sysback.3.3.3.11

 



Support Line: sbfwd: Cannot attach to shared memory for buffer status. ITEM: BR1720L

Dated: November 1996 Category: N/A

This HTML file was generated 99/06/24~13:30:20

Comments or suggestions?
Contact us