Crispy1975 commented on issue #1214: CouchDB 2.1.1 View OS Timeouts
   @wohali Ok, have done some more testing, this time I decided to skip the 
`apt` repos and go for the Docker image from `apache/couchdb:latest` (2.1.1 and 
using the latest docker-ce install). This all installed exactly as expected and 
I was able to set-up as a single node. However when running the verify install 
step it fails in exactly the same place (view creation), also the same happens 
if I create a database manually and then create a simple view, here are the 
relevant logs from the container:
   [notice] 2018-03-10T11:55:06.656272Z nonode@nohost <0.7573.0> 79b51a6dca undefined GET /verifytestdb 404 ok 0
   [notice] 2018-03-10T11:55:06.758187Z nonode@nohost <0.7573.0> d6580e8993 undefined GET /verifytestdb_replicate 404 ok 0
   [info] 2018-03-10T11:55:07.161223Z nonode@nohost <0.10705.0> -------- 
Opening index for db: shards/80000000-9fffffff/_replicator.1520682842 idx: 
_design/_replicator sig: "3e823c2a4383ac0c18d4e574135a5b08"
   [notice] 2018-03-10T11:55:07.305601Z nonode@nohost <0.7573.0> 1f7839d7b2 admin PUT /verifytestdb 201 ok 496
   [info] 2018-03-10T11:55:07.353690Z nonode@nohost <0.10731.0> -------- 
Opening index for db: shards/40000000-5fffffff/_users.1520682842 idx: 
_design/_auth sig: "3e823c2a4383ac0c18d4e574135a5b08"
   [notice] 2018-03-10T11:55:07.514649Z nonode@nohost <0.9273.0> fa9aea8734 admin PUT /verifytestdb/test_doc_1 201 ok 173
   [info] 2018-03-10T11:55:07.515650Z nonode@nohost <0.10758.0> -------- 
Opening index for db: _users idx: _design/_auth sig: 
   [info] 2018-03-10T11:55:07.516344Z nonode@nohost <0.10763.0> -------- 
Opening index for db: _replicator idx: _design/_replicator sig: 
   [notice] 2018-03-10T11:55:07.636805Z nonode@nohost <0.9273.0> 343b70342a admin PUT /verifytestdb/test_doc_1 201 ok 65
   [notice] 2018-03-10T11:55:07.809337Z nonode@nohost <0.9273.0> 4d7ff8829e admin DELETE 
/verifytestdb/test_doc_1?rev=2-d588d3e93ee155c5afffdf0247a2c5ef 200 ok 139
   [notice] 2018-03-10T11:55:07.989632Z nonode@nohost <0.9273.0> f2ed059174 admin PUT /verifytestdb/test_doc_10 201 ok 108
   [notice] 2018-03-10T11:55:08.012906Z nonode@nohost <0.10041.0> 7b588e5c33 admin PUT /verifytestdb/test_doc_20 201 ok 127
   [notice] 2018-03-10T11:55:08.088114Z nonode@nohost <0.10547.0> 45dfce317d admin PUT /verifytestdb/test_doc_30 201 ok 172
   [info] 2018-03-10T11:55:13.187114Z nonode@nohost <0.206.0> -------- 
couch_proc_manager <0.10833.0> died normal
   [error] 2018-03-10T11:55:13.187124Z nonode@nohost <0.10831.0> -------- OS 
Process Error <0.10833.0> :: {os_process_error,"OS process timed out."}
   [info] 2018-03-10T11:55:18.284132Z nonode@nohost <0.206.0> -------- 
couch_proc_manager <0.10943.0> died normal
   [error] 2018-03-10T11:55:18.284197Z nonode@nohost <0.10831.0> -------- OS 
Process Error <0.10943.0> :: {os_process_error,"OS process timed out."}
   [info] 2018-03-10T11:55:23.394099Z nonode@nohost <0.206.0> -------- 
couch_proc_manager <0.11025.0> died normal
   [error] 2018-03-10T11:55:23.394162Z nonode@nohost <0.10831.0> -------- OS 
Process Error <0.11025.0> :: {os_process_error,"OS process timed out."}
   [info] 2018-03-10T11:55:28.495147Z nonode@nohost <0.206.0> -------- 
couch_proc_manager <0.11109.0> died normal
   [error] 2018-03-10T11:55:28.495233Z nonode@nohost <0.10831.0> -------- OS 
Process Error <0.11109.0> :: {os_process_error,"OS process timed out."}
   [info] 2018-03-10T11:55:33.610131Z nonode@nohost <0.206.0> -------- 
couch_proc_manager <0.11191.0> died normal
   [error] 2018-03-10T11:55:33.610208Z nonode@nohost <0.10831.0> -------- OS 
Process Error <0.11191.0> :: {os_process_error,"OS process timed out."}
   [info] 2018-03-10T11:55:38.749125Z nonode@nohost <0.206.0> -------- 
couch_proc_manager <0.11275.0> died normal
   [error] 2018-03-10T11:55:38.749207Z nonode@nohost <0.10831.0> -------- OS 
Process Error <0.11275.0> :: {os_process_error,"OS process timed out."}
   [info] 2018-03-10T11:55:43.867119Z nonode@nohost <0.206.0> -------- 
couch_proc_manager <0.11357.0> died normal
   [error] 2018-03-10T11:55:43.867202Z nonode@nohost <0.10831.0> -------- OS 
Process Error <0.11357.0> :: {os_process_error,"OS process timed out."}
   [info] 2018-03-10T11:55:49.006130Z nonode@nohost <0.206.0> -------- 
couch_proc_manager <0.11441.0> died normal
   [error] 2018-03-10T11:55:49.006209Z nonode@nohost <0.10831.0> -------- OS 
Process Error <0.11441.0> :: {os_process_error,"OS process timed out."}
   As before the `couchjs` process just keeps spawning until the host machine 
crashes. This feels like it is a CouchDB issue, but perhaps relating to 
something specific in the underlying server... processor perhaps? The machine 
has 8 cores, but I am only listing the output of `cat /proc/cpuinfo` for one of 
them to save space:
   processor    : 0
   vendor_id    : GenuineIntel
   cpu family   : 6
   model                : 60
   model name   : Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz
   stepping     : 3
   microcode    : 0x1d
   cpu MHz              : 3399.070
   cache size   : 8192 KB
   physical id  : 0
   siblings     : 8
   core id              : 0
   cpu cores    : 4
   apicid               : 0
   initial apicid       : 0
   fpu          : yes
   fpu_exception        : yes
   cpuid level  : 13
   wp           : yes
   flags                : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb xsaveopt 
pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 
avx2 smep bmi2 erms invpcid
   bogomips     : 6784.53
   clflush size : 64
   cache_alignment      : 64
   address sizes        : 39 bits physical, 48 bits virtual
   power management:
   There is plenty of memory (32GB) and disk space there is about 1.8TB free.

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:

With regards,
Apache Git Services

Reply via email to