Received: by 10.50.42.225 with SMTP id r1mr1545348igl.1.1351118669114;
        Wed, 24 Oct 2012 15:44:29 -0700 (PDT)
X-BeenThere: serval-project-developers@googlegroups.com
Received: by 10.42.200.69 with SMTP id ev5ls5449046icb.5.gmail; Wed, 24 Oct
 2012 15:44:28 -0700 (PDT)
Received: by 10.50.159.201 with SMTP id xe9mr2615164igb.0.1351118668483;
        Wed, 24 Oct 2012 15:44:28 -0700 (PDT)
Received: by 10.50.159.201 with SMTP id xe9mr2615163igb.0.1351118668471;
        Wed, 24 Oct 2012 15:44:28 -0700 (PDT)
Return-Path: <kimhaw...@gmail.com>
Received: from mail-ob0-f181.google.com (mail-ob0-f181.google.com [209.85.214.181])
        by gmr-mx.google.com with ESMTPS id dx8si577962igc.1.2012.10.24.15.44.28
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 24 Oct 2012 15:44:28 -0700 (PDT)
Received-SPF: pass (google.com: domain of kimhaw...@gmail.com designates 209.85.214.181 as permitted sender) client-ip=209.85.214.181;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of kimhaw...@gmail.com designates 209.85.214.181 as permitted sender) smtp.mail=kimhaw...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-ob0-f181.google.com with SMTP id un3so1070270obb.26
        for <serval-project-developers@googlegroups.com>; Wed, 24 Oct 2012 15:44:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=t54rf7pFXbbm1Mqm4UuDjV2j2mlx6jSMcVOAcRnEusY=;
        b=Yo/Uas/VmWX09Z9pk7OQ9rJldo7BA0gBLASXQeWF3Tm2AsF/LVNvFlOtnv78wpzTtg
         MZK9RtYxevoPPTQBf/ro9+N7CX6C3reIEtfndQ77j6OOkqaJMKLyJWaBSxFDO8zHm1XA
         3V/n4D32sTb2hGnMSdt8oI6saMvs5fQSW3E+3VgZQRCqm/JGq39j0yhwYlWGRmhEdDKl
         6afQOWV4XFXaevRfPce/ozOiFsoTuAGL8Km66gKN7p94Af3ubQTeDtkR8GOf47LmHn/S
         uTHzSi8BMpdqCwq3WZXU5GcsJUEGFo330tHrcroD5iMVG/1N7rjushnlcgiyejXP/waN
         yymQ==
MIME-Version: 1.0
Received: by 10.182.192.74 with SMTP id he10mr14315127obc.87.1351118668175;
 Wed, 24 Oct 2012 15:44:28 -0700 (PDT)
Received: by 10.76.8.97 with HTTP; Wed, 24 Oct 2012 15:44:27 -0700 (PDT)
In-Reply-To: <CAJZNfZrJrYr6+2H=NekebuV7D-VqssdJnk82799eV12GODQ...@mail.gmail.com>
References: <40b3e2a4-9a8d-4e23-b210-760288015e96@googlegroups.com>
	<CAAjnzmBvkDM8-f=Q1WZcb5wCL5YvDdeSmBXOcfgDVbe6Y5b...@mail.gmail.com>
	<CAJZNfZoEmnsVwgQDRqDYGe+ozadF+_LvWSyFRRHyS6apo_F...@mail.gmail.com>
	<CAAjnzmDtDReUTWu2rhA+wMeBG-mo4iPoFfHa1B6JSqK8ErB...@mail.gmail.com>
	<CAJZNfZovscYhYKy42B4LqpTGQg__0=x4ikq3x80-gZyXPa8...@mail.gmail.com>
	<CA+_T8-CJZxH=CJs=Tk7v2P-qcVCOP0EinM=D7WhG2B6NOW5...@mail.gmail.com>
	<CAJZNfZo24UFtr8Q6OvdN4m=cF+3Ti=7kJhyUonGBctzHoQe...@mail.gmail.com>
	<CA+_T8-BkgRPmh9mHEoAKsvKctqer0B9THO8-VVsfLmBaiiX...@mail.gmail.com>
	<CA+_T8-AtDPVV+VvVU4Y-dwUr2DYeD9CR+Cfj2VavgJt7igV...@mail.gmail.com>
	<CAJZNfZp_H062Y3FxW-fVks7kwmXq+=A5GHEcAHemgND8cQy...@mail.gmail.com>
	<CAJZNfZqD71F5C1LuRxPq=y7V=WEdVsXjJJpPgyeuZQsCcRe...@mail.gmail.com>
	<CAJZNfZqqMji7W_Jx6Oj_Yiez5Q0m_m4M1wG_WF4BsNC2a-E...@mail.gmail.com>
	<CA+_T8-CCWveyvM_ZDRR30cqAvAOoOcFkryaWD1aXgvANoMA...@mail.gmail.com>
	<CAAjnzmBLKN_UR7F=snQ3aESDE=81ONvHcHFRSFAeePBTHVc...@mail.gmail.com>
	<CAJZNfZrJrYr6+2H=NekebuV7D-VqssdJnk82799eV12GODQ...@mail.gmail.com>
Date: Thu, 25 Oct 2012 09:14:27 +1030
Message-ID: <CAAY3yb2=KPSfb5pdVtuGUyX5P+QjTAkU-GoXL7hPU0x_TRb...@mail.gmail.com>
Subject: Re: [serval-project-dev] Using an existing mesh network to extend the
 range of serval
From: Kim Hawtin <kimhaw...@gmail.com>
To: serval-project-developers@googlegroups.com
Content-Type: text/plain; charset=UTF-8

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