Reproducing the error results with following errorlog information. ###################### heart_beat_kill_pid = 33715 heart_beat_timeout = 11 heart: Sat Jan 10 14:16:23 2009: heart-beat time-out.^M heart: Sat Jan 10 14:16:24 2009: Executed "/Users/neil/couchLatest/bin/couchdb -k". Terminating.^M
On Sat, Jan 10, 2009 at 10:39 AM, Chris Anderson (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/COUCHDB-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662670#action_12662670 > ] > > Chris Anderson commented on COUCHDB-204: > ---------------------------------------- > > I've never heard of this problem before. It'd be helpful if you could > reproduce while watching the log file. The easiest thing to do would be to > have CouchDB running in a terminal. > > Here's instructions on how to get running in the foreground: > http://wiki.apache.org/couchdb/Running_Couchdb_in_Dev_Mode > > You might also want to edit local_dev.ini to bring the log level up to info > or debug. > >> CouchDB stops/crashes/hangs (?) after resume from Mac OS X system >> hibernation ("safe sleep") >> -------------------------------------------------------------------------------------------- >> >> Key: COUCHDB-204 >> URL: https://issues.apache.org/jira/browse/COUCHDB-204 >> Project: CouchDB >> Issue Type: Bug >> Components: Administration Console, Database Core, HTTP Interface, >> Infrastructure >> Affects Versions: 0.8.1 >> Environment: Mac OS X 10.5.6 "Leopard" >> Reporter: Philipp Schumann >> Priority: Critical >> Fix For: 0.8.1 >> >> Original Estimate: 8h >> Remaining Estimate: 8h >> >> I'm running CouchDB 0.8.1 on Mac OS X 10.5.6 "Leopard" and after resuming >> from system hibernation ("safe sleep" -- by closing and reopening the laptop >> lid in my case, which is the factory default), the process either refuses >> all incoming connections, including my own Python scripts, web browser and >> the Futon, or has stopped running altogether. That is, I don't know which >> exactly is the case here but the fact is that CouchDB cannot be connected to >> after resuming. >> This issue does not appear using "fast sleep" (hibernation turned off), >> which is kind of my short-term work-around for now. >> This isn't a "critical" issue for server deployments, of course, but one of >> the core ideas of CouchDB is that eventually it will be deployed even to >> desktop clients for app & data replication across machines, so in this >> context this *is* a critical issue since you can't ask "ordinary" Mac OS X >> users to change their sleep settings from "safe" to "fast" using >> uncomprehensable terminal commands. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
