Page 1 of 3
Problems after Upgrading to 5.5 - nagvis
Posted: Mon Jul 09, 2018 12:39 pm
by bosecorp
After upgrading to 5.5, I dont seem to be able to access nagvis
The section is not supported in main configuration. Please take a look at the documentation.
Re: Problems after Upgrading to 5.5 - nagvis
Posted: Mon Jul 09, 2018 12:53 pm
by tgriep
Can you post the following files from the Nagios server so we can check their settings?
Code: Select all
/usr/local/nagvis/etc/nagvis.ini.php
/etc/httpd/conf.d/nagvis.conf
Please run the following command as root and post the output to the ticket.
Code: Select all
ls -l /usr/local/nagvis/share/server/core/classes/
Re: Problems after Upgrading to 5.5 - nagvis
Posted: Tue Jul 10, 2018 6:55 am
by bosecorp
Code: Select all
# ls -l /usr/local/nagvis/share/server/core/classes/
total 848
-rwxrwxr-x 1 apache apache 6802 May 4 14:38 CoreAuthHandler.php
-rwxrwxr-x 1 apache apache 6596 May 4 14:38 CoreAuthModMySQL.php
-rwxrwxr-x 1 apache apache 6097 May 4 14:38 CoreAuthModSession.php
-rwxrwxr-x 1 apache apache 6758 May 4 14:38 CoreAuthModSQLite.php
-rwxrwxr-x 1 apache apache 1747 May 4 14:38 CoreAuthModule.php
-rwxrwxr-x 1 apache apache 7440 May 4 14:38 CoreAuthorisationHandler.php
-rwxrwxr-x 1 apache apache 7491 May 4 14:38 CoreAuthorisationModMySQL.php
-rwxrwxr-x 1 apache apache 7499 May 4 14:38 CoreAuthorisationModSQLite.php
-rwxrwxr-x 1 apache apache 1221 May 4 14:38 CoreAuthorisationModule.php
-rwxrwxr-x 1 apache apache 16987 May 4 14:38 CoreBackendMgmt.php
-rwxrwxr-x 1 apache apache 1380 May 4 14:38 CoreExceptions.php
-rwxrwxr-x 1 apache apache 736 May 4 14:38 CoreLog.php
-rwxrwxr-x 1 apache apache 3529 May 4 14:38 CoreMessage.php
-rwxrwxr-x 1 apache apache 4830 May 4 14:38 CoreModAuth.php
-rwxrwxr-x 1 apache apache 7705 May 4 14:38 CoreModAutoMap.php
-rwxrwxr-x 1 apache apache 5563 May 4 14:38 CoreModChangePassword.php
-rwxrwxr-x 1 apache apache 7586 May 4 14:38 CoreModGeneral.php
-rwxrwxr-x 1 apache apache 5089 May 4 14:38 CoreModLogonEnv.php
-rwxrwxr-x 1 apache apache 8226 May 4 14:38 CoreModMainCfg.php
-rwxrwxr-x 1 apache apache 5190 May 4 14:38 CoreModManageBackgrounds.php
-rwxrwxr-x 1 apache apache 3829 May 4 14:38 CoreModManageShapes.php
-rwxrwxr-x 1 apache apache 33296 May 4 14:38 CoreModMap.php
-rwxrwxr-x 1 apache apache 4754 May 4 14:38 CoreModMultisite.php
-rwxrwxr-x 1 apache apache 2135 May 4 14:38 CoreModOverview.php
-rwxrwxr-x 1 apache apache 6466 May 4 14:38 CoreModRoleMgmt.php
-rwxrwxr-x 1 apache apache 1729 May 4 14:38 CoreModSearch.php
-rwxrwxr-x 1 apache apache 2582 May 4 14:38 CoreModuleHandler.php
-rwxrwxr-x 1 apache apache 7408 May 4 14:38 CoreModule.php
-rwxrwxr-x 1 apache apache 2032 May 4 14:38 CoreModUrl.php
-rwxrwxr-x 1 apache apache 9575 May 4 14:38 CoreModUserMgmt.php
-rwxrwxr-x 1 apache apache 24648 May 4 14:38 CoreMySQLHandler.php
-rwxrwxr-x 1 apache apache 2206 May 4 14:38 CoreRequestHandler.php
-rwxrwxr-x 1 apache apache 9025 May 4 14:38 CoreRotation.php
-rwxrwxr-x 1 apache apache 3149 May 4 14:38 CoreSessionHandler.php
-rwxrwxr-x 1 apache apache 19548 May 4 14:38 CoreSQLiteHandler.php
-rwxrwxr-x 1 apache apache 1390 May 4 14:38 CoreTemplateSystem.php
-rwxrwxr-x 1 apache apache 4502 May 4 14:38 CoreUriHandler.php
-rwxrwxr-x 1 apache apache 3271 May 4 14:38 GlobalBackendInterface.php
-rwxrwxr-x 1 apache apache 29820 May 4 14:38 GlobalBackendmerlinmy.php
-rwxrwxr-x 1 apache apache 37824 May 4 14:38 GlobalBackendmklivestatus.php
-rwxrwxr-x 1 apache apache 47666 May 4 14:38 GlobalBackendndomy.php
-rwxrwxr-x 1 apache apache 23050 May 4 14:38 GlobalBackendTest.php
-rwxrwxr-x 1 apache apache 5698 May 4 14:38 GlobalBackground.php
-rwxrwxr-x 1 apache apache 14666 May 4 14:38 GlobalCore.php
-rwxrwxr-x 1 apache apache 5359 May 4 14:38 GlobalFileCache.php
-rwxrwxr-x 1 apache apache 14328 May 4 14:38 GlobalIndexPage.php
-rwxrwxr-x 1 apache apache 9525 May 4 14:38 GlobalLanguage.php
-rwxrwxr-x 1 apache apache 60632 May 4 14:38 GlobalMainCfg.php
-rwxrwxr-x 1 apache apache 68747 May 4 14:38 GlobalMapCfg.php
-rwxrwxr-x 1 apache apache 2395 May 4 14:38 GlobalMap.php
-rwxrwxr-x 1 apache apache 3191 May 4 14:38 GlobalMessage.php
-rwxrwxr-x 1 apache apache 2917 May 4 14:38 NagVisAutomapCfg.php
-rwxrwxr-x 1 apache apache 24903 May 4 14:38 NagVisAutoMap.php
-rwxrwxr-x 1 apache apache 5528 May 4 14:38 NagVisContextMenu.php
-rwxrwxr-x 1 apache apache 7934 May 4 14:38 NagVisHoverMenu.php
-rwxrwxr-x 1 apache apache 3330 May 4 14:38 NagVisHoverUrl.php
-rwxrwxr-x 1 apache apache 1862 May 4 14:38 NagVisMapCfg.php
-rwxrwxr-x 1 apache apache 1860 May 4 14:38 NagVisMap.php
-rwxrwxr-x 1 apache apache 3555 May 4 14:38 NagVisUrl.php
-rwxrwxr-x 1 apache apache 3048 May 4 14:38 NagVisViewAutomapModifyParams.php
-rwxrwxr-x 1 apache apache 2013 May 4 14:38 NagVisViewAutomapToMap.php
-rwxrwxr-x 1 apache apache 2420 May 4 14:38 NagVisViewChangePassword.php
-rwxrwxr-x 1 apache apache 3310 May 4 14:38 NagVisViewManageRoles.php
-rwxrwxr-x 1 apache apache 1775 May 4 14:38 NagVisViewSearch.php
-rwxrwxr-x 1 apache apache 3802 May 4 14:38 NagVisViewUserMgmt.php
drwxrwxr-x 2 apache apache 4096 Apr 18 2011 objects
-rwxrwxr-x 1 apache apache 8884 May 4 14:38 WuiForm.php
-rwxrwxr-x 1 apache apache 13813 May 4 14:38 WuiMapCfg.php
-rwxrwxr-x 1 apache apache 8080 May 11 13:47 WuiViewEditMainCfg.php
-rwxr-xr-x 1 root root 8042 May 11 13:47 WuiViewEditMainCfg.php.bak
-rwxrwxr-x 1 apache apache 2960 May 4 14:38 WuiViewManageBackends.php
-rwxrwxr-x 1 apache apache 2927 May 4 14:38 WuiViewManageBackgrounds.php
-rwxrwxr-x 1 apache apache 3439 May 4 14:38 WuiViewManageMaps.php
-rwxrwxr-x 1 apache apache 2405 May 4 14:38 WuiViewManageShapes.php
-rwxrwxr-x 1 apache apache 18172 May 4 14:38 WuiViewMapAddModify.php
Code: Select all
cat /usr/local/nagvis/etc/nagvis.ini.php
; <?php return 1; ?>
; the line above is to prevent
; viewing this file from web.
; DON'T REMOVE IT!
; ----------------------------
; Default NagVis Configuration File
; At delivery everything here is commented out. The default values are set in the NagVis code.
; You can make your changes here, they'll overwrite the default settings.
; ----------------------------
; ----------------------------
; !!! The sections/variables with a leading ";" won't be recognised by NagVis (commented out) !!!
; ----------------------------
; General options which affect the whole NagVis installation
[global]
; Enable/Disable logging of security related user actions in Nagvis. For
; example user logins and logouts are logged in var/nagvis-audit.log
;audit_log="1"
;
; Defines the authentication module to use. By default NagVis uses the built-in
; SQLite authentication module. On delivery there is no other authentication
; module available. It is possible to add own authentication modules for
; supporting other authorisation mechanisms. For details take a look at the
; documentation.
;authmodule="CoreAuthModSQLite"
;
; Defines the authorisation module to use. By default NagVis uses the built-in
; SQLite authorisation module. On delivery there is no other authorisation
; module available. It is possible to add own authorisation modules for
; supporting other authorisation mechanisms. For details take a look at the
; documentation.
;authorisationmodule="CoreAuthorisationModSQLite"
;
; Dateformat of the time/dates shown in nagvis (For valid format see PHP docs)
;dateformat="Y-m-d H:i:s"
;
; Defines which translations of NagVis are available to the users
;language_available="de_DE,en_US,es_ES,fr_FR,pt_BR"
; Language detection steps to use. Available:
; - User: The user selection
; - Session: Language saved in the session (Usually set after first setting an
; explicit language)
; - Browser: Detection by user agent information from the browser
; - Config: Use configured default language (See below)
;language_detection="user,session,browser,config"
;
; Select language (Available by default: en_US, de_DE, fr_FR, pt_BR)
;language="en_US"
;
; Defines the logon module to use. There are three logon modules to be used by
; default. It is possible to add own logon modules for serving other dialogs or
; ways of logging in. For details take a look at the documentation.
;
; The delivered modules are:
;
; LogonMixed: The mixed logon module uses the LogonEnv module as default and
; the LogonDialog module as fallback when LogonEnv returns no username. This
; should fit the requirements of most environments.
;
; LogonDialog: This is an HTML logon dialog for requesting authentication
; information from the user.
;
; LogonEnv: It is possible to realise a fully "trusted" authentication
; mechanism like all previous NagVis versions used it before. This way the user
; is not really authenticated with NagVis. NagVis trusts the provided username
; implicitly. NagVis uses the configured environment variable to identify the
; user. You can add several authentication mechanisms to your webserver,
; starting from the basic authentication used by Nagios (.htaccess) to single
; sign-on environments.
; Simply set logonmodule to "LogonEnv", put the environment variable to use as
; username to the option logonenvvar and tell the authentication module to
; create users in the database when provided users does not exist. The option
; logonenvcreaterole tells the module to assign the new user to a specific role
; set to empty string to disable that behaviour.
;logonmodule="LogonSession"
;;logonenvvar="REMOTE_USER"
;logonenvcreateuser="1"
;logonenvcreaterole="Guests"
;
; Default rotation time of pages in rotations
;refreshtime=60
;
; Some user information is stored in sessions which are identified by session
; cookies placed on the users computer. The options below set the properties
; of the session cookie.
; Domain to set the cookie for. By default NagVis tries to auto-detect this
; options value by using the webserver's environment variables.
;sesscookiedomain="auto-detect"
; Absolute web path to set the cookie for. This defaults to configured
; paths/htmlbase option
;sesscookiepath="/nagvis"
; Lifetime of the NagVis session cookie in seconds. The default value is set to
; 24 hours. The NagVis session cookie contents will be renewed on every page
; visit. If a session is idle for more time than configured here it will become
; invalid.
;sesscookieduration="86400"
;
; Start page to redirect the user to when first visiting NagVis without
; special parameters.
;startmodule="Overview"
;startaction="view"
; The startshow parameter is only used by some views at the moment. It is used
; by the Map and the AutoMap modules.
;startshow=""
; Path definitions[paths]
; absolute physical NagVis path
;base="/usr/local/nagvis/"
; absolute html NagVis path
;htmlbase="/nagvis"
;absolute html NagVis cgi path
;htmlcgi="/nagios/cgi-bin"
; Default values which get inherited to the maps and its objects
[defaults]
; default backend (id of the default backend)
;backend="live_1"
;background color of maps
;backgroundcolor="#ffffff"
;Enable/Disable the context menu on map objects. With the context menu you are
;able to bind commands or links to your map objects
;contextmenu=1
;Choose the default context template
;contexttemplate="default"
; Enable/Disable changing background color on state changes (Configured color is
; shown when summary state is PENDING, OK or UP)
;eventbackground=0
; Enable/Disable highlighting of the state changing object by adding a flashing
; border
;eventhighlight=1
; The duration of the event highlight in milliseconds (10 seconds by default)
;eventhighlightduration=10000
; The interval of the event highlight in milliseconds (0.5 seconds by default)
;eventhighlightinterval=500
; Enable/Disable the eventlog in the new javascript frontend. The eventlog keeps
; track of important actions and information
;eventlog=0
; Loglevel of the eventlog (available: debug, info, warning, critical)
;eventloglevel="info"
; Height of the eventlog when visible in px
;eventlogheight="75"
; Hide/Show the eventlog on page load
;eventloghidden="1"
; Enable/Disable scrolling to the icon which changed the state when the icon is
; out of the visible scope
;eventscroll=1
; Enable/Disable sound signals on state changes
;eventsound=1
; enable/disable header menu
;headermenu="1"
; header template
;headertemplate="default"
; Enable/Diable the fading effect of the submenus in the header menu
;headerfade=1
; enable/disable hover menu
;hovermenu=1
; hover template
;hovertemplate="default"
; hover menu open delay (seconds)
;hoverdelay=0
; show children in hover menus
;hoverchildsshow=1
; limit shown child objects to n
;hoverchildslimit="10"
; order method of children (desc: descending, asc: ascending)
;hoverchildsorder="asc"
; sort method of children (s: state, a: alphabetical)
;hoverchildssort="s"
; default icons
;icons="std_medium"
; recognize only hard states (not soft)
;onlyhardstates=0
; recognize service states in host/hostgroup objects
;recognizeservices=1
; show map in lists (dropdowns, index page, ...)
;showinlists=1
; show map in multisite snapin
;showinmultisite=1
; Name of the custom stylesheet to use on the maps (The file needs to be located
; in the share/nagvis/styles directory)
;stylesheet=""
; target for the icon links
;urltarget="_self"
; URL template for host object links
;hosturl="[htmlcgi]/status.cgi?host=[host_name]"
; URL template for hostgroup object links
;hostgroupurl="[htmlcgi]/status.cgi?hostgroup=[hostgroup_name]"
; URL template for service object links
;serviceurl="[htmlcgi]/extinfo.cgi?type=2&host=[host_name]&service=[service_description]"
; URL template for servicegroup object links
;servicegroupurl="[htmlcgi]/status.cgi?servicegroup=[servicegroup_name]&style=detail"
; URL template for nested map links
;mapurl="[htmlbase]/index.php?mod=Map&act=view&show=[map_name]"
backend="nagiosxi"
; Options to configure the Overview page of NagVis
[index]
; Color of the overview background
;backgroundcolor=#ffffff
; Set number of map cells per row
;cellsperrow=4
; enable/disable header menu
;headermenu="1"
; header template
;headertemplate="default"
; Enable/Disable automap listing
;showautomaps=1
; Enable/Disable map listing
;showmaps=1
; Enable/Disable geomap listing
; Note: It is disabled here since it is unfinished yet and not for production
; use in current 1.5 code.
;showgeomap=0
; Enable/Disable rotation listing
;showrotations=1
; Enable/Disable map thumbnails
;showmapthumbs=0
; Options for the Automap
[automap]
; Default URL parameters for links to the automap
;defaultparams="&childLayers=2"
; Default root host (NagVis uses this if it can't detect it via NDO)
;defaultroot=""
; Path to the graphviz binaries (dot,neato,...); Only needed if not in ENV PATH
;graphvizpath="/usr/bin/"
; Show the automap in the lists (Map index and dropdown menu in header)
;showinlists=1
;Options for the WUI
;[wui]
;Users which are allowed to change the NagVis configuration (comma separated list)
;allowedforconfig=EVERYONE
;auto update frequency
;autoupdatefreq=25
;enable/disable header menu in the WUI
;headermenu="1"
;header template to use in the WUI
;headertemplate="default"
;map lock time (minutes)
;maplocktime=5
; Options for the new Javascript worker
[worker]
; The interval in seconds in which the worker will check for objects which need
; to be updated
;interval=10
; The maximum number of parameters used in ajax http requests
; Some intrusion detection/prevention systems have a problem with
; too many parameters in the url. Give 0 for no limit.
;requestmaxparams=0
; The maximum length of http request urls during ajax http requests
; Some intrusion detection/prevention systems have a problem with
; queries being too long
;requestmaxlength=1900
; The retention time of the states in the frontend in seconds. The state
; information will be refreshed after this time
;updateobjectstates=30
; ----------------------------
; Backend definitions
; ----------------------------
; Example definition of a livestatus backend.
; In this case the backend_id is live_1
; The path /usr/local/nagios/var/rw has to exist
;[backend_live_1]
;backendtype="mklivestatus"
; The status host can be used to prevent annoying timeouts when a backend is not
; reachable. This is only useful in multi backend setups.
;
; It works as follows: The assumption is that there is a "local" backend which
; monitors the host of the "remote" backend. When the remote backend host is
; reported as UP the backend is queried as normal.
; When the remote backend host is reported as "DOWN" or "UNREACHABLE" NagVis won't
; try to connect to the backend anymore until the backend host gets available again.
;
; The statushost needs to be given in the following format:
; "<backend_id>:<hostname>" -> e.g. "live_2:nagios"
;statushost=""
socket="tcp:127.0.0.1:7668"
; Example definition for a MySQL backend
; in this example the ID of the Backend is "ndomy_1" you can define another ID.
[backend_nagiosxi]
; type of backend - MUST be set
backendtype="ndomy"
; The status host can be used to prevent annoying timeouts when a backend is not
; reachable. This is only useful in multi backend setups.
;
; It works as follows: The assumption is that there is a "local" backend which
; monitors the host of the "remote" backend. When the remote backend host is
; reported as UP the backend is queried as normal.
; When the remote backend host is reported as "DOWN" or "UNREACHABLE" NagVis won't
; try to connect to the backend anymore until the backend host gets available again.
;
; The statushost needs to be given in the following format:
; "<backend_id>:<hostname>" -> e.g. "live_2:nagios"
;statushost=""
; hostname for NDO-db
;dbhost="localhost"
; portname for NDO-db
;dbport=3306
; database name for NDO-db
;dbname="nagios"
; username for NDO-db
;dbuser="root"
; password for NDO-db
;dbpass=""
; prefix for tables in NDO-db
;dbprefix="nagios_"
; instance name for tables in NDO-db
;dbinstancename="default"
; maximum delay of the NDO Database in seconds
;maxtimewithoutupdate=180
; path to the cgi-bin of this backend
;htmlcgi="/nagios/cgi-bin"
dbhost="localhost"
dbport=3306
dbname="nagios"
dbuser="nagios"
dbpass="nagios"
dbinstancename="localhost"
maxtimewithoutupdate=180
dbprefix="nagios_"
; Example definition of a Merlin backend
; in this example the ID of the Backend is "merlinmy_1" you can define another ID.
[backend_merlinmy_1]
; type of backend - MUST be set
backendtype="merlinmy"
; hostname for Merlin db
;dbhost="localhost"
; portname for Merlin db
;dbport=3306
; database name for Merlin db
;dbname="merlin"
; username for Merlin db
;dbuser="merlin"
; password for Merlin db
;dbpass="merlin"
; maximum delay of the Merlin Database in seconds
;maxtimewithoutupdate=180
; path to the cgi-bin of this backend
;htmlcgi="/nagios/cgi-bin"
; ----------------------------
; Rotation pool definitions
; ----------------------------
; in this example the browser switches between the maps demo and demo2 every 15
; seconds, the rotation is enabled by url: index.php?rotation=demo
[rotation_demo]
; These steps are rotated. The "Demo2:" is a label which is being displayed in
; the index pages rotation list.
; You may also add external URLs as steps. Simply enclose the url using []
; instead of the map name. It is also possible to add automaps to rotations,
; add an @ sign before the automap name to add an automap to the rotation.
maps="CoreDC-Enviroment,Internet-Enviroment"
; rotation interval (seconds)
interval=15
; ------------------------------------------------------------------------------
; Below you find some advanced stuff
; ------------------------------------------------------------------------------
; Configure different state related settings
[states]
; State coverage/weight: This defines the state handling behaviour. For example
; a critical state will cover a warning state and an acknowledged critical
; state will not cover a warning state.
;
; These options are being used when calculating the summary state of the map
; objects. The default values should fit most needs.
;
;unreachable=9
;unreachable_ack=5
;unreachable_downtime=5
;down=8
;down_ack=5
;down_downtime=5
;critical=7
;critical_ack=5
;critical_downtime=5
;warning=6
;warning_ack=4
;warning_downtime=4
;unknown=3
;unknown_ack=2
;unknown_downtime=2
;error=3
;error_ack=2
;error_downtime=2
;up=1
;ok=1
;pending=0
;
; Colors of the different states. The colors are used in lines and hover menus
; and for example in the frontend highlight and background event handler
;
;unreachable_bgcolor=#F1811B
;unreachable_color=#F1811B
;unreachable_ack_bgcolor=
;unreachable_downtime_bgcolor=
;down_bgcolor=#FF0000
;down_color=#FF0000
;down_ack_bgcolor=
;down_downtime_bgcolor=
;critical_bgcolor=#FF0000
;critical_color=#FF0000
;critical_ack_bgcolor=
;critical_downtime_bgcolor=
;warning_bgcolor=#FFFF00
;warning_color=#FFFF00
;warning_ack_bgcolor=
;warning_downtime_bgcolor=
;unknown_bgcolor=#FFCC66
;unknown_color=#FFCC66
;unknown_ack_bgcolor=
;unknown_downtime_bgcolor=
;error_bgcolor=#0000FF
;error_color=#0000FF
;up_bgcolor=#00FF00
;up_color=#00FF00
;ok_bgcolor=#00FF00
;ok_color=#00FF00
;pending_bgcolor=#C0C0C0
;pending_color=#C0C0C0
;
; Sound of the different states to be used by the sound eventhandler in the
; frontend. The sounds are only being fired when changing to some
; worse state.
;
;unreachable_sound=std_unreachable.mp3
;down_sound=std_down.mp3
;critical_sound=std_critical.mp3
;warning_sound=std_warning.mp3
;unknown_sound=
;error_sound=
;up_sound=
;ok_sound=
;pending_sound=
; -------------------------
; EOF
; -------------------------
root@usvanagiospxi3:(07-10 07:57): /root
Code: Select all
# cat /etc/httpd/conf.d/nagvis.conf
# NagVis Apache2 sample configuration file
#
# #############################################################################
Alias /nagvis "/usr/local/nagvis/share"
<Directory "/usr/local/nagvis/share">
Options FollowSymLinks
AllowOverride None
#Order allow,deny
#i$Allow from all
Require all granted
# To enable Nagios basic auth on NagVis use the following options
# Just uncomment it. Maybe you need to adjust the path to the
# Auth user file.
#
# If you use the NagVis internal auth mechanism based on the web
# for you won't need this.
#
##Authname "NagVis Access"
##AuthType Basic
##AuthUserFile /usr/local/nagios/etc/htpasswd.users
#Require all granted
# With installed and enabled mod_rewrite there are several redirections
# available to fix deprecated and/or wrong urls. None of those rules is
# mandatory to get NagVis working.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /nagvis
# Use mod_rewrite for old url redirection even if there are php files which
# redirect the queries itselfs. In some cases the mod_rewrite redirect
# is better than the php redirect.
RewriteCond %{REQUEST_URI} ^/nagvis(/index\.php|/|)(\?.*|)$
RewriteRule ^(index\.php|)(\?.*|)$ /nagvis/frontend/nagvis-js/$1$2 [R=301,L]
RewriteCond %{REQUEST_URI} ^/nagvis/config\.php.*$
RewriteRule ^config\.php(.*) /nagvis/frontend/wui/$1 [R=301,L]
# Redirect old regular map links
RewriteCond %{REQUEST_URI} ^/nagvis/frontend/nagvis-js
RewriteCond %{QUERY_STRING} map=(.*)
RewriteRule ^(.*)$ /nagvis/frontend/nagvis-js/index.php?mod=Map&act=view&show=%1 [R=301,L]
# Redirect old wui map links
RewriteCond %{REQUEST_URI} ^/nagvis/frontend/wui
RewriteCond %{QUERY_STRING} map=(.*)
RewriteRule ^(.*)$ /nagvis/frontend/wui/index.php?mod=Map&act=edit&show=%1 [R=301,L]
# Redirect old rotation calls
RewriteCond %{REQUEST_URI} ^/nagvis/frontend/nagvis-js
RewriteCond %{QUERY_STRING} !mod
RewriteCond %{QUERY_STRING} rotation=(.*)
RewriteRule ^(.*)$ /nagvis/frontend/nagvis-js/index.php?mod=Rotation&act=view&show=%1 [R=301,L]
</IfModule>
</Directory>
Re: Problems after Upgrading to 5.5 - nagvis
Posted: Tue Jul 10, 2018 10:15 am
by tgriep
I would have to see the upgrade.log file to be sure but it looks like the Nagvis component did not get fully updated.
The upgrade.log file would be in the /tmp/nagiosxi folder if you ran the manual XI upgrade.
Lets manually upgrade Nagvis again and see if starts to function for you.
First, if you have any Nagvis Maps created, back them up first. They are located in this folder.
Run the following as root to download XI 5.5 so we know that you have a fresh copy.
Code: Select all
cd /tmp
rm -rf nagiosxi xi*.tar.gz
wget https://assets.nagios.com/downloads/nagiosxi/5/xi-5.5.0.tar.gz
tar xzf xi-latest.tar.gz
cd /tmp/nagiosxi/subcomponents/xicomponents/components/nagvis
Then edit the upgrade.sh script to comment out the section that checks the version of Naviis so change this from
Code: Select all
if ! grep -q "NagVis 1.5" /usr/local/nagvis/README; then
echo "You must have NagVis version 1.5.x to automatically upgrade."
echo "Note: In this situation we recommend installing the latest version of XI"
echo "on a clean system for best results."
exit 0
fi
to
Code: Select all
#if ! grep -q "NagVis 1.5" /usr/local/nagvis/README; then
# echo "You must have NagVis version 1.5.x to automatically upgrade."
# echo "Note: In this situation we recommend installing the latest version of XI"
# echo "on a clean system for best results."
# exit 0
#fi
Save the file and run the upgrade
Then check this file
Code: Select all
/usr/local/nagvis/etc/nagvis.ini.php
To verify that the logonmodule option is set to the following
If not, update it, save the file and restart apache by running
service httpd restart
After this, see if you can login to the Nagvis GUI.
Re: Problems after Upgrading to 5.5 - nagvis
Posted: Tue Jul 10, 2018 12:33 pm
by bosecorp
the nagvis directory doesnt exist. I see a file called nagvis.zip
Re: Problems after Upgrading to 5.5 - nagvis
Posted: Tue Jul 10, 2018 2:29 pm
by lmiltchev
the nagvis directory doesnt exist. I see a file called nagvis.zip
Unzip the nagvis.zip file:
then cd into the nagivis folder:
Proceed with the tgriep's instructions.
Let us know if this helped. Thank you!
Re: Problems after Upgrading to 5.5 - nagvis
Posted: Tue Jul 10, 2018 3:31 pm
by bosecorp
upgrade done, but still have the same issue
root@usvanagiospxi3:(07-10 16:34): /tmp/nagiosxi/subcomponents/xicomponents/components/nagvis
# ./upgrade.sh
Backing up old NagVis install ...
tar: Removing leading `/' from member names
Loaded plugins: amazon-id, rhui-lb, search-disabled-repos, versionlock
Package rsync-3.1.2-4.el7.x86_64 already installed and latest version
Nothing to do
| Do you want to update the backend configuration? [n]: mv: cannot move ‘/usr/local/nagvis’ to ‘/usr/local/nagvis.old-2018-07-10_16:35:07’: Device or resource busy
| Error moving old NagVis /usr/local/nagvis.old-2018-07-10_16:35:07 Return Code: 1
Updating for apache 2.4 if we need to...
Redirecting to /bin/systemctl reload httpd.service
NagVis upgraded to 1.9.8-nagios
Re: Problems after Upgrading to 5.5 - nagvis
Posted: Tue Jul 10, 2018 3:39 pm
by scottwilkerson
Do you have this server modified for /usr/local/nagvis is a symlink?
Re: Problems after Upgrading to 5.5 - nagvis
Posted: Tue Jul 10, 2018 3:42 pm
by bosecorp
NO, it's an actual mount point. so the script wont be able to mv that directory.
Re: Problems after Upgrading to 5.5 - nagvis
Posted: Tue Jul 10, 2018 3:49 pm
by scottwilkerson
You will have to modify the install script, Nagios XI doesn't expect to to be a mount point, it expects it to just be a folder.
This is unfortunately some of the pain that comes with modifying the server like this.