Hi everyone, I have just figured out that I can not have any information on what's going on in the /var/log/messages. At first I thought they were all compressed first but then it did not make sense. I have not done anything lately ie (install new programs remove old ones change suse config the naswer is no to all. Can some one point to me where I should be checking to uncover the story ? thx -- Togan Muftuoglu toganm@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Togan Muftuoglu writes:
Hi everyone,
I have just figured out that I can not have any information on what's going on in the /var/log/messages. At first I thought they were all compressed first but then it did not make sense.
Why not? It is a big file, but there is nothing preventing you looking at it. You must be root on most systems, but you can change that. You can do a 'tail -f /var/log/messages' because it is typically big and all you are concerned with is at the end anyway.
I have not done anything lately ie (install new programs remove old ones change suse config the naswer is no to all.
Can some one point to me where I should be checking to uncover the story ?
Did I miss something here? What story?
thx -- Togan Muftuoglu toganm@yahoo.com
__________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Jesse Marlin wrote:
Why not? It is a big file, but there is nothing preventing you looking at it. You must be root on most systems, but you can change that. You can do a 'tail -f /var/log/messages' because it is typically big and all you are concerned with is at the end anyway. ^^^^^^^^^^^^^^^ not necessarily
That is I know already yet when I do it there is nothing displayed the file is completely empty.
Can some one point to me where I should be checking to uncover the story ?
Did I miss something here? What story?
Well if I do not see something as I used to and if nothing is done specific I personally would call it story. -- Togan Muftuoglu toganm@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Togan Muftuoglu writes:
Jesse Marlin wrote:
Why not? It is a big file, but there is nothing preventing you looking at it. You must be root on most systems, but you can change that. You can do a 'tail -f /var/log/messages' because it is typically big and all you are concerned with is at the end anyway. ^^^^^^^^^^^^^^^ not necessarily
That is I know already yet when I do it there is nothing displayed the file is completely empty.
Can some one point to me where I should be checking to uncover the story ?
Did I miss something here? What story?
Well if I do not see something as I used to and if nothing is done specific I personally would call it story.
OK, I see your point. Is it running: ps aux | grep syslogd If not try to run it by hand as root: /usr/sbin/syslogd And see if you get any messages. Check for the following files in /etc/rc.d: lrwxrwxrwx 1 root root 9 Aug 31 1999 rc1.d/S09syslog -> ../syslog lrwxrwxrwx 1 root root 9 Aug 31 1999 rc2.d/K35syslog -> ../syslog lrwxrwxrwx 1 root root 9 Aug 31 1999 rc2.d/S09syslog -> ../syslog lrwxrwxrwx 1 root root 9 Aug 31 1999 rc3.d/K35syslog -> ../syslog lrwxrwxrwx 1 root root 9 Aug 31 1999 rc3.d/S09syslog/rc1.d/S09syslog The capital 'S' means to start whereas a lowercase 's' means to not start. The capital 'K' means to kill whereas a lowercase 'k' means to not kill.
-- Togan Muftuoglu toganm@yahoo.com
__________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Jesse Marlin wrote:
OK, I see your point. Is it running:
ps aux | grep syslogd well it is running and it started to log things also.
However my question is still valid what caused it to stop and start aagain which is not under my control -- Togan Muftuoglu toganm@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Togan Muftuoglu wrote:
Jesse Marlin wrote:
OK, I see your point. Is it running:
ps aux | grep syslogd well it is running and it started to log things also.
However my question is still valid what caused it to stop and start aagain which is not under my control
-- Togan Muftuoglu toganm@yahoo.com
did I ask that before? What params do you start syslog with? rc.config, SYSLOGD_PARAMS: # for example SYSLOGD_PARAMS="-r -s my.dom.ain" SYSLOGD_PARAMS=" -m120 -f /etc/syslog.conf" Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
juergen.braukmann@ruhr-west.de wrote:
did I ask that before? What params do you start syslog with? rc.config, SYSLOGD_PARAMS: # for example SYSLOGD_PARAMS="-r -s my.dom.ain" SYSLOGD_PARAMS=" -m120 -f /etc/syslog.conf"
Below is taken directly from the rc.config. The whole thing is created by YaST I didn't put anything manually # if not empty: parameters for syslogd # for example SYSLOGD_PARAMS="-r -s my.dom.ain" # SYSLOGD_PARAMS="" -- Togan Muftuoglu toganm@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Togan Muftuoglu wrote:
juergen.braukmann@ruhr-west.de wrote:
did I ask that before? What params do you start syslog with? rc.config, SYSLOGD_PARAMS: # for example SYSLOGD_PARAMS="-r -s my.dom.ain" SYSLOGD_PARAMS=" -m120 -f /etc/syslog.conf"
Below is taken directly from the rc.config. The whole thing is created by YaST I didn't put anything manually
# if not empty: parameters for syslogd # for example SYSLOGD_PARAMS="-r -s my.dom.ain" # SYSLOGD_PARAMS=""
well I thought the above would be cause of the trouble, but I just crosschecked my experimental machine I just set up -same entry, but logging-. What about /etc/syslog.conf ? This sets up which messages go where. There are some nice man pages around; "man syslog.conf" and "man logger", the latter allows entrys to messages file passed on manually. Juergen
-- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Togan Muftuoglu wrote:
Jesse Marlin wrote:
Why not? It is a big file, but there is nothing preventing you looking at it. You must be root on most systems, but you can change that. You can do a 'tail -f /var/log/messages' because it is typically big and all you are concerned with is at the end anyway. ^^^^^^^^^^^^^^^ not necessarily
That is I know already yet when I do it there is nothing displayed the file is completely empty.
I had this happen due to a typo in rc.config: SYSLOG_PARAMS contained a typo. ;-) What happens if you cd /sbin/init.d ./syslog start Any green or red lights ??? Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
juergen.braukmann@ruhr-west.de wrote:
I had this happen due to a typo in rc.config: SYSLOG_PARAMS contained a typo. ;-) What happens if you cd /sbin/init.d ./syslog start Any green or red lights ???
it says it is retarting the syslogd and writes down one What does this mean -- Togan Muftuoglu toganm@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Thu, 13 Apr 2000, Togan Muftuoglu wrote:
Jesse Marlin wrote:
Why not? It is a big file, but there is nothing preventing you looking at it. You must be root on most systems, but you can change that. You can do a 'tail -f /var/log/messages' because it is typically big and all you are concerned with is at the end anyway. ^^^^^^^^^^^^^^^ not necessarily
That is I know already yet when I do it there is nothing displayed the file is completely empty.
Oh, THAT problem again. There is a nightly job that checks a great many log files for size. If a log file exceeds a certain size, it is compressed to another name and an empty file of the same name is created. Then this job is SUPPOSED to restart a process, preferably the process that writes the log file - in this case, syslogd. However, in my case I found the configuration file was incorrect, and did NOT restart ANY of the processes it was supposed to. Which caused exactly the symptoms you referred to. In fact I found that manually clobbering /var/log/messages has the same effect. To fix the immediate problem: killall -HUP syslogd This tells syslogd to reinitialize itself, which includes closing all its log files (including the now-invalid one) and reopening them (new, valid connections). You will see that when this is complete, syslogd itself immediately logs the event to /var/log/messages. The configuration file that was incorrect is /etc/logfiles. Here's the valid (I think) line in my file - with a few spaces removed so it will remain one line: /var/log/messages +4096k 640 root.root syslogd I don't remember exactly what the original line looked like - I think there was something else between root.root and syslogd. The column headers in the file are useful in this case. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
does syslog actually stop, or does it just lose its fd? "/etc/rc.d/syslogd status" should tell you. if it is still running, and just not updating the log file anymore, then stop and restart it. seems sometimes it doesnt get restarted properly when the logrotate program rotates it. i have hella problems with this on the mail log. i havent had time to try to track the bug down yet, but the logrotate seems to be the most likely cause. -- ======================================================================== Rocky McGaugh Atipa Linux Solutions Product Development www.atipa.com rocky@smluc.org rmcgaugh@atipa.com ======================================================================== On Thu, 13 Apr 2000, Togan Muftuoglu wrote:
Hi everyone,
I have just figured out that I can not have any information on what's going on in the /var/log/messages. At first I thought they were all compressed first but then it did not make sense.
I have not done anything lately ie (install new programs remove old ones change suse config the naswer is no to all.
Can some one point to me where I should be checking to uncover the story ?
thx
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (5)
-
jlm＠compgen.com -
juergen.braukmann＠ruhr-west.de -
rmcgaugh＠atipa.com -
toganm＠yahoo.com -
warrl＠blarg.net