Aaron Burt wrote:
> On Tue, Jul 13, 2010 at 08:13:19AM -0700,
Michael wrote:
> Cool problem! I used to have fun working on VoIP
equipment.
If fun is having your phone freeze up. Yes, we're
having a bit of it.
>> However after a few hours we see a
backwards drift in timestamps - as if
>> the syslog server is
falling behind. I also see that syslog is
>> resolving
IP addresses and writing FQDN to the log.
>
> So timestamps
in logged messages are falling behind current-time?
>
> Do
you suppose the UDP receive queue is filling up with messages before
>
they hit syslogd, or syslogd is backing up behind the disk I/O?
I
suspect syslog processing of messages is the culprit.
iostat
applied after I sent my original message showed no glut of traffic
generally the system load is very low
renicing the syslogd process with
-18 had no effect.
dtrace is not available on this system
> Ah, the joy of Solaris manpages. You might find other
settings in
> /etc/default/syslogd or /etc/netconfig or
/etc/net/transport/ but I think
> Solaris syslogd behaviour is pretty
much set in stone.
/etc/default/syslogd - bah more useless than the
man page. "uncomment the following default line to change
behavior" the line being "LOG_FROM_REMOTE"
/etc/netconfig
- nothing appropriate
/etc/net/transport - does not exist on this
system
> Have you considered using syslog-ng and/or a more
powerful (Linux- or
> OpenSolaris-based) log-server?
Scheduled for after close of business tonight. A Linux based system
will be logging.
It would still be nice to figure out where the
syslog bottleneck is. It is neither keeping up with the task or exerting
a load on the system. That's not right and it bugs me to not know what
is going on.
--
Michael Rasmussen
http://www.jamhome.us/
Be Appropriate && Follow Your Curiosity
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
