search

sw360 / sw360chores

WARNING - Work in Progress - It is not Bug Free! Use with Caution. This repository contains Dockerfiles and accompanying scripts that allow deployment of sw360 via docker
Eclipse Public License 1.0
13 stars 18 forks source link

Help needed with running SW360 - 502 Bad Gateway #84

Open ZCdenheijer opened 3 years ago

ZCdenheijer commented 3 years ago

I got the latest sources from sw360chores and followed the instructions of V2 to build everything. That works fine, however when I run startUp.sh and go to https://localhost:8443 I get an Bad Gateway error with the following Nginx error. image

I'm running this on a VirtualBox and all docker containers are running image

Did I miss something? Any help will very much appreciated.

mcjaeger commented 3 years ago

I am not sure if the bad gateway issue is related to the sw360chores setup in docker, but I just merged the main code changes to let it run with version 12. It will not work beyond commit:

https://github.com/eclipse/sw360/commit/71348b4fffa6e3e5fd761a3f63590a0a60663827

(because the apache compress dependency is not ether as prerequisite)

Apart from that:

AlexFTrapp commented 3 years ago

I too have this problem on my hosts. As far as I can tell, the problem arises from a not runing couchDB which results in the server to wait for it endlessly. In my case the following error ist found in the docker logs:

from sw360_sw360couchDB: [notice] 2021-01-26T08:11:36.758647Z nonode@nohost <0.324.0> -------- chttpd_auth_cache changes listener died database_does_not_exist at mem3_shards:load_shards_from_db/6(line:403) <= mem3_shards:load_shards_from_disk/1(line:378) <= mem3_shards:load_shards_from_disk/2(line:407) <= mem3_shards:for_docid/3(line:91) <= fabric_doc_open:go/3(line:38) <= chttpd_auth_cache:ensure_auth_ddoc_exists/2(line:187) <= chttpd_auth_cache:listen_for_changes/1(line:134)

from sw360_sw360: DEBUG: Waiting for CouchDB to be up... DEBUG: curl --output /dev/null --silent --head --fail http://sw360:sw360@sw360couchdb:5984/_up

@ZCdenheijer : do you have any updates on this matter yet?

mcjaeger commented 3 years ago

Hm, usually, if the couchdb is not running, then the web pages load but areas will have a red rectangle saying "The portlet is currently not available".

What would be really required here is some log output from the tomcat to understand what happens if nginx tries to contact the tomcat. 502 means if I am not mistaken that the nginx is working, but the application / service does not respond.