HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Syslog error messages
Operating System - HP-UX
1835259
Members
2229
Online
110078
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2008 08:51 AM
01-16-2008 08:51 AM
Syslog error messages
My syslog in various servers give the following errors some time, any body got an idea who is this all about:
Jan 15 08:02:16 usunx45 vmunix: SCSI TAPE: dev = 0xcd044000 Failed open - st_san_safe enabled
Jan 15 08:02:16 usunx45 vmunix: SCSI TAPE: dev = 0xcd193000 Failed open - st_san_safe enabled
Jan 15 08:02:16 usunx45 vmunix: SCSI TAPE: dev = 0xcd1b3000 Failed open - st_san_safe enabled
Jan 15 08:02:16 usunx45 vmunix: SCSI TAPE: dev = 0xcd1c3000 Failed open - st_san_safe enabled
Jan 15 08:02:16 usunx45 vmunix: SCSI TAPE: dev = 0xcd044000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd1d3000 Failed open - st_san_safe enabled
Jan 15 08:02:16 usunx45 vmunix: SCSI TAPE: dev = 0xcd193000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd1e3000 Failed open - st_san_safe enabled
Jan 15 08:02:16 usunx45 vmunix: SCSI TAPE: dev = 0xcd1b3000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd1f3000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd1c3000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd203000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd1d3000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd213000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd1e3000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd223000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd1f3000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd065000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd203000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd075000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd213000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd233000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd223000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd245000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd065000 Failed open - st_san_safe enabled
Jan 15 08:02:28 usunx45 vmunix: SCSI TAPE: dev = 0xcd0e3000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd075000 Failed open - st_san_safe enabled
Jan 15 08:02:28 usunx45 vmunix: SCSI TAPE: dev = 0xcd0f3000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd233000 Failed open - st_san_safe enabled
Jan 15 08:02:28 usunx45 vmunix: SCSI TAPE: dev = 0xcd103000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd245000 Failed open - st_san_safe enabled
Jan 15 08:02:28 usunx45 vmunix: SCSI TAPE: dev = 0xcd113000 Failed open - st_san_safe enabled
Jan 15 08:02:28 usunx45 vmunix: SCSI TAPE: dev = 0xcd0e3000 Failed open - st_san_safe enabled
Jan 15 08:02:16 usunx45 vmunix: SCSI TAPE: dev = 0xcd044000 Failed open - st_san_safe enabled
Jan 15 08:02:16 usunx45 vmunix: SCSI TAPE: dev = 0xcd193000 Failed open - st_san_safe enabled
Jan 15 08:02:16 usunx45 vmunix: SCSI TAPE: dev = 0xcd1b3000 Failed open - st_san_safe enabled
Jan 15 08:02:16 usunx45 vmunix: SCSI TAPE: dev = 0xcd1c3000 Failed open - st_san_safe enabled
Jan 15 08:02:16 usunx45 vmunix: SCSI TAPE: dev = 0xcd044000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd1d3000 Failed open - st_san_safe enabled
Jan 15 08:02:16 usunx45 vmunix: SCSI TAPE: dev = 0xcd193000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd1e3000 Failed open - st_san_safe enabled
Jan 15 08:02:16 usunx45 vmunix: SCSI TAPE: dev = 0xcd1b3000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd1f3000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd1c3000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd203000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd1d3000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd213000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd1e3000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd223000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd1f3000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd065000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd203000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd075000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd213000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd233000 Failed open - st_san_safe enabled
Jan 15 08:02:17 usunx45 vmunix: SCSI TAPE: dev = 0xcd223000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd245000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd065000 Failed open - st_san_safe enabled
Jan 15 08:02:28 usunx45 vmunix: SCSI TAPE: dev = 0xcd0e3000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd075000 Failed open - st_san_safe enabled
Jan 15 08:02:28 usunx45 vmunix: SCSI TAPE: dev = 0xcd0f3000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd233000 Failed open - st_san_safe enabled
Jan 15 08:02:28 usunx45 vmunix: SCSI TAPE: dev = 0xcd103000 Failed open - st_san_safe enabled
Jan 15 08:02:22 usunx45 vmunix: SCSI TAPE: dev = 0xcd245000 Failed open - st_san_safe enabled
Jan 15 08:02:28 usunx45 vmunix: SCSI TAPE: dev = 0xcd113000 Failed open - st_san_safe enabled
Jan 15 08:02:28 usunx45 vmunix: SCSI TAPE: dev = 0xcd0e3000 Failed open - st_san_safe enabled
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2008 08:56 AM
01-16-2008 08:56 AM
Re: Syslog error messages
See this doc for explanation:
http://docs.hp.com/en/B2355-60105/st_san_safe.5.html
"...
This tunable notifies the stape driver whether it should allow access to device special files without the no-rewind-on-close option. With this tunable on, the stape driver will fail any open on a stape device special file without the no-rewind-on-close option (i.e., /dev/rmt/1m or /dev/rmt/1mb) with a status of EINVAL.
The st_san_safe tunable allows the safe sharing of tape devices in SAN tape backup solution configurations. The disabling of device special files without no-rewind-on-close in a SAN tape backup solution configuration prevents the accidental sending of a rewind command on close from HP-UX systems via standard tape commands like mt(1) which would corrupt a backup in process"
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
http://docs.hp.com/en/B2355-60105/st_san_safe.5.html
"...
This tunable notifies the stape driver whether it should allow access to device special files without the no-rewind-on-close option. With this tunable on, the stape driver will fail any open on a stape device special file without the no-rewind-on-close option (i.e., /dev/rmt/1m or /dev/rmt/1mb) with a status of EINVAL.
The st_san_safe tunable allows the safe sharing of tape devices in SAN tape backup solution configurations. The disabling of device special files without no-rewind-on-close in a SAN tape backup solution configuration prevents the accidental sending of a rewind command on close from HP-UX systems via standard tape commands like mt(1) which would corrupt a backup in process"
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2008 09:44 AM
01-16-2008 09:44 AM
Re: Syslog error messages
... so some process on this server is trying to open rewind-on-close device files. My first thought would be some sort of backup software?
HTH
Duncan
I am an HPE Employee
HTH
Duncan
I am an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2008 11:21 PM
01-16-2008 11:21 PM
Re: Syslog error messages
Hi Ali,
With this parameter only no-rewind-on-close tape device files can be used.
Please confirm
WK
Problem never ends, you must know how to fix it
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP