cannot start the Win-64 service about node-opcua-logger HOT 5 CLOSED

Passing the config file with a flag won't work, if you want to use a custom location you should set it in the Environment (see also https://superuser.com/questions/79612/setting-and-getting-windows-environment-variables-from-the-command-prompt)

However, config.toml is the default location for the config file, and from the syntax error it looks like it's not formatted correctly. The error specifies it found a {, did you perhaps use JSON instead of TOML?

Can you share the contents of the file here?

from node-opcua-logger.

from node-opcua-logger.

Hello,

the application determines the format based on the extension of the config file. You would set the necessary environment variable by running the following command:

set CONFIG_FILE=c:\path\to\config.json

and then in the same command line window you run the binary of the logger!

Usually, after testing config etc, you'd run the logger through a windows service. I usually suggest using nssm to do so. During the installation, you can also specify the environment variables for the service.

from node-opcua-logger.

from node-opcua-logger.

You're welcome!

from node-opcua-logger.