Process Event handler to fire external script

[khuang]

@mattfox said in Process Event handler to fire external script:

/usr/local/bin/virtualenvwrapper.sh

Ok, I'm going to debug just the source command for now.
If I add #!/bin/bash to the top of my script, it acts as if all my settings in bashrc are ignored. I get an error saying it cannot find the virtualenvwrapper module. Are you suggesting to use #!/bin/bash in order to only run bash and not any of the other shells?

On the other hand, if I do not have #!/bin/bash:

1. using:

source /usr/local/bin/virtualenvwrapper.sh

it seems like it doesn't understand the command

2. using

. /usr/local/bin/virtualenvwrapper.sh

it gives a bad substitution error

[MattFox]

I've just tested on a mango seeing if I could get the contents of the fans file in /home/mango

here is my script:

#!/bin/bash
. /home/mango/fans

and in my log I get:

/home/mango/fans: line 1: /usr/lib/python2.7/distutils/fancy_getopt.pyc: Permission denied /home/mango/fans: line 2: /usr/lib/python2.7/distutils/fancy_getopt.py: Permission denied /home/mango/fans: line 3: /usr/share/perl5/Regexp/Common/profanity.pm: Permission denied /home/mango/fans: line 4: /usr/share/man/man3/Regexp::Common::profanity.3pm.gz: Permission denied /home/mango/fans: line 5: /usr/include/linux/fanotify.h: Permission denied /home/mango/fans: line 6: /usr/include/arm-linux-gnueabihf/sys/fanotify.h: Permission denied /home/mango/fans: line 7: /home/mango/fans: Permission denied /home/mango/fans: line 8: /opt/mango/web/modules/sstGraphics/web/graphics/Fan/fan_on.gif: Permission denied /home/mango/fans: line 9: /opt/mango/web/modules/sstGraphics/web/graphics/Fan/fan_off.gif: Permission denied /home/mango/fans: line 10: /etc/udev/rules.d/60-odroid_fan.rules: No such file or directory /home/mango/fans: line 11: /sys/devices/platform/pwm-fan:: Is a directory /home/mango/fans: line 12: /sys/devices/platform/pwm-fan:/hwmon/hwmon0/fan_speed: Permission denied /home/mango/fans: line 13: /sys/firmware/devicetree/base/pwm-fan: Is a directory /home/mango/fans: line 14: /sys/bus/platform/devices/pwm-fan:: Is a directory /home/mango/fans: line 15: /sys/bus/platform/drivers/pwm-fan: Is a directory /home/mango/fans: line 16: /sys/bus/platform/drivers/pwm-fan/pwm-fan:: Is a directory /home/mango/fans: line 17: /sys/module/rcutree/parameters/rcu_fanout_exact: Permission denied /home/mango/fans: line 18: /sys/module/rcutree/parameters/rcu_fanout_leaf: Permission denied '

which is correct since they are owned by root.
If you're getting grief still. I recommend you don't fiddle with the .bashrc file until your script works first.

[khuang]

I'm pretty confident the scripts work as the scripts execute perfectly on my end. It is only via the process event handler that I get an error. I've added #!/bin/bash to the virtualenvwrapper.sh script and it gives me an error saying:

Process error: '/usr/bin/python: No module named virtualenvwrapper virtualenvwrapper.sh: There was a problem running the initialization hooks. If Python could not import the module virtualenvwrapper.hook_loader, check that virtualenvwrapper has been installed for VIRTUALENVWRAPPER_PYTHON=/usr/bin/python and that PATH is set properly

This script came with my virtualenv and virtualenvwrapper packages so I should not be editing it. This script uses environmental variables like $HOME in its path, which could contribute to the error, but should I be editing read-only scripts that came with packages that work by default to get things integrated with Mango?

EDIT: Is there another way to interface my script with Mango other than a process event handler? The trigger is on a data point value change.

[phildunlap]

Hi khuang,

EDIT: Is there another way to interface my script with Mango other than a process event handler? The trigger is on a data point value change.

You could invoke it through an SSH data source / data point, perhaps. Then you should have the environment the user would upon ssh'ing.

[phildunlap]

I probably should have chimed in this bit earlier:

I can execute the script just fine manually on the MangoES by running:
/home/mango/shell_name.sh virtualEnv "python script_name.py arg1 arg2"

Unfortunately the tokenizing of the process event handler is not the same as the shell that it will pass the arguments to. Quotes and subshells are ignored. The Process Event Handler will pass a list of space delimited strings as arguments to whatever is the first argument.

