[Nfd-dev] [EXT] Issue with getting nfd-log

[Junxiao Shi]

Hi Ishita

Your installation is broken. Purge and reinstall the nfd package via APT.
If problem persists, reimage the machine and start from scratch.

Yours, Junxiao

On Thu, Apr 16, 2020 at 13:59 Ishita Dasgupta <ishita.dasgupta at gmail.com>
wrote:

> *External Email*
> Hi Junxiao,
>
> I see
>
> Failed to issue method call: Unit nfd.service failed to load: No such file
> or directory. See system logs and 'systemctl status nfd.service' for
> details.
> On looking at the log
>
> nfd.service
>
>    Loaded: error (Reason: No such file or directory)
>    Active: inactive (dead)
> My path is set to include /usr/bin where nfd resides so I am not sure why
> I might be seeing this.
>
> Regards,
> Ishita Dasgupta
> Regards,
> Ishita Dasgupta
>
> *Graduate Student**College of Information and Computer Sciences*
> *,UMass Amherst*
>
>
> On Thu, Apr 16, 2020 at 1:50 PM Junxiao Shi <shijunxiao at email.arizona.edu>
> wrote:
>
>> Hi Ishita
>>
>> Clear up your earlier mistake: (you should never invoke nfd binary
>> directly; only start it via systemd)
>> sudo rm -rf $HOME/.ndn
>>
>> Start NFD systemd service:
>> sudo systemctl restart nfd
>>
>> View logs:
>> journalctl -u nfd
>>
>> Yours, Junxiao
>>
>> On Thu, Apr 16, 2020 at 13:44 Ishita Dasgupta via Nfd-dev <
>> nfd-dev at lists.cs.ucla.edu> wrote:
>>
>>> *External Email*
>>> Hi,
>>>
>>> I want to be able to see the nfd-logs hen I perform ndnping or ndnperf
>>> on the node.
>>> I have made the following modifications to the nfd.conf in /etc/ndn
>>> (default_level INFO
>>> Forwarder TRACE)
>>> As explained here
>>> <https://www.lists.cs.ucla.edu/pipermail/nfd-dev/2018-September/003387.html>,
>>> when I do the following
>>>
>>>    1. sudo start nfd &> nfd.log &
>>>
>>> *I only see nfd start/running, process 75093 in the log. Even with all
>>>    the successful ndnperf downloads or ndnpings. This made me think that
>>>    probably I need to explicitly specify the nfd.conf which led to 2.*
>>>    2. sudo start nfd -c /etc/ndn/nfd.conf > nfd.log &
>>>
>>> *start: invalid option: -c nfd starts but doesn't take in the config
>>>    file command*
>>>    3. sudo nfd -c /etc/ndn/nfd.conf > nfd.log & (from here)
>>>    <https://named-data.net/doc/NFD/current/manpages/nfd.html>
>>>
>>>
>>> *1587058707.444119 DEBUG: [Forwarder] onIncomingInterest face=259
>>>    interest=/localhost/nfd/faces/events/%FE%04   what():  Error in setting
>>>    interest filter (/localhost/nfd): Internal implementation error
>>>    (Validator/policy did not invoke success or failure callback)
>>>    1587058707.444167 DEBUG: [Forwarder] onContentStoreMiss
>>>    interest=/localhost/nfd/faces/events/%FE%04*
>>>
>>>
>>> Can anyone point out what I might be doing wrong? How can I have a
>>> verbose look at the nfd-log?
>>> I have the entire log from number 3 if anyone needs to see it.
>>>
>>> Regards,
>>> Ishita Dasgupta
>>>
>>> _______________________________________________
>>> Nfd-dev mailing list
>>> Nfd-dev at lists.cs.ucla.edu
>>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20200416/91b0d57f/attachment.html>