Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Serval Project Developers
Home
+ new post
About this group
Join this group
Message from discussion Using an existing mesh network to extend the range of serval
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Kim Hawtin  
View profile  
 More options Oct 24 2012, 6:44 pm
From: Kim Hawtin <kimhaw...@gmail.com>
Date: Thu, 25 Oct 2012 09:14:27 +1030
Local: Wed, Oct 24 2012 6:44 pm
Subject: Re: [serval-project-dev] Using an existing mesh network to extend the range of serval
Print | View thread | Show original | Report this message | Find messages by this author

On Thu, Oct 25, 2012 at 12:03 AM, Jonathan Lahav <j.la...@gmail.com> wrote:
>> 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
> then.

INFO:  rhizome_http.c:157:rhizome_http_server_start()  RHIZOME HTTP
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
Segmentation fault

> That segfault is funny. They don't come and go without recompilation in my
> experience so it's most likely that I somehow overlooked it yesterday, and
> that is why it didn't work.

What user is the process running as?

If it is not root, it might barf if trying to open a socket to listen
on below 1024 as a non-root users.

SIG 11's are not exactly common?
Does mkstemp() have permission to write to disk in the expected
location? Is there enough space?
Is mkstemp() expecting an argument with a null terminated string?

cheers,

Kim
--
"Art without engineering is dreaming; engineering without art is
calculating."  --SKR


 
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.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google