Troubleshooting | Multi-Platform Probe for PRTG

Multi-Platform Probe for PRTG

Troubleshooting

Configuration and connection

The multi-platform probe does not start and exits with the code 78.

The configuration file or the identity key is missing or invalid. The multi-platform probe lists every problem that it found and does not try again, because a restart fails the same way.

To see the same list without a start, run the following command:

sudo probe-admin-tool check

If the multi-platform probe has no configuration yet, configure it as described in section Configuration.

The multi-platform probe does not appear in PRTG and the log shows probe auth handshake failed.

The access token in PRTG is missing, or it does not match the access token of this multi-platform probe. The multi-platform probe keeps running and retries the connection every 30 seconds.

1.Show the access token of the multi-platform probe:

sudo probe-admin-tool identity show

2.Compare it with the access token in the PRTG web interface under Setup | System Administration | Probes | Multi-Platform Probes | Access Tokens.

The multi-platform probe retries forever and your firewall blocks UDP.

The default connection type QUIC uses UDP. If your network blocks UDP, switch the multi-platform probe to TCP and restart it.

General

I want to debug and test different settings.

If you want to temporarily change a variable to debug or test different settings, you can use systemctl edit:

sudo systemctl edit prtg.mpprobe.service

When you finish Troubleshooting, remember to revert your changes to make sure that the multi-platform probe continues to run properly:

sudo systemctl revert prtg.mpprobe.service

The data from my multi-platform probe sensors are appearing at the incorrect time or not appearing at all.

If you run your multi-platform probe on a probe system with different time zone settings, PRTG automatically accounts for the time differential. However, if your probe system time setting is not set to adjust automatically or to follow the universal time standards, you might experience interruptions or errors in the timestamps of your monitoring data. Adjust the time settings of your probe system to either conform to universal time standards or to match the time settings of the system that runs the PRTG core server to avoid this behavior.

i_round_blueRestart the multi-platform probe after you make any changes to your probe system to apply the changes.

i_round_redThere might be a loss of monitoring data when you change the time of the probe system.

The Script v2 sensor on my multi-platform probe keeps going to the Down status.

Python 3.9 has a bug in some versions of the ping3 module. If you receive the error message TypeError: unsupported operand type(s) for |: 'type' and 'NoneType', upgrade your ping3 module to as of version 4.0.7:

python -m pip install --upgrade ping3