hanche@imf.unit.no (Harald Hanche-Olsen) (03/01/91)
Has anyone ever seen tracebacks like this one: Process 383 (parent 288, group 0) Time 91/02/28.19:09(MET) Program /etc/inetd Status 03010002: process had a fatal error (process manager/process manager) In routine "/sys/node_data.a0b0/systmp/global_readonly" offset 363A Called from "pgm_$exec_uid_pn" line 1450 Called from "pgm_$exec_xoid_pn" line 1287 Called from "execve" line 224 Called from "execv" line 146 Called from "main" line 382 Called from "unix_$main" line 114 Called from "<apollo_c_startup>" line 31999 Called from "PM_$CALL" line 176 Called from "pgm_$load_run" line 903 Called from "pgm_$invoke_uid_pn" line 1124 This is the result of my trying to telnet, rsh or rlogin to a SR10.3 DN3000 (they all leave a tracebcak identical to the above). Interestingly, telnet to the node opens a connection (accepting the connection is done by the primordial inetd, right?) and the connection just stays open with nothing happening on it. I have reason (empirically) to believe that this is related to the fact that someone is presently logged in on the node and has oodles of X clients displaying there. And he reports no problems! When I first saw this problem, I believed it was related to my not-so-successful attempts at running X11R4 on it. But now it running vanilla HPollo-supplied software, so that is not the explanation. So do we have another O/S bug here? I love that status code! So informative... But in that other context (running X11R4), when this happened to a child of a process that duly logged everything that happened, a signal 11 (segmentation violation) was reported. - Harald Hanche-Olsen <hanche@imf.unit.no> Division of Mathematical Sciences The Norwegian Institute of Technology N-7034 Trondheim, NORWAY
rees@pisa.citi.umich.edu (Jim Rees) (03/03/91)
In article <HANCHE.91Feb28201637@hufsa.imf.unit.no>, hanche@imf.unit.no (Harald Hanche-Olsen) writes:
Status 03010002: process had a fatal error (process manager/process manager)
In routine "/sys/node_data.a0b0/systmp/global_readonly" offset 363A
Called from "pgm_$exec_uid_pn" line 1450
Called from "pgm_$exec_xoid_pn" line 1287
This happens when an exec fails after the process is unrecoverably committed
to running the new program. Since it can't get back to the original program
at this point, the process just exits. This "shouldn't happen" (be glad
it's not a kernel panic).
I love that status code! So informative...
Me too. Sounds like what you'd say when your three-year-old accidentally
pees on the carpet.