I have the following Perl scripts (though this applies to Python and other scripting languages): `script1.pl`, `script2.pl`, `script3.pl`

The way these scripts where written, users execute them with input flags, and the output is a file saved. 

```
perl script1.pl --i input1.tsv   ## this outputs the file `outputs1`
perl script2.pl --i outputs1     ## this outputs the file `outputs2`
perl script3.pl --i outputs2     ## this outputs the file `final_output`

```

Now, I would like to create an executable bash script that allows users to simply work with `input1` and get the output in return `final_output`. 

Here's how I would do this with only one perl script, `execute.sh`:

```
#!/bin/sh

source ~/.bash_profile

FLAG1="--i=$1"

perl script1.pl $FLAG1

```

which could be run on the command line `execute.sh input1.tsv`

For my example with three scripts, how would I pipe the intermediate outputs into the intermediate scripts to created one `execute.sh` script, e.g. `outputs1` into `script2.pl`, then `outputs2` into `scripts3.pl`, etc.? 

Isn't there a way for me to do this without rewriting the perl/python scripts?
['https://unix.stackexchange.com/questions/341338', 'https://unix.stackexchange.com', 'https://unix.stackexchange.com/users/115891/']
It seems that the path node\_exporter is not correct.

```
    ExecStart=/usr/bin/node_exporter

```

I have another path to it on Ubuntu 16.04

```
~# cat /etc/issue
Ubuntu 16.04.3 LTS \n \l

~# which node_exporter
/usr/sbin/node_exporter

```

If it's not the root of the issue, check your `/var/log/syslog`. It must show the reason of the failure, something similar to:

```
Oct 20 12:30:30 prom systemd[8848]: node_exporter.service: Failed at step EXEC spawning /usr/bin/node_exporter: No such file or directory
Oct 20 12:30:30 prom systemd[1]: node_exporter.service: Main process exited, code=exited, status=203/EXEC
Oct 20 12:30:30 prom systemd[1]: node_exporter.service: Unit entered failed state.
Oct 20 12:30:30 prom systemd[1]: node_exporter.service: Failed with result 'exit-code'.
Oct 20 12:30:30 prom systemd[1]: node_exporter.service: Service hold-off time over, scheduling restart.
Oct 20 12:30:30 prom systemd[1]: Stopped Prometheus exporter for machine metrics, written in Go with pluggable metric collectors..
Oct 20 12:30:30 prom systemd[1]: Started Prometheus exporter for machine metrics, written in Go with pluggable metric collectors..

```
I got this error. Solved as @Saex.

Reason for getting this error is that I have downloaded the wrong package `node_exporter-1.2.2.darwin-amd64.tar.gz` instead of `node_exporter-1.2.2.linux-amd64.tar.gz`

```
    node_exporter.service - Node Exporter
         Loaded: loaded (/etc/systemd/system/node_exporter.service; enabled; vendor preset: enabled)
         Active: failed (Result: exit-code) since Wed 2021-08-18 11:22:44 UTC; 17s ago
       Main PID: 3830 (code=exited, status=203/EXEC)

Aug 18 11:22:44 ip-10-0-101-80 systemd[1]: Started Node Exporter.
Aug 18 11:22:44 ip-10-0-101-80 systemd[3830]: node_exporter.service: Failed to execute command: Exec format error
Aug 18 11:22:44 ip-10-0-101-80 systemd[3830]: node_exporter.service: Failed at step EXEC spawning /opt/node_exporter/node_exporter: Exec>
Aug 18 11:22:44 ip-10-0-101-80 systemd[1]: node_exporter.service: Main process exited, code=exited, status=203/EXEC
Aug 18 11:22:44 ip-10-0-101-80 systemd[1]: node_exporter.service: Failed with result 'exit-code'.

```