On Thu, Oct 25, 2012 at 12:03 AM, Jonathan Lahav <j.la...@gmail.com> wrote:INFO: rhizome_http.c:157:rhizome_http_server_start() RHIZOME HTTP
>> servald start foreground
> I'm a bit confused. Yesterday I ran servald on the routers, and checked with
> htop that servald is indeed running in the background. Today when I ran it
> like that, in foreground, I saw that it segfaults right away and quits. The
> output is attached in a text file. I don't know what happened, maybe
> yesterday I was dreaming or something, or maybe I changed something since
SERVER, START port=4110 fd=9
INFO: dna_helper.c:156:dna_helper_start() DNAHELPER none configured
ERROR: server.c:378:crash_handler() Caught SIGSEGV (11) Segmentation fault
INFO: performance_timing.c:178:dump_stack() overlay_interface_discover
INFO: performance_timing.c:178:dump_stack() parseCommandLine
ERROR: log.c:436:log_backtrace() mkstemp: Invalid argument [errno=22]
INFO: server.c:402:crash_handler() Re-sending signal 11 to self
> That segfault is funny. They don't come and go without recompilation in myWhat user is the process running as?
> experience so it's most likely that I somehow overlooked it yesterday, and
> that is why it didn't work.
If it is not root, it might barf if trying to open a socket to listen
SIG 11's are not exactly common?
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.