Problem with PhantomJS for full page load?

Modified on 2025-06-10 14:06:29 +0200

Hi Everone,

I'm working with some web tests. I have created 2 tests with the PhantomJS headless webkit. One is working fine and shows reasonable values. The other one shows all zeroes. If I change this one to Chrome it seems to work fine. However, I prefer the PhantomJS thing.

How can I figure out what is wrong here? And eventually solve this? The settings for both tests are the same - other then the URL of course.

Best regards, Will

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hello,

both Full Page Sensors running on the same Probe?

Please try to run PhantomJS via command shell. Run 2 tests with and without Administrative rights.

Open shell and change directory to C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXE.

Then start script with: phantomjs.exe phloadspeed.js "http://www.google.com"

Change the Url to your preferred one.

Do you get a value greater then zero?

Regards, Thomas

Oct, 2013 - Permalink

Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

Problem with PhantomJS for full page load?

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.