
6 Apr
2004
6 Apr
'04
3:36 p.m.
I was getting this same error yesterday, and it turned out that syslogd
wasn't running and OTRS wasn't happy because it couldn't talk to
syslog. I haven't been following this thread and don't know if this is
your specific problem, but it's easy to check and could be worth looking
into. If "/" were 100% full, I think it could crash syslogd and cause a
similar problem with OTRS wanting to talk to syslogd.
--
Jonathan Dill