Can I install a PRTG probe on a Linux OS?

We still work on a probe that works on Linux (currently targeting a Wine based solution that will not support WMI). We have already seen some promising experiments in our labs, but a release-level product is not in sight for the near future. Sorry that I can not tell you a more specific timeframe at this time.

I would reiterate Scott's request.

We manage several Linux-only SaaS hosting locations where we need to add win servers just for running PRTG probe.

Is there a tentative date for native Linux probe?

• OR*

Did you ever test current win probe under various Linux-win emulators, thus avoiding us to go through the same process?

Of course, we are not asking for officially supported configurations, just knowing if someone successfully tested that.

Thank you in advance,

gdelconti

BravoSolution

Having at least a probe of PRTG running on Linux is something we have looked at a number of times, but until recently no emulator was able to support that.

The official binaries of PRTG run as "Windows Services". We have looked at Wine, and that did not support services.

I have not seen an emulator that can run services on Linux.

Do you have any other emulators that we should look at?

Are there some new developments in relation with running the PRTG probe on Linux?

Maybe cross-over is interesting for the emulation of Windows in Linux: http://www.codeweavers.com/products/impersonator/

On the other hand, is it not possile to write a dedicated probe for the Linux platform? Maybe the mono project can help you with the integration of vbscript.

We installed the PRTG client on PC-BSD 9 using Wine/Swine/Winetricks. It installed as a service fine, connected to the master probe server, but it was unstable, kept disconnecting.

Hi,
we know about the stability issues using Wine but at the moment we still only have a lab version of this (means nothing which can be released).
We are also doing some experiments with native Linux Probes but this is nothing more than playing around at the moment. Sorry.
Best regards

Here's the PC-BSD 9 log of PRTG Client for anyone serious enough to take it further (playing around):

1/23/2013 1:57:36 PM 
1/23/2013 1:57:36 PM PRTG Probe V12.2.2.2211
1/23/2013 1:57:36 PM PRTG Probe starting on "pcbsd-1126"
1/23/2013 1:57:36 PM OS: Windows XP (5.1.1 Build 2600 Service Pack 3), 1 CPUs, Single x86 Model 0 Step 

0, on "UNKNOWN"
1/23/2013 1:57:36 PM Data Path: C:\users\Public\Application Data\
1/23/2013 1:57:36 PM System Path: C:\Program Files\PRTG Network Monitor\
1/23/2013 1:57:36 PM Local IP: 0.0.0.0
1/23/2013 1:57:36 PM Core Server IP: *.*.*.* [ip removed]
1/23/2013 1:57:36 PM Core Server Port: 23560
1/23/2013 1:57:36 PM SSL Enabled
1/23/2013 1:57:36 PM Probe GID: {6C81462D-E5AF-4BB4-99DE-B911F01F58E7}
1/23/2013 1:57:36 PM Error init SNMP, Windows error code 5
1/23/2013 1:57:36 PM Could not initialize Traffic Control API: ??????????????
1/23/2013 1:57:42 PM Connected to *.*.*.*:23560 [ip removed]
1/23/2013 1:57:43 PM Connected

[and then we wait a few minutes and get]

1/23/2013 2:02:44 PM No Message Timeout, last message was 1/23/2013 6:57:42 PM
1/23/2013 2:02:55 PM Create new Connection
1/23/2013 2:03:01 PM Disconnected from *.*.*.*:23560 [ip removed]
1/23/2013 2:03:07 PM Connected to *.*.*.*:23560 [ip removed]
1/23/2013 2:03:57 PM WinPcap Packet Sniffer Driver could not be initialized
1/23/2013 2:04:02 PM Send Login
1/23/2013 2:04:02 PM Login OK: Welcome to PRTG

[however, the probe is actually connected to server with Probe Health 100%]

[it disconnects a few minutes after and PRTG Probe Administrator is closed on PC-BSD automatically after which, PRTG Probe Update? opens, closed that and reopened Admin and this log follows]

1/23/2013 2:10:56 PM Trying to restart PRTG Probe. Reason: Connection Watchdog: Last ping 1/23/2013 

7:07:45 PM
1/23/2013 2:10:56 PM Server TimeSync from 1/23/2013 7:10:57 PM to 1/23/2013 7:07:58 PM
1/23/2013 2:10:57 PM Restart initiated
1/23/2013 2:10:58 PM Stopping Probe...
1/23/2013 2:10:58 PM Step 1: Disconnect Core Connection
1/23/2013 2:10:58 PM Core Connection Terminated
1/23/2013 2:10:59 PM Step 2: Terminating monitoring threads... (this can take up to 3 minutes)
1/23/2013 2:11:01 PM Sending "Terminate" to monitoring threads...
1/23/2013 2:11:01 PM Waiting for threads to terminate...
1/23/2013 2:11:01 PM 2 threads left
1/23/2013 2:11:01 PM 0 threads left
1/23/2013 2:11:01 PM Step 3: Free Syslog Manager
1/23/2013 2:11:01 PM Step 4: Free Trap Manager
1/23/2013 2:11:01 PM Step 5: Free Qos Manager
1/23/2013 2:11:01 PM Step 6: Free PaesslerTrafficControl DLL
1/23/2013 2:11:01 PM Step 7: Free Collector Manager
1/23/2013 2:11:01 PM Step 8: Free Core Connection
1/23/2013 2:11:02 PM Step 9: Free WMI Connection Manager
1/23/2013 2:11:06 PM Step 10: Free Garbage Collector
1/23/2013 2:11:06 PM Step 11: Free SNMP Alias Cache
1/23/2013 2:11:06 PM Stop Done
1/23/2013 2:11:14 PM 
1/23/2013 2:11:14 PM PRTG Probe V12.2.2.2211
1/23/2013 2:11:14 PM PRTG Probe starting on "pcbsd-1126"
1/23/2013 2:11:14 PM OS: Windows XP (5.1.1 Build 2600 Service Pack 3), 1 CPUs, Single x86 Model 0 Step 

0, on "UNKNOWN"
1/23/2013 2:11:14 PM Data Path: C:\users\Public\Application Data\
1/23/2013 2:11:14 PM System Path: C:\Program Files\PRTG Network Monitor\
1/23/2013 2:11:14 PM Local IP: 0.0.0.0
1/23/2013 2:11:14 PM Core Server IP: *.*.*.* [ip removed]
1/23/2013 2:11:14 PM Core Server Port: 23560
1/23/2013 2:11:14 PM SSL Enabled
1/23/2013 2:11:14 PM Probe GID: {6C81462D-E5AF-4BB4-99DE-B911F01F58E7}
1/23/2013 2:11:14 PM Error init SNMP, Windows error code 5
1/23/2013 2:11:14 PM Could not initialize Traffic Control API: ??????????

[probe is stopped on Start/Stop tab, clicking Start Probe Service again]

[entire process above is repeated, probe doesn't connect any more after this unless OS is rebooted]

What this means as a managed services provider is we have to buy Windows 7 or Embedded for a probe on our clients network.

Hi,
thank you for the additional information I have forwarded them to the development team.
Best regards

I would like to add my vote for a PRTG linux probe. Would really like to be able to use Raspberry PIs as probes e.g. placing a raspberry pi in a comms cabinet on a floor testing VOIP quality to another location etc.

Hello All:

We posted the original request in 2010 for this feature. I will share with you how we have worked around this.

Like those who have posted follow up comments on this question, we needed a rock-solid platform to install probes in not only remote locations, but in locations that had less than desirable and environmental conditions. We tested probes on a large number of hardware platforms (Fit-2PC, Lanner, Dell, etc), as well as, different windows OS (WinXP, Win-7, Win-7 embedded, Server 2003-R2).

We found that MS Server 2003-R2 was an excellent OS to run as a probe. It is very stable, very mature, supports a huge array of hardware, and provides for not only an excellent OS for the PRTG probe to run, but also serves as an excellent platform to perform remote diagnostics.

In addition, the OS does not require significant hardware resources. We have probes running on small form factor appliances with 1GB RAM and 2.0GHz processors and the probes are rock solid.

I know many of you may be thinking that Server 2003-R2 is too expensive, however, with so many companies migrating to Server 2008/2012, there are thousands of fully licensed copies of Server 2003-R2 software available on eBay to purchase for less than $100.00.

I know that since Microsoft plans to End-of-Life the Server 2003-R2 this summer, still the OS is incredibly secure - especially if it is behind a firewall. However, in the IT world, ideal solutions rarely exist, so you have to make compromises.

Given all of the options we have had to try, this one has worked out beautifully for us and we will continue to use this solution until Paessler finally releases a Linux probe.

I know it is only a matter of time till they do as 95% of our sensors are SNMP anyway and not WMI based.

The bulk of our remote probes don't even query sensors from a Windows OS anyway, most are some linux derivative from switches, cameras, access control, UPS, routers, etc.

Thanks.

Just wanted to share with the community how we have worked through the situation.

Hi, Is there any more news on a native linux probe?

Still on the wishlist. Sorry. Please bear with us.

Hi, Is there any more news on a native linux probe? Maybe one without WMI, just with SNMP Sensors.

Hello Sven,

I am sorry, for now there is no news about a native Linux Probe.

Best regards

Scott, I have been looking to options for running a remote probe on Linux (Raspbian to be precise; RPi 3) and have succeeded as far as everything works and auto discovers once installed.

As I am using a raspberry pi, I run ExaGear to be able to install wine in order to emulate the Remote Probe Installer. As long as the Administration console stays open, the connection to the Local Probe stays. This shouldn't be an issue as the CPU stabilises around 5% when running.

For anyone else trying this method, I have a tip...

Even though running Wine as root (sudo) is not recommended, it is the only way I could enable the Linux Kernel to run Ping and subsequently Auto-Discover.

I believe that running a script to ensure the Administration console is running (and if not, to launch it) does count as a work-around to enable to application to run! At the moment, I still consider this a 'proof of concept' design but if anyone has any further information, please post.

Thanks, Alex.