ERROR！！！ Connection reset by peer

[terencepp]

[XeonHis]

Could you paste the full error log, it will help a lot. :)

[terencepp]

Could you paste the full error log, it will help a lot. :)

Thank you for you help，but I have fixed it again. but I meet a new problem. my process are stop in this procedure, I waited for a long time and can't see the green instruction for input.

[XeonHis]

Could you show the container.yaml in examples/step1_simpleVQA, it seems there is no data in redis.

[terencepp]

conductor_config:
name: Configuration
base_url:
value: http://localhost:8080
description: The Conductor Server API endpoint
env_var: CONDUCTOR_SERVER_URL
auth_key:
value: null
description: The authorization key
env_var: AUTH_KEY
auth_secret:
value: null
description: The authorization secret
env_var: CONDUCTOR_AUTH_SECRET
auth_token_ttl_min:
value: 45
description: The authorization token refresh interval in minutes.
env_var: AUTH_TOKEN_TTL_MIN
debug:
value: false
description: Debug mode
env_var: DEBUG
connectors:
redis_stream_client:
name: RedisConnector
host:
value: localhost
env_var: HOST
port:
value: 6379
env_var: PORT
password:
value: null
env_var: PASSWORD
username:
value: null
env_var: USERNAME
db:
value: 0
env_var: DB
redis_stm_client:
name: RedisConnector
host:
value: localhost
env_var: HOST
port:
value: 6379
env_var: PORT
password:
value: null
env_var: PASSWORD
username:
value: null
env_var: USERNAME
db:
value: 0
env_var: DB
components:
AppCallback:
name: AppCallback
bot_id:
value: ''
env_var: BOT_ID
start_time:
value: 2024-12-20_04:20:46
env_var: START_TIME
folder_name:
value: ./running_logs/2024-12-20_04:20:46
env_var: FOLDER_NAME
AppInput:
name: AppInput
DefaultCallback:
name: DefaultCallback
bot_id:
value: ''
env_var: BOT_ID
start_time:
value: 2024-12-20_04:20:46
env_var: START_TIME
folder_name:
value: ./running_logs/2024-12-20_04:20:46
env_var: FOLDER_NAME
RedisSTM:
name: RedisSTM

[djwu563]

Check if there are many running workflows on your conductor that have not been interrupted. If so, you need to select them and set them to terminal. The conductor page address is: http://localhost:5001/. If there are any further issues, you can communicate on Discord: https://discord.gg/G9n5tq4qfK.

[terencepp]

I can't go to the page address (my server cannot be visited by this way). How can I avoid this situation (conductor that have not been interrupted.), I end my process use Ctrl + C every time, and this problem happened now!

[XeonHis]

Hi, it's the problem of the conductor's feature, since the last task was not fully executed correctly, data will be prioritized from the task that wasn't completed properly.
As you mentioned, the server might not be able to expose the specified port. We provide a debug mode that it will kill all same name task before you start a new task, and it is merged into main branch.
Once you pull the latest code, set conductor_config.debug.value = true in container.yaml of your example folder, it will help.

[terencepp]

Hi, it's the problem of the conductor's feature, since the last task was not fully executed correctly, data will be prioritized from the task that wasn't completed properly. As you mentioned, the server might not be able to expose the specified port. We provide a debug mode that it will kill all same name task before you start a new task, and it is merged into main branch. Once you pull the latest code, set conductor_config.debug.value = true in container.yaml of your example folder, it will help.

Thank you, bro