The "Unknown Parameter" Error during the server loading can happen to several reasons.


Not Acceptable Character

In this scenario the server would produce the log similar to the following:


$ netconfd-pro --fileloc-fhs=true


Starting netconfd-pro...
Copyright (c) 2008-2012, Andy Bierman, All Rights Reserved.
Copyright (c) 2012-2020, YumaWorks, Inc., All Rights Reserved.

Error: Unknown parameter ()
netconfd-pro: init returned (unknown parameter)


Note, that the error "Error: Unknown parameter ()" does not specify what parameter is unknown. This means that some of the characters that was provided to the server is not acceptable.


First, you need to check that you used correct characters in the parameter. For example:


sudo netconfd-pro –fileloc-fhs=true


The above parameter has invalid character (dash) in front of it.

The server accepts only the following characters in front of the parameter:

 

1) double hyphen:  --fileloc-fhs=true
2) single hyphen: -fileloc-fhs=true
3) no hyphens:  fileloc-fhs=true

If you copy paste some parameter from a FAQ or manual make sure that it does not have any long dashes in front.
Sometimes, the double hyphen can get converted to a single long dash character in the FAQ or in the manual.



Unknown Parameter


In this scenario the server would produce the log similar to the following:


$ netconfd-pro --fileloc-fhs-invalid=true


Starting netconfd-pro...
Copyright (c) 2008-2012, Andy Bierman, All Rights Reserved.
Copyright (c) 2012-2020, YumaWorks, Inc., All Rights Reserved.

Error: Unknown parameter (fileloc-fhs-invalid)
netconfd-pro: init returned (unknown parameter)


Note that in this case the server log file specifies what is the unknown parameter.

In this case make sure that the parameter is valid.



Not supported parameter

In case you use some old version of the server and trying to use new parameter that is only supported in new version you also may get the "Unknown parameter" Error during the server loading.


In this case make sure that the version of the server is appropriate for the parameter. You may use older version of the server that does not support specific parameter that you specify.


You can check if specific parameter is supported by the server by running:


$ netconfd-pro --help
Or 
$ man netconfd-pro