[ 
https://issues.apache.org/jira/browse/COUCHDB-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991847#comment-12991847
 ] 

Dave Cottlehuber commented on COUCHDB-963:
------------------------------------------

Also replicated, EC2 large instance, w2008 r1sp2 datacenter ed. 

My reading is that this is an erlang vm problem.

Not all restarts fail:
[Tue, 08 Feb 2011 08:16:25 GMT] [info] [<0.362.0>] 125.236.236.206 - - 'POST' 
/_restart 200

[Tue, 08 Feb 2011 08:16:27 GMT] [info] [<0.398.0>] Apache CouchDB has started 
on http://0.0.0.0:5984/

but others do - 7 minute delay is my manual restart coming in:

[Tue, 08 Feb 2011 08:23:37 GMT] [debug] [<0.2056.0>] 'POST' /_restart {1,1}
Headers: [{'Accept',"application/json"},
          {'Accept-Charset',"ISO-8859-1,utf-8;q=0.7,*;q=0.7"},
          {'Accept-Encoding',"gzip, deflate"},
          {'Accept-Language',"en-us,en;q=0.5"},
          {'Cache-Control',"no-cache"},
          {'Connection',"keep-alive"},
          {'Content-Length',"0"},
          {'Content-Type',"application/json; charset=UTF-8"},
          {'Cookie',"AuthSession="},
          {'Host',"ec2-204-236-204-144.compute-1.amazonaws.com:5984"},
          {'Keep-Alive',"115"},
          {'Pragma',"no-cache"},
          
{'Referer',"http://ec2-204-236-204-144.compute-1.amazonaws.com:5984/_utils/couch_tests.html?script/couch_tests.js"},
          {'User-Agent',"Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; 
rv:2.0b10) Gecko/20100101 Firefox/4.0b10"}]

[Tue, 08 Feb 2011 08:23:37 GMT] [debug] [<0.2056.0>] OAuth Params: []

[Tue, 08 Feb 2011 08:23:37 GMT] [info] [<0.2056.0>] 125.236.236.206 - - 'POST' 
/_restart 200

[Tue, 08 Feb 2011 08:30:30 GMT] [info] [<0.34.0>] Apache CouchDB has started on 
http://0.0.0.0:5984/

So it looks as if couchdb shuts down cleanly through;:

handle_restart_req(#httpd{method='POST'}=Req) ->
    couch_httpd:validate_ctype(Req, "application/json"),
    ok = couch_httpd:verify_is_server_admin(Req),
    couch_server_sup:restart_core_server(),

which is short & sweet:
restart_core_server() ->
    init:restart().

leaving couch now & into (I think) the vm:

restart() -> init ! {stop,restart}, ok.




> Erlang processes crash when running the delayed_commits test on Windows 
> Server 2008
> -----------------------------------------------------------------------------------
>
>                 Key: COUCHDB-963
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-963
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: 1.0.1
>         Environment: This Windows box is a virtual machine
> Windows Server 2008 Standard without Hyper-V Service Pack 2 64-bit
> 2 GB RAM
> 2 Core Intel Xeon CPU @ 2.53GHz each
>            Reporter: Terry Smith
>         Attachments: Apache CouchDB.debug.2, couch.log
>
>
> The debugging I've done points to this being an erlsrv.exe bug. Here my steps 
> to recreate.
> Install 1.0.1 CouchDB as a service using the Windows Binary Installer. I did 
> not select to "Start service after installation".
> Edit the local.ini to set the logging level to "debug".
> Go to the service control panel and start the Apache CouchDB service.
> Go to Test Suite in Futon and run the "delayed_commits" test.
> After about 15 - 20 seconds go to the service control panel and refresh to 
> see that the service is no longer running. ProcessExplorer verifies the 
> erlsrv.exe and erl.exe processes are not running. The last message in the log 
> is a _restart command that returns 200. 
> When I run CouchDB using CouchDB.bat. The test completes without crashing.
> When I set the DebugType in the registry 
> HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Ericsson\Erlang\ErlSrv\1.1\Apache 
> CouchDB to 1 (DEBUG_TYPE_NEW) to get a erlsrv.exe log, the test completes 
> without crashing.
> I will attach the log files from CouchDB and erlsrv.exe.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to