Sponsored Content
Operating Systems Solaris Cannot start system-log on Solaris 10 Post 303018934 by Peasant on Tuesday 19th of June 2018 11:09:19 AM
Old 06-19-2018
I would say the issue is in space char.
syslog uses tabs as separators, be sure to check for those.
Code:
*.err;kern.debug;daemon.notice;mail.crit;auth.debug;user.debug;local6.info<tab>@<IP Address of Syslog server>

Personaly, i use disable/enable with svcadm, when restarting stuff.

During startup, also syslog should log a line or two why it failed in /var/log/ suggesting some course of action.

Hope that helps
Regards
Peasant.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

System Log for Sun Solaris 2.6

G'day. I have some questions on the Sun Solaris 2.6 OS. I would appreciate if you could refer me some write up or information on the following questions. 1. Terminal Time Out feature ? - Is this OS capable of doing this ? If the terminal is idle for a certain time of period. The system should... (2 Replies)
Discussion started by: tbtan
2 Replies

2. HP-UX

how to start the x window system

hi, am new to hp-ux, i just bought an hp-ux with the hp-ux 11.0 os, is very old, and i wnat to start the x window system but it send an error that said that couldn't open the x server, i try startx, xinit, and nothing, and also where i can find tutorials for hp-ux os for beginners (7 Replies)
Discussion started by: nobody
7 Replies

3. SCO

System will not start

I am running OpenServer 5.0.5a on a Compaq Proliant 800. When trying to start the system it goes through loading everything and at the end I get the following message. WARNING: hd: no root disk controller was found H iinit ime Loadable Driver May be requiredG drain8042 PANIC: srmontfun -... (1 Reply)
Discussion started by: karlb1
1 Replies

4. Shell Programming and Scripting

Cron job at system start up

I want to know if there is a way to make a certain set of programs start in order at system startup with cron or something else i dont know about. (3 Replies)
Discussion started by: rcunn87
3 Replies

5. UNIX for Dummies Questions & Answers

How can i reinstall unix or solaris if i can't log into the system?

I just got a Sun solaris workstation from my friend but i don't know the password to his username. I have all the software but i dont know how to reinstall the operating system without logging in first. I dont need any of the info already on the system. Someone please help :) (5 Replies)
Discussion started by: Hoops31237
5 Replies

6. UNIX for Advanced & Expert Users

Xend cannot start in my system

Hi all,,i'm sorry if my post is repost..but i'm need help about my problem... My specifications is : Sony Vaio VGN CR-323 Intel Dual-Core T2390(1.86 GHz) Memory 2GB DDR Harddisk 200GB with Debian lenny 2.6.26-1-686 i'm install xen via apt-get install xen blah..blah blah root@hell:~#... (4 Replies)
Discussion started by: demhyt
4 Replies

7. AIX

Q: how to start a service when system start

As topic, assume we have a service called "blahservice" and we can start it by: startsrc -s blahservice what is the best practice to run such command when system start? - directly use mkitab to add it into /etc/inittab or - drop startup scripts in /etc/rc.d/rcX.d I know they... (4 Replies)
Discussion started by: acerlinux
4 Replies

8. UNIX for Advanced & Expert Users

Adding hdparm to system start-up

Hi, I have read about a vulnerability that allows to lock any IDE/SATA hard drive with a password, unless the BIOS "freezes" the drive's (no-password) status. Even though less secure, this protection can also be archieved by software (only few BIOSes have that feature). hdparm offers a... (4 Replies)
Discussion started by: Gunther
4 Replies

9. Solaris

How to start system console in ELOM?

Hi, The system is Sun x4150. I use putty ssh to access to it. I can't start system console: (hung) Any help will be greatly appreciated! (5 Replies)
Discussion started by: aixlover
5 Replies

10. What is on Your Mind?

How to start in System Administration?

Hi all, I wonder if you guys could give me some advice on this. I have messed around with Linux for the last few years, and I'm at the point where I would like to become a system administrator - as a career. I already have a bachelor's degree, but it is in the humanities (art history) so... (2 Replies)
Discussion started by: ScottLew
2 Replies
SYSLOG.CONF(5)						      BSD File Formats Manual						    SYSLOG.CONF(5)

