mirror of
https://github.com/RD17/ambar.git
synced 2026-04-25 15:35:49 +03:00
[GH-ISSUE #99] ERROR: for webapi Container "5ab789bc6ddb" is unhealthy. #97
Labels
No labels
$$ Paid Support
bug
bug
enhancement
help wanted
invalid
pull-request
question
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ambar#97
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @joseabraham on GitHub (Nov 28, 2017).
Original GitHub issue: https://github.com/RD17/ambar/issues/99
Hi,
I'm having the following issue:
ERROR: for webapi Container "5ab789bc6ddb" is unhealthy.
Docker version 17.09.0-ce, build afdb6d4
docker-compose version 1.17.0, build ac53b73
Running at AWS: ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-20171121.1 (ami-45ead225)
What could be going on?
Docker version 17.09.0-ce, build afdb6d4
docker-compose version 1.17.0, build ac53b73
vm.max_map_count = 262144
net.ipv4.ip_local_port_range = 15000 61000
net.ipv4.tcp_fin_timeout = 30
net.core.somaxconn = 1024
net.core.netdev_max_backlog = 2000
net.ipv4.tcp_max_syn_backlog = 2048
vm.overcommit_memory = 1
Creating network "ambar_internal_network" with the default driver
Creating ambar_db_1 ...
Creating ambar_rabbit_1 ...
Creating ambar_es_1 ...
Creating ambar_db_1
Creating ambar_redis_1 ...
Creating ambar_rabbit_1
Creating ambar_es_1
Creating ambar_rabbit_1 ... done
ERROR: for webapi Container "5ab789bc6ddb" is unhealthy.
ERROR: Encountered errors while bringing up the project.
Traceback (most recent call last):
File "./ambar.py", line 264, in
start(configuration)
File "./ambar.py", line 209, in start
runShellCommandStrict('docker-compose -f {0}/docker-compose.yml -p ambar up -d'.format(PATH))
File "./ambar.py", line 64, in runShellCommandStrict
subprocess.check_call(command, shell = True)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'docker-compose -f /home/ubuntu/docker-compose.yml -p ambar up -d' returned non-zero exit status 1
@sochix commented on GitHub (Nov 28, 2017):
@joseabraham is it clean install or update?
@joseabraham commented on GitHub (Nov 28, 2017):
It is a clean install Ilya
[image: photo]
http://www.facebook.com/profile.php?id=100001035440281
http://pa.linkedin.com/in/jose-abraham-garcia-79250a13
José Abraham García
Phone: +50763107105 <+5218118002040>
Email: joseabraham.garcia@gmail.com joseabraham.garcia@gmail.com
Website: http://nomadbranding.com https://thebridge.social/
https://webapp.wisestamp.com/#
On Tue, Nov 28, 2017 at 8:48 AM, Ilya Pirozhenko notifications@github.com
wrote:
@rseals commented on GitHub (Dec 1, 2017):
I have a clean install on a local VM machine and get this error message.
Docker version 17.09.0-ce, build afdb6d4
docker-compose version 1.17.1, build 6d101fb
vm.max_map_count = 262144
net.ipv4.ip_local_port_range = 15000 61000
net.ipv4.tcp_fin_timeout = 30
net.core.somaxconn = 1024
net.core.netdev_max_backlog = 2000
net.ipv4.tcp_max_syn_backlog = 2048
vm.overcommit_memory = 1
Creating network "ambar_internal_network" with the default driver
Creating ambar_db_1 ...
Creating ambar_es_1 ...
Creating ambar_rabbit_1 ...
Creating ambar_redis_1 ...
Creating ambar_es_1
Creating ambar_db_1
Creating ambar_redis_1
Creating ambar_es_1 ... done
ERROR: for webapi Container "8939088396bf" is unhealthy.
ERROR: Encountered errors while bringing up the project.
Traceback (most recent call last):
File "./ambar.py", line 264, in
start(configuration)
File "./ambar.py", line 209, in start
runShellCommandStrict('docker-compose -f {0}/docker-compose.yml -p ambar up -d'.format(PATH))
File "./ambar.py", line 64, in runShellCommandStrict
subprocess.check_call(command, shell = True)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'docker-compose -f /home/trseals/docker-compose.yml -p ambar up -d' returned non-zero exit status 1
@jamesjara commented on GitHub (Jan 19, 2018):
Same here! trying to fix it!
@cerberus10 commented on GitHub (Jan 19, 2018):
""python3 ambay.py stop
python3 ambar.py restart""
Will stop and remove docker containers , but as there is persistence (-v mount) in the containers they will be recreated using the same information by the script restart(i think, but not sure).
This fixed the problem for me.
i think it was in my case due to a unexpexted reboot of the server.
Just to be sure you could backup the data on the directory you use for storage and remove all the containers ambar uses and do a reinstall , copying over the data.
@jamesjara commented on GitHub (Jan 20, 2018):
Hello @cerberus10 thank you for your help, I'm starting a fresh install, using amazon ec2 containers not sure if it is related to any AWS policy but I have disabled almost all the restrictions.
Could be realated to this?:
WARNING: Network ambar_internal_network not found.@jamesjara commented on GitHub (Jan 20, 2018):
Actually, it is looping somehow,
docker-compose --verbose -f /home/ubuntu/docker-compose.yml -p ambar up@david-morton commented on GitHub (Jan 23, 2018):
Was facing this exact issue and have managed to solve it ... for myself at least.
My debug was to look at the logs from the container which was complaining:
The line of interest was
java.nio.file.AccessDeniedExceptionwhich was interesting as I used a mount on my NAS (CIFS) as the data store location.I've changed this to a location locally (/tmp/ambar for now) ... performed a reset / start and all is well !! Perhaps others have the same permissions issue ?
Some pretty interesting owners / groups going on ... wonder if we can steer them to a specific user/group ?
@jamesjara commented on GitHub (Jan 24, 2018):
@david-morton could you help via skype to setup a instance of this?
@aashish commented on GitHub (Feb 5, 2018):
kill all containers and images and start ambar.
@geekspeed commented on GitHub (Feb 24, 2018):
I wound up fixing this on CentOS. The issue came down to actually having two seperate docker installations (docker, and docker-latest). Dockerd was a different version than the docker client. Once i realized i had both rpms installed -- i removed everything, went back and installed only docker-latest restarted dockerd and everything is working at this point.