Menu
▾
▴
Re: [opennms-discuss] Sylogd Service does not start.
|
From: olaf b. <ola...@gm...> - 2010-08-17 08:39:07
|
Hello,
forget this thread - I have overseen the comment in
services-configuration.xml right below jetty Service.
Sorry
BR Olaf
-------- Original-Nachricht --------
Datum: Tue, 17 Aug 2010 09:39:10 +0200
Von: "olaf balzer" <ola...@gm...>
An: ope...@li...
Betreff: Sylogd Service does not start.
Hello,
I want to use this Syslogd Service in Opennms, but can't use it, as
it seems that it is not running, but configured:
cat /opt/opennms/etc/service-configuration.xml.
clip
<service>
<name>OpenNMS:Name=Syslogd</name>
<class-name>org.opennms.netmgt.syslogd.jmx.Syslogd</class-name>
<invoke at="start" pass="0" method="init"/>
<invoke at="start" pass="1" method="start"/>
<invoke at="status" pass="0" method="status"/>
<invoke at="stop" pass="0" method="stop"/>
</service>
<service>
clap
[root@vm-opennms ~]#
/etc/init.d/opennms -v status
OpenNMS.Eventd : running
OpenNMS.Trapd : running
OpenNMS.Queued : running
OpenNMS.Dhcpd : running
OpenNMS.Actiond : running
OpenNMS.Capsd : running
OpenNMS.Notifd : running
OpenNMS.Scriptd : running
OpenNMS.Rtcd : running
OpenNMS.Pollerd : running
OpenNMS.PollerBackEnd : running
OpenNMS.Ticketer : running
OpenNMS.Collectd : running
OpenNMS.Threshd : running
OpenNMS.Discovery : running
OpenNMS.Vacuumd : running
OpenNMS.EventTranslator: running
OpenNMS.PassiveStatusd : running
OpenNMS.Statsd : running
OpenNMS.Provisiond : running
OpenNMS.Reportd : running
OpenNMS.Alarmd : running
OpenNMS.AsteriskGateway: running
OpenNMS.Ackd : running
OpenNMS.JettyServer : running
opennms is running
The syslogd
confiuguration is like this the default one)
[root@vm-opennms etc]# cat syslogd-configuration.xml
<?xml version="1.0"?>
<syslogd-configuration>
<configuration
syslog-port="10514"
new-suspect-on-message="false"
forwarding-regexp="^.*\s(19|20)\d\d([-/.])(0[1-9]|1[012])\2(0[1-9]|[12][0-9]|3[01])(\s+)(\S+)(\s)(\S.+)"
matching-group-host="6"
matching-group-message="8"
discard-uei="DISCARD-MATCHING-MESSAGES"
/>
<!-- Use the following to convert UEI ad-hoc -->
<ueiList>
<ueiMatch>
<match type="substr" expression="CRISCO"/>
<uei>CISCO</uei>
</ueiMatch>
<ueiMatch>
<match type="regex" expression=".*fancyd: .*failed
for user (\S+) on ((pts\/\d+)|(tty\d+)).*"/>
<uei>uei.example.org/syslog/fancyd/userFailure</uei>
<!-- In the event definition for the above UEI, you
can refer to the
parenthesized match groups above:
%parm[group1]% or %parm[#1]% will have the
username
%parm[group2[% or %parm[#2]% will have the
device name
These mappings are
created by default. The definition below
shows how to suppress them and how to map
matching groups
to user-specified event parameters.
-->
</ueiMatch>
<ueiMatch>
<match type="regex" expression=".*shmancyd: .*failed
for user (\S+) on ((pts\/\d+)|(tty\d+)).*"
default-parameter-mapping="false"/>
<uei>uei.example.org/syslog/shmancyd/userFailure</uei>
<parameter-assignment matching-group="1"
parameter-name="userName" />
<parameter-assignment matching-group="2"
parameter-name="terminalName" />
<parameter-assignment matching-group="3"
parameter-name="ptsName" />
<parameter-assignment matching-group="4"
parameter-name="ttyName" />
<!-- The event created by this definition will not
have the "groupN" parameters.
If the message refers to a user on
terminal pts/3, the "ptsName" parameter
will be set to "pts/3" and the "ttyName"
parameter will be present with an
empty string value. If the message
instead refers to a user on tty4, then
the "ttyName" parameter will be set to
"tty4" and the "ptsName" parameter
will have an empty string value. In
either case, the "terminalName" parameter
will contain the terminal name that
matched.
-->
</ueiMatch>
<!-- Use the following to discard a syslog message without
ever creating an event for it.
If you change the value of "discard-uei" above,
you must change the UEI used here to match. -->
<ueiMatch>
<match type="substr" expression="JUNK"/>
<uei>DISCARD-MATCHING-MESSAGES</uei>
</ueiMatch>
</ueiList>
<!-- Use the following to remove a syslog
message from the event-trail -->
<hideMessage>
<hideMatch>
<match type="substr" expression="SECRET"/>
</hideMatch>
<hideMatch>
<match type="regex"
expression=".*(double|triple)secret.*"/>
</hideMatch>
</hideMessage>
</syslogd-configuration>
Can someone help ?
BR Olaf
|