Project

General

Profile

Actions

Bug #2023

closed

ERROR: Failed to register prefix in local hub's daemon

Added by Ali Khan about 10 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
-
Start date:
10/03/2014
Due date:
% Done:

100%

Estimated time:
3.00 h

Description

The ndn-repo generated an error while it was running on OpenWRT router.

The error messages are written as follows:

root@NDN11:/var/db/ndn-repo-ng# ndn-repo-ng 
initialize storage cost: 0 millisecondsms
1412040874.154965 INFO: [FaceTable] Added face id=260 remote=fd://19 local=unix:///var/run/nfd.sock
ERROR: Failed to register prefix in local hub's daemon
Command Interest timed out
terminate called after throwing an instance of 'repo::WriteHandle::Error'
Aborted
root@NDN11:/var/db/ndn-repo-ng# 1412040884.826144 WARNING: [UnixStreamFace] [id:260,uri:fd://19] Send or receive operation failed, closing face: Broken pipe
1412040885.518848 INFO: [FaceTable] Removed face id=260 remote=fd://19 local=unix:///var/run/nfd.sock

Related issues 1 (1 open0 closed)

Blocks repo-ng - Feature #4129: Management Dispatcher for repo commandsNewMuktadir Chowdhury

Actions
Actions #1

Updated by Ali Khan about 10 years ago

Precisely, I have cross compiled the NFD, ndn-cxx and repo-ng for the OpenWRT router. All are the latest version from github. The NFD was running properly, but error messages were generated while it was running the ndn-repo-ng.

However, the ndn-repo-ng is working properly when it runs on Linux machine.

The error messages (rearrange from previous post) are written as follows:

root@NDN11:/var/db/ndn-repo-ng# ndn-repo-ng 
initialize storage cost: 0 millisecondsms
ERROR: Failed to register prefix in local hub's daemon
Command Interest timed out
terminate called after throwing an instance of 'repo::WriteHandle::Error'
Aborted

1412040874.154965 INFO: [FaceTable] Added face id=260 remote=fd://19 local=unix:///var/run/nfd.sock
1412040884.826144 WARNING: [UnixStreamFace] [id:260,uri:fd://19] Send or receive operation failed, closing face: Broken pipe
1412040885.518848 INFO: [FaceTable] Removed face id=260 remote=fd://19 local=unix:///var/run/nfd.sock
Actions #2

Updated by Alex Afanasyev about 10 years ago

  • Description updated (diff)
Actions #3

Updated by Alex Afanasyev about 10 years ago

From what I can see, you have started just nfd process, which is not enough.

You need nfd and nrd processes to be started in order for NDN applications to work properly.

Actions #4

Updated by Ali Khan about 10 years ago

I have just checked the running process on this router. The nfd and nrd processes have already run, but I still have the same error messages after running the "ndn-repo-ng" command.

Besides, I also tested with other NDN applications (i.e. ndnping, nun-traffic-geneartor), they were running properly on this mobile router.

If you need more information such as logs or nfd' status, please suggest.

Thank you

Actions #5

Updated by Junxiao Shi over 7 years ago

  • Assignee set to Junxiao Shi
  • Estimated time set to 3.00 h

This is probably caused by repo-ng registering four separate routes into NFD-RIB, but ndn::nfd::Controller does not have stop-and-wait (#2293), cause some commands being rejected.
Another possibility is simply insufficient computation power on OpenWRT.
I'll try to address the first cause.

Actions #6

Updated by Junxiao Shi over 7 years ago

  • Tracker changed from Task to Bug
Actions #7

Updated by Junxiao Shi over 7 years ago

  • Status changed from New to In Progress
Actions #8

Updated by Junxiao Shi over 7 years ago

  • Blocks Feature #4129: Management Dispatcher for repo commands added
Actions #9

Updated by Junxiao Shi over 7 years ago

  • Status changed from In Progress to Code review
  • % Done changed from 0 to 100

https://gerrit.named-data.net/3940

I decide to make a small change to fix the excessive FIB entries problem, which has bothered me in my deployments for some months.
Eventually this needs to be switched over to the dispatcher.

Actions #10

Updated by Junxiao Shi over 7 years ago

  • Status changed from Code review to Closed
Actions

Also available in: Atom PDF