sinitean commented on issue #979: Error while create a view
URL: https://github.com/apache/couchdb/issues/979#issuecomment-344791666
 
 
   I'm seeing a similar issue on OSX 10.13.1. It happens with any view or if 
you decide to replicate anything that has a design doc attached. 
   The couchdb.log entry is:
   [info] 2017-11-15T23:05:22.685021Z couchdb@localhost <0.218.0> -------- 
couch_proc_manager <0.24207.0> died normal
   [error] 2017-11-15T23:05:22.685029Z couchdb@localhost <0.9320.0> c5d0527261 
OS Process Error <0.24207.0> :: {os_process_error,{exit_status,134}}
   
   The moment I try to create a view the message above floods the log and 
memory consumption on my mac maxes out (I have 40gig of memory). I end up 
killing couch before it kills my machine. 
   
   I see the upgrade nodes for 2.1.1 and wonder if it is related to #914 and 
#916. 
   https://github.com/apache/couchdb/pull/916
   https://github.com/apache/couchdb/pull/914
   
   The problems are not limited to my Mac install.
   I see also similar errors on ubuntu 16.04 on 2 separate servers.
   Using curl, trying a replication of a db ("mydb") that contains views get 
me: 
   {"error":"error","reason":"{http_request_failed,\"GET\",\n    
\"https://admin:*****@127.0.0.1:5984/mydb/\",\n    
{error,{error,{conn_failed,{error,{tls_alert,\"record overflow\"}}}}}}"}
   
   If I 'm trying to create or delete a db via curl:
    curl -X PUT http://admin:****@127.0.0.1:5984/testdb
    or 
   curl -X DELETE http://admin:****@127.0.0.1:5984/testdb
    I get the following error:
   {"error":"error","reason":"internal_server_error"}
   Interestingly, the db is created / deleted as it can be seen on Fauxton or 
by doing a curl get _all_dbs.
   This works also with the verifydb test. If you run the verification step you 
get an error and then in Fauxton you see it greyed out with "database could not 
be loaded". But you can remove (and re-add) it via curl despite getting the 
error.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to