We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have Ubuntu 16.04, with node 6.14. I get the following error while starting:
ubuntu@ip-172-31-16-24:~$ opcua-commander -e opc.tcp://localhost:26543 /usr/bin/env: ‘node\r’: No such file or directory
Here is my environment:
ubuntu@ip-172-31-16-24:~$ which node /usr/bin/node ubuntu@ip-172-31-16-24:~$ ll /usr/bin/node* -rwxr-xr-x 1 root root 30726190 Aug 15 13:15 /usr/bin/node* lrwxrwxrwx 1 root root 24 Aug 20 09:56 /usr/bin/nodejs -> /etc/alternatives/nodejs* lrwxrwxrwx 1 root root 13 Aug 20 09:59 /usr/bin/nodejs6.10 -> /usr/bin/node* ubuntu@ip-172-31-16-24:~$ node -v v6.14.4 ubuntu@ip-172-31-16-24:~$ uname -a Linux ip-172-31-16-24 4.4.0-1066-aws #76-Ubuntu SMP Thu Aug 16 16:21:21 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
I can go to the installation folder and run with node command to connect to the locally running node-opcua, but it closes immediately:
node-opcua
root@ip-172-31-16-24:/usr/lib/node_modules/opcua-commander# pwd /usr/lib/node_modules/opcua-commander root@ip-172-31-16-24:/usr/lib/node_modules/opcua-commander# node index.js -e opc.tcp://localhost:26543
The text was updated successfully, but these errors were encountered:
duplicates #8
Sorry, something went wrong.
No branches or pull requests
I have Ubuntu 16.04, with node 6.14. I get the following error while starting:
Here is my environment:
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
I can go to the installation folder and run with node command to connect to the locally running
node-opcua
, but it closes immediately:The text was updated successfully, but these errors were encountered: