priyabratap opened a new issue #2038: CouchDB : Getting 502 Bad Gateway from CouchDB v2.2.0 and beam.smp restarted every time with new PID URL: https://github.com/apache/couchdb/issues/2038 CouchDB: Getting 502 Bad Gateway from CouchDB (**v2.2.0**) and beam.smp restarted every time with new PID. Sometimes I am getting 200 OK response. I am experiencing this issue from last 2 days(note: I was using this system from last 1.5yrs without any issues) and getting below error from **couchdb.log**. The action I have taken is "Restart the machine along with CouchDB". But it did not help me. [![enter image description here][1]][1] state: {os_proc,"bash /tmp/baby",#Port<0.8007>,#Fun<couch_os_process.writejson.2>,#Fun<couch_os_process.readjson.1>,5000,300000} [error] 2019-05-27T09:25:22.821551Z [email protected] <0.1306.0> -------- Update notificatio process <0.1307.0> died: {exit_status,127} [error] 2019-05-27T09:25:22.821834Z [email protected] <0.1307.0> -------- CRASH REPORT Process (<0.1307.0>) with 0 neighbors exited with reason: {exit_status,127} at gen_server:terminate/7(line:826) <= proc_lib:init_p_do_apply/3(line:240); initial_call: {couch_os_process,init,['Argument__1']}, ancestors: [<0.1306.0>,couch_event_os_sup,couch_event_sup2,...], messages: [], links: [<0.1306.0>], dictionary: [], trap_exit: false, status: running, heap_size: 987, stack_size: 27, reductions: 807 [error] 2019-05-27T09:25:22.821948Z [email protected] <0.1199.0> -------- Supervisor couch_event_os_sup had child "index-updater" started with couch_event_os_listener:start_link("bash /tmp/baby") at <0.1306.0> exit with reason normal in context child_terminated [error] 2019-05-27T09:25:22.834620Z [email protected] <0.1317.0> -------- OS Process died with status: 127 [error] 2019-05-27T09:25:22.834864Z [email protected] <0.1317.0> -------- gen_server <0.1317.0> terminated with reason: {exit_status,127} last msg: {#Port<0.8012>,{exit_status,127}} state: {os_proc,"bash /tmp/baby",#Port<0.8012>,#Fun<couch_os_process.writejson.2>,#Fun<couch_os_process.readjson.1>,5000,300000} [error] 2019-05-27T09:25:22.834934Z [email protected] <0.1316.0> -------- Update notificatio process <0.1317.0> died: {exit_status,127} [error] 2019-05-27T09:25:22.835131Z [email protected] <0.1317.0> -------- CRASH REPORT Process (<0.1317.0>) with 0 neighbors exited with reason: {exit_status,127} at gen_server:terminate/7(line:826) <= proc_lib:init_p_do_apply/3(line:240); initial_call: {couch_os_process,init,['Argument__1']}, ancestors: [<0.1316.0>,couch_event_os_sup,couch_event_sup2,...], messages: [], links: [<0.1316.0>], dictionary: [], trap_exit: false, status: running, heap_size: 987, stack_size: 27, reductions: 807 [error] 2019-05-27T09:25:22.835279Z [email protected] <0.1199.0> -------- Supervisor couch_event_os_sup had child "index-updater" started with couch_event_os_listener:start_link("bash /tmp/baby") at <0.1316.0> exit with reason normal in context child_terminated [error] 2019-05-27T09:25:22.835602Z [email protected] <0.1199.0> -------- Supervisor couch_event_os_sup had child "index-updater" started with couch_event_os_listener:start_link("bash /tmp/baby") at <0.1316.0> exit with reason reached_max_restart_intensity in context shutdown [error] 2019-05-27T09:25:22.835963Z [email protected] <0.181.0> -------- Supervisor couch_event_sup2 had child couch_event_os_sup started with couch_event_os_sup:start_link() at <0.1199.0> exit with reason shutdown in context child_terminated [error] 2019-05-27T09:25:22.836219Z [email protected] <0.181.0> -------- Supervisor couch_event_sup2 had child couch_event_os_sup started with couch_event_os_sup:start_link() at <0.1199.0> exit with reason reached_max_restart_intensity in context shutdown [info] 2019-05-27T09:25:22.838955Z [email protected] <0.7.0> -------- Application couch_event exited with reason: shutdown [error] 2019-05-27T09:25:22.853663Z [email protected] <0.323.0> -------- gen_server <0.323.0> terminated with reason: killed [1]: https://i.stack.imgur.com/m9Q7o.png
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
