Connection to xxx-yyy.rhcloud.com closed by remote host

[marianoguerra]

Connection to xxx-yyy.rhcloud.com closed by remote host

[marianoguerra]

maybe it's a timeout thing?

can you check it it happens at a specific time after starting the build?

I think you should ask the openshift guys since it's a problem on their side, but maybe it's just some kind of timeout we are reaching.

[kaosko]

Perhaps. I also tried mucking with different timeout settings but didn't find anything suitable. After it fails, I found that the only way to fix it is to ssh to the instance and manually run ./app-root/runtime/repo/.openshift/action_hooks/build. However, that still leaves me with some (permission?) errors when I try to do something with the instance:
[Mon, 01 Dec 2014 07:17:23 GMT] [error] [<0.103.0>] httpd 500 error response:
{"error":"{http_request_failed,"HEAD","http://get.acralyzer.com/distrib-acra-storage/\",\n {error,{error,{conn_failed,{error,eacces}}}}}"}

so I wonder if there's something else I need to run or the latest simply doesn't work with the current version of Openshift?

[kaosko]

Are you able to successfully replicate any databases? After manually running ./app-root/runtime/repo/.openshift/action_hooks/build, I can start the couchdb instance and it passes installation verification but I'm not able to replicate any remote database. I asked on the couchdb user list (see http://markmail.org/thread/ywabc4ws3gjnm6nw) and they say it's a permission error, pointing to https://github.com/apache/couchdb/blob/1.6.x/INSTALL.Unix#L232-L248 for a fix. That didn't help but it's likely some permission issue with your couchdb cartridge. Perhaps something has changed either in openshift instance configuration or couchdb version that requires a change in the installation script?

[kaosko]

Sure enough, even

1> inets:start().
ok
2> httpc:request(get, {"http://www.erlang.org", []}, [], []).
{error,{failed_connect,[{to_address,{"www.erlang.org",80}},
                        {inet,[inet],eacces}]}}

doesn't work. curl/wget is able to access the same url so looks like it's something in the erlang install. Perhaps it requires write permissions to some specific temp directory but I really don't know anything about erlang and haven't found much by googling.