On Thu, 2013-02-21 at 11:14 +0100, Xavier Fustero wrote: > Hi, > > I would like to ask if there is any Ubuntu expert here who could help me on > creating the rsyslog package to have rsyslog 7.2.5 running in my Ubuntu > 10.04. > > I have created several packages: > > json-c_0.9-1_amd64.deb > libee_0.4.1-1_amd64.deb > libestr_0.1.4-1_amd64.deb > liblognorm_0.3.5-1_amd64.deb > librelp_1.0.1-1_amd64.deb > rsyslog_7.2.5-1_amd64.deb > > Then I have 2 scenarios where one is working and the other no. > > > - *Scenario1:* > > > I have installed all above packages except rsyslog_7.2.5-1_amd64.deb. Then > I have installed any extra required package, downloaded the rsyslog and > compiled it in this box: > > apt-get install uuid-dev > > cd rsyslog-7.2.5 > > ./configure --libdir=/usr/lib --includedir=/usr/include > --enable-gssapi-krb5 --enable-kmsg --enable-debug --enable-memcheck > --enable-diagtools --enable-usertools --enable-mysql --enable-elasticsearch > --enable-gnutls --enable-mmnormalize --enable-mmjsonparse --enable-relp > --enable-imfile --enable-imptcp --enable-impstats --enable-pmlastmsg > > This seems to be working for me. If I launch the rsyslog by hand > /usr/local/sbin/rsyslogd the PrivDrop also seems to be working fine. It > takes a while for the root process to disappear but it does. > > > > - *Scenario 2* > > > This is the desired scenario as I am building server through templates and > I would like just to install packages at boot time. > I have installed all above packages. I don't know why but my rsyslog > package produces a segmentation fault every time I send a message. I have > created it according the above configuration parameters. > > But when I launch it in debug mode I get the last line when I get a message: > > ... > 6250.465837291:7fbc779ce700: regular consumer finished, iret=4, szlog > 0 sz phys 0 > 6250.465841734:7fbc779ce700: main Q:Reg/w0: worker IDLE, waiting for work. > 6253.511342997:7fbc799d2700: Message from UNIX socket: #3 > Segmentation fault > can you run this under valgrind? It hopefully points to the actual proiblem location. Make sure symbols are not stripped during compile/link.
Rainer > I might miss something during the package creation because I am not able to > make a solid package for the rsyslog. > Does anyone have any hint on how to fix this? > > Thanks a log, > Xavi > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of > sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T > LIKE THAT. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
