-- mvh - Vidar >From magnus at ntnu.no Wed Jun 1 17:01:33 2005 From: magnus at ntnu.no (Magnus Nordseth) Date: Wed Jun 1 16:01:35 2005 Subject: [Nav-users] Another questions about vlanPlot In-Reply-To: s29dd972.064@HVO-3.hivolda.no References: s29dd972.064@HVO-3.hivolda.no Message-ID: 20050601140133.GH17281@stud.ntnu.no Peder Magne Sefland: > I'm running nav3 on debian-sarge and found the file under > > locate vlanPlot.py > /usr/lib/python2.3/site-packages/nav/web/pyproxy/vlanPlot.py > /usr/lib/python2.3/site-packages/nav/web/pyproxy/vlanPlot.pyc > /usr/lib/python2.3/site-packages/nav/web/pyproxy/vlanPlot.pyo > > I made a copy of the original file and tried to do some changes here, > but no success. > How do I manually set the hostname or ip-address? It assumes you are running tomcat, the cricket front end and the NAV frontend on the same server. This could be a bit inflexible for some installations. The hostname is defined on the line server = req.server.server_hostname which extracts the hostname from the current http request. You can modify this line so it suits your needs. However, this hostname is used for vPServerURL, lastURL, cricketURL and netflowURL. If you want different hostnames for only some of them, you have to modify how the params are defined. I probably should move all this out to a config file some day. Also note that you have to restart apache after you have made your changes to ensure mod_python reloads the new file. HTH and best regards, -- Magnus Nordseth echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc >From peder.sefland at hivolda.no Wed Jun 1 17:59:56 2005 From: peder.sefland at hivolda.no (Peder Magne Sefland) Date: Wed Jun 1 17:00:38 2005 Subject: SV: Re: Re: [Nav-users] Another questions about vlanPlot Message-ID: s29de9ae.024@HVO-3.hivolda.no Thank you Kristian and Magnus. I can see the local gatewayswitch(GSW) and all the switches(SW) under it. I don't see any data being collected, but maybe I need to set up a link between our gatewayswitch uninett's router before I can see any traffic. Peder >>> Kristian Eide kreide@gmail.com 01.06.2005 15:58:09 >>> > /usr/lib/python2.3/site-packages/nav/web/pyproxy/vlanPlot.py > /usr/lib/python2.3/site-packages/nav/web/pyproxy/vlanPlot.pyc > /usr/lib/python2.3/site-packages/nav/web/pyproxy/vlanPlot.pyo I see on our production server we have: /usr/local/nav/lib/python/nav/web/pyproxy/vlanPlot.py You can probably edit the file in site-packages as well. You may need to delete the two last files and restart apache for the changes to take effect. The hostname can be manually set in this file, e.g. add: server = 'myserver.domain.no' Right above the line params = "". -- Kristian >From kreide at gmail.com Thu Jun 2 00:08:53 2005 From: kreide at gmail.com (Kristian Eide) Date: Wed Jun 1 23:15:50 2005 Subject: [Nav-users] BoxDown 0 d, 00 h, 00 min In-Reply-To: s29b066b.091@HVO-3.hivolda.no References: s29b066b.091@HVO-3.hivolda.no Message-ID: 200506012308.58888.kreide@gmail.com > I have tried your solution Kristian, and it got better. I don't get > BoxDown 0 d, 00 h, 00 min anymore, but I still get too many alerts with > very short time between down and up. After having looked at the logs I now know why this is happening. If a box is going down and up with very short intervals it can happen that eventengine sends out messages right after a box is reported down like your are experiencing. I will try to come up with a change to eventengine to prevent this from happening. -- Kristian