[Mini-NDN] [mini-ndn] Failed to read configuration file

[Ashlesh Gawande (agawande)]

Hi


Seems like either NFD is not running or NFD got killed somehow or client.conf cannot find NFD sock hence the error:

ERROR: error while connecting to the forwarder (No such file or directory).


I am guessing it is the second case since pingall experiment worked. Was the ndnping command the first one you ran after mini-NDN command line came up?

1) ndnping will not work if you don't have ndnpingserver running on a node (mininet>a ndnpingserver /ndn/edu/a &, don't forget the & to run it in background other wise you can no longer use the command line and would have to press control C to exit). Then you can ping it from other nodes as long as there is route to that (which NLSR should take care of).

2) NFD gets killed if you press Control-C on mininet command line (For example if you ran: mininet> a ndnpingserver /ndn/edu/a and then pressed Control-C, NFD on node a would get killed).

3) Radius and angle are to do with the hyperbolic (geometric) routing (--hr option). Normally mini-NDN uses link state routing and those options are

4) Instead of --pingall use --experiment=pingall

Thank you for notifying us, we will try to update the documentation soon.

Ashlesh
________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Teng Liang <philoliang2011 at gmail.com>
Sent: Thursday, November 12, 2015 7:16 PM
To: Vince Lehman (vslehman)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] [mini-ndn] Failed to read configuration file

Hi Vince,

Thanks for your help.

I tried again, following your instructions. As a result, there were no errors in log file, but ndnping didn't work. The results were either

mininet> a ndnping b
PING /1.0.0.2<http://1.0.0.2>
timeout from /1.0.0.2<http://1.0.0.2>: seq=17432959044867093349
timeout from /1.0.0.2<http://1.0.0.2>: seq=17432959044867093350
timeout from /1.0.0.2<http://1.0.0.2>: seq=17432959044867093351

or

mininet> a ndnping b
ERROR: error while receiving data from socket (End of file)
PING /1.0.0.2<http://1.0.0.2>
ERROR: error while connecting to the forwarder (No such file or directory)

The pingall experiment worked well.

For the topologies, docs/CONFIG.md doesn't explain parameters radius or angle for nodes. In INSALL.md, the verification command doesn't work, as there is no --pingall option for minindn.

Teng



On Mon, Nov 9, 2015 at 1:09 PM, Vince Lehman (vslehman) <vslehman at memphis.edu<mailto:vslehman at memphis.edu>> wrote:
Hi Teng,

Can you first confirm that the file ‘/tmp/a/a.conf’ exists? If so, make sure there are no instances of NFD currently running, remove the folders for each node in the /tmp directory, and then try starting Mini-NDN again.

Another question is how are topologies files generated, manually or by some scripts from minindn? What's the format?

The topologies can be written by hand or by using the GUI. The format is described in docs/CONFIG.md (https://github.com/named-data/mini-ndn/blob/master/docs/CONFIG.md), and the GUI is explained in docs/GUI.md (https://github.com/named-data/mini-ndn/blob/master/docs/GUI.md).

--
Vince Lehman

On Nov 9, 2015, at 1:55 PM, Teng Liang <philoliang2011 at gmail.com<mailto:philoliang2011 at gmail.com>> wrote:

Hi folks,

I failed to run the latest version of mini-ndn (on Linux) with the following errors.

First, mini-ndn tried to copy the nfd configuration file from '/usr/local/etc/ndn/', but failed.

> cp: cannot stat `/usr/local/etc/ndn/nfd.conf.sample': No such file or directory

My configuration files were in '/etc/ndn/'; I tried to copy them to '/usr/local/etc/ndn/' and ran minindn again. Here are the error messages from a.log:

1446853834.224102 FATAL: [NFD] Failed to read configuration file: /tmp/a/a.conf [from ../core/config-file.cpp:94 in void nfd::ConfigFile::parse(const string&, bool)]
1446853889.262472 FATAL: [NFD] Failed to read configuration file: /tmp/a/a.conf [from ../core/config-file.cpp:94 in void nfd::ConfigFile::parse(const string&, bool)]
1446932899.171233 FATAL: [NFD] Socket file at /run/a.sock belongs to another NFD process [from ../daemon/face/unix-stream-channel.cpp:83 in void nfd::UnixStreamChannel::listen(const FaceCreatedCallback&, const ConnectFailedCallback&, int)]
1447003753.226606 FATAL: [NFD] Socket file at /run/a.sock belongs to another NFD process [from ../daemon/face/unix-stream-channel.cpp:83 in void nfd::UnixStreamChannel::listen(const FaceCreatedCallback&, const ConnectFailedCallback&, int)]
1447003833.855714 FATAL: [NFD] Socket file at /run/a.sock belongs to another NFD process [from ../daemon/face/unix-stream-channel.cpp:83 in void nfd::UnixStreamChannel::listen(const FaceCreatedCallback&, const ConnectFailedCallback&, int)]
1447005216.105377 FATAL: [NFD] Socket file at /run/a.sock belongs to another NFD process [from ../daemon/face/unix-stream-channel.cpp:83 in void nfd::UnixStreamChannel::listen(const FaceCreatedCallback&, const ConnectFailedCallback&, int)]

Another question is how are topologies files generated, manually or by some scripts from minindn? What's the format?

Thanks,

Teng
_______________________________________________
Mini-NDN mailing list
Mini-NDN at lists.cs.ucla.edu<mailto:Mini-NDN at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20151113/c5aa67c7/attachment.html>