Re: [dtn-users] Problem DTN2 daemon

Nik Ansell <nikansell00@gmail.com> Mon, 04 January 2016 05:03 UTC

Return-Path: <nikansell00@gmail.com>
X-Original-To: dtn-users@ietfa.amsl.com
Delivered-To: dtn-users@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE0E81B2AF6 for <dtn-users@ietfa.amsl.com>; Sun, 3 Jan 2016 21:03:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.251
X-Spam-Level:
X-Spam-Status: No, score=0.251 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gdJ7RJIVkvcx for <dtn-users@ietfa.amsl.com>; Sun, 3 Jan 2016 21:03:23 -0800 (PST)
Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36C451B2AF7 for <dtn-users@ietfa.amsl.com>; Sun, 3 Jan 2016 21:03:21 -0800 (PST)
Received: by mail-wm0-f54.google.com with SMTP id f206so159803926wmf.0 for <dtn-users@ietfa.amsl.com>; Sun, 03 Jan 2016 21:03:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=iItEqOQMKk7fFziPgBf84BNfut1bctJvmVobItuWRlw=; b=P02MfWVktV8W9l6mVjWFBgoF21fZXYlF0fpbovkOIyiaP48gtW37hqSMf83+oasg0W 2lbmoMGRrKoxEMAi9BinrBJkXIdCS28nwiJ2EpEgoqEwwBqhq8kdFbMbAmT+6zBFH+Zc 4MPDYsfU5DHTUv6RxGcxKYv024VdAymbnX8W7eC4/Iiuo3Fznp4jQ7cVx1ppsWnzQhA9 uAY5JRdSfalm1TFumwlq8j4dWyaLncyBuI3yOdU0PruBSlWiyS8yJlsVwjR75PgqA2yQ t1hWkFvJOdw4AfALnU3+AoP0P0DT13DXy/UCIs1qzKWQ59GnYwBKn6qWv1b3Y+bpM4Yf FkVg==
MIME-Version: 1.0
X-Received: by 10.195.18.100 with SMTP id gl4mr35691377wjd.177.1451883799209; Sun, 03 Jan 2016 21:03:19 -0800 (PST)
Received: by 10.194.92.164 with HTTP; Sun, 3 Jan 2016 21:03:19 -0800 (PST)
In-Reply-To: <CAKvrc=1DB_4ajY1YNPSvmW6F2Rvp3k5a_LpxXUtgi2ctMm5UrQ@mail.gmail.com>
References: <CAKvrc=1DB_4ajY1YNPSvmW6F2Rvp3k5a_LpxXUtgi2ctMm5UrQ@mail.gmail.com>
Date: Mon, 04 Jan 2016 09:03:19 +0400
Message-ID: <CAKLzrV94AfuZ5-wrN9gqOtJqLuEF+k3-eAU6Zpp62tJgKHdSvQ@mail.gmail.com>
From: Nik Ansell <nikansell00@gmail.com>
To: kevin prima <sir.kevinprima@gmail.com>
Content-Type: multipart/alternative; boundary="001a11c296081b6b0505287b0a50"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtn-users/PJcdtBt3_UiX_ZEKxDIWRH-feC0>
Cc: dtn-users@ietfa.amsl.com
Subject: Re: [dtn-users] Problem DTN2 daemon
X-BeenThere: dtn-users@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: nikansell00@gmail.com
List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Users." <dtn-users.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/dtn-users>, <mailto:dtn-users-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn-users/>
List-Post: <mailto:dtn-users@irtf.org>
List-Help: <mailto:dtn-users-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/dtn-users>, <mailto:dtn-users-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jan 2016 05:03:25 -0000

Hi Kevin,

I am pretty new to DTN2, so not really the best person to give advice.
However, I did come across a similar spin lock error during my recent
testing.
In my case, the spin lock error was a symptom of an unrelated problem i.e a
red herring, I ended up fixing my problem by updating my configs.
This view is also shared by the N4C project, who hid the spin lock error by
changing the log level to INFO/NOTICE.

http://www.n4c.eu/Download/8.4/n4c-wp8-006-M8.5-summer_test_2010_Slovenia_V06.pdf

Good luck fixing your problem.

Kind Regards,
Nik

On Thu, Dec 31, 2015 at 12:17 PM, kevin prima <sir.kevinprima@gmail.com>
wrote:

> Dear all,
>
> I want to run 5 DTN node in 2 hop topology scenario with DTLSR routing,
> source and destination node connected with dtn node 1,2,and 3 but couldn't
> reach each other.
> When I try to send ping packet use dtnping, sometimes it show error like
> this in node 1, node 2, and node 3:
>
> warning: Bundle::del_ref is waiting for spin lock held by (null), which
> has reached spin limit
> STACK TRACE: 0x76f51c84 0x3eda8 0x3ed00 0x59444
>
> The impact is node 1, 2 or 3 become unavailable. What should I do to fix
> this problem ?
>
> Thanks,
> Kevin
>
> _______________________________________________
> dtn-users mailing list
> dtn-users@irtf.org
> https://www.irtf.org/mailman/listinfo/dtn-users
>
>