On Fri, 16 Jan 2009, Rainer Gerhards wrote: > Lorenzo and others: > > I hopefully got a system today where I can reproduce. I am setting it up > right now. I also have written a stub wiki page with information useful to > hunt this bug:
one other thing that you can do for this sort of thing is to use the amazon cloud. to quote a message from Rob Landley to the linux-kernel mailing list > My friend Mark's been experimenting with the amazon "cloud" thing, > feeding in an image with a qemu instance and distcc+cross-compiler, and > running builds under that. Renting an 8-way ~2.5 ghz server with 7 > gigabytes of ram and 1.6 terabytes of disk is 80 cents/hour through them > plus another few cents/day for bandwidth and persistent storage and > such. That's likely to get cheaper as time goes on. > > We're still planning to buy a build server of our own to have something > in- house, but for running nightly builds it's almost to the point where > depreciation on the hardware is more than buying time from a server > farm. Just _one_ of those 8-way servers is enough hardware to build an > entire distro in an hour or so. > > What this really allows us to do is experiment with "how parallel can we > get our build"? Because renting ten 8-way servers in a cluster is > $8/hour, and distcc already scales trivially over that. Down the road > what Firmware Linux is working towards is multiple qemu instances > running in parallel with a central instance distributing builds to each > one, so each can do its own ./configure in parallel, distribute > compilation to the distccd instances as it has stuff to compile, and > then package up the resulting binary into one of those portage tarballs > and send it back to the central node to install on a network mount that > the lot of 'em can mount as build context, so the packages can get their > dependencies right. (You don't want your build taking place in a > network mount, but your OS being on one you never write to isn't so bad > as long as you have local storage to build in.) > > We'll probably leverage the heck out of Portage for this, and might wind > up modifying it heavily. Dunno yet. (We can even force dependencies on > portage so it doesn't need to calculate 'em, the central node can do > that and then say "you have these packages, _build_"...) > > But yeah, hobbyists with a laptop, network access, and a monthly budget > of $20 can do cluster builds these days. would it make sense to start a fund to pay for some time for you to use like this? David Lang > http://wiki.rsyslog.com/index.php/V3_Race_Condition_Hunt_Page > > Lorenzo, can you please double-check I have used the right config indeed. > > All others: if you can add scenarios/information, please do. I'll try to > repro the problem as soon as the system is ready. Hope it will work... > > Rainer > >> -----Original Message----- >> From: [email protected] [mailto:rsyslog- >> [email protected]] On Behalf Of Rainer Gerhards >> Sent: Friday, January 16, 2009 5:20 PM >> To: rsyslog-users >> Subject: Re: [rsyslog] rsyslog still crashes >> >> Lorenzo, >> >> one thing: can you change the actionqueuemode to "direct" just for a >> short period. I would be very interested to see what happens. >> >> Rainer >> >>> -----Original Message----- >>> From: [email protected] [mailto:rsyslog- >>> [email protected]] On Behalf Of Lorenzo M. Catucci >>> Sent: Friday, January 16, 2009 5:10 PM >>> To: rsyslog-users >>> Subject: Re: [rsyslog] rsyslog still crashes >>> >>> On Fri, 16 Jan 2009, Lorenzo M. Catucci wrote: >>> >>> LMC> >>> LMC> The -n crash was completely silent; the -d run was chatty (as >>> expected); >>> LMC> with stdout redirected, it took a lot more time to crash, but >> here >>> are >>> LMC> both the logfile and the gdb backtrace. >>> LMC> >>> >>> As for the last crash, I found on the screen session the line: >>> >>> rsyslogd: queue.c:1393: queueChkDiscardMsg: Assertion `(unsigned) >>> ((obj_t*)(pUsr))->iObjCooCKiE == (unsigned) 0xBADEFEE' failed. >>> >>> since I forgot redirecting stderr too. >>> >>> Yours, >>> >>> lorenzo >>> >>> +-------------------------+------------------------------------------ >> -- >>> --+ >>> | Lorenzo M. Catucci | Centro di Calcolo e Documentazione >>> | >>> | [email protected] | Universit? degli Studi di Roma "Tor >>> Vergata" | >>> | | Via O. Raimondo 18 ** I-00173 ROMA ** >>> ITALY | >>> | Tel. +39 06 7259 2255 | Fax. +39 06 7259 2125 >>> | >>> +-------------------------+------------------------------------------ >> -- >>> --+ >> _______________________________________________ >> 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
