Task #4429
closed
nlsr: error while loading shared libraries: libChronoSync.so.0.4.0: cannot open shared object file: No such file or directory
0%
Description
Hi all,
As the title indicates, I met with the error when running nlsr.
Chronosync, ndn-cxx and NFD have all been installed. ndn-cxx and NFD can run normally.
***nlsr: error while loading shared libraries: libChronoSync.so.0.4.0: cannot open shared object file: No such file or directory
I could find libChronoSync.so.0.4.0 in /usr/local/lib/.
I'm not sure if manually exporting a path could help.
Thanks.
Updated by Pengyuan Zhou almost 7 years ago
Ashlesh Gawande wrote:
sudo ldconfig
Hi Ashlesh,
Thank you so much. It works.
Although I find it kinda wierd, because I didn't resolve the problem by runing .jenkins. And sudo ldconfig is contained in .jenkins.d/02-chronosync.sh.
I'll be appreciate if you could help me elaborate the reason.
Thanks.
Updated by Ashlesh Gawande almost 7 years ago
You should not run files under .jenkins folder - they are meant to be run on jenkins server (continuous integration server). So if you ran it then "sudo ldconfig" would have never run because it checks which platform you are on that only resolves correctly when running on jenkins (https://github.com/named-data/NLSR/blob/master/.jenkins.d/02-chronosync.sh#L55).
If you want a script mini-ndn's install.sh script is better to use:
https://github.com/named-data/mini-ndn/blob/master/install.sh
Updated by Pengyuan Zhou almost 7 years ago
Ashlesh Gawande wrote:
You should not run files under .jenkins folder - they are meant to be run on jenkins server (continuous integration server). So if you ran it then "sudo ldconfig" would have never run because it checks which platform you are on that only resolves correctly when running on jenkins (https://github.com/named-data/NLSR/blob/master/.jenkins.d/02-chronosync.sh#L55).
If you want a script mini-ndn's install.sh script is better to use:
https://github.com/named-data/mini-ndn/blob/master/install.sh
Thanks again. I've learned a lot from you.
Now I could run nlsr with sudo. Another problem is shown as follows:
log4cxx: No appender could be found for logger (LsdbDatasetInterestHandler).
log4cxx: Please initialize the log4cxx system properly.
log4cxx: Could not read configuration file [/usr/include/log4cxx/].
Router's Identity /peering/test/cp1/%C1.Router/router1 does not existNLSR is running without security (Only for testing, should not be used in production.) If security is enabled NLSR will not converge.
The other functions seem work fine. Related lines in nlsr.conf look like this:
log4cxx-conf /usr/include/log4cxx/ ; path for log4cxx configuration file (Absolute path)
The system is Ubuntu 16.06, I also tried other paths:
/usr/share/doc/liblog4cxx10-dev
/usr/share/doc/liblog4cxx10v5
/usr/share/doc/liblog4cxx-dev
Shoud I change the name of "log4cxx-conf" to a specific one?
Thank you.
Updated by Muktadir Chowdhury almost 7 years ago
log4cxx: Could not read configuration file [/usr/include/log4cxx/].
You need to specify the name of log4cxx config file. For example if your log4cxx config file is in home folder you can have it like this: log4cxx ~/log4cxx.conf.
Router's Identity /peering/test/cp1/%C1.Router/router1 does not existNLSR is running without security (Only for testing, should not be used in production.) If security is enabled NLSR will not converge.
You need create an identity named /peering/test/cp1/%C1.Router/router1 . You can use ndnsec-key-gen command (https://github.com/named-data/ndn-cxx/blob/master/docs/manpages/ndnsec-key-gen.rst).
And I think we can close this issue. If you have further problem we can mail us in NLSR mailing list.
Updated by Muktadir Chowdhury almost 7 years ago
- Status changed from New to Abandoned
Updated by Ashlesh Gawande almost 7 years ago
Keep the log4cxx line commented out unless you want the log format to be different (I strongly recommend to comment it out for the first time). A sample is given here: https://github.com/named-data/NLSR/blob/master/log4cxx.properties.sample.in
Updated by Pengyuan Zhou almost 7 years ago
Ashlesh Gawande wrote:
Keep the log4cxx line commented out unless you want the log format to be different (I strongly recommend to comment it out for the first time). A sample is given here: https://github.com/named-data/NLSR/blob/master/log4cxx.properties.sample.in
Thank you!
Updated by Pengyuan Zhou almost 7 years ago
Muktadir Chowdhury wrote:
log4cxx: Could not read configuration file [/usr/include/log4cxx/].
You need to specify the name of log4cxx config file. For example if your log4cxx config file is in home folder you can have it like this: log4cxx ~/log4cxx.conf.
Router's Identity /peering/test/cp1/%C1.Router/router1 does not existNLSR is running without security (Only for testing, should not be used in production.) If security is enabled NLSR will not converge.
You need create an identity named /peering/test/cp1/%C1.Router/router1 . You can use ndnsec-key-gen command (https://github.com/named-data/ndn-cxx/blob/master/docs/manpages/ndnsec-key-gen.rst).
And I think we can close this issue. If you have further problem we can mail us in NLSR mailing list.
Thank you! I'll send you email for further problem