Menu

Server Monitoring Instructions for Services Customers

 

What Are You Installing?

For general information about the monitoring software check out the product information. The software is designed to be installed on production systems, and does not modify the registry or anything outside of the installation directory.  The downside is that on Windows the software is not a service and must be started by hand before the test. There are two modes of working– either the statistics can be collected by hand from each server and emailed to our engineers, OR the firewall has to be modified to open two ports to connect to the monitor.  Note that each server requires a different two ports, each of which needs to be configured both on the firewall and on the server, so most often customers choose to collect the server stats files by hand. Obviously this is sub-optimal, and we are working on a different architecture that requires less configuration.

 

Download Installers

http://www.webperformance.com/download/
The installer you’re looking for is for the Server Monitor.   Click on green Server Monitor button to download the default Windows 64-bit monitoring software. Click on “Other platforms” to reveal the download links for other operating systems.

 

Installation

Installation is as easy as using the windows installer, or untar’ing a file on Linux. Either the firewall can be opened up to the ports required for live monitoring, or you can just email us the test results.

 

Windows Operation

Controlling from the Command Line

 

Linux Operation

On Linux just run ./Start and then run start-log. Notice on my machine it does throw some errors because multicast isn’t available, and in some other environments you might have some other kind of similar log spew. All that matters is that it prints the path to the logfile after you run start-log:
(note I bold and color some text below for emphasis)
This is important: if you SSH into the server, run the monitor in screen or some similar utility. The monitor isn’t a daemon or background process. It’ll die the moment your SSH session times out, unless you do something to keep it up.
lane@lane-debian:~/playground/wpservermonitor-x64_6.6.14851$ ./Start 
[21:42:51.300] Starting logger: ConsoleLogger.
[21:42:51.302] ——————————————————————
Diagnostic settings:
AWS.progress=true
Debug.show_time=true
——————————————————————
[21:42:51.302] Switching to logger: FileAndConsoleLogger: /home/lane/playground/wpservermonitor-x64_6.6.14851/diagnostic.log
[21:42:51.304] Starting logger: FileAndConsoleLogger: /home/lane/playground/wpservermonitor-x64_6.6.14851/diagnostic.log.
 (switched from ConsoleLogger)
[21:42:51.305] ——————————————————————
Diagnostic settings:
AWS.progress=true
Debug.show_time=true
——————————————————————
[21:42:51.806] Web Performance Server Monitoring Agent version 6.6.14851 now monitoring.
[21:42:51.806] Using hostname override: 192.168.10.147
[21:42:51.807] Agent listening on port 1099.
java.net.SocketException: bad argument for IP_MULTICAST_IF: address not bound to any interface
    at java.net.PlainDatagramSocketImpl.socketSetOption0(Native Method)
    at java.net.PlainDatagramSocketImpl.socketSetOption(PlainDatagramSocketImpl.java:74)
    at java.net.AbstractPlainDatagramSocketImpl.setOption(AbstractPlainDatagramSocketImpl.java:309)
    at java.net.MulticastSocket.setInterface(MulticastSocket.java:471)
    at jtools.net.MulticastServerThread.run(MulticastServerThread.java:112)
    at java.lang.Thread.run(Thread.java:745)
[21:42:51.819] Error subscribing for automatic detection from Web Performance Tester
java.net.SocketException: bad argument for IP_MULTICAST_IF: address not bound to any interface
    at java.net.PlainDatagramSocketImpl.socketSetOption0(Native Method)
    at java.net.PlainDatagramSocketImpl.socketSetOption(PlainDatagramSocketImpl.java:74)
    at java.net.AbstractPlainDatagramSocketImpl.setOption(AbstractPlainDatagramSocketImpl.java:309)
    at java.net.MulticastSocket.setInterface(MulticastSocket.java:471)
    at jtools.net.MulticastServerThread.run(MulticastServerThread.java:112)
    at java.lang.Thread.run(Thread.java:745)
[21:42:51.847] Agent waiting for test controller or command to begin recording data.
Use the “quit” command to stop the agent.
start-log
[21:42:55.922] ServerMonitorAgent: prepared for test 2017_07_12_214255_EDT_8cfdc_agent_log. Results will be logged to /home/lane/.webperformance/AgentLogs/2017_07_12_214255_edt_8cfdc_agent_log.dat
Save

Add Your Comment

You must be logged in to post a comment.

Resources

Search

Copyright © 2017 Web Performance, Inc.

A Durham web design company

×

For Prices Call (1) 919-845-7601 9AM-5PM EST

After hours? Prefer email? Just complete this form and we will get back to you as soon as possible with a quote. Please note: Technical support questions should be posted to our online support system.

About You
Product Needs
×

Request a Quote

Our experienced performance engineers have tuned hundreds of systems for companies large and small, and know just where to look, saving you time to market and money. We'll run your website through a complete performance evaluation, then tell you exactly how many users your site can support, including such important details as the effects of "the last mile." We'll also pinpoint potential problem areas and give you a full report detailing what needs to be fixed and where.

About You
Product Needs