@sjawhar/pi-legion 19.41.2 → 19.41.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/legion.js CHANGED
@@ -29931,7 +29931,7 @@ import { logger as logger3 } from "@oh-my-pi/pi-utils";
29931
29931
  // package.json
29932
29932
  var package_default = {
29933
29933
  name: "@sjawhar/pi-legion",
29934
- version: "19.41.2",
29934
+ version: "19.41.4",
29935
29935
  license: "Apache-2.0",
29936
29936
  type: "module",
29937
29937
  omp: {
@@ -68,8 +68,22 @@ heavy run goes where your deployment's instructions say.
68
68
  server is the roles container's launcher's job — it runs `legion-testpg ensure` before any role
69
69
  starts and again every 15 seconds — so wait about that interval and try again. Never start a
70
70
  server of your own beside it, and never reach for another DSN. Still refused after that wait:
71
- report it, with the error you got and the port you used, as a fault of the pod rather than of
72
- your change.
71
+ report it, with the error you got, the port you used and the server's log lines from the minute
72
+ it failed (next bullet), as a fault of the pod rather than of your change.
73
+ - The server's log is the read-only file `$LEGION_TEST_PG_LOG` names
74
+ (`tail -n 200 "$LEGION_TEST_PG_LOG"`). For every connect the server takes, the process it starts
75
+ for it writes a `connection received: host=127.0.0.1 port=<client port>` line, then
76
+ `connection ready` with the setup and fork times, and a `disconnection` line at the end. A
77
+ connect that failed with lines of its own failed in the server, and the log says why; one the
78
+ server could not start a process for leaves `could not fork new process for connection`
79
+ instead. A connect with neither line at the time it failed never reached the server: a burst of
80
+ more connects at once than the server's listen queue (about 940) is dropped before the server
81
+ sees it, and libpq reports such a connect as `server closed the connection unexpectedly` or
82
+ waits until its own timeout. Open the connections in smaller steps, or retry them. Your login
83
+ holds `pg_monitor`, so `pg_stat_activity` also shows the detail of connections under the other
84
+ logins of the server, such as the ones a suite creates. `LEGION_TEST_PG_LOG` unset: a server
85
+ you started yourself (next bullet) logs to `$LEGION_TESTPG_DIR/server.log`; with the DSN your
86
+ pod set and no such variable, your pod's image predates the log, so report without it.
73
87
  - `LEGION_TEST_PG_DSN` unset: your deployment has not turned the pod's server on, so no launcher
74
88
  is starting one and nothing will appear while you wait. With `legion-testpg` on `PATH`, start
75
89
  one yourself on the issue's volume: the directory it defaults to is a 1 MiB filesystem your
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/pi-legion",
3
- "version": "19.41.2",
3
+ "version": "19.41.4",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "omp": {