[Nfd-dev] nfd-start yield nothing after fresh installation

[Junxiao Shi]

There's no obvious error in this output.
If ndn-cxx and NFD are compiled at the same time (either from a newly
cloned repository, or ./waf distclean has been execute before compiling
NFD), this shall eliminate library ABI mismatch problem.
On Jun 3, 2016 11:50 AM, "Thiago Teixeira" <tteixeira at engin.umass.edu>
wrote:

Hi Junxiao,



Thanks for your email. Please find the output below. Is that what I should
expect?



$ which nfd

/usr/local/bin/nfd

$ ldd /usr/local/bin/nfd

                linux-vdso.so.1 =>  (0x00007fff62dfe000)

                libboost_system.so.1.54.0 =>
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.54.0 (0x00007f36cb9e9000)

                libboost_program_options.so.1.54.0 =>
/usr/lib/x86_64-linux-gnu/libboost_program_options.so.1.54.0
(0x00007f36cb77b000)

                libboost_thread.so.1.54.0 =>
/usr/lib/x86_64-linux-gnu/libboost_thread.so.1.54.0 (0x00007f36cb564000)

                libboost_log.so.1.54.0 =>
/usr/lib/x86_64-linux-gnu/libboost_log.so.1.54.0 (0x00007f36cb2a0000)

                libndn-cxx.so.0.4.1 => /usr/local/lib/libndn-cxx.so.0.4.1
(0x00007f36cad97000)

                libboost_filesystem.so.1.54.0 =>
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.54.0 (0x00007f36cab80000)

                libcrypto++.so.9 => /usr/lib/libcrypto++.so.9
(0x00007f36ca4b5000)

                libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f36ca297000)

                libpcap.so.0.8 => /usr/lib/x86_64-linux-gnu/libpcap.so.0.8
(0x00007f36ca058000)

                libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007f36c9d54000)

                libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6
(0x00007f36c9a4e000)

                libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x00007f36c9837000)

                libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
(0x00007f36c9472000)

                librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1
(0x00007f36c926a000)

                /lib64/ld-linux-x86-64.so.2 (0x00007f36cbbfb000)

                libboost_regex.so.1.54.0 =>
/usr/lib/x86_64-linux-gnu/libboost_regex.so.1.54.0 (0x00007f36c8f62000)

                libboost_chrono.so.1.54.0 =>
/usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.54.0 (0x00007f36c8d5b000)

                libboost_random.so.1.54.0 =>
/usr/lib/x86_64-linux-gnu/libboost_random.so.1.54.0 (0x00007f36c8b57000)

                libsqlite3.so.0 =>
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007f36c889e000)

                libicuuc.so.52 => /usr/lib/x86_64-linux-gnu/libicuuc.so.52
(0x00007f36c8525000)

                libicui18n.so.52 =>
/usr/lib/x86_64-linux-gnu/libicui18n.so.52 (0x00007f36c811d000)

                libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
(0x00007f36c7f19000)

                libicudata.so.52 =>
/usr/lib/x86_64-linux-gnu/libicudata.so.52 (0x00007f36c66ab000)



Rgds,

Thiago



*From:* Junxiao Shi [mailto:shijunxiao at email.arizona.edu]
*Sent:* Friday, June 3, 2016 10:01 AM
*To:* Thiago Teixeira <tteixeira at engin.umass.edu>; nfd-dev at lists.cs.ucla.edu
*Subject:* RE: [Nfd-dev] nfd-start yield nothing after fresh installation



Hi Thiago



I suspect there’s a library ABI mismatch. It’s most likely to happen if
ndn-cxx and NFD are not installed together.

You may check this possibility with:

1.       find where is your NFD binary with which nfd

2.       check whether libraries are linked correctly with ldd /usr/bin/nfd
(use the nfd binary path found in step1)



Yours, Junxiao



*From: *Thiago Teixeira <tteixeira at engin.umass.edu>
*Sent: *Thursday, June 2, 2016 03:30
*To: *nfd-dev at lists.cs.ucla.edu
*Subject: *[Nfd-dev] nfd-start yield nothing after fresh installation



Hi all,



I installed the NFD 0.4.1-21 binaries on two Ubuntu 14-64 bits and
everything went well. The two machines are on the same subnet 10.10.1.0/24.

When I run *$ nfd-start* I get the following message: *NFD is already
running…*



So I run *$ nfdc register /ndn udp://10.10.1.1 <http://10.10.1.1>* and I
should get the *Successful…* message, but I get nothing.

*nfd-status* yields nothing too.

I tried *nfd-stop* > *nfd-start* and nothing shows up.



I searched on the mailing list and couldn’t find anything.



Do you have any suggestions or tests to do?



Thanks,

Thiago



PS: There’s a typo in the building documentation instructions. It should be
./waf doxygen instead of doxgyen

http://named-data.net/doc/NFD/current/INSTALL.html#building-documentation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160603/78d088d5/attachment.html>