Skip to content

Panick on Result::unwarp() in src/lib.rs line 192:55 #7

@wmader23

Description

@wmader23

Always after a couple of hours of executing of modbus-proxy-rs (docker compose deployment) the service panics with

modbus-proxy | [2025-10-28T06:31:39Z INFO modbus_proxy_rs] modbus reply 192.168.178.61:502: 11 bytes
modbus-proxy | [2025-10-28T06:31:39Z DEBUG modbus_proxy_rs] modbus reply 192.168.178.61:502: [37, 102, 0, 0, 0, 5, 1, 3, 2, 255, 37]
modbus-proxy | thread 'main' panicked at 'called Result::unwrap() on an Err value: Os { code: 24, kind: Uncategorized, message: "No file descriptors available" }', /modbus-proxy-rs/src/lib.rs:192:55
modbus-proxy | stack backtrace:
modbus-proxy | 0: 0x7f016cae4c12 -
modbus-proxy | 1: 0x7f016ca883ec -
modbus-proxy | 2: 0x7f016cae37c4 -
modbus-proxy | 3: 0x7f016cae3e09 -
modbus-proxy | 4: 0x7f016cae3443 -
modbus-proxy | 5: 0x7f016caffd53 -
modbus-proxy | 6: 0x7f016caffcd6 -
modbus-proxy | 7: 0x7f016caffc92 -
modbus-proxy | 8: 0x7f016ca37e90 -
modbus-proxy | 9: 0x7f016ca38172 -
modbus-proxy | 10: 0x7f016ca41f78 -
modbus-proxy | 11: 0x7f016ca49bd4 -
modbus-proxy | 12: 0x7f016ca3cfb8 -
modbus-proxy | 13: 0x7f016ca4c6ae -

The problem sounds to me like the OS ran out of file descriptors. I wonder if the problem is in the code, in my setup, or in the docker image? I would be happy about help and would contribute to a solution.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions