-
Notifications
You must be signed in to change notification settings - Fork 64
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
socat error on Monday mornings only #119
Comments
are you restarting every sunday? if not is normal that on Monday it will not work. |
Gonzalo, Why should I need to restart every Sunday? I just have the AUTO_RESTART_TIME=02:59 AM setting in my .env |
you need to enter credentials once per week, on sunday will disconnect and require credentials. basically when you restart on mondays you are entering credentials again and works. if you do this on sunday, it will be ready on mondays. |
Is there any way around entering credentials once per week? |
Entering credentials once per week is the way around entering credentials every day. So no, there is no way around it AFAIK. |
But don't understand the difference between restaring the container and the AUTO_RESTART_TIME=02:59 AM parameter ? I thought the AUTO_RESTART_TIME was entering credentials to restart the gateway inside the container.... |
some usefull links on this subject IBC user guide and 3.19 release notes honestly IBC documentation is much clear than TWS's docs |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
#102 I am encountering a consistent issue on the container . Every Monday morning, the following error prompts a need for a manual container restart:
2024/06/03 05:00:12 socat[63188] E connect(5, AF=2 127.0.0.1:4002, 16): Connection refused .> 😘 Received SIGINT or SIGTERM. Shutting down IB Gateway. .> Stopping Xvfb. .> Stopping socat. .> Stopping IBC. IBC returned exit status 1 autorestart file not found
This error indicates that the connection to a local service on port 4002 is refused, triggering a shutdown sequence. Moreover, it appears the autorestart functionality is not working as expected, as evidenced by "autorestart file not found."
Could anyone please provide insights or suggest modifications to ensure the container can automatically recover from such errors without requiring manual intervention? This would significantly enhance stability and usability on ARM64 systems.
Thank you for any help or suggestions you can provide.
Best regards,
The text was updated successfully, but these errors were encountered: