.. I should add that I have often completely restarted the go program during testing here, so I don't think it could be a case of some long-term 'leak' in the go tool's own code since it's been relaunched and doesn't have any big 'state' to restore or anything.
On Sat, Mar 2, 2024 at 7:57 PM Russtopia <rma...@gmail.com> wrote: > It no longer does.. so it suggests to me there's something external that > has changed, but I have no clue as to what that might be -- as the process > being started by my go tool will run just fine from a shell. And, it *does* > run fine on my laptop (which granted is beefier, but again this server was > running the tool just fine for years and I haven't done any big upgrades, > but it *is* possible some minor underlying package update has severely > changed the environment somehow). Unfortunately I don't have a system-wide > 'snapshot' I can revert to. > > Perhaps this will end up being a question of Linux diagnostics more than > Go but I haven't yet seen any way to tell *why* the process is being > killed, whether it be due to some bug tickled by Go's exec or something > else. The oom_reaper doesn't say a thing to system logs; I don't see my > free RAM or swap suddenly drop.. I've even checked my server for rootkits > out of paranoia :). Everything else on the system is just fine, I just > cannot seem to run these scripts any more when launched from my go program > (again, even a 'do-nothing' script that just sleeps a few times, then > completes with exit status 0, no longer works -- it just gets 'killed'). > > > On Sat, Mar 2, 2024 at 7:39 PM Robert Engels <reng...@ix.netcom.com> > wrote: > >> Please clarify - does it work using the older versions of Go? >> >> On Mar 2, 2024, at 12:53 PM, Russtopia <rma...@gmail.com> wrote: >> >> >> I have tried rebuilding with go1.18.6, go1.15.15 with no difference. >> >> On Sat, Mar 2, 2024 at 6:23 PM Robert Engels <reng...@ix.netcom.com> >> wrote: >> >>> I would be also try reverting the Go version and ensure that it >>> continues to work. Other system libraries may have been updated. >>> >>> > On Mar 2, 2024, at 12:05 PM, Ian Lance Taylor <i...@golang.org> wrote: >>> > >>> > On Sat, Mar 2, 2024 at 9:59 AM Russtopia <rma...@gmail.com> wrote: >>> >> >>> >> Symptom: mysterious "signal: killed" occurrences with processes >>> spawned from Go via exec.Cmd.Start()/Wait() >>> > >>> > The first step is to tell us the exact and complete error that you >>> > see. "signal: killed" can have different causes, and the rest of the >>> > information should help determine what is causing this one. >>> > >>> > Ian >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups "golang-nuts" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> an email to golang-nuts+unsubscr...@googlegroups.com. >>> > To view this discussion on the web visit >>> https://groups.google.com/d/msgid/golang-nuts/CAOyqgcXR6hBSnGLjehwng%2BXp4QQ8ZznramEAZTmD%3D6tVwFirTg%40mail.gmail.com >>> . >>> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAN4yCu_ZdjevdFUiMbCtmHk44rEi-zHeye4L-mTe11TT8G2eNg%40mail.gmail.com.
