HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Mail.log and Syslog.log Problem
Operating System - HP-UX
1837257
Members
2331
Online
110115
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
Forums
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
03-28-2001 03:03 AM
03-28-2001 03:03 AM
Mail.log and Syslog.log Problem
Hi,
In our HP 9000 L1000 Server running HP-UX 11.00, we are using sendmail 8.11.0. In that often the /var/adm/syslog/mail.log and /var/adm/syslog/syslog.log are not getting logged, even inspite of the syslog daemon running properly.
This is getting solved only by stopping and starting the syslogd again.
This had happened in 4 of our servers for 3 to 4 times within a week's time.
Can anyone tell why this is happening? and how to overcome this problem?
Thanks and Regards.
In our HP 9000 L1000 Server running HP-UX 11.00, we are using sendmail 8.11.0. In that often the /var/adm/syslog/mail.log and /var/adm/syslog/syslog.log are not getting logged, even inspite of the syslog daemon running properly.
This is getting solved only by stopping and starting the syslogd again.
This had happened in 4 of our servers for 3 to 4 times within a week's time.
Can anyone tell why this is happening? and how to overcome this problem?
Thanks and Regards.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2001 03:26 AM
03-28-2001 03:26 AM
Re: Mail.log and Syslog.log Problem
I do not know this problem, but I advise you to run the inetd daemon with the -l option. This will log every single thing that happens on the system to syslog. Maybe then you can do some more troubleshooting.
good luck.
good luck.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2001 04:34 AM
03-28-2001 04:34 AM
Re: Mail.log and Syslog.log Problem
If you are removing this files w/o stop the syslog daemon , the files will be not recreated and this is the cause.
You can send HUP signal to force syslogd reconfiguration after remove them.
# kill HUP `cat /var/run/syslog.pid `
See man syslogd.
You can send HUP signal to force syslogd reconfiguration after remove them.
# kill HUP `cat /var/run/syslog.pid `
See man syslogd.
unsupported
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2001 11:18 PM
03-28-2001 11:18 PM
Re: Mail.log and Syslog.log Problem
inetd has NOTHING to do with logging, at least not for sendmail. If you want to "rotate" logfiles (if they get too big for example), it's most easily done like this:
% cp log log.1
% cp /dev/null log
With this, there's no need to re-start syslogd, since the filehandle for log still exists (but the file is empty again).
% cp log log.1
% cp /dev/null log
With this, there's no need to re-start syslogd, since the filehandle for log still exists (but the file is empty again).
Postfix/BIND/Security/IDS/Scanner, you name it...
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP