Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class
211 views

Script Error

Jump to solution

Hello,

 

I have a script alert that is generating a generic error message on one of my SiteScope instances.  I use the same alert configuration and script template on two different instances, but this is only occurring on one of them and just for this alert trigger..

 

The error is:  ERROR: , Bad file descriptor (9)

 

I am unsure how to troubleshoot this one.  The script simply sends a template to the OM connector, which as mentioned, works fine on one instance.  I use the OM connector for any alerts that need to go to OM so it does work for other alerts, just not this specific one.  I use the same alert template on both instances and send the same 4 extra variables (alert::description, etc).

 

Thanks!

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

This turned out to be some textual data in the script output (the Mainproperties variable) that must have caused some type of exception.  So, basically, i had to remove that variable for this to process properly.  Something in the text must have been an escape character or something that caused the output to break the script.


This was specifically using the OM/opcMsg method to read a script template file for opcMsg processing..

 

Anyhow, it's resolved.

 

View solution in original post

3 Replies
Absent Member.
Absent Member.

Hi,

 

Could you please go to the master.config and review if you have the same information in the both instances:
_scriptMonitorExtensions=
_scriptInterpreters=

 

Regards.

0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class
Hello,

Those entries do not exist the master.config file for either instance..

Thanks,
Lance
0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

This turned out to be some textual data in the script output (the Mainproperties variable) that must have caused some type of exception.  So, basically, i had to remove that variable for this to process properly.  Something in the text must have been an escape character or something that caused the output to break the script.


This was specifically using the OM/opcMsg method to read a script template file for opcMsg processing..

 

Anyhow, it's resolved.

 

View solution in original post

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.