Unable to upgrade beyond 4.17.4 #1661
Replies: 2 comments 8 replies
-
|
I have similar issue but I am able to go upto 4.22.2. Moving beyond that version causes the same problem as you are facing. I wonder if you tried 4.22.2? |
Beta Was this translation helpful? Give feedback.
-
|
Just to confirm, you did follow the upgrade process as described here: https://github.com/simple-login/app/blob/4.6.2-beta/docs/upgrade.md#upgrade-to-the-latest-version-463-beta |
Beta Was this translation helpful? Give feedback.
-
|
I'm pretty sure I followed those instructions for upgrading to the beta, although it was a while ago. Are you saying you don't see those errors? And did you do the upgrade from a pre-beta version, or just setup from clean at a higher version? Edit: to add, the standard upgrade process only requires running the migration container, not the init container as well. I haven't been running the init container to do these other updates |
Beta Was this translation helpful? Give feedback.
-
|
I upgraded a few months ago from v3.4 to the beta version. Until version 4.22.2 I was able to upgrade just fine. After that I see this error in the app logs I have not seen the errors that you mentioned in the sl-email container logs. And I ran the init container as well as it was mentioned in the upgrade instructions. |
Beta Was this translation helpful? Give feedback.
-
|
My issue seem to be more related to this #1618 |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, that's something different, although you do have the same 'unreachable' messages scattered in there. Like you said, maybe to do with #1618. I agree that you run init in the major upgrade, but otherwise update is described as just needing to run the migrate container. So I haven't been running init past the beta |
Beta Was this translation helpful? Give feedback.
-
|
I believe the timeout is happening due to Docker level networking configuration - creating a new VM with the same configuration (including networking), the issue does not occur. So I'm not sure it's anything wrong with SimpleLogin. Maybe a decreased timeout time was added as part of 4.17.5 hence why the issue arose there. I'm going to rebuild the VM SimpleLogin is running on, and go from there |
Beta Was this translation helpful? Give feedback.
-
|
I was able to fix my issue with this in the compose file: app:
image: simplelogin/app-ci:v4.23.0
container_name: 'simplelogin-app'
command: 'gunicorn wsgi:app -b 0.0.0.0:7777 -w 2 --timeout 60'The last line allowed me to override the default timeout of 15 to 60. This works without issue. So it looks like for some reason the new code is taking more than 15 second to startup. |
Beta Was this translation helpful? Give feedback.
-
|
Fair enough. That's a different issue. My timeout is caused by a long delay in the docker network doing DNS resolution, that only happens when I create my own masquerade rule instead of letting Docker create one for me. So it's not SimpleLogin at fault, I'm fairly sure. |
Beta Was this translation helpful? Give feedback.
-
OS: Ubuntu 22.04, running on Oracle ARM VM
Hello, hope you're all well :)
I build my own container for ARM from the Git releases so I can remain up to date(ish). This has been working just fine for some time.
I have gone to upgrade from 4.17.0 up to 4.22.5, but when doing so an issue arose that seemed to prevent the email container from connecting to postfix (also running in a container). My testing has identified that I could upgrade up to 4.17.4, but could not go beyond - issues begun with 4.17.5.
The connection appears to timeout between sl-email and sl-postfix. Logs (sanitized):
simplelogin.env:
Has anything changed that would mean a working setup in 4.17.4 no longer works in 4.17.5+? I appreciate I'm running the SaaS build, but would be grateful for any suggestions. Happy to provide more detail/configs if needed
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions