- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: odd console message
HPE 9000 and HPE e3000 Servers
1753718
Members
6104
Online
108799
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
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
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
06-05-2002 01:15 PM
06-05-2002 01:15 PM
Solution
Hello Paul,
Engineering note KBRC00006935 suggests "There is probably one or more corrupt logfiles in /var/opt/hparray/log which is
causing the syslog daemon to loop."
And "If you had a system abort it is quite probable that the log file that was open
for writing at the time has become corrupt. To fix this do the following:
Abort JARMSRVD and JSYSLOGD.
sh
cd /var/opt/hparray/log
mkdir oldlog
cp * oldlog
touch LOGCATLG
exit
Restream JARMSRVD and JSYSLOGD.
The above steps will allow syslogd to start a new log file. The job should run
normally now."
Engineering note KBRC00006935 suggests "There is probably one or more corrupt logfiles in /var/opt/hparray/log which is
causing the syslog daemon to loop."
And "If you had a system abort it is quite probable that the log file that was open
for writing at the time has become corrupt. To fix this do the following:
Abort JARMSRVD and JSYSLOGD.
sh
cd /var/opt/hparray/log
mkdir oldlog
cp * oldlog
touch LOGCATLG
exit
Restream JARMSRVD and JSYSLOGD.
The above steps will allow syslogd to start a new log file. The job should run
normally now."
A problem well defined is half solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2002 05:31 AM
06-07-2002 05:31 AM
Re: odd console message
Ok you jokers, this thread is closed (and thanks for the info Eric).
- « Previous
-
- 1
- 2
- Next »
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