05-17-2006
Thanks for the feedback. I've loaded "stape" again, and verified that "tgt" is loaded. I don't see "ccio", "bus_adaptor", or "c720" listed in my list of available modules via SAM. Unfortunately, I'm still unable to execute the "Add" function within the tape drive area of SAM.
![Frown Smilie](https://www.unix.com/images/smilies/frown.gif)
Looks like I'm gonna have to make a call to their support center and see if I can get someone out here. Once again, thanks for the help!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I do daily backups running a shell script. I use 6 different tapes for each day (monday through saturday).
First of all I insert the tape then run the script and when it finished I eject the tape.
Until today I was doing this with no problem, but now I'm getting this message constantly (even... (4 Replies)
Discussion started by: rrivas
4 Replies
2. UNIX for Dummies Questions & Answers
I'm running SCO OS 505 on a Compaq proliant 1600, and my tape drive will just not work. It was working properly and whent to Sh?ts when I tried to get the cd rom working. I have uninstalled any configured tape drive and rebooted and then configured a tape drive and rebooted still nothing. I'm... (4 Replies)
Discussion started by: kikkin
4 Replies
3. UNIX for Dummies Questions & Answers
When I am trying to read any tape I getthe following message on my screen:
"stp: Error on SCSI tape=0 (ha=0 id=6 lun=0)"
Does anybody know how to solve this problem and what the message means.
I already have rebooted the server and cleaned the heads of the tape unit.
HELP!!!! (1 Reply)
Discussion started by: Andre
1 Replies
4. Solaris
hi-
I just installed a quad gigaswift ethernet scsi card to my sunblade 150. I checked with the docs, and got all of the required drivers on the box. Now, I'm trying to mount an external scsi tape drive with no luck. I set the scsi address on the external drive to 0. Here's what I'm coming... (9 Replies)
Discussion started by: ECBROWN
9 Replies
5. SCO
Hello,
I'm having some issues with installing SCSI tape drive on SCO 5.0.6
hardware config shows the following adapters
%adapter 0xE800-0xE8FF 10 - type=alad ha=0 bus=0 id=7 fts=sto
%adapter 0x0170-0x0177 15 - type=IDE ctlr=secondary dvr=wd
%adapter - 3 - ... (3 Replies)
Discussion started by: ananth_ak
3 Replies
6. SCO
Running into an interesting problem here:
I can add the tape with "mkdev tape" the system appears to see it wwith "hwconfig -hc" however a 'tape status /dev/rStp0' says 'no device found',
checked the configuration files in 'etc' all appear to be correct.
Any suggestion appreciated
Jim (3 Replies)
Discussion started by: jimj1369
3 Replies
7. Solaris
Hi Gurus,
I need help. Mine is an Ultra 10 machine running on solaris 7. Problem with solaris 7 is, it can no longer recognize IDE disks greater that 10GB. My workaround is ro use an external SCSI disk since it is recognizable with solaris 7. I backup my filesystems (residing on the IDE... (2 Replies)
Discussion started by: domesat
2 Replies
8. UNIX for Dummies Questions & Answers
Currenty running SCO Openserver 6 at a Dell PowerEdge T300. I recently installed a driver for an Adaptec SCSI card (adpu320). When I connect a tape drive to it and re-start the system,it freezes and displays the following message: "WARNING: adpu320: Command timed out (ha= 4)" and the system... (2 Replies)
Discussion started by: RicardoM
2 Replies
9. Hardware
I've had a scsi hard drive, scsi tape drive, and cd rom working off an adaptec 29160 controller. Everything worked great until a few days ago. I begin getting tar format errors (running sco 5.0.6) on the tape drive and occasionally the entire system would hang up while trying to access data on... (0 Replies)
Discussion started by: powwm
0 Replies
10. Programming
Having a script.pl how can I automatically download from CPAN all required modules and install and update as required? Something like "emerge -uDNav world" for the perl?
---------- Post updated at 05:38 PM ---------- Previous update was at 05:28 PM ----------
Doesn't matter I've found it
... (6 Replies)
Discussion started by: Tribe
6 Replies
LEARN ABOUT DEBIAN
sam_overview
SAM_OVERVIEW(8) Corosync Cluster Engine Programmer's Manual SAM_OVERVIEW(8)
NAME
sam_overview - Overview of the Simple Availability Manager
OVERVIEW
The SAM library provide a tool to check the health of an application. The main purpose of SAM is to restart a local process when it fails
to respond to a healthcheck request in a configured time interval.
During sam_initialize(3), a duplicate copy of the process is created using the fork(3) system call. This duplicate process copy contains
the logic for executing the SAM server. The SAM server is responsible for requesting healthchecks from the active process, and controlling
the lifecycle of the active process when it fails. If the active process fails to respond to the healthcheck request sent by the SAM
server, it will be sent a user configurable signal (default SIGTERM) to request shutdown of the application. After a configured time
interval, the process will be forcibly killed by being sent a SIGKILL signal. Once the active process terminates, the SAM server will cre-
ate a new active process.
The Simple Availability Manager is meant to be used in conjunction with the cpg service. Used together, it is possible to restart a cpg
process that fails healthchecking during operation.
The main features of SAM include:
o A configurable recovery policy.
o A configurable time interval for health check operations.
o A notification via signal before recovery action is taken.
o A mechanism to indicate to the application the number of times an active process has been created by the SAM server.
o Both application driven health checking and event driven health checking.
Initializing SAM
The SAM library is initialized by sam_initialize(3). sam_initalize(3) may only be called once per process. Calling it more then once has
undefined results and is not recommended or tested.
Setting warning callback
User configurable signal (default SIGTERM) is sent to the application when a recovery action is planned. The application can use the sig-
nal(3) system call to monitor for this signal.
There are no special constraints on what SAM apis may be called in a warning callback. After time_interval expires, a SIGKILL signal is
sent to the active process to force its termination.
Registering the active process
The active process is registered with SAM by calling sam_register(3). This function should only be called one time in a process. After a
recovery action is taken, the new active process will begin execution at the next line of code in a user process after sam_register(3).
Enabling event driven healthchecking
Two types of healthchecking are available to the user. The first model is one where the user application healthchecks during its normal
operation. It is never requested to healtcheck, and if the active process doesn't respond within the time interval, the process will be
restarted.
A more useful mechanism for healthchecking is event driven healthchecking. Because this model is directed by the SAM server, It isn't nec-
essary to guess or add timers to the active process to signal a healthcheck operation is successful. To use event driven healthchecking,
the sam_hc_callback_register(3) function should be executed.
BUGS
SEE ALSO
sam_initialize(3), sam_finalize(3), sam_start(3), sam_stop(3), sam_register(3), sam_warn_signal_set(3), sam_hc_send(3), sam_hc_call-
back_register(3)
corosync Man Page 12/01/2009 SAM_OVERVIEW(8)