We invoke it with "memcached -d -p 11211 -u nobody -c 1024 -m 512". The way we tell it is crashed is that a "ps aux | grep memcached" does not show a process running memcached. This was compiled from source.
I have no idea what else to do? Chuck On Jan 13, 4:09 am, dormando <[email protected]> wrote: > What've you done so far? > > How exactly are you invoking memcached? How are you verifying that it > crashed? > > Did you compile it yourself, get it from an rpm somewhere, etc? > > -Dormando > > On Mon, 12 Jan 2009, Chuck Weinstock wrote: > > > Not surprising since no changes have been made since I last brought > > this up in October. We are seeing it survive for a week or two at a > > time (infrequently), a day or two at a time (more frequently), or an > > hour or more at a time (infrequently). > > > Can someone tell me what I need to do to provide good debugging info? > > > Thanks, > > > Chuck > > > Platform: Red Hat Enterprise Linux ES 4 - 64 Bit > > Configure options: not sure > > Compiler: gcc > > Core Dump: Not sure how to obtain > > Load: around 2 to 3 with memcached running. Around 7 to 10 without. > > Client: vBulletin and vbseo