NAME
syslog.conf -- configuration file for syslogd(8) DESCRIPTION
The syslog.conf file is the configuration file for the syslogd(8) program. It consists of lines with two fields: the selector field which specifies the types of messages and priorities to which the line applies, and an action field which specifies the action to be taken if a message syslogd receives matches the selection criteria. The selector field is separated from the action field by one or more tab or space characters. A rule can be splitted in several lines if all lines except the last are terminated with a backslash (``''). The Selectors function are encoded as a facility, a period (``.''), and a level, with no intervening white-space. Both the facility and the level are case insensitive. The facility describes the part of the system generating the message, and is one of the following keywords: auth, authpriv, cron, daemon, kern, lpr, mail, mark, news, syslog, user, uucp and local0 through local7. These keywords (with the exception of mark) correspond to the similar ``LOG_'' values specified to the openlog(3) and syslog(3) library routines. The level describes the severity of the message, and is a keyword from the following ordered list (higher to lower): emerg, alert, crit, err, warning, notice and debug. These keywords correspond to the similar (LOG_) values specified to the syslog library routine. See syslog(3) for a further descriptions of both the facility and level keywords and their significance. If a received message matches the specified facility and is of the specified level (or a higher level), the action specified in the action field will be taken. Multiple selectors may be specified for a single action by separating them with semicolon (``;'') characters. It is important to note, how- ever, that each selector can modify the ones preceding it. Multiple facilities may be specified for a single level by separating them with comma (``,'') characters. An asterisk (``*'') can be used to specify all facilities or all levels. By default, a level applies to all messages with the same or higher level. The equal (``='') character can be prepended to a level to restrict this line of the configuration file to messages with the very same level. An exclamation mark (``!'') prepended to a level or the asterisk means that this line of the configuration file does not apply to the speci- fied level (and higher ones). In conjunction with the equal sign, you can exclude single levels as well. The special facility ``mark'' receives a message at priority ``info'' every 20 minutes (see syslogd(8)). This is not enabled by a facility field containing an asterisk. The special level ``none'' disables a particular facility. The action field of each line specifies the action to be taken when the selector field selects a message. There are five forms: o A pathname (beginning with a leading slash). Selected messages are appended to the file. You may prepend a minus (``-'') to the path to omit syncing the file after each message log. This can cause data loss at system crashes, but increases performance for programs which use logging extensively. o A named pipe (fifo), beginning with a vertical bar (``|'') followed by a pathname. The pipe must be created with mkfifo(8) before syslogd reads its configuration file. This feature is especially useful fo debugging. o A hostname (preceded by an at (``@'') sign). Selected messages are forwarded to the syslogd program on the named host. o A comma separated list of users. Selected messages are written to those users if they are logged in. o An asterisk. Selected messages are written to all logged-in users. Blank lines and lines whose first non-blank character is a hash (``#'') character are ignored. EXAMPLES
A configuration file might appear as follows: # Log all kernel messages, authentication messages of # level notice or higher and anything of level err or # higher to the console. # Don't log private authentication messages! *.err;kern.*;auth.notice;authpriv.none /dev/console # Log anything (except mail) of level info or higher. # Don't log private authentication messages! *.info;mail.none;authpriv.none /var/log/messages # The authpriv file has restricted access. authpriv.* /var/log/secure # Log all the mail messages in one place. mail.* /var/log/maillog # Everybody gets emergency messages, plus log them on another # machine. *.emerg * *.emerg @arpa.berkeley.edu # Root and Eric get alert and higher messages. *.alert root,eric # Save mail and news errors of level err and higher in a # special file. uucp,news.crit /var/log/spoolerr FILES
/etc/syslog.conf The syslogd(8) configuration file. BUGS
The effects of multiple selectors are sometimes not intuitive. For example ``mail.crit,*.err'' will select ``mail'' facility messages at the level of ``err'' or higher, not at the level of ``crit'' or higher. SEE ALSO
syslog(3), syslogd(8) 4.4BSD June 9, 1993 4.4BSD
All times are GMT -4. The time now is 07:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy