zonai ping

zonai ping

Starts each compiled worker in .zonai/executables/, asks it to answer, reports the result, and kills it again. The server does not need to be running, and nothing listens on a port.

Ping extension succeeded
Ping rules succeeded
Ping operation succeeded
Ping config succeeded
Ping cron succeeded
Ping rate limit succeeded

Six workers are checked, in that order: extensions, rules, operations, config, crons and rate limits. Each is spawned, pinged and shut down before the next one starts, so a failure names the worker rather than leaving you to guess from a stack trace.

What it is for#

zonai serve compiles workers and then starts serving, which means a worker that cannot start looks like a server problem. ping separates the two questions: it exercises the IPC handshake — spawn, send, receive, exit — and nothing else.

Reach for it when:

• a worker was rebuilt and you want to know it runs before a request depends on it;
• serve fails in a way that does not say which piece is broken;
• a deploy target should be checked without exposing a port.

Ops and rules are pinged here even though requests do not use them. On the default path they are compiled into the project-linked binary and called in-process; the .exe files still exist for compatibility, for ZONAI_FORCE_WORKERS=1, and for this command. See Workers.

Options#

A worker that cannot be reached prints Ping <name> failed and the command moves on to the next one.

A failed ping does not change the exit code — ping exits 0 whether every worker answered or none did, so it is a diagnostic to read rather than a gate to script. (--help exits 1.) If you need a CI check, assert on the output.

Related#

• Workers — what each of these six processes does.
• zonai serve — the command that compiles them and serves requests.