- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Logfiles of Chassis Loggin Daemon
Operating System - HP-UX
1820390
Members
3473
Online
109623
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
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
тАО06-28-2001 03:33 AM
тАО06-28-2001 03:33 AM
Hello,
in the error log of our ADSM backup client there frequently appears the following entry:
06/27/01 20:19:08 ANS1228E Sending of object '/var/stm/logs/os/ccbootlog' fail
ed
06/27/01 20:19:08 ANS4037E File '/var/stm/logs/os/ccbootlog' changed during pr
ocessing. File skipped.
06/27/01 20:19:10 ANS1802E Incremental backup of '/var' finished with 1 failur
e
Though the above is rather obvious I wonder if we really need to have cclogd's logfiles incrementally backed up.
Even by reading cclogd's manpage I haven't found out what the various logs are good for.
I only gathered that their contents can be diplayed from within stm.
Possibly the HP techies would need the info to see whether some piece of hardware is defunct?
Regards
Ralph
in the error log of our ADSM backup client there frequently appears the following entry:
06/27/01 20:19:08 ANS1228E Sending of object '/var/stm/logs/os/ccbootlog' fail
ed
06/27/01 20:19:08 ANS4037E File '/var/stm/logs/os/ccbootlog' changed during pr
ocessing. File skipped.
06/27/01 20:19:10 ANS1802E Incremental backup of '/var' finished with 1 failur
e
Though the above is rather obvious I wonder if we really need to have cclogd's logfiles incrementally backed up.
Even by reading cclogd's manpage I haven't found out what the various logs are good for.
I only gathered that their contents can be diplayed from within stm.
Possibly the HP techies would need the info to see whether some piece of hardware is defunct?
Regards
Ralph
Madness, thy name is system administration
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2001 03:52 AM
тАО06-28-2001 03:52 AM
Re: Logfiles of Chassis Loggin Daemon
Hi Ralph.
This is what I found:
Chassis View Boot Log.
The Chassis View Boot Log command allows you to display the contents of the chassis code boot log file (ccbootlog).
The boot log contains mostly informational log entries output by the system as it boots. If the system is experiencing problems booting, this log may contain useful information about the problem.
The boot log is created by the logging daemon (diaglogd). Log entries can come from various system hardware, software and firmware modules.
Chassis logging was implemented beginning with the introduction of N-class systems on HP-UX 11.00, and will be featured on some newer systems as they are released.
--------
Chassis View Error Log.
The Chassis View Error Log command allows you to display the contents of the chassis code error log file (ccerrlog).
The chassis code error log contains entries for chassis codes reported with an alert level indicating that an error has occurred.
For instance, chassis codes are logged if problems occur with the power supplies. By examining the error log, you could see a record of these power supply problems.
The error log is created by the logging daemon (diaglogd). Log entries can come from various system hardware, software and firmware modules.
Chassis logging was implemented beginning with the introduction of N-class systems on HP-UX 11.00, and will be featured on some newer systems as they are released.
hope this helps.
This is what I found:
Chassis View Boot Log.
The Chassis View Boot Log command allows you to display the contents of the chassis code boot log file (ccbootlog).
The boot log contains mostly informational log entries output by the system as it boots. If the system is experiencing problems booting, this log may contain useful information about the problem.
The boot log is created by the logging daemon (diaglogd). Log entries can come from various system hardware, software and firmware modules.
Chassis logging was implemented beginning with the introduction of N-class systems on HP-UX 11.00, and will be featured on some newer systems as they are released.
--------
Chassis View Error Log.
The Chassis View Error Log command allows you to display the contents of the chassis code error log file (ccerrlog).
The chassis code error log contains entries for chassis codes reported with an alert level indicating that an error has occurred.
For instance, chassis codes are logged if problems occur with the power supplies. By examining the error log, you could see a record of these power supply problems.
The error log is created by the logging daemon (diaglogd). Log entries can come from various system hardware, software and firmware modules.
Chassis logging was implemented beginning with the introduction of N-class systems on HP-UX 11.00, and will be featured on some newer systems as they are released.
hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2001 03:55 AM
тАО06-28-2001 03:55 AM
Solution
Hi again.
you can check this information by accessing: http://www.docs.hp.com/hpux/onlinedocs/diag/logtool/lgr_summ.htm
select "commands".
you can check this information by accessing: http://www.docs.hp.com/hpux/onlinedocs/diag/logtool/lgr_summ.htm
select "commands".
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
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP