Script Results not showing on the web since upgrade to Redhat 8.9

[halamalagarli]

Hi

We have been running the prometheus-script-exporter on Redhat 7, but we have had to upgrade our machies to Redhat 8.9, this also included an upgrade of Java from 8 to 11 and tomcat went from v8 to v9

Whilst many of our scripts are still working, these are all very basic Bash output, but we have a slightly more complex script that connects to ETCD cluster to get some github hashes.

The first line of this script is export PATH="${PATH}:/usr/local/bin" which now includes the v11 Java.

If I run the script manually from within the server I can see the results, when I hit the endpoint url with the probe?script=script_name I see some of the starting text, all the way up to

HELP script_success Script exit status (0 = error, 1 = success).

TYPE script_success gauge

script_success{script="script_name"} 1

HELP script_duration_seconds Script execution time, in seconds.

TYPE script_duration_seconds gauge

script_duration_seconds{script="script_name"} 0.170699

HELP script_exit_code The exit code of the script.

TYPE script_exit_code gauge

script_exit_code{script="script_name"} 0

but I don't see anything below this where the actual results of the script would come out.

This is the only script not working, and we are trying to figure it out. If you have any notion of pre-requisites or how changes in the OS would possibly affect things that would help

Many thanks
MP

[ricoberger]

Hi @halamalagarli, normally there shouldn't be any different between the used OS version.

Since the metrics added by the exporter are displayed, I think the issue must be within the following lines https://github.com/ricoberger/script_exporter/blob/main/pkg/exporter/metrics.go#L91-L114

Is it possible that the output of the script has slightly changed within the update, so that the output could not be generated anymore, because the regex doesn't match?

[ricoberger]

Hi @halamalagarli, since there is no activity for some time, I will close the issue for now. If this is still a problem please let me know and we can reopen the issue.