search

Jacques44 / node-red-contrib-bigssh

remote command using ssh big node
Apache License 2.0
8 stars 12 forks source link

bash: ${payload.ip}: bad substitution #23

Closed bkdfkup closed 3 years ago

bkdfkup commented 3 years ago

Hey again!

I have deployed 1.2.7 via npm as advised, and checking the version via command line verifies the correct version is installed, however in the node-red palette list it shows ver 1.2.4. As shown here:

image vs image

Potentially as a result of this i cannot get substituting the payload to function correctly, getting the "bad substitution" error, even with your example flow.

Examples: image

Thanks in advance for any advice!

Jacques44 commented 3 years ago

Hello,

Did you restart node-red?

Btw, can you give me informations on how do you run node-red? System?

Regards

On 26 Nov 2020, at 01:35, bkdfkup notifications@github.com wrote:

Hey again!

I have deployed 1.2.7 via npm as advised, and checking the version via command line verifies the correct version is installed, however in the node-red palette list it shows ver 1.2.4. As shown here:

https://user-images.githubusercontent.com/74683396/100294476-04cfc280-2fdb-11eb-9481-0fd4e9832b22.png vs https://user-images.githubusercontent.com/74683396/100294518-203acd80-2fdb-11eb-94c8-f545185ece44.png Potentially as a result of this i cannot get substituting the payload to function correctly, getting the "bad substitution" error, even with your example flow.

Examples: https://user-images.githubusercontent.com/74683396/100294373-b7ebec00-2fda-11eb-8c8a-a1dd09c9d3b1.png Thanks in advance for any advice!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Jacques44/node-red-contrib-bigssh/issues/23, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKS6M56A46ME3HN6DMQOOTSRWPDXANCNFSM4UDBZPIQ.

bkdfkup commented 3 years ago

Hi!

Yes I restarted node red after installing the new version. No change. Did an "npm uninstall" and reinstall (and reboot), no change. Versions as captured in the first post if this issue.

I have the node-RED configured to start as a service upon boot.

Hope that helps 🤷

Thanks!

Jacques44 commented 3 years ago

That sounds strange.

By my side, I’m using

It seems that you node-red uses another node-modules directory

Maybe you can check your file system for node-red-contrib-bigssh directories You can check the node version by opening the package.json file inside. You should see 1.2.7

I don’t see the node version in the palette...

On 26 Nov 2020, at 07:29, bkdfkup notifications@github.com wrote:

Hi!

Yes I restarted node red after installing the new version. No change. Did an "npm uninstall" and reinstall (and reboot), no change. Versions as captured in the first post if this issue.

I have the node-RED configured to start as a service upon boot.

Hope that helps 🤷

Thanks!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Jacques44/node-red-contrib-bigssh/issues/23#issuecomment-734102232, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKS6M2RILWCYB2OSPR5HVDSRXYUFANCNFSM4UDBZPIQ.

Jacques44 commented 3 years ago

I’ve downgraded my node-red-contrib-bigssh installation to 1.2.4 and I’m getting the same error messages as yours.

So I think node-red is still using another node-red-contrib-bigssh installation which has not been upgraded…

On 26 Nov 2020, at 07:29, bkdfkup notifications@github.com wrote:

Hi!

Yes I restarted node red after installing the new version. No change. Did an "npm uninstall" and reinstall (and reboot), no change. Versions as captured in the first post if this issue.

I have the node-RED configured to start as a service upon boot.

Hope that helps 🤷

Thanks!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Jacques44/node-red-contrib-bigssh/issues/23#issuecomment-734102232, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKS6M2RILWCYB2OSPR5HVDSRXYUFANCNFSM4UDBZPIQ.

bkdfkup commented 3 years ago

Interesting. I am on the same ver of node red, and am on node.js v15.2.1.

I'll keep searching for the alternate node dir....

bkdfkup commented 3 years ago

So... you have put me on the right path, and the steps listed here https://nodered.org/docs/user-guide/runtime/adding-nodes (in particular running the npm commands from ~/.node-red specifically (as opposed to the root dir) fixed the issue!

Jacques44 commented 3 years ago

Great :-)

On 26 Nov 2020, at 08:17, bkdfkup notifications@github.com wrote:

So... you have put me on the right path, and the steps listed here https://nodered.org/docs/user-guide/runtime/adding-nodes https://nodered.org/docs/user-guide/runtime/adding-nodes (in particular running the npm commands from ~/.node-red specifically (as opposed to the root dir) fixed the issue!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Jacques44/node-red-contrib-bigssh/issues/23#issuecomment-734121185, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKS6M45WKBLHPZT57CFYQLSRX6I3ANCNFSM4UDBZPIQ.

bkdfkup commented 3 years ago

Thanks very much! Closing this issue.