- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Syslog getting full
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
Forums
Discussions
Discussions
Discussions
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
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
02-22-2001 12:03 PM
02-22-2001 12:03 PM
Syslog getting full
1. What does this error message mean?
2. How do we make the syslog to not log this error?
3. How to trim the syslog automatically?
Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -> snpair
Feb 22 02:29:04 udcpdc last message repeated 2 times
Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_ACCEPT snpair -> snpair
Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_PEERADDR snpair -> snpair
Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -> snpair
Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_ACCEPT snpair -> snpair
Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_PEERADDR snpair -> snpair
Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -> snpair
Feb 22 02:29:04 udcpdc last message repeated 4 times
Feb 22 02:29:04 udcpdc vmunix: TcpReq 4: PRU_ACCEPT snpair -> snpair
Feb 22 02:30:03 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -> snpair
Feb 22 02:30:03 udcpdc vmunix: TcpReq 4: PRU_CONNECT snpair -> snpair
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2001 03:56 PM
02-22-2001 03:56 PM
Re: Syslog getting full
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2001 03:37 AM
02-23-2001 03:37 AM
Re: Syslog getting full
#!/bin/sh
cat /var/adm/syslog/syslog.log | grep -v udcpdc > /tmp/tmpsyslog
cp /tmp/tmpsyslog /var/adm/syslog.log
rm /tmp/tmpsyslog
This will display all lines which do not contain the string udcpdc to a seperate file which then can be coppied over the original syslog file.
You need to be careful not to delete the original file with the rm command as this does not delete the space just the inode entry until the systlogd process is killed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2001 06:38 AM
02-23-2001 06:38 AM
Re: Syslog getting full
So I can get rid of a few bothersome messages I don't need to read from syslog....I set this little script up and cron it in the morning before I generally do a quick check of my logs.... I cron this script every morning to keep my syslog manageable.
/rcw
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2001 07:50 AM
02-23-2001 07:50 AM