Project

General

Profile

Actions

Bug #4261

closed

ValidationPolicyConfig causes NFD to exit upon start

Added by Eric Newberry about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Urgent
Category:
Security
Target version:
Start date:
08/29/2017
Due date:
% Done:

100%

Estimated time:

Description

When starting the latest development version of NFD, I encounter this error, causing NFD to exit:

FATAL: [NFD] ValidationPolicyConfig can be configured only once

I encountered this issue on Ubuntu 17.04 64-bit. The NFD commit is c25737cd9a8d43856591cdec52d8df037a7de352 and the ndn-cxx commit is 605671de0111bd67bdcfa3b9a2486b0e684492ef. This occurs with the default config file provided in the NFD git repo.

Actions #1

Updated by Davide Pesavento about 7 years ago

  • Priority changed from High to Urgent
  • Target version set to v0.6
Actions #2

Updated by Eric Newberry about 7 years ago

I installed NFD on a new installation of Ubuntu 16.04 64-bit and still encountered this issue.

Actions #3

Updated by Alex Afanasyev about 7 years ago

  • Project changed from NFD to ndn-cxx
  • Category set to Security
  • Assignee set to Alex Afanasyev
  • Target version changed from v0.6 to v0.6
  • Start date changed from 08/27/2017 to 08/29/2017
Actions #4

Updated by Alex Afanasyev about 7 years ago

  • Status changed from New to Code review
  • % Done changed from 0 to 100

https://gerrit.named-data.net/#/c/4156/

Eric, can you check if this commit fixes the issues (it should).

Actions #5

Updated by Alex Afanasyev about 7 years ago

I run tests myself. Without this patch, I cannot start NFD. With the patch, NFD is being started.

I will update nfd.conf.in in another commit.

Actions #6

Updated by Alex Afanasyev about 7 years ago

  • Status changed from Code review to New
Actions #7

Updated by Eric Newberry about 7 years ago

@Alex, did your fix not work (the status got changed to new)?

Actions #8

Updated by Alex Afanasyev about 7 years ago

  • Status changed from New to Closed

Hmm. I moved to "new" to track progress with documentation, but now realized it is a wrong place for it.

Yes, this issue has been resolved. At least in my local test it is working.

Actions

Also available in: Atom PDF