Have you used a different pidfile?

> -----Original Message-----
> From: [email protected] [mailto:rsyslog-
> [email protected]] On Behalf Of Ayelet Regev
> Sent: Monday, August 15, 2011 4:01 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] rsyslog 4.7.2 weird bahaviour on Solaris 10
> 
> want to have multiple instances of rsyslog on Solaris 10. (rsyslog
> 7.4.7)
> 
> Currently my "Client" instance is running, when trying to start the
> "server"
> instance i get these errors:
> 
> 2334.046496319:4: Called LogError, msg: syslogd pid 2000 already
> running.
> Cannot start another syslogd pid 2059
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> smu15a:/ ROOT > ps -ef | grep -i ryslog
>     root 25275     1   0 15:35:29 pts/1       0:00
> /usr/local/Rsyslog/sbin/
> rsyslogd -i /var/run/rsyslog-client.pid -f /etc/rsyslog
> 
> 
> 
> 
> smu15a:/ ROOT > /usr/local/Rsyslog/sbin/rsyslogd-server -c4 -i
> /var/run/rsyslog-server.pid -f /etc/rsyslog-server.conf -dn
> 
> 2334.011338550:1: logmsg: flags 1, from 'smu15a', msg  [origin
> software="rsyslogd" swVersion="4.7.4" x-pid="2059" x-info="
> http://www.rsyslog.com";] (re)start
> 2334.011406966:1: Message has legacy syslog format.
> 2334.011507680:1: main Q: entry added, size now 1 entries
> 2334.011581950:1: wtpAdviseMaxWorkers signals busy
> 2334.011675143:1: main Q: EnqueueMsg advised worker start
> 2334.043650492:1:  (re)started.
> 2334.043746746:1: Debugging enabled, SIGUSR1 to turn off debugging.
> 2334.043833149:2: main Q: entry deleted, state 0, size now 0 entries
> 2334.043961439:2: testing filter, f_pmask 0
> 2334.044045312:2: testing filter, f_pmask 0
> 2334.044171036:2: testing filter, f_pmask 0
> 2334.044256129:2: testing filter, f_pmask 0
> 2334.044334439:2: testing filter, f_pmask 0
> 2334.044449766:2: main Q:Reg/w0: worker IDLE, waiting for work.
> 2334.044615812:5: Listening on UDP syslogd socket 5 (IPv6/port 514).
> 2334.044727969:5: Listening on UDP syslogd socket 6 (IPv4/port 514).
> 2334.044828376:6: caller requested object 'nsd_ptcp', not found (iRet -
> 3003)
> 2334.044930106:6: Requested to load module 'lmnsd_ptcp'
> 2334.045030006:5: Listening on UDP syslogd socket 7 (IPv6/port 1514).
> 2334.045136246:6: loading module
> '/usr/local/Rsyslog/lib/rsyslog/lmnsd_ptcp.so'
> 2334.045240239:5: Listening on UDP syslogd socket 8 (IPv4/port 1514).
> 2334.045341399:5: --------imUDP calling select, active file descriptors
> (max
> 8): 5 6 7 8
> 2334.045639822:4: imsolaris: doing startup poll before openeing door()
> 2334.045740942:4: imsolaris: waiting for next message (timeout 0)...
> 2334.045855769:1: initialization completed, transitioning to regular
> run
> mode
> 2334.045974162:4: imsolaris: no more messages, getMsgs() terminates
> 2334.046107179:4: open_door: /var/run/syslog_door opened successfully
> 2334.046200922:4: open_door: door_info:info.di_target = 2000
> 2334.046289506:4: open_door: error: syslogd pid 2000 already running.
> Cannot
> start another syslogd pid 2059
> 2334.046367409:6: source file nsd_ptcp.c requested reference for module
> 'lmnetstrms', reference count now 4
> 2334.046496319:4: Called LogError, msg: syslogd pid 2000 already
> running.
> Cannot start another syslogd pid 2059
> 2334.046605986:6: rsyslogd: syslogd pid 2000 already running. Cannot
> start
> another syslogd pid 2059 [try http://www.rsyslog.com/e/2147 ]
> module of type 2 being loaded.
> 2334.046728132:6: source file netstrms.c requested reference for module
> 'lmnsd_ptcp', reference count now 1
> 2334.046833796:4: logmsg: flags 1, from 'smu15a', msg syslogd pid 2000
> already running. Cannot start another syslogd pid 2059 [try
> http://www.rsyslog.com/e/2147 ]
> 2334.046932806:4: Message has legacy syslog format.
> 2334.047029329:6: creating tcp listen socket on port 50514
> 2334.047134849:4: main Q: entry added, size now 1 entries
> 2334.047243859:4: wtpAdviseMaxWorkers signals busy
> 2334.047323739:6: error 125 while binding tcp socket
> 2334.047440136:2: main Q: entry deleted, state 0, size now 0 entries
> 2334.047552799:6: error 125 while binding tcp socket
> 2334.047688889:2: testing filter, f_pmask 0
> 2334.047782922:2: testing filter, f_pmask 0
> 2334.047874212:2: testing filter, f_pmask 0
> 2334.047964582:2: testing filter, f_pmask 0
> 2334.048056012:2: testing filter, f_pmask 0
> 2334.048154126:4: main Q: EnqueueMsg advised worker start
> 2334.048285092:2: main Q:Reg/w0: worker IDLE, waiting for work.
> 
> 
> On Thu, Aug 11, 2011 at 3:45 PM, Ayelet Regev
> <[email protected]>wrote:
> 
> > All ok.
> > I didn't compile with imsolaris.
> >
> > Ayelet Regev-Dabah
> > Sent from my iPhone
> >
> >
> > On 11 באוג 2011, at 13:34, Rainer Gerhards <[email protected]>
> > wrote:
> >
> > > As usual, patch -p1 < patchfile
> > >
> > >> -----Original Message-----
> > >> From: [email protected] [mailto:rsyslog-
> > >> [email protected]] On Behalf Of Ayelet Regev
> > >> Sent: Thursday, August 11, 2011 12:34 PM
> > >> To: rsyslog-users
> > >> Subject: Re: [rsyslog] rsyslog 4.7.2 weird bahaviour on Solaris 10
> > >>
> > >> How do I apply this patch?
> > >>
> > >> Ayelet Regev-Dabah
> > >> Sent from my iPhone
> > >>
> > >>
> > >> On 11 באוג 2011, at 13:33, Rainer Gerhards
> <[email protected]>
> > >> wrote:
> > >>
> > >>> Pls try attached patch and send debug log. Note that I currently
> do
> > >> not have
> > >>> solaris at hand, so I could not compile-test the patch. Expect
> minor
> > >> quircks,
> > >>> should be easy to fix.
> > >>>
> > >>> Rainer
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: [email protected] [mailto:rsyslog-
> > >>>> [email protected]] On Behalf Of Rainer Gerhards
> > >>>> Sent: Thursday, August 11, 2011 12:25 PM
> > >>>> To: rsyslog-users
> > >>>> Subject: Re: [rsyslog] rsyslog 4.7.2 weird bahaviour on Solaris
> 10
> > >>>>
> > >>>>> -----Original Message-----
> > >>>>> From: [email protected] [mailto:rsyslog-
> > >>>>> [email protected]] On Behalf Of Ayelet Regev
> > >>>>> Sent: Thursday, August 11, 2011 12:23 PM
> > >>>>> To: rsyslog-users
> > >>>>> Subject: Re: [rsyslog] rsyslog 4.7.2 weird bahaviour on Solaris
> 10
> > >>>>>
> > >>>>> No, now it worse events are not logged anywhere...
> > >>>>
> > >>>> OK, I see if I can craft a patch quickly so that weg et more
> info. I
> > >>>> don't
> > >>>> see the actual PRI as it comes in. But I see that none of the
> > >> filters
> > >>>> match.
> > >>>>
> > >>>> RAiner
> > >>>>>
> > >>>>> On Thu, Aug 11, 2011 at 1:21 PM, Ayelet Regev
> > >>>>> <[email protected]>wrote:
> > >>>>>
> > >>>>>> No, now it worse events are not logged anywhere.
> > >>>>>>
> > >>>>>> Ayelet Regev-Dabah
> > >>>>>> Sent from my iPhone
> > >>>>>>
> > >>>>>>
> > >>>>>> On 11 באוג 2011, at 13:13, "Rainer Gerhards"
> > >>>>> <[email protected]>
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>> -----Original Message-----
> > >>>>>>
> > >>>>>> From: [email protected] [mailto:rsyslog-
> > >>>>>>
> > >>>>>> [email protected]] On Behalf Of Ayelet Regev
> > >>>>>>
> > >>>>>> Sent: Thursday, August 11, 2011 11:36 AM
> > >>>>>>
> > >>>>>> To: rsyslog-users
> > >>>>>>
> > >>>>>> Subject: Re: [rsyslog] rsyslog 4.7.2 weird bahaviour on
> Solaris 10
> > >>>>>>
> > >>>>>>
> > >>>>>> Sorry, this time my event dosnt log anywhere...
> > >>>>>>
> > >>>>>>
> > >>>>>> Does that mean the original problem is solved? If not, I'll
> create
> > >>>> a
> > >>>>> patch
> > >>>>>> for you, as I don't see the PRI in the current debug log...
> > >>>>>> RAiner
> > >>>>>>
> > >>>>>>
> > >>>>>> On Thu, Aug 11, 2011 at 10:04 AM, Rainer Gerhards
> > >>>>>>
> > >>>>>> <[email protected]>wrote:
> > >>>>>>
> > >>>>>>
> > >>>>>> OK, I should remind myself not to check for bugs in older
> versions
> > >>>> ;)
> > >>>>>>
> > >>>>>> This
> > >>>>>>
> > >>>>>> one is fixed in 4.7.4...
> > >>>>>>
> > >>>>>>
> > >>>>>> Rainer
> > >>>>>>
> > >>>>>>
> > >>>>>> -----Original Message-----
> > >>>>>>
> > >>>>>> From: [email protected] [mailto:rsyslog-
> > >>>>>>
> > >>>>>> [email protected]] On Behalf Of Ayelet Regev
> > >>>>>>
> > >>>>>> Sent: Wednesday, August 10, 2011 7:05 PM
> > >>>>>>
> > >>>>>> To: rsyslog-users
> > >>>>>>
> > >>>>>> Subject: Re: [rsyslog] rsyslog 4.7.2 weird bahaviour on
> Solaris 10
> > >>>>>>
> > >>>>>>
> > >>>>>> Hi Rainer,
> > >>>>>>
> > >>>>>>
> > >>>>>> Thanks for the quick response.
> > >>>>>>
> > >>>>>> Attched.
> > >>>>>>
> > >>>>>>
> > >>>>>> On Wed, Aug 10, 2011 at 6:51 PM, Rainer Gerhards
> > >>>>>>
> > >>>>>> <[email protected]>wrote:
> > >>>>>>
> > >>>>>>
> > >>>>>> Can you provide a debug log that contains an occurence of this
> > >>>>>>
> > >>>>>> problem?
> > >>>>>>
> > >>>>>> This
> > >>>>>>
> > >>>>>> helps us understand what happens.
> > >>>>>>
> > >>>>>>
> > >>>>>> Rainer
> > >>>>>>
> > >>>>>>
> > >>>>>> -----Original Message-----
> > >>>>>>
> > >>>>>> From: [email protected] [mailto:rsyslog-
> > >>>>>>
> > >>>>>> [email protected]] On Behalf Of Ayelet Regev
> > >>>>>>
> > >>>>>> Sent: Wednesday, August 10, 2011 10:00 AM
> > >>>>>>
> > >>>>>> To: <[email protected]>[email protected]
> > >>>>>>
> > >>>>>> Subject: [rsyslog] rsyslog 4.7.2 weird bahaviour on Solaris 10
> > >>>>>>
> > >>>>>>
> > >>>>>> ** <[email protected]>
> > >>>>>>
> > >>>>>>
> > >>>>>> Hi All,
> > >>>>>>
> > >>>>>>
> > >>>>>> Im testing rsyslog 4.7.2 on Solaris 10.
> > >>>>>>
> > >>>>>>
> > >>>>>> You may see below  my syslog-client.conf file.
> > >>>>>>
> > >>>>>>
> > >>>>>> Im running the rsyslog with these parameters and I have
> > >>>>>>
> > >>>>>> validated
> > >>>>>>
> > >>>>>> config
> > >>>>>>
> > >>>>>> file.:
> > >>>>>>
> > >>>>>> (I had to comment imklog module loading and listener commands
> > >>>>>>
> > >>>>>> to
> > >>>>>>
> > >>>>>> make
> > >>>>>>
> > >>>>>> it
> > >>>>>>
> > >>>>>> work without errors.)
> > >>>>>>
> > >>>>>> My biggest problem at the moment is that all events are
> written
> > >>>>>>
> > >>>>>> to
> > >>>>>>
> > >>>>>> /tmp/kuku
> > >>>>>>
> > >>>>>> no matter their severity...
> > >>>>>>
> > >>>>>> Im executing "logger -p "mail.emerg" "test"" and its written
> > >>>>>>
> > >>>>>> into
> > >>>>>>
> > >>>>>> /tmp/kuku
> > >>>>>>
> > >>>>>> and not to the correct file.
> > >>>>>>
> > >>>>>>
> > >>>>>> Your help is more then apprichiated....
> > >>>>>>
> > >>>>>>
> > >>>>>> smu15a:/ ROOT > /usr/local/sbin/rsyslogd -c4 -f /etc/rsyslog-
> > >>>>>>
> > >>>>>> client.conf
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> smu15a:/ ROOT > /usr/local/sbin/rsyslogd -c4 -f /etc/rsyslog-
> > >>>>>>
> > >>>>>> client.conf -N4
> > >>>>>>
> > >>>>>> rsyslogd: version 4.7.2, config validation run (level 4),
> > >>>>>>
> > >>>>>> master
> > >>>>>>
> > >>>>>> config
> > >>>>>>
> > >>>>>> /etc/rsyslog-client.conf
> > >>>>>>
> > >>>>>> rsyslogd: End of config validation run. Bye
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> # Modules
> > >>>>>>
> > >>>>>>
> > >>>>>> $ModLoad imtcp
> > >>>>>>
> > >>>>>> $ModLoad imudp
> > >>>>>>
> > >>>>>> #$ModLoad imuxsock
> > >>>>>>
> > >>>>>> $ModLoad imsolaris
> > >>>>>>
> > >>>>>> #$ModLoad imklog
> > >>>>>>
> > >>>>>>
> > >>>>>> # Templates
> > >>>>>>
> > >>>>>> # log every host in its own directory
> > >>>>>>
> > >>>>>> #$template
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>
> RemoteHost,"/var/syslog/hosts/%HOSTNAME%/%$YEAR%/%$MONTH%/%$DAY%/syslog
> > >>>>>>
> > >>>>>> .log"
> > >>>>>>
> > >>>>>> ### Rulesets
> > >>>>>>
> > >>>>>> # Local Logging
> > >>>>>>
> > >>>>>> $RuleSet local
> > >>>>>>
> > >>>>>> ###user,daemon,uucp,cron,mark.notice
> > >>>>>>
> > >>>>>> /var/adm/messages
> > >>>>>>
> > >>>>>> user.notice             /tmp/kuku
> > >>>>>>
> > >>>>>> ###kern.debug
> > >>>>>>
> > >>>>>> /var/adm/messages
> > >>>>>>
> > >>>>>> ###*.emerg;mail.none                            *
> > >>>>>>
> > >>>>>> #Central logging events
> > >>>>>>
> > >>>>>> #Security logs
> > >>>>>>
> > >>>>>> auth,authpriv.debug             /var/log/central/auth.debug
> > >>>>>>
> > >>>>>> #MIPS applicaation logs
> > >>>>>>
> > >>>>>> mail.emerg                      /var/log/central/MIPSlog
> > >>>>>>
> > >>>>>> #Comverse applications events (other than MIPS)
> > >>>>>>
> > >>>>>> local0.debug                    /var/log/central/local0.debug
> > >>>>>>
> > >>>>>> #Strore local4 events in /var/log/central/traceall
> > >>>>>>
> > >>>>>> local4.debug                    /var/log/central/traceall
> > >>>>>>
> > >>>>>> local6.debug
> > >>>>>>
> > >>>>>> /var/cti/logs/SDT/SDT_Audit_Information.log
> > >>>>>>
> > >>>>>> # use the local RuleSet as default if not specified otherwise
> > >>>>>>
> > >>>>>> $DefaultRuleset local
> > >>>>>>
> > >>>>>> # Remote Logging
> > >>>>>>
> > >>>>>> $RuleSet remote
> > >>>>>>
> > >>>>>> *.crit                  @localhost:666
> > >>>>>>
> > >>>>>> # Send messages we receive to Gremlin
> > >>>>>>
> > >>>>>> ### Listeners
> > >>>>>>
> > >>>>>> # bind ruleset to tcp listener
> > >>>>>>
> > >>>>>> ###$InputTCPServerBindRuleset remote
> > >>>>>>
> > >>>>>> # and activate it:
> > >>>>>>
> > >>>>>> $InputTCPServerRun 50514
> > >>>>>>
> > >>>>>> ###$InputUDPServerBindRuleset remote
> > >>>>>>
> > >>>>>> $UDPServerRun 514
> > >>>>>>
> > >>>>>> $UDPServerRun 1514
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> Ayelet Regev-Dabah
> > >>>>>>
> > >>>>>> System Software Platform TL
> > >>>>>>
> > >>>>>> *Comverse
> > >>>>>>
> > >>>>>> *Office: +972 3 6459362
> > >>>>>>
> > >>>>>> *[email protected]* <[email protected]>
> > >>>>>>
> > >>>>>> *www.comverse.com* <http://www.comverse.com/>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> *  ________________________________  *
> > >>>>>>
> > >>>>>> "This e-mail message may contain confidential, commercial or
> > >>>>>>
> > >>>>>> privileged
> > >>>>>>
> > >>>>>> information that constitutes proprietary information of
> > >>>>>>
> > >>>>>> Comverse
> > >>>>>>
> > >>>>>> Technology
> > >>>>>>
> > >>>>>> or its subsidiaries. If you are not the intended recipient of
> > >>>>>>
> > >>>>>> this
> > >>>>>>
> > >>>>>> message,
> > >>>>>>
> > >>>>>> you are hereby notified that any review, use or distribution
> of
> > >>>>>>
> > >>>>>> this
> > >>>>>>
> > >>>>>> information is absolutely prohibited and we request that you
> > >>>>>>
> > >>>>>> delete
> > >>>>>>
> > >>>>>> all
> > >>>>>>
> > >>>>>> copies and contact us by e-mailing to: [email protected].
> > >>>>>>
> > >>>>>> Thank
> > >>>>>>
> > >>>>>> You."
> > >>>>>>
> > >>>>>> _______________________________________________
> > >>>>>>
> > >>>>>> rsyslog mailing list
> > >>>>>>
> > >>>>>> http://lists.adiscon.net/mailman/listinfo/rsyslog
> > >>>>>>
> > >>>>>> http://www.rsyslog.com
> > >>>>>>
> > >>>>>> _______________________________________________
> > >>>>>>
> > >>>>>> rsyslog mailing list
> > >>>>>>
> > >>>>>> http://lists.adiscon.net/mailman/listinfo/rsyslog
> > >>>>>>
> > >>>>>> http://www.rsyslog.com
> > >>>>>>
> > >>>>>>
> > >>>>>> _______________________________________________
> > >>>>>>
> > >>>>>> rsyslog mailing list
> > >>>>>>
> > >>>>>> http://lists.adiscon.net/mailman/listinfo/rsyslog
> > >>>>>>
> > >>>>>> http://www.rsyslog.com
> > >>>>>>
> > >>>>>>
> > >>>>>> _______________________________________________
> > >>>>>>
> > >>>>>> rsyslog mailing list
> > >>>>>>
> > >>>>>> http://lists.adiscon.net/mailman/listinfo/rsyslog
> > >>>>>>
> > >>>>>> http://www.rsyslog.com
> > >>>>>>
> > >>>>>> _______________________________________________
> > >>>>>> rsyslog mailing list
> > >>>>>> http://lists.adiscon.net/mailman/listinfo/rsyslog
> > >>>>>> http://www.rsyslog.com
> > >>>>>>
> > >>>>>>
> > >>>>> _______________________________________________
> > >>>>> rsyslog mailing list
> > >>>>> http://lists.adiscon.net/mailman/listinfo/rsyslog
> > >>>>> http://www.rsyslog.com
> > >>>> _______________________________________________
> > >>>> rsyslog mailing list
> > >>>> http://lists.adiscon.net/mailman/listinfo/rsyslog
> > >>>> http://www.rsyslog.com
> > >>> <solaris.patch>
> > >>> _______________________________________________
> > >>> rsyslog mailing list
> > >>> http://lists.adiscon.net/mailman/listinfo/rsyslog
> > >>> http://www.rsyslog.com
> > >> _______________________________________________
> > >> rsyslog mailing list
> > >> http://lists.adiscon.net/mailman/listinfo/rsyslog
> > >> http://www.rsyslog.com
> > > _______________________________________________
> > > rsyslog mailing list
> > > http://lists.adiscon.net/mailman/listinfo/rsyslog
> > > http://www.rsyslog.com
> >
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

Reply via email to