GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- consequences of stop and start hparray
Operating System - HP-UX
1854888
Members
4979
Online
104105
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
back
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
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
04-15-2001 05:53 PM
04-15-2001 05:53 PM
I want to clear out some log at the / directory which appear to be hold up by hparray daemon.
What is the impact if I stop and start the following services?
/sbin/init.d/hparray stop
/sbin/init.d/hparamgr stop
Will this affect the availability of the server? Can I do it during the normal office hour? Any help will be appreciated
What is the impact if I stop and start the following services?
/sbin/init.d/hparray stop
/sbin/init.d/hparamgr stop
Will this affect the availability of the server? Can I do it during the normal office hour? Any help will be appreciated
abc
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2001 01:15 AM
04-16-2001 01:15 AM
Solution
The script, hparray, start and stop the functions required for C2430A, what we called CASCADE and hparamgr does the same thing for AutoRAID, FC60.
It starts deamon that monitors disk array at startup and kills it at shutdown.
Because it keeps track of disk array sub-system, it reports problems to console or designated places when something unexpected or undesirable happened.
And it creates log files at a given interval which is important when we troubleshoot problems.
If these log files bother you, I recommend that you delete old files using cron.
In the following example,
Any file greater than 7 days old and located in /var/opt/harray/log will be deleted.
# find /var/opt/hparray/log/ -mtime +7 -exec rm {} \;
It doesnt't effect system for you to stop these functions while system is up but you need it when you maintain disk arrays.
Best regards,
It starts deamon that monitors disk array at startup and kills it at shutdown.
Because it keeps track of disk array sub-system, it reports problems to console or designated places when something unexpected or undesirable happened.
And it creates log files at a given interval which is important when we troubleshoot problems.
If these log files bother you, I recommend that you delete old files using cron.
In the following example,
Any file greater than 7 days old and located in /var/opt/harray/log will be deleted.
# find /var/opt/hparray/log/ -mtime +7 -exec rm {} \;
It doesnt't effect system for you to stop these functions while system is up but you need it when you maintain disk arrays.
Best regards,
Never say "no" first.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2001 02:31 AM
04-16-2001 02:31 AM
Re: consequences of stop and start hparray
You won't be able to configure the arrays from the host as a result of stopping those daemons.
You can still use the array based config though.
Log files on the controllers may fill up if there are problems on the array too.
You should start them periodically and use the logprint and arraylog -C -c to flush the logs.
Later,
Bill
You can still use the array based config though.
Log files on the controllers may fill up if there are problems on the array too.
You should start them periodically and use the logprint and arraylog -C -c to flush the logs.
Later,
Bill
It works for me (tm)
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 2026 Hewlett Packard Enterprise Development LP