Skip to content

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

Closed
johnjohnk2 opened this issue Jun 7, 2024 · 7 comments
Closed

socat error on Monday mornings only #119

johnjohnk2 opened this issue Jun 7, 2024 · 7 comments
Labels
wontfix This will not be worked on

Comments

@johnjohnk2
Copy link

johnjohnk2 commented Jun 7, 2024

#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,

@gnzsnz
Copy link
Owner

gnzsnz commented Jun 7, 2024

are you restarting every sunday? if not is normal that on Monday it will not work.

@johnjohnk2
Copy link
Author

Gonzalo, Why should I need to restart every Sunday? I just have the AUTO_RESTART_TIME=02:59 AM setting in my .env

@gnzsnz
Copy link
Owner

gnzsnz commented Jun 8, 2024

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.

@omair-rit
Copy link

Is there any way around entering credentials once per week?

@gnzsnz
Copy link
Owner

gnzsnz commented Jun 9, 2024

Entering credentials once per week is the way around entering credentials every day. So no, there is no way around it AFAIK.

@johnjohnk2
Copy link
Author

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....

@gnzsnz
Copy link
Owner

gnzsnz commented Jun 9, 2024

some usefull links on this subject IBC user guide and 3.19 release notes

honestly IBC documentation is much clear than TWS's docs

Repository owner locked and limited conversation to collaborators Jun 9, 2024
@gnzsnz gnzsnz converted this issue into discussion #120 Jun 9, 2024
@gnzsnz gnzsnz added the wontfix This will not be worked on label Jun 22, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants