- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- How to capture system console messages
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-03-2009 10:23 AM
тАО03-03-2009 10:23 AM
mail.debug /var/adm/syslog/mail.log
*.info;mail.none /var/adm/syslog/syslog.log
*.alert /dev/console
*.debug /var/adm/syslog/console.log
*.alert root
*.emerg *
syslog.conf: END
I added the *.debug line to log messages to console.log. Not all messages are making it to that file. The goal is to log all messages to a file, and I can tail -f that file at my desk to watch system messages. Sometimes we have programs that display messages that I can not see, because they are not logged and have scrolled off the console. Any suggestions?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2009 10:42 AM
тАО03-03-2009 10:42 AM
Re: How to capture system console messages
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=662658
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2009 12:54 PM
тАО03-03-2009 12:54 PM
Re: How to capture system console messages
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2009 12:22 AM
тАО03-04-2009 12:22 AM
Re: How to capture system console messages
If this does not help, then the 3rd party software obviously does not use syslog for its messaging.
How is that 3rd party software started?
For any program that starts via /etc/inittab, the standard output and standard error will point to the console, unless explicitly redirected elsewhere.
If the software starts using a typical init script (located in /sbin/init.d), you should examine the script to see where the output of the software is directed. If the software startup includes specific redirections like "> /dev/console", just change them to point to a file instead of the console.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2009 08:39 AM
тАО03-04-2009 08:39 AM
Re: How to capture system console messages
Thank you for the reply. The 3rd party software is fired through a PC front end. The windows app calls a program on the Unix box.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2009 09:21 AM
тАО03-04-2009 09:21 AM
Re: How to capture system console messages
if it starts something and redirects the output via the ">" operator, then you might be able to get at it of you can access the startup code for the application. (Its entirely possible that the 3rd party stuff is started at boot time and listening to a socket for input from windows.....)
If it does happen to use syslog facility, and all of the messages you want to see are being displayed on the console, then using the syslog.conf file that you provided, duplicate every line that has /dev/console in it and substitute /var/adm/syslog/console.log...
should wind up with something like:
mail.debug /var/adm/syslog/mail.log
*.info;mail.none /var/adm/syslog/syslog.log
*.alert /dev/console
*.alert /var/adm/syslog/console.log
*.debug /var/adm/syslog/console.log
*.alert root
*.emerg *
without knowing what the "3rd party software" is, or how does what it does, all of the above are just unverifiable guesses.
as noted above, the syslog daemon will need restarted.
pester the vendor of the software until they provide answers as to how they display the messages on the console as that's why you pay for support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2009 09:53 AM
тАО03-04-2009 09:53 AM
Re: How to capture system console messages
Thank you for the info. I'm going to pester the 3rd party software vendor more. Maybe if I'm persistent, they can explain how the messages are displaying on the console.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2009 10:20 AM
тАО03-04-2009 10:20 AM
Solutionsome_command 2>/dev/console
or
/a/b/c/some_script 2>/dev/console
or, inside "/d/e/f/some_other_script" they have a line
some_other_command >/dev/console
IOW, the messages from the 3rd-party s/w may be sent directly to your console device, in which case it's going to be up to the vendor to explain to you how to capture them.
HP-Server-Literate since 1979