Skip to content
This repository has been archived by the owner on Nov 12, 2024. It is now read-only.

Failsafe option when galaxy config file is not in the expected place. #213

Closed
wants to merge 1 commit into from

Conversation

pcm32
Copy link
Member

@pcm32 pcm32 commented Jul 6, 2018

An old commit that I failed to PR, which sorts out issue bgruening/docker-galaxy#433 at docker-galaxy-stable.

@pcm32 pcm32 requested a review from bgruening July 6, 2018 15:18
@pcm32
Copy link
Member Author

pcm32 commented Jul 10, 2018

Hi there! I need this added to the main branch for 18.05 as well... I'm starting to use 18.05 on k8s and still seeing this issue:

IOError: [Errno 2] No such file or directory: '/etc/galaxy/galaxy.yml'

Thanks!

@pcm32
Copy link
Member Author

pcm32 commented Jul 10, 2018

I'm a bit troubled by this. I recently started testing 18.05 on k8s, but I keep getting some HTTP errors (welcome page doesn't show up, file uploads fail with Warning: Not Found (404)), and before that I was getting some red errors at the very beginning (they went away with me setting galaxy.filter-with=/galaxy, although from documentation I'm not sure that this is even correct to do).

On one side, the dagobah training slides it state that a galaxy.yaml file is not needed... yet without it (and the commit on this PR), galaxy 18.05 doesn't start on the compose setup (at least on k8s, maybe I'm doing something wrong). On the other hand, using the default yaml file, as proposed here, seems to be imposing some defaults for UWSGI that I'm not sure are correct, and that I'm starting to think might be related to my http errors...

Any comments @bgruening ?

@bgruening
Copy link
Member

I'm not sure what is going on there. The yml should not be needed as Galaxy will fallback to the sample file. Also no configuration is done with the yaml file, everything should happen through supervisor and ENVs. I'm super confused here :(

And I have trouble to test this, as it seems to work for me with compose :(

@pcm32
Copy link
Member Author

pcm32 commented Jul 11, 2018

Maybe we are building the containers with slightly different env vars that in one case make certain scripts try to read the yaml file?

@pcm32
Copy link
Member Author

pcm32 commented Jul 12, 2018

My http part setup is working, and looking at the default yaml setup there is no much there, so I presume that this is not affecting that part.

@pcm32
Copy link
Member Author

pcm32 commented Nov 7, 2018

I see this again on 18.09 with a completely clean installation.... complete error is:

Waiting for database
Traceback (most recent call last):
  File "/usr/local/bin/check_database.py", line 18, in <module>
    db_url = get_config(sys.argv)['db_url']
  File "/export/galaxy-central/lib/galaxy/model/orm/scripts.py", line 126, in get_config
    properties = load_app_properties(config_file=config_file, config_prefix=config_override, config_section=config_section)
  File "/export/galaxy-central/lib/galaxy/util/properties.py", line 91, in load_app_properties
    with open(config_file, "r") as f:
IOError: [Errno 2] No such file or directory: '/etc/galaxy/galaxy.yml'

@pcm32
Copy link
Member Author

pcm32 commented Jan 22, 2019

This has been merged by some other PR, as changes are there already:

934af93#diff-205c98235541487412061d12953dc4c0

will close then this PR.

@pcm32 pcm32 closed this Jan 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants