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

[Teng Liang]

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
timeout from /1.0.0.2: seq=17432959044867093349
timeout from /1.0.0.2: seq=17432959044867093350
timeout from /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
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> 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> 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
> 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/20151112/9ba696a6/attachment.html>