Back to Geneos FAQ

Netprobe - Unable to start up Netprobe

Related to Copied

Netprobe startup issue, unable to start Netprobe, Netprobe crashes on startup

Problem Copied

Unable to start up Netprobe

Possible Causes Copied

There are numerous reasons why the Netprobe would not start. In this article we will discuss some of the common ones.

• Root Cause 1: Incomplete or incompatible libraries
• Root Cause 2: Port not available
• Root Cause 3: Not enough system resources
• Root Cause 4: Netprobe crashes on startup
• Root Cause 5: Others

Possible Solutions Copied

• Solution Root Cause 1 : Incomplete or incompatible libraries
  • Make sure that you are using the correct netprobe binary and version for your platform. Make sure as well that you are deploying the netprobe on a supported platform. Please see our Compatibility Matrix.
  • Check for missing libraries originally packaged with the netprobe. There are instances where the netprobe needs to run a certain plugin but the library needed to run the plugin is missing. This will cause the netprobe to crash at startup.
    • Example scenario:
      • User creates a bloomberg-bpipe sampler but libblpapi3_64.so is missing from the netprobe directory.
      • If the netprobe still crashes once libblpapi3_64.so file has been set in Netprobe package’s lib64 folder, make sure to set the path in the LD_LIBRARY_PATH.
  • The Linux version of the netprobe depends on certain libraries to run. Not all libraries are packaged with the netprobe. Therefore, you may need to install these libraries independently. Please refer to Considerations for Linux - Library dependencies. Sample log below.
    • [mdprd@lonrs10998 netprobe] $ ./netprobe.linux_64: /lib64/libc.so.6: version `GLIBC_2.7' not found (required by /opt/app/production/geneos/Netprobe-NWM-ITRS01/netprobe/lib64/libcrypto.so.1.1)
• Solution Root Cause 2: Port not available
  • This should be easy to spot on the netprobe log. Make sure that you use an open port. Check as well that no other applications or processes are using the port for the netprobe. Sample log below.
    • Jul 16 07:51:07> INFO: CONMGR bind() failed on fd 4, port 7036. Details: tryListen(); None; errno=98 (Address already in use)
• Solution Root Cause 3: Not enough system resources
  • Check if the host has enough CPU, memory, storage, max number of processes, max number of open file descriptors, etc. to run the netprobe. Please see below system requirements:
    • Windows
    • Linux and other platforms
• Solution Root Cause 4: Netprobe crashes on startup
  • On some occasions certain plugins cause the Netprobe to crash at startup. Try to remove all samplers assigned to the managed entities that use the netprobe. Save the setup on GSE and then start the netprobe. If it starts properly, add the samplers one by one. Eventually you will be able to isolate which plugin is causing the crash. Please refer to My gateway/netprobe crashed, what information do I need to gather first before opening a ticket and reporting the issue to ITRS?
• Solution Root Cause 5: Others
  • Check the netprobe log to see warning and error messages.

Related Articles Copied

• Start the Netprobe on Windows.
• Start the Netprobe on Linux and other platforms.
• Why is the Netprobe not starting on a Windows Server?
• Netprobe FAQs
• Netprobe documentation.