Hi all,
re: Racket 6.5, prebuilt Linux x86_64 distribution
on Centos 6.8
Had a crash in one of my headless webserver/database applications. The
application itself is 100% Racket (no FFI libs), using the webserver
and db modules heavily. The Racket install is default with no added
packages.
The application has been in use for over a year with with no issues.
The server was restarted last on Dec 3, so at the time of the crash
the program had been running for ~37 days, though it was quiet through
much of the holidays.
The logs show business as usual up until UTC 21:55h on Jan 9.
In the stdout (normal log) I found this:
SIGSEGV SEGV_ACCERR SI_CODE 2 fault on 0x7f20fbd8fd30
And in the stderr (error log), which normally always is empty, I found
this:
mprotect failed: 7f20f4eb8000, 16760832, 1, 12
mprotect failed: 7f20f8364000, 16777216, 1, 12
mprotect failed: 7f20fb86c000, 8388608, 1, 12
mprotect failed: 7f20fc988000, 4194304, 1, 12
mprotect failed: 7f20fcff8000, 2097152, 1, 12
Seg fault (internal error during gc) at 0x7f20fbd8fd30
That's all.
The server administrator restarted the application daemon (not the
server) about a 1/2 hour later. He saw nothing else wrong [with the
DBMS, HTTP server, etc.] and everything appeared to return to normal
as soon as he restarted the application.
I did check the server's update logs, but there had been no updates
installed in the days prior to the crash. And no restarts for 37
days.
So I'm stumped. I can see the seg fault occurred in GC, but unless
somebody can say definitively that it looks like a bug in Racket, I
have to assume my code is somehow at fault.
Since this problem has never occurred previously, I haven't a clue as
to how to troubleshoot it or prevent it from happening again. The
deployed application was not compiled with debug information.
Anybody?
Thanks,
George
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