cat 'hello.txt' and the error I get is:
Process error: 'cat: 'Hello.txt': No such file or directory cat.

Assuredly the cause of this is the single quotes are ignored as shell markup and tokenized into the first argument passed to cat, and there is no file named 'Hello.txt'

Edit: Note that this is not the case when using the SSH Data Source, where all subshells and quotes and whatnot should be honored appropriately.

[MattFox]

Thanks Phil

[khuang]

@phildunlap Hi Phil, right now I have a Virtual data source for the purpose of simulation but in production we will have a Modbus I/P datasource. So thinking ahead - say I were to use an ssh data source and data point to trigger my script. Then I would have to set up a point link between the Modbus I/P datapoint to trigger my SSH datapoint which would then trigger my script?

As for the SSH datapoint, are you suggesting to use either of the query command/settable command to execute my shell script?

I just want to make sure I understand the full picture before I attempt something that might not be suited for my production environment.

[phildunlap]

Then I would have to set up a point link between the Modbus I/P datapoint to trigger my SSH datapoint which would then trigger my script? As for the SSH datapoint, are you suggesting to use either of the query command/settable command to execute my shell script?

You could use a Set Point Event Handler. That's what I'd probably do. My script would look like,

//Since the command is hardcoded, we don't need to provide a meaningful
// string to replace VALUE in the set command (see SSH DP help doc)
return "";

which would send the Set Command and try to get a value, so that you can check the SSH point somewhere to see if the script did what it was supposed to.

Alternatively you could use the query command, but then the data source will poll with that command. In the SSH data source, after the set command is sent the query command if nonempty is sent as well, and then the response to either is read. Using the set would just be simpler: it will just be the command to invoke.

[khuang]

@phildunlap I've generated my private key and provided the path to the data source but it's not finding the private key. In my case the server I am ssh'ing to is my MangoES, which also is where my data source lies.

[phildunlap]

The id_rsa is the private key. So, you'll need to cat id_rsa.pub >> authorized_keys and the provide the path to id_rsa as the private key.

[khuang]

@phildunlap Yes, I have already done that and my authorized_keys file looks like:

ssh-rsa AAAAB3N...N3EU3 mango@mangoES3439

In the log it just says:

java.io.FileNotFoundException: Private key file not found

To test that my key pair works, I've tested ssh IP_MANGOES via shell and I get in without being prompted for the user/pw. It looks like there might be an error with my datasource configuration.

[MattFox]

Phil, woiuld a config file in the .ssh directory for ssh keys work in this case?
I do that and try SSH'ing manually first to make sure the remote ID is authenticated and that I go straight through with no issue.

[phildunlap]

You could try an absolute path instead of a ~/, like /home/mango/.ssh/id_rsa

[khuang]

Ok, I think providing the full path worked. Thanks. Interesting that ~/.ssh/id_rsa is provided by default for the private key field but does not work.

For the set command field, is that where I could execute my shell script? For example:

[MattFox]

That should work as usually the home directory is the default location a user logs in as unless stated otherwise in the user profile. This is assuming you've kept it in the /home/mango directory.. All else fails, absolute paths shouldn't fail you.

[khuang]

Yes, the script did fire after doing what Phil suggested (to create a Set Point event handler). Changing the value of the target data point caused the set command of the SSH data point to fire. Unfortunately, I get the same errors as before when I had my process event handler.

[MattFox]

Since that's the case it's likely best you find the causes of them through virtualenv.
If they have env paths, echo them in the bash file. This will tell you if your ssh connection is inheriting all of the required information.

[khuang]

Actually I mispoke - my set point event handler is not firing. It was the old process event handler that was firing that I forgot to deactivate. So now I am trying to set my ssh data point through the set point event handler.

This is what I have for the set point event handler ("MangoES - Trigger" is the SSH datapoint)"

It does not look like the event is firing though because my SSH datapoint is N/A.

[MattFox]

@khuang Is there no information in logs??
Also enable logging on the ssh datasource and tail -f the log file. Would be interesting to see if anything comes through at all.
EDIT: check your syslogs as well.

[khuang]

There isn't anything in the sys logs but tail -f for the session log file of the datasource gives me:

So it does look my test script is running but when I try to flip the bit back to 0 for my ssh data point, it just automatically executes my set point handler again and sets it back to 1. The set point handler shouldn't be activating unless there is a change from 0->1 for my source.