[🐛 BUG]: debug and max_jobs does not work

[wapmorgan]

No duplicates 🥲.

• I have searched for a similar issue in our bug tracker and didn't find any solutions.

What happened?

A bug happened!

http.pool.debug and http.pool.max_jobs are buggy.

Version (rr --version)

2023.1.0 / 2023.1.5 / 2023.2.1

How to reproduce the issue?

Dockerfile
FROM ghcr.io/roadrunner-server/roadrunner:2023.1.0 AS roadrunner
.rr.yaml

version: '3'
server:
  command: "php web/api.php"

http:
  address: 0.0.0.0:8080
  pool:
    debug: ${DEBUG}
    num_workers: ${NUM_WORKERS}
    max_jobs: ${NUM_REQUESTS_BEFORE_RESET}

rpc:
  listen: tcp://127.0.0.1:6001

server command

• does not matter.

Relevant log output

when debug=true

[INFO] RoadRunner server started; version: 2023.1.0, buildtime: 2023-04-13T16:47:17+0000
2023-08-06T18:07:37+0000        DEBUG   http            http server was started {"address": "0.0.0.0:8080"}
2023-08-06T18:07:47+0000        DEBUG   server          worker is allocated     {"pid": 19, "internal_event_name": "EventWorkerConstruct"}
2023-08-06T18:07:47+0000        DEBUG   server          sending stop request to the worker      {"pid": 19}
2023-08-06T18:07:57+0000        WARN    server          worker doesn't respond on stop command, killing process {"PID": 19}
2023-08-06T18:07:57+0000        DEBUG   server          debug mode: worker stopped      {"reason": "worker error", "pid": 19, "internal_event_name": "EventWorkerError", "error": "process_stop: Network"}
2023-08-06T18:07:57+0000        ERROR   http            execute {"start": "2023-08-06T18:07:47+0000", "elapsed": "10.015244843s", "error": "process_stop: Network"}
2023-08-06T18:07:57+0000        INFO    http            http log        {"status": 500, "method": "GET", "URI": "/", "remote_address": "172.17.0.1:45720", "read_bytes": 0, "write_bytes": 0, "start": "2023-08-06T18:07:47+0000", "elapsed": "10.015352563s"}

when debug=false and max_jobs=1

2023-08-06T18:15:48+0000        DEBUG   server          sending stop request to the worker      {"pid": 32}

2023-08-06T18:15:58+0000        WARN    server          worker doesn't respond on stop command, killing process {"PID": 32}
2023-08-06T18:15:58+0000        DEBUG   server          worker release  {"error": "process_stop: Network"}
2023-08-06T18:15:58+0000        INFO    http            http log        {"status": 200, "method": "GET", "URI": "/", "remote_address": "172.17.0.1:57640", "read_bytes": 0, "write_bytes": 17, "start": "2023-08-06T18:15:48+0000", "elapsed": "10.002420988s"}
2023-08-06T18:15:58+0000        DEBUG   server          worker stopped  {"internal_event_name": "EventWorkerWaitExit", "error": "signal: killed\nprocess_wait: signal: killed"}
2023-08-06T18:15:58+0000        DEBUG   server          worker is allocated     {"pid": 33, "internal_event_name": "EventWorkerConstruct"}

[rustatian]

Hey @wapmorgan 👋🏻
I double-checked this case on the latest v2023.2.1 release. Looks like the problem is somewhere on your end. Double check your worker, docker configuration. Looks like the process can't be allocated on the second run for some reason. The issue is not locked.

[wapmorgan]

Problem is in sample #145