Skip to content

Support

5.1k Topics 22.0k Posts

Questions about installing, configuring and using NetXMS.

  • Building a Filter Script for a Template

    2
    0 Votes
    2 Posts
    20k Views
    T
    I figured this out, thanks.. I will post the code later this week
  • Moving a lot of nodes between zones

    3
    0 Votes
    3 Posts
    21k Views
    M
    hmmm i took the easy way, got the helpdesk to do the manual work...
  • V2.1-M2 build problem

    2
    0 Votes
    2 Posts
    21k Views
    G
    Never mind I got it fixed... I manually removed all nextms libs in my /usr/local/lib  and ran make install again and it worked not sure what happend 
  • Script as Instance Discovery

    3
    1
    0 Votes
    3 Posts
    23k Views
    L
    Thanks For the Help. It works. 
  • Automated Interface Name poll Script

    5
    0 Votes
    5 Posts
    28k Views
    A
    Configueration Poll is set to default  -> 3600
  • Script access to Mapping Table data comments

    2
    0 Votes
    2 Posts
    15k Views
    V
    No, you can only get value. Best regards, Victor
  • {instance} is showing the actual value of the OID

    4
    1
    0 Votes
    4 Posts
    23k Views
    V
    Hi, this is correct behavior - instance here is OID instance, which is determined by OID suffix (part after walk base). If you want to give other name to the instance, you can use instance filter to change it (and in DCI description you can use {instance-name} then). For example: return %(true, $1, "New name for " . $1); Best regards, Victor
  • Migrating NetXMS database on New NetXMS server

    5
    0 Votes
    5 Posts
    27k Views
    A
    Thanks for the help ! Best Regards, Adrian
  • Expand All in conjunction with Filter

    1
    0 Votes
    1 Posts
    14k Views
    S
    When filtering objects it would be very useful to have Expand All functionality to show where in the Infrastructure Services tree the node is referenced.
  • Ready templates

    2
    0 Votes
    2 Posts
    17k Views
    L
    https://www.netxms.org/forum/general-support/sharing-standard-templates-for-netxms/
  • NetXMS and Fail2Ban

    3
    0 Votes
    3 Posts
    19k Views
    M
    Currently everything points at my NetXMS server. I could, I suppose, put in a dst-nat rule above the NetXMS server that redirects all port 514 to a different box that processes it. it's probably something I'd forget while troubleshooting a broken syslog system in the future. 
  • Startup Script

    5
    0 Votes
    5 Posts
    31k Views
    M
    Looks like I use this one: #!/bin/sh # vim: syntax=sh ### BEGIN INIT INFO # Provides: netxms-server # Required-Start: $network $local_fs nxagentd # Required-Stop: # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: NetXMS server # Description: Network monitoring daemon, which collect and process metrics # from native and SNMP agents. ### END INIT INFO # Author: Alex Kirhenshtein <[email protected]> PATH=/sbin:/usr/sbin:/bin:/usr/bin DESC="NetXMS server" NAME=netxmsd DAEMON=/usr/bin/netxmsd DAEMON_ARGS="-d" PIDFILE=/var/run/$NAME.pid SCRIPTNAME=/etc/init.d/$NAME # Exit if the package is not installed [ -x $DAEMON ] || exit 0 # Read configuration variable file if it is present [ -r /etc/default/$NAME ] && . /etc/default/$NAME # Load the VERBOSE setting and other rcS variables . /lib/init/vars.sh # Define LSB log_* functions. # Depend on lsb-base (>= 3.0-6) to ensure that this file is present. . /lib/lsb/init-functions # # Function that starts the daemon/service # do_start() { # Return # 0 if daemon has been started # 1 if daemon was already running # 2 if daemon could not be started start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \ || return 1 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \ $DAEMON_ARGS \ || return 2 # Add code here, if necessary, that waits for the process to be ready # to handle requests from services started subsequently which depend # on this one. As a last resort, sleep for some time. } # # Function that stops the daemon/service # do_stop() { # Return # 0 if daemon has been stopped # 1 if daemon was already stopped # 2 if daemon could not be stopped # other if a failure occurred start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME RETVAL="$?" [ "$RETVAL" = 2 ] && return 2 # Wait for children to finish too if this is a daemon that forks # and if the daemon is only ever run from this initscript. # If the above conditions are not satisfied then add some other code # that waits for the process to drop all resources that could be # needed by services started subsequently. A last resort is to # sleep for some time. start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON [ "$?" = 2 ] && return 2 # Many daemons don't delete their pidfiles when they exit. rm -f $PIDFILE return "$RETVAL" } # # Function that sends a SIGHUP to the daemon/service # do_reload() { # # If the daemon can reload its configuration without # restarting (for example, when it is sent a SIGHUP), # then implement that here. # start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME return 0 } case "$1" in start) [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC " "$NAME" do_start case "$?" in 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; esac ;; stop) [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME" do_stop case "$?" in 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; esac ;; status) status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $? ;; #reload|force-reload) # # If do_reload() is not implemented then leave this commented out # and leave 'force-reload' as an alias for 'restart'. # #log_daemon_msg "Reloading $DESC" "$NAME" #do_reload #log_end_msg $? #;; restart|force-reload) # # If the "reload" option is implemented then remove the # 'force-reload' alias # log_daemon_msg "Restarting $DESC" "$NAME" do_stop case "$?" in 0|1) do_start case "$?" in 0) log_end_msg 0 ;; 1) log_end_msg 1 ;; # Old process is still running *) log_end_msg 1 ;; # Failed to start esac ;; *) # Failed to stop log_end_msg 1 ;; esac ;; *) echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2 exit 3 ;; esac : There was also this one: #! /bin/sh ### BEGIN INIT INFO # Provides: netxmsd # Required-Start: $remote_fs nxagentd # Required-Stop: $remote_fs # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: NetXMS server initscript # Description: NetXMS server startup script ### END INIT INFO # Author: Raden Solutions <[email protected]> # Do NOT "set -e" # PATH should only include /usr/* if it runs after the mountnfs.sh script PATH=/sbin:/usr/sbin:/bin:/usr/bin DESC="NetXMS Server" NAME=netxmsd DAEMON=~BINDIR~/$NAME DAEMON_ARGS="-d" PIDFILE=/var/run/$NAME.pid SCRIPTNAME=/etc/init.d/$NAME # Exit if the package is not installed [ -x "$DAEMON" ] || exit 0 # Read configuration variable file if it is present [ -r /etc/default/$NAME ] && . /etc/default/$NAME # Load the VERBOSE setting and other rcS variables . /lib/init/vars.sh # Define LSB log_* functions. # Depend on lsb-base (>= 3.0-6) to ensure that this file is present. . /lib/lsb/init-functions # # Function that starts the daemon/service # do_start() { # Return # 0 if daemon has been started # 1 if daemon was already running # 2 if daemon could not be started start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \ || return 1 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \ $DAEMON_ARGS \ || return 2 # Add code here, if necessary, that waits for the process to be ready # to handle requests from services started subsequently which depend # on this one. As a last resort, sleep for some time. } # # Function that stops the daemon/service # do_stop() { # Return # 0 if daemon has been stopped # 1 if daemon was already stopped # 2 if daemon could not be stopped # other if a failure occurred start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME RETVAL="$?" [ "$RETVAL" = 2 ] && return 2 # Wait for children to finish too if this is a daemon that forks # and if the daemon is only ever run from this initscript. # If the above conditions are not satisfied then add some other code # that waits for the process to drop all resources that could be # needed by services started subsequently. A last resort is to # sleep for some time. start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON [ "$?" = 2 ] && return 2 # Many daemons don't delete their pidfiles when they exit. rm -f $PIDFILE return "$RETVAL" } # # Function that sends a SIGHUP to the daemon/service # do_reload() { # # If the daemon can reload its configuration without # restarting (for example, when it is sent a SIGHUP), # then implement that here. # start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME return 0 } case "$1" in start) [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME" do_start case "$?" in 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; esac ;; stop) [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME" do_stop case "$?" in 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;; 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;; esac ;; #reload|force-reload) # # If do_reload() is not implemented then leave this commented out # and leave 'force-reload' as an alias for 'restart'. # #log_daemon_msg "Reloading $DESC" "$NAME" #do_reload #log_end_msg $? #;; restart|force-reload) # # If the "reload" option is implemented then remove the # 'force-reload' alias # log_daemon_msg "Restarting $DESC" "$NAME" do_stop case "$?" in 0|1) do_start case "$?" in 0) log_end_msg 0 ;; 1) log_end_msg 1 ;; # Old process is still running *) log_end_msg 1 ;; # Failed to start esac ;; *) # Failed to stop log_end_msg 1 ;; esac ;; status) status_of_proc $DAEMON $NAME && exit 0 || exit $? ;; *) #echo "Usage: $SCRIPTNAME {start|stop|restart|reload|force-reload|status}" >&2 echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload|status}" >&2 exit 3 ;; esac : The second one was modified around the time I was trying to fix it. However now it's starting fine on reboot.  *sigh*
  • Remote power and temperature monitoring

    3
    0 Votes
    3 Posts
    22k Views
    A
    Thank you.  I have reached out to them.
  • Template DCI & Instance name in transformation script

    6
    0 Votes
    6 Posts
    23k Views
    V
    $dci is global variable containing reference to current DCI object. You can find class description here: https://wiki.netxms.org/wiki/NXSL:DCI. Instance is it's attribute. Transformation scripts in templates never executed - it is just a template for real DCIs. It is not possible to disable DCI from script. Best regards, Victor
  • Powershell commands in Agent config

    8
    0 Votes
    8 Posts
    24k Views
    V
    It is supposed to be generic. I'll check it on Windows 7. Best regards, Victor
  • Network map link speed colours

    2
    0 Votes
    2 Posts
    11k Views
    A
    There are two options (all accessible in link properties, right click on the link to open): you add label on the link (in "Data Sources"), label color will reflect active threshold on the DCI create dummy node (with IP=0.0.0.0), and add it to General->Color->Based on object status Then create scripted DCI on this node. Select Other Options -> Use this DCI for node status calculation. Script should return 0-4 (normal-critical) based on current link usage. Don't forget to set retention time to "Do not save to the database"
  • IP conflict with deleted/changed node

    2
    0 Votes
    2 Posts
    11k Views
    V
    Hi, seems to be a bug. We will investigate it further. I've created issue in our tracker (https://track.radensolutions.com/issue/NX-1148). Best regards, Victor
  • LogWatch EventRecordId

    2
    0 Votes
    2 Posts
    11k Views
    V
    Hi, currently no. Feel free to register feature request for that. Best regards, Victor
  • False Agent Detection

    2
    0 Votes
    2 Posts
    16k Views
    V
    Hi, seems to be a bug. It could also be misconfiguration in NAT - if switch IP address NAT'ed to some node with agent you'll get this effect. Try to access switch IP address with nxget tool (nxget ip_addr Agent.Version) - will it respond? I also suggest to upgrade top latest stable version (2.0.8). Best regards, Victor
  • Screenshot enabled on view only accounts?

    2
    0 Votes
    2 Posts
    13k Views
    V
    Hi, currently screenshot requires read access. We can change it to separate access right in next release. I've added it as feature request: https://track.radensolutions.com/issue/NX-1147. Best regards, Victor