-
-
Notifications
You must be signed in to change notification settings - Fork 992
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
Problem: Container is not starting after getting v2.9.109 with Error Messages #2060
Comments
same issue...This was after the update. |
@kelvin-keegen , @DaBlubber what OS do you use? |
Do you map |
Hey i am using Debian 12 with Docker Managed by Portainer
Yes, this is mounted. With version 2.9.75 everything works well To add something i have to semaphore on the same machine because one testing and one more produtice and the test machine dont have the problem. Just this one machine. So no idea about the problem. |
@DaBlubber Please try |
Hi, Thank you. |
Does not work. Same error: |
@agarzon-orangerine you are talking about something totally different then this reported issue. |
…@05c9a6f by renovate (#22652) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [semaphoreui/semaphore](https://togithub.com/semaphoreui/semaphore) | patch | `v2.9.75` -> `v2.9.112` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>semaphoreui/semaphore (semaphoreui/semaphore)</summary> ### [`v2.9.112`](https://togithub.com/semaphoreui/semaphore/releases/tag/v2.9.112) [Compare Source](https://togithub.com/semaphoreui/semaphore/compare/v2.9.75...v2.9.112) #### Bugfixes - Docker: Fixed zombie processes [semaphoreui/semaphore#2069 - Docker: Moved Python venv from `~/venv` to `/opt/semaphore/venv` to fix issue [semaphoreui/semaphore#2060 - Docker: LDAP issue [semaphoreui/semaphore#2063 - UI: Remove extra close button in Template dialog </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://togithub.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zODIuMCIsInVwZGF0ZWRJblZlciI6IjM3LjM4Mi4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbImF1dG9tZXJnZSIsInVwZGF0ZS9kb2NrZXIvZ2VuZXJhbC9ub24tbWFqb3IiXX0=-->
Issue
After updating the Semaphore to the latest version
the container is not able to start anymore.
Impact
Semaphore Project
Installation method
Docker
Database
MySQL
Browser
Firefox, Chrome, Microsoft Edge
Semaphore Version
latest version
Ansible Version
Logs & errors
Attempting to connect to database semaphore on 10.10.10.250:3306 with user semaphore ...
/usr/local/bin/server-wrapper: source: line 184: can't open './venv/bin/activate': No such file or directory
Attempting to connect to database semaphore on 10.10.10.250:3306 with user semaphore ...
/usr/local/bin/server-wrapper: source: line 184: can't open './venv/bin/activate': No such file or directory
Attempting to connect to database semaphore on 10.10.10.250:3306 with user semaphore ...
Manual installation - system information
haproxy
Configuration
Env Variables
0 SEMAPHORE_PLAYBOOK_PATH=/tmp/semaphore/
1 SEMAPHORE_ADMIN_PASSWORD=-----------
2 SEMAPHORE_ADMIN_NAME=---------
3 SEMAPHORE_ADMIN_EMAIL=-----------
4 SEMAPHORE_ADMIN=--------------
5 ANSIBLE_HOST_KEY_CHECKING=false
6 SEMAPHORE_DB_DIALECT=mysql
7 SEMAPHORE_DB_HOST=10.10.10.250:3306
8 SEMAPHORE_DB=--------------
9 SEMAPHORE_DB_USER=-------------------
10 SEMAPHORE_DB_PASS=---------------
11 GIT_SSL_NO_VERIFY=true
12 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
13 ANSIBLE_VERSION=9.4.0
Additional information
No response
The text was updated successfully, but these errors were encountered: