- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: kern.log almost empty upon firmware update
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО03-27-2005 06:22 PM
тАО03-27-2005 06:22 PM
kern.log almost empty upon firmware update
We have updated the firmware of the GS80 server form 6.3 to 6.9.
We have Tru64 version 5.1 running in cluster with other GS80 server via memory channel.
Upon succesful update of the firmware, the kern.log doesn't contain starup messages of the OS. It only conains couple of not important error messages. We have checked the syslog.conf file, but it seems ok with
kern.debug /var/adm/syslog.dated/kern.log
Please advise,
Emilija
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2005 10:53 PM
тАО03-27-2005 10:53 PM
Re: kern.log almost empty upon firmware update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2005 11:37 PM
тАО03-27-2005 11:37 PM
Re: kern.log almost empty upon firmware update
It's not logging anywhere.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-28-2005 03:17 PM
тАО03-28-2005 03:17 PM
Re: kern.log almost empty upon firmware update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-28-2005 05:57 PM
тАО03-28-2005 05:57 PM
Re: kern.log almost empty upon firmware update
From Administration Manual - "The syslogd daemon logs all messages of
the specified severity level plus all messages of greater severity.For
example,if you specify level err all messages of levels err crit
alert and emerg or panic are logged."
Debug has lowest priority.
Any other ideas...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-13-2005 09:13 PM
тАО04-13-2005 09:13 PM
Re: kern.log almost empty upon firmware update
We tried with higher values, but the problem was solved with maximum value.
From SysAdmin Guide:
"For large systems with many adapters and devices,the default value might be insufficient,causing messages to be dropped from the /var/adm/messages.
If your system ├в s boot-log record is incomplete, or if you want to reduce the
assigned value to reclaim the buffer space, use the following procedure to modify the value of the msgbuf_size attribute:
1.Invoke the dxkerneltuner graphical user interface from the command line.
2.Select the generic subsystem.
3.Set the new boot time value of the msgbuf_size subsystem.
4.Click the Apply button to implement the change,and exit from the dxkerneltuner utility."
On next boot everything was OK.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-13-2005 09:14 PM
тАО04-13-2005 09:14 PM