Hi all, After a power outage, I had some troubles restarting my galaxy instance using Ansible and have encountered some issues : :puzzle_piece: 1. Gunicorn socket (gunicorn.sock) not created :page_facing_up: Setup Galaxy is run via galaxyctl The systemd unit galaxy-gunicorn.service calls: ExecS…

Dear, Hello again. So finally I managed somehow to generate my socket again. With the last error given, I “saw” that there was a problem with the tool_search_index directory so I Stopped the gunicorn.service sudo systemctl stop galaxy-gunicorn.service Removed the directory sudo rm -rf /hom…

Welcome @NairaNaouar This will need some advanced help. I’ve cross posted over the Admin Chat. They usually reply back here but feel free to join, too! :hammer_and_wrench: You're invited to talk on Matrix XRef: [image] Private Galaxy Servers Local Galaxy A local Galaxy server is a choice for p…

[image] NairaNaouar: Despite Galaxy reporting as running (galaxyctl status shows active (running)), the expected socket file is not created: your Galaxy configs seem correct to me, I’d explore your system’s state further [image] NairaNaouar: Should we be explicitly creating dependency_re…

Hi @marten [image] marten: your Galaxy configs seem correct to me, I’d explore your system’s state further What should I look into in the system that may block the creation of the gunicorn.socket? [image] marten: I don’t think so, but make sure you are not specifying its path in galaxy.…

[image] NairaNaouar: What should I look into in the system that may block the creation of the gunicorn.socket? Could you post your galaxy.yml config? Namely the gravity section. But please mind any secrets. [image] NairaNaouar: How could I change the galaxy.yml in this case? in my und…

[image] marten: Could you post your galaxy.yml config? Namely the gravity section. But please mind any secrets. Here is the gravity section : gravity: galaxy_root: /home/galaxy/galaxy galaxy_user: galaxy gunicorn: bind: unix:/home/galaxy/galaxy/config/gunicorn.sock …

And here the galaxy section galaxy: admin_users: **** allow_path_paste: true allow_user_dataset_purge: true allow_user_deletion: true allow_user_impersonation: true brand: 🧬 Mississippi[2] builds_file_path: shared/ucsc/builds.txt cleanup_job: onsuccess containe…

I would suggest that you set conda_auto_init: false in the galaxy section of galaxy.yml. conda_auto_init would otherwise attempt to install conda to the default location. This only works if a single process is being started, otherwise multiple processes attempt to install conda at the same time, fai…

Thanks @mvdbeek Il will check that and send the logs if needed. I will let you know!

Hi @marten & @mvdbeek I have encountered a new error that might explain that the gunicorn.sock is not created. After running the journalctl of the gunicorn.service I got the following errors: $sudo journalctl -u galaxy-gunicorn.service -n 50 --no-pager [***some skipped lines***] Jul 15 15:06:38 …

Thanks for posting back what worked @NairaNaouar :rocket:

🔧 gunicorn.sock not created despite Galaxy running — and dependency_resolvers_conf.xml missing

jennaj July 10, 2025, 9:27pm 2

Welcome @NairaNaouar

This will need some advanced help. I’ve cross posted over the Admin Chat. They usually reply back here but feel free to join, too! You're invited to talk on Matrix

XRef: