Search the Community

Showing results for tags 'linux'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • LogicModule Exchange
    • LM Exchange
    • LM Staff Contributions
  • Product Announcements
    • LogicMonitor Notices
  • LogicMonitor Product Q&A
    • Feature Requests
    • Ask the Community
    • From the Front

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 8 results

  1. You might have received an alert saying your linux based device has just rebooted, but you know that it has been up a long time. A switch might have just sent an alert for every interface flapping when they have all been up solidly. The important question to ask here is how long has the device been up? If its been up for 497 days,994 days,1491 days or any multiple of 497 then you are seeing the 497 day bug, that hits almost every linux based device that is up for a good length of time. Anything using a kernel less than 2.6 computes the system uptime based on the internal jiffies counter, which counts the time since boot in units of 10 milliseconds, or jiffies. This counter is a 32-bit counter, which has a maximum value of 2^32, or 4,294,967,296. When the counter reaches this value (after 497 days, 2 hours, 27 minutes, and 53 seconds, or approximately 16 months), it wraps back around to zero and continues to increment. This can result in alerts about reboots that didn’t happen and cause switches to report a flap on all interfaces. Systems that use 2.6 Kernel and properly supply a 64 bit counter will still alert incorrectly when the 64 bit counter wraps. A 32 bit counter can hold 4,294,967,295( /4,294,967,295864000/8640000 = 497.1 days) A 64 bit counter can hold 18,446,744,073,709,551,615 . (18,446,744,073,709,551,615/8640000 = 2135039823346 days or 5849424173 years) Though I expect in 6,000 million years we will all have other things to worry over.
  2. Hello all, Recently, I had mounted a RHEL ISO on a /data/rhel_iso directory, on a system that is monitored with LogicMonitor. 5 minutes later I received an alert about 105% utilization of /data/rhel_iso, which is reasonable but strange, as ISO takes same space as the files inside it. When I unmounted the ISO I got an alert of a filesystem that is not responding. How to disable those ISO related alerts? They are irrational. Many thanks in advance, Szymon
  3. Exporting Netflow from Linux with softflowd NetFlow is an industry standard network protocol for monitoring traffic flows across a network interface. It is used most commonly by devices like firewalls, routers, and switches, but some software packages make it possible to export Netflow data from a server operating system - in this case Linux (with softflowd) - to a Netflow collector (LogicMonitor) for traffic analysis. Ubuntu Documentation here: http://manpages.ubuntu.com/manpages/xenial/man8/softflowd.8.html The following assumes you have an Ubuntu device in your portal which you can access with sudoer permissions. It also assumes Netflow has been enabled for the device and the collector in question. Install softflowd: sudo apt-get install softflowd Open /etc/default/softflowd for editing: sudo nano /etc/default/softflowd Set the value for INTERFACE and add the destination ip:port (<collectorIP>:2055) under OPTIONS. Other options are available, check the link above for full documentation. # # configuration for softflowd # # note: softflowd will not start without an interface configured. # The interface softflowd listens on. You may also use "any" to listen # on all interfaces. INTERFACE="eth0" # Further options for softflowd, see "man softflowd" for details. # You should at least define a host and a port where the accounting # datagrams should be sent to, e.g. # OPTIONS="-n 127.0.0.1:9995" OPTIONS="-n 192.168.170.130:2055" Save your changes by pressing Ctrl-O, then exit nano by pressing Ctrl-X. Restart softflowd. sudo service softflowd restart Add a rule to the firewall to allow traffic on 2055. sudo ufw allow 2055 CentOs This is a bit more work since you can't just install a package; you'll need to download the source and compile. Most of the information here comes from https://www.scribd.com/doc/199440303/Cacti-Netflow-Collector-Flowview-and-Softflowd More good info: https://thwack.solarwinds.com/thread/59620 Check to see if you have the compiler installed. which gcc If you don't get /usr/bin/gcc as the response, you'll need to install it. sudo yum install gcc Install libpcap-devel (you'll need this to compile softflowd). sudo yum install libpcap-devel Download the softflowd source. wget https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/softflowd/softflowd-0.9.9.tar.gz Make sure you're in the directory where you saved the download, then untar the dowloaded source files. tar -xzvf softflowd-0.9.9.tar.gz Switch to the softflowd directory, then run the commands to compile and install it. cd softflowd-0.9.9 ./configure make make install Now we want to have softflowd start when the system boots. We'll need to add a line to the end of /etc/rc.d/rc.local. Use your device's interface after -i and your collector's IP address after -n. sudo nano /etc/rc.d/rc.local <add the following line to the end of the file> /usr/local/sbin/softflowd -i eth0 -n 10.13.37.111:2055 Save your changes with Ctrl-O, exit nano with Ctrl-X. Make sure /etc/rc.d/rc.local is executable. sudo chmod +x /etc/rc.d/rc.local Open port 2055 in the firewall so the collector can receive the data. sudo firewalld-cmd --zone=public --add-port=2055/tcp --permanent Reboot the machine for all changes to take effect. *Original guide courtesy of @Kurt Huffman at LogicMonitor
  4. A pair of modules that will perform the following: NVidia GPU Core Temperatures NVidia GPU Fan Speed LM Locator: 2J3MEX Requirements Linux NVidia's set of proprietary video drivers and tools. Specifically the nvidia-smi binary. ssh.user && ssh.user
  5. A very basic DataSource that leverages lm_sensors to pull CPU temps. It does this over ssh via the cli. LM Locator: KT3TXK Requirements: lm_sensors package installed on target device(s) ssh.user and ssh.pass properties must be set CPU Core Instances: Overview Graph of Temps:
  6. In case some of you are not aware, Microsoft released Linux-compatible version of PowerShell. I would love to see the Linux Collector come bundled with PowerShell so it can be supported natively. Just for giggles, I installed PowerShell on a random RHEL 7 collector and tried to use the !posh debug command, but sadly it didn't work .
  7. So this is less of an ask the community and more of a show the community. Ive written some Ruby code that makes it much much easier to use the LogicMonitor API. It does all the signing for you so you can just focus on your API calls and worry less about the secure signing. https://gist.github.com/ITJamie/4937de9139c682c02c34ff2d17051d58 It uses the following rest-client library https://github.com/rest-client/rest-client and injects the authentication method into the rest-client library. Ive included some examples of usage in my gist. Let me know if your having difficulty and i will test and patch as needed For an example of how easy this makes using the Rest API temp_url = @URL + '/service/services' response = RestClient.get(temp_url) # Printing API server response puts "\nServer response: #{response}"
  8. Good Day LM Folks, I'm a DBA setting up LM for our databases. Setup went well but i've noticed that newly mounted disk is not automatically added on the monitors. Do we need to restart the SNMP collectors? Thanks, mac