- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Syslogd on Tru64
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
тАО09-25-2007 09:57 PM
тАО09-25-2007 09:57 PM
I change my syslog.conf for this:
# facilities: kern user mail daemon auth syslog lpr binary
# priorities: emerg alert crit err warning notice info debug
kern.debug /var/adm/syslog.dated/kern.log
user.debug /var/adm/syslog.dated/user.log
mail.debug /var/adm/syslog.dated/mail.log
daemon.debug /var/adm/syslog.dated/daemon.log
auth.debug /var/adm/syslog.dated/auth.log
syslog.debug /var/adm/syslog.dated/syslog.log
lpr.info /var/adm/syslog.dated/lpr.log
# New lines here.
auth.debug @xxx.xxx.xxx.xxx
kern.debug @xxx.xxx.xxx.xxx
user.debug @xxx.xxx.xxx.xxx
mail.debug @xxx.xxx.xxx.xxx
daemon.debug @xxx.xxx.xxx.xxx
syslog.debug @xxx.xxx.xxx.xxx
lpr.info @xxx.xxx.xxx.xxx
After I stop and start syslog
:/sbin/init.d>#./syslog stop
:/sbin/init.d>#./syslog start
System error logger started
:/var/adm/syslog.dated/current>#ps -eaf |grep syslog
root 1351502 1048577 0.0 06:41:04 ?? 0:00.01 /usr/sbin/syslogd -e
root 1354185 1351227 0.0 06:54:52 pts/1 0:00.01 grep syslog
After this error, syslog write only mail.log, whats happen?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2007 10:28 PM
тАО09-25-2007 10:28 PM
SolutionExcerpt from /sbin/init.d/syslog :
if /usr/sbin/syslogd -e ; then
echo "System error logger started"
else
echo "Cannot start system error logger"
fi
So your syslog daemon started fine, as you can see from the ps command you have ... it is running ..
Try to generate some events with logger command in order to test your instalation.
Liviu.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2007 10:43 PM
тАО09-25-2007 10:43 PM
Re: Syslogd on Tru64
:>#logger -p kern.debug teste 2
:>#more user.log
Sep 26 07:40:25 ctame1 acsg31: teste 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2007 12:45 AM
тАО09-26-2007 12:45 AM
Re: Syslogd on Tru64
But syslog is running well, sending log lines to the logging server with appropriate facilities.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-27-2007 12:07 AM
тАО09-27-2007 12:07 AM
Re: Syslogd on Tru64
ctame1:/sbin/init.d>#syslogd -d
Unix socket receive buffer set to 128 KB
Inet socket receive buffer set to 128 KB
off & running....
init
cfline(kern.debug /var/adm/syslog.dated/kern.log)
cfline(kern.* /var/adm/syslog.dated/kern.log)
syslogd: Unknown priority name: "*"
logmsg: pri 53, flags 4, from ctame1, msg syslogd: Unknown priority name: "*"
Logging to CONSOLE /dev/console
cfline(user.debug /var/adm/syslog.dated/user.log)
cfline(mail.debug /var/adm/syslog.dated/mail.log)
cfline(daemon.debug /var/adm/syslog.dated/daemon.log)
cfline(auth.debug /var/adm/syslog.dated/auth.log)
cfline(syslog.debug /var/adm/syslog.dated/syslog.log)
cfline(lpr.info /var/adm/syslog.dated/lpr.log)
cfline(kern.debug;user.debug;mail.debug;daemon.debug;auth.debug;syslog.debug;lpr.info @10.48.144.18)
cfline(msgbuf.err /var/adm/crash/msgbuf.savecore)
cfline(kern.debug /var/adm/messages)
cfline(kern.debug /dev/console)
cfline(*.emerg *)
cfline(local7.debug /var/adm/syslog.dated/ss7.log)
cfline(local7.debug /dev/console)
7 X X X X X X X X X X X X X X X X X X X X X X X X FILE: /var/adm/syslog.dated/27-Sep-09:03/kern.log
X X X X X X X X X X X X X X X X X X X X X X X X X UNUSED:
X 7 X X X X X X X X X X X X X X X X X X X X X X X FILE: /var/adm/syslog.dated/27-Sep-09:03/user.log
X X 7 X X X X X X X X X X X X X X X X X X X X X X FILE: /var/adm/syslog.dated/27-Sep-09:03/mail.log
X X X 7 X X X X X X X X X X X X X X X X X X X X X FILE: /var/adm/syslog.dated/27-Sep-09:03/daemon.log
X X X X 7 X X X X X X X X X X X X X X X X X X X X FILE: /var/adm/syslog.dated/27-Sep-09:03/auth.log
X X X X X 7 X X X X X X X X X X X X X X X X X X X FILE: /var/adm/syslog.dated/27-Sep-09:03/syslog.log
X X X X X X 6 X X X X X X X X X X X X X X X X X X FILE: /var/adm/syslog.dated/27-Sep-09:03/lpr.log
7 7 7 7 7 7 6 X X X X X X X X X X X X X X X X X X FORW: 10.48.144.18
X X X X X X X X X X X X X X X X X X X X X X X X X UNUSED:
7 X X X X X X X X X X X X X X X X X X X X X X X X FILE: /var/adm/messages
7 X X X X X X X X X X X X X X X X X X X X X X X X CONSOLE: /dev/console
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X WALL:
X X X X X X X X X X X X X X X X X X X X X X X 7 X FILE: /var/adm/syslog.dated/27-Sep-09:03/ss7.log
X X X X X X X X X X X X X X X X X X X X X X X 7 X CONSOLE: /dev/console
The /etc/syslog.auth file does not exist. Messages from all remote
hosts will be accepted.
The EVM subscriptions follow:
emerg alert crit err warning notice info debug
kern 1 1 1 1 1 1 1 0
user 1 1 1 1 1 1 0 0
mail 1 1 1 1 1 1 0 0
daemon 1 1 1 1 1 1 0 0
auth 1 1 1 1 1 1 0 0
syslog 1 1 1 1 1 1 0 0
lpr 1 1 1 1 1 1 0 0
news 1 1 1 1 1 1 0 0
uucp 1 1 1 1 1 1 0 0
cron 1 1 1 1 1 1 0 0
megasafe 1 1 1 1 1 1 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
local0 1 1 1 1 1 1 0 0
local1 1 1 1 1 1 1 0 0
local2 1 1 1 1 1 1 0 0
local3 1 1 1 1 1 1 0 0
local4 1 1 1 1 1 1 0 0
local5 1 1 1 1 1 1 0 0
local6 1 1 1 1 1 1 0 0
local7 1 1 1 1 1 1 0 0
logmsg: pri 56, flags 4, from ctame1, msg syslogd: restart
Logging to FILE /var/adm/syslog.dated/27-Sep-09:03/syslog.log
Logging to FORW 10.48.144.18
syslogd: restarted
read_dump: no msgbuf dump file found
readfds = 0x78
syslogd: exiting on signal 2
syslogd: exiting on signal 2
logmsg: pri 53, flags 4, from ctame1, msg syslogd: exiting on signal 2
Logging to FILE /var/adm/syslog.dated/27-Sep-09:03/syslog.log
Logging to FORW 10.48.144.18
Forwarding the message to evm (fac=5 pri=3) ..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2007 06:50 PM
тАО10-02-2007 06:50 PM
Re: Syslogd on Tru64
Just check if there is some escape character etc in the modified file.
you may use cat -e
If you have saved old file use this file again and check if error is there.
Because whatever you have done is perfect nothing seems wrong.
Kapil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2007 08:16 PM
тАО10-02-2007 08:16 PM
Re: Syslogd on Tru64
I don't know why the manual page of logger still specifies that you can use KERN facility, since none of the following OS's I tried logger with doesn't work : Tru64, Linux, FreeBSSD.
Eventually try to generate kern messages: if I remember right unplug the network cable, fill a disk or the worst case reboot. Of course all these apply if it's not a production system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2007 11:27 PM
тАО10-07-2007 11:27 PM
Re: Syslogd on Tru64
follows result of cat -e syslog.conf:
# $
# *****************************************************************$
# * *$
# * Copyright 2002 Compaq Information Technologies Group, L.P. *$
# * *$
# * The software contained on this media is proprietary to *$
# * and embodies the confidential technology of Compaq *$
# * Computer Corporation. Possession, use, duplication or *$
# * dissemination of the software and media is authorized only *$
# * pursuant to a valid written license from Compaq Computer *$
# * Corporation. *$
# * *$
# * RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure *$
# * by the U.S. Government is subject to restrictions as set *$
# * forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, *$
# * or in FAR 52.227-19, as applicable. *$
# * *$
# *****************************************************************$
# $
# HISTORY$
# $
# @(#)$RCSfile: syslog.conf,v $ $Revision: 4.1.8.1 $ (DEC) $Date: 2000/10/19 19:13:52 $ $
# $
# $
# syslogd config file$
# $
# facilities: kern user mail daemon auth syslog lpr binary$
# priorities: emerg alert crit err warning notice info debug$
kern.debug /var/adm/syslog.dated/kern.log$
user.debug /var/adm/syslog.dated/user.log$
mail.debug /var/adm/syslog.dated/mail.log$
daemon.debug /var/adm/syslog.dated/daemon.log$
auth.debug /var/adm/syslog.dated/auth.log$
syslog.debug /var/adm/syslog.dated/syslog.log$
lpr.info /var/adm/syslog.dated/lpr.log$
kern.debug;user.debug;mail.debug;daemon.debug;auth.debug;syslog.debug;lpr.info @xxx.xxx.xxx.xx$
$
$
$
$
msgbuf.err /var/adm/crash/msgbuf.savecore$
$
kern.debug /var/adm/messages$
kern.debug /dev/console$
*.emerg *$
$
# $_DESC Logging Facility uses LOCAL7 facility code.$
local7.debug /var/adm/syslog.dated/ss7.log$
local7.debug /dev/console$
All the lines as finish with $ caracter.
And I tried logger command with others facilitys, works but logs only in user.log.
Now only auth and mail.log works, nothing more. ;)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-08-2007 05:51 PM
тАО10-08-2007 05:51 PM
Re: Syslogd on Tru64
file lloks good except a few blank line in between you can see 4-5 $ sign.Try removing those blank lines and kill the syslog processes using kill -9 and restart using
/usr/sbin/syslogd -e
i seriously do not understand what is wrong as everything seems to be fine....are you getting some mesaages in /var/adm/messages file.
BR,
Kapil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-10-2007 09:50 PM
тАО10-10-2007 09:50 PM
Re: Syslogd on Tru64
I remove the blank lines and kill the syslog using kill -9 and restart using /usr/sbin/syslogd -e but no way, very strange.
If install syslog-ng on the Tru64, is a good idea or not? If yes, where I find the installation, and the instructions for Tru64?
Best, Cadu...