jihoson/The-Ouroboros
0
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

bug: live runtime exits shortly after startup during #409 monitor #412

New Issue
Closed
opened 2026-03-04 10:21:51 +09:00 by agentson · 0 comments
agentson commented 2026-03-04 10:21:51 +09:00
Collaborator
Copy Link

Summary

  • During post-merge monitoring prep for #409/#318/#325, runtime restart succeeded initially but app process exited shortly after startup.

Observed At

  • 2026-03-04 10:19 KST (2026-03-04 01:19 UTC)

Evidence

  • run log: data/overnight/run_20260304_101925.log
  • watchdog log: data/overnight/watchdog_20260304_101925.log
  • pgrep -af "[s]rc.main --mode=live" returned no process after startup

Relevant excerpts:

  • app pid allocated: 3576017
  • startup lines present through Startup sync: US_NASDAQ/KTB recorded as open position (qty=23)
  • no subsequent cycle logs and process disappeared

Impact

  • 24h runtime monitoring for #409/#318/#325 cannot proceed reliably because live process is not staying up.

Related

Next Actions

  1. Investigate why process exits after startup sync (app crash vs watchdog/session handling).
  2. Stabilize live process lifecycle, then re-run 24h monitor.
## Summary - During post-merge monitoring prep for #409/#318/#325, runtime restart succeeded initially but app process exited shortly after startup. ## Observed At - 2026-03-04 10:19 KST (2026-03-04 01:19 UTC) ## Evidence - run log: `data/overnight/run_20260304_101925.log` - watchdog log: `data/overnight/watchdog_20260304_101925.log` - `pgrep -af "[s]rc.main --mode=live"` returned no process after startup Relevant excerpts: - app pid allocated: `3576017` - startup lines present through `Startup sync: US_NASDAQ/KTB recorded as open position (qty=23)` - no subsequent cycle logs and process disappeared ## Impact - 24h runtime monitoring for #409/#318/#325 cannot proceed reliably because live process is not staying up. ## Related - #409 - #318 - #325 ## Next Actions 1. Investigate why process exits after startup sync (app crash vs watchdog/session handling). 2. Stabilize live process lifecycle, then re-run 24h monitor.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agentson jihoson
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: jihoson/The-Ouroboros#412
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?