- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- wrong messges in daemon.log file
Operating System - Tru64 Unix
1748166
Members
3823
Online
108758
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО02-12-2006 06:43 PM
тАО02-12-2006 06:43 PM
Feb 13 15:09:33 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzc3b
there are so many wrong messages in file daemon.log
what's wrong with our system?
/dev/rrzc3b
there are so many wrong messages in file daemon.log
what's wrong with our system?
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2006 10:16 PM
тАО02-12-2006 10:16 PM
Solution
Hi,
You have an old V4 cluster.
This is logged on member yj2801. However, this is logged by the aseagent of the other member mc_8201.
member mc_8201 has a diskservice that uses rzc3b. A SCSI reservation is set on this device in order to protect it for IO from other members. In V4, no concurrent IO of different hosts is supported.
The Availibility Manager on mc_8201 has detected that the Reservation was reset. This occurs if a SCSI bus reset is applied on the shared SCSI bus. Probably because an other member rebooted. Another possibility is that for certain hw reasons, a scsi bus reset was givven in order to reset all the devices.
What happens now is that mc_8201 will issue again a SCSI Reservation to all the devices, configured for that particular diskservice.
So, this is not a real problem.
I suppose that the aselogger is configured to log also "INFORMATIONAL" messages. This generates a lot of info in the daemon.log.
You might change this with asemgr.
Regards
Joris
You have an old V4 cluster.
This is logged on member yj2801. However, this is logged by the aseagent of the other member mc_8201.
member mc_8201 has a diskservice that uses rzc3b. A SCSI reservation is set on this device in order to protect it for IO from other members. In V4, no concurrent IO of different hosts is supported.
The Availibility Manager on mc_8201 has detected that the Reservation was reset. This occurs if a SCSI bus reset is applied on the shared SCSI bus. Probably because an other member rebooted. Another possibility is that for certain hw reasons, a scsi bus reset was givven in order to reset all the devices.
What happens now is that mc_8201 will issue again a SCSI Reservation to all the devices, configured for that particular diskservice.
So, this is not a real problem.
I suppose that the aselogger is configured to log also "INFORMATIONAL" messages. This generates a lot of info in the daemon.log.
You might change this with asemgr.
Regards
Joris
To err is human, but to really faul things up requires a computer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2006 05:07 PM
тАО02-22-2006 05:07 PM
Re: wrong messges in daemon.log file
Feb 21 14:53:17 yj8201 ASE: mc_8202 Agent Info: AM reports reservation reset on
/dev/rrzg3b
Feb 21 14:53:18 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzf3b
Feb 21 14:53:18 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzb2b
Feb 21 14:53:18 yj8201 ASE: mc_8202 Agent Info: AM reports reservation reset on
/dev/rrz2b
Feb 21 14:53:18 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzd2b
Feb 21 14:53:18 yj8201 ASE: mc_8202 Agent Info: AM reports reservation reset on
/dev/rrz3b
Feb 21 14:55:54 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzd1b
Feb 21 14:55:54 yj8201 ASE: mc_8202 Agent Info: AM reports reservation reset on
/dev/rrz1b
Feb 21 14:55:55 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzb1b
Feb 21 14:55:55 yj8201 ASE: mc_8202 Agent Info: AM reports reservation reset on
/dev/rrzc1b
Feb 21 14:55:55 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzf3b
Feb 21 14:55:55 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzb2b
why are all the device files " b "partition
/dev/rrzg3b
/dev/rrzf3b
/dev/rrzb2b
/dev/rrzd2b
/dev/rrz2b
/dev/rrzg3b
Feb 21 14:53:18 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzf3b
Feb 21 14:53:18 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzb2b
Feb 21 14:53:18 yj8201 ASE: mc_8202 Agent Info: AM reports reservation reset on
/dev/rrz2b
Feb 21 14:53:18 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzd2b
Feb 21 14:53:18 yj8201 ASE: mc_8202 Agent Info: AM reports reservation reset on
/dev/rrz3b
Feb 21 14:55:54 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzd1b
Feb 21 14:55:54 yj8201 ASE: mc_8202 Agent Info: AM reports reservation reset on
/dev/rrz1b
Feb 21 14:55:55 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzb1b
Feb 21 14:55:55 yj8201 ASE: mc_8202 Agent Info: AM reports reservation reset on
/dev/rrzc1b
Feb 21 14:55:55 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzf3b
Feb 21 14:55:55 yj8201 ASE: mc_8201 Agent Info: AM reports reservation reset on
/dev/rrzb2b
why are all the device files " b "partition
/dev/rrzg3b
/dev/rrzf3b
/dev/rrzb2b
/dev/rrzd2b
/dev/rrz2b
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP