-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
During AWS_Task Setup Django failing #116
Comments
This is pretty similar to this issue: #23 for which I have a PR available. Basically, when migrations are running (and they can take a while) the interface will just return errors. However, the task container is the one that should be running the migrations. The log seems clipped though... did it generate an error when attempting to run the migrations? |
@matburt I'm getting the logs from the "docker logs -f awx_task" command. During the install.yml run it returned no errors, as far as I could see. The output is gone because I've been trying to watch the docker logs to see if there was any change in them. |
One of the first things the task container will do is attempt to run migrations so if you can grab the output of that when it experiences the problem that'd be super helpful. |
@matburt Is there a recommended way for me to grab those? |
just get to the log output early I'd reckon?
|
I can second having this issue, the error messages have been repeating for about 10 minutes. The other thing I'm noticing which may be related is when I navigate to http://localhost a pop up box says "ERROR Failed to read/api. GET status: 500 A server error has occured". I can close the box, and when I attempt to login, it just hangs with the 'Working' gear spinning in the bottom corner. |
@matburt Following Steps taken:
migrations finished and everything seemed to be happy. Curious if there is an issue on the wait time, or something similar? Here are the migration logs from the second run.
|
@knechtionscoding @matburt I followed those steps and it's also working here now. Thanks! |
@phandolin Good to hear. |
blah, part of me hoped you would run into it again so I could see what the error was :/ I'll close this and if you have any other information feel free to open it with more logs. |
Before I attach the ad nauseum logs from awx_task repeating the celery failure every 10 seconds, is there some sort of persistent data directory for the database that should be removed/moved during a re-install even if you're not using the postgres docker container? I rebuilt my setup because the postgres container would constantly restart and setup a separate host for postgres and when I install into the new database, I'm having the same issues listed here. I'm on the most up to date git pull. |
If you are managing the database externally then you'll need to drop and re-create the database and let AWX run the migrations... otherwise you're just using the same data. |
Yes I do that in place of removing the postgres container. Each time I run the installer.yml I am starting with a brand new database. I remove the docker images with I've just downloaded a fresh copy of 1.0.4 (instead of cloning the repo). We'll see how it goes! |
Actually, I failed to list my external hostname, so it created a postgres docker :-/. When I'm setting up the external one (with another freshly dropped/created database) I get the celery errors repeating again and the web interface is the migrations_notran page. |
The 1.0.4 tar from https://github.com/ansible/awx/releases |
ISSUE TYPE
COMPONENT
SUMMARY
After successful completion of the local docker installation on Centos 7.3.1611 docker properly has 5 containers running. When looking at the logs for the AWS Task container however the celery process keeps dying due to anissue in the Django python code.
ENVIRONMENT
STEPS TO REPRODUCE
Run installation on Centos 7.3.1611
EXPECTED RESULTS
Correct configuration of AWX post installation
ACTUAL RESULTS
This continues repeatedly. I've let it run for 15 minutes with no change in the attempts.
ADDITIONAL INFORMATION
This is unrelated to issue #115. I managed to get the installer working on another instance.
The text was updated successfully, but these errors were encountered: