The UNIX and Linux Forums  

Go Back   The UNIX and Linux Forums > Top Forums > UNIX for Dummies Questions & Answers
Google UNIX.COM


UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !!

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
syslogd 30% utilization in top, solaris 9 chugheshc SUN Solaris 2 05-28-2008 08:18 AM
Syslogd silvaman UNIX for Advanced & Expert Users 3 08-29-2006 04:53 AM
Message from syslogd Hitori Linux 18 07-27-2006 12:25 PM
multiple instances of syslogd - is it possible? Gary Dunn UNIX for Advanced & Expert Users 9 07-20-2004 06:10 AM
HELP!!! syslogd is down... skotapal Security 5 12-05-2002 02:11 PM

Closed Thread
 
Submit Tools LinkBack Thread Tools Search this Thread Display Modes
  #1  
Old 11-25-2002
buRst
Guest
 

Posts: n/a
syslogd

Working out of AIX 4.3.

All logs that were written via application suddenly stopped. executing a tail -f <logfile> was not producing any results.

Tried to refresh the syslogd (daemon). When executing "refresh -s syslogd" system would display
<<0513-036 The request could not be passed to the syslogd subsystem.>>

I then grep'd for the syslogd daemon which was up and running.

<< root 52722 5444 0 Nov 22 - 1:29 /usr/sbin/syslogd >>

Since I did not know what to do next I thought I'd restart the process.
Then I killed the process.
Then restarted the daemon .... got this message <<0821-600 ./syslogd: continuing without SRC support>>

Then executed the refresh again, this time
got message << 0513-036 The request could not be passed to the syslogd subsystem.
Start the subsystem and try your command again. >>

Went into smitty " Processes and Subsystems". Started the subsystem. However when checked via listing all subsystems the syslogd showed up as , 'inoperative'

My concerns are.....

Firstly, eventhough the syslogd daemon was up and running, why was the refresh message 0513-036 displayed?
Secondly, why does the status show inoperative, even when I started the subsystem.
and finally how do I get the syslogd status to active..


Thnx
Forum Sponsor
  #2  
Old 11-26-2002
Kelam_Magnus's Avatar
Registered User
 

Join Date: Aug 2001
Location: DFW McKinney, TX,
Posts: 1,069
You may have already tried this, but here goes.

I would simply kill and restart the daemon with the "-D" option. This will redirect all responses that would normally go to the console. Also, if you have an /etc/syslog.conf file make sure it is readable. This file tells the daemon where to put the logs it receives. YOu can specify it with the -f FILENAME option.

Use this command line::
/usr/sbin/syslogd -d -D -f /etc/syslog.conf

The lower -d turns on debugging.

Read thru the manpage again maybe you missed something.
__________________
My brain is your brain
  #3  
Old 11-26-2002
buRst
Guest
 

Posts: n/a
Thank you very much for the input..
I did however go crazy over the man pages and Document Library at AIX, finally got into "Operating System Devices" where currently Iam going through the "Starting and Stopping of a Subsystem".

So, back to the cure... Before I started the Subsystem, I HUP'd the syslogd. Then went into smitty and then continued with the Starting of Subsystem process and ... guess what, the system now lists as 'active'. Once completed I also refresh -s syslogd and I got the message below
"0513-095 The request for subsystem refresh was completed successfully. "

The reading still continues.........

Thnx
Google The UNIX and Linux Forums
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes




All times are GMT -7. The time now is 10:41 AM.


Powered by: vBulletin, Copyright ©2000 - 2006, Jelsoft Enterprises Limited.
The UNIX and Linux Forums Content Copyright ©1993-2008. All Rights Reserved.Ad Management by RedTyger Visit The Complex Event Processing Blog

Content Relevant URLs by vBSEO 3.2.0