BertP Comments - Windmill

fetch updated invoices returns an empty array. at a high level the for loop should "just" complete because of nothing to do. The done indicator gives 100% completed, but the step breakdown says the for loop component hasn't run yet. what this lowlevel means i assume you can deduct from the logs?

24 replies

WWindmill

•Created by BertP on 8/16/2023 in #general

I seem to have some zombie runs

to clarify; no sleep or suspends. and these symptoms appeared after I added a shared directory + exponential backoff on the two scripts inside the for loop

24 replies

WWindmill

•Created by BertP on 8/16/2023 in #general

I seem to have some zombie runs

24 replies

WWindmill

•Created by BertP on 8/16/2023 in #general

I seem to have some zombie runs

script/flow data is not sensitive, names are just random words thrown together

24 replies

WWindmill

•Created by BertP on 8/16/2023 in #general

I seem to have some zombie runs

1 of 3 workers had these lines in their log

24 replies

WWindmill

•Created by BertP on 8/16/2023 in #general

I seem to have some zombie runs

this flow is ported through 2 months of upgrades, i see schedules now also have a path. maybe that's related

24 replies

WWindmill

•Created by BertP on 8/16/2023 in #general

I seem to have some zombie runs

the flow has a shared directory activated

24 replies

WWindmill

•Created by BertP on 8/16/2023 in #general

I seem to have some zombie runs

every 5 minutes a new zombie spawns, and this seems to be the related message

24 replies

WWindmill

•Created by BertP on 8/16/2023 in #general

I seem to have some zombie runs

2023-08-16T12:45:00.908654Z  INFO windmill_worker::worker: fetched job 0189fe5c-2caa-1bfb-be33-4dc2b7c0f50d, root job: none worker=wk-b660936c0a6c-MY9lW workspace_id=e-power-nieuwerkerken id=0189fe5c-2caa-1bfb-be33-4dc2b7c0f50d root_id=none

thread 'tokio-runtime-worker' panicked at 'could not create job dir: Os { code: 17, kind: AlreadyExists, message: "File exists" }', /windmill/windmill-worker/src/worker.rs:689:26

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Error: task 50 panicked

2023-08-16T12:45:01.692046Z  INFO windmill: Connecting to database...

2023-08-16T12:45:01.737229Z  INFO windmill: Database connected

2023-08-16T12:45:01.745235Z  INFO windmill: 

##############################

Windmill Community Edition v1.148.0-7-g0af264f6

##############################

2023-08-16T12:45:00.908654Z  INFO windmill_worker::worker: fetched job 0189fe5c-2caa-1bfb-be33-4dc2b7c0f50d, root job: none worker=wk-b660936c0a6c-MY9lW workspace_id=e-power-nieuwerkerken id=0189fe5c-2caa-1bfb-be33-4dc2b7c0f50d root_id=none

thread 'tokio-runtime-worker' panicked at 'could not create job dir: Os { code: 17, kind: AlreadyExists, message: "File exists" }', /windmill/windmill-worker/src/worker.rs:689:26

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Error: task 50 panicked

2023-08-16T12:45:01.692046Z  INFO windmill: Connecting to database...

2023-08-16T12:45:01.737229Z  INFO windmill: Database connected

2023-08-16T12:45:01.745235Z  INFO windmill: 

##############################

Windmill Community Edition v1.148.0-7-g0af264f6

##############################

24 replies