-
Notifications
You must be signed in to change notification settings - Fork 2
Description
The system appears to crash when running under the split process. It also produces some unclear system behavior when doing so.
According to system logs the process dies within 1 hour of startup with the last log entries being bade within 60 minutes of initial launch (11:35am). However some individual logs do appear to be timestamped well after the crash using a user-recorded or metadata time of: '2025-09-05T15:35:18.488Z' Moreover, after the last recorded entry the logfiles for processes 9001 and 2 begin showing entries of the following form:
INFO:aiohttp.access:127.0.0.1 [05/Sep/2025:10:34:48 -0500] "GET /wsapi/in/ HTTP/1.1" 101 0 "-" "Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gec
ko) Chrome/139.0.0.0 Safari/537.36"
which is followed by repeated entries of the form:
ws connection closed for reason 1006
We are done passing events through the pipeline.
These entries are paired with system recorded logfiles which contain only the following entry:
[Empty log file -- no events captured]
No other errors arise in the logs.
Clearly the system is either timing out or facing some other limit that is not being addressed. This calls for a long-term test.