1 | 1 | simandl | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" |
2 | | | "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> |
3 | | | |
4 | | | <html lang="en" xml:lang="en"> |
5 | | | <head> |
6 | | | <link rel="stylesheet" type="text/css" media="screen" href= |
7 | | | "weathermap.css" /> |
8 | | | <meta name="generator" content= |
9 | | | "HTML Tidy for Mac OS X (vers 1st December 2004), see www.w3.org" /> |
10 | | | |
11 | | | <title>PHP Weathermap |
12 | 85 | simandl | v0.97a |
13 | 1 | simandl | -FAQ</title> |
14 | | | <style type="text/css" media="print"> |
15 | | | /*<![CDATA[*/ |
16 | | | body { font-size: 12pt; } |
17 | | | a { color: black; text-decoration: underline; font-weight: normal;} |
18 | | | /*]]>*/ |
19 | | | </style> |
20 | | | </head> |
21 | | | |
22 | | | <body> |
23 | | | <div id="frame"> |
24 | | | |
25 | | | <div class="navcontainer"> |
26 | | | <ul id="navlist"> |
27 | | | <li><a href="main.html">Main Page</a></li> |
28 | | | <li><a href="main.html#installation">Installation</a></li> |
29 | | | <li><a href="main.html#basics">Basics</a></li> |
30 | | | <li><a href="faq.html">FAQ and Tips</a></li> |
31 | | | <li><a href="main.html#example">Sample Map</a></li> |
32 | | | <li><a href="cli-reference.html">CLI Reference</a></li> |
33 | | | <li><a href="config-reference.html">Config Reference</a></li> |
34 | | | <li><a href="advanced.html">Advanced Topics</a></li> |
35 | | | <li><a href="editor.html">Editor</a></li> |
36 | | | <li><a href="cacti-plugin.html">Cacti Plugin</a></li> |
37 | | | <li><a href="http://www.network-weathermap.com/">Site</a></li> |
38 | | | </ul> |
39 | | | </div> |
40 | | | |
41 | | | <div id="header"> |
42 | | | <h1>PHP Weathermap |
43 | 85 | simandl | v0.97a |
44 | 1 | simandl | </h1> |
45 | 85 | simandl | <h4>Copyright © 2005-2010 Howard Jones, <tt><a |
46 | 1 | simandl | href="mailto:howie@thingy.com">howie@thingy.com</a></tt>. (<a |
47 | | | href="http://www.network-weathermap.com/">Website</a>)</h4> |
48 | | | </div> |
49 | | | |
50 | | | |
51 | | | <h2><a name="faq" id="faq">FAQ & Useful Tips</a></h2> |
52 | | | |
53 | | | <h3>FAQs</h3> |
54 | | | |
55 | | | <p>Here are a few things that have come up more than once from |
56 | | | previous versions. Also, it's worth checking the <a href= |
57 | | | "http://www.network-weathermap.com/">online |
58 | 85 | simandl | copy</a> of this document, which will be updated over time. </p> |
59 | | | <p class="important">If something isn't described here, <em>check the cacti.log for errors</em>. Weathermap usually produces a useful error message if there is a problem. Next, try setting Cacti's Log Level to DEBUG for 10 minutes, and then have a look in cacti.log. Don't forget to turn the Log Level back down again! </p> |
60 | 1 | simandl | |
61 | | | <dl class="faq"> |
62 | | | <dt><a name="module_not_found"></a>I get some error about 'module not found', or |
63 | | | similar...can you help?</dt> |
64 | | | |
65 | | | <dd><p>The answer is probably no, or at least not directly. In |
66 | | | most cases, this is the result of a missing dependency, |
67 | | | either PHP with no GD, or with an older version, or without |
68 | | | PHP support, or without TrueColour support. I do try to |
69 | | | extend weathermap to make these error messages more |
70 | | | explanatory wherever possible, but ultimately, you need to |
71 | | | get PHP working first. </p><p>Beware that on some systems you can |
72 | | | have a working GD in your 'web' PHP (mod_php) and still have |
73 | | | a non-working command-line PHP - Debian and derivatives (Ubuntu) can suffer from this. </p><p>Also be sure that the PHP you |
74 | | | get from the command-line is the same installation as you |
75 | | | expect - 'which php' and 'whereis php' will provide some *nix |
76 | | | users with an idea that they are running the right one, as |
77 | | | does 'php -m' and 'php -v' (is it the version you expect?). |
78 | | | Also, some packaged PHP systems (MAMP, XAMPP, WAMP etc) have |
79 | | | the module installed, but disabled by default. Check your |
80 | | | php.ini to see if there is a commented-out line like |
81 | 85 | simandl | 'extension=php_gd.dll'. </p> |
82 | | | <p>In 0.91 and newer, you may find the check.php to be useful when figuring out which php.ini and php version you should be looking at - http://yourserver/plugins/weathermap/check.php for the webserver (editor/rebuild now) version, and <tt>php check.php</tt> from the command-line for the CLI (Cacti Poller/command-line tool) version. </p> |
83 | 1 | simandl | </dd> |
84 | | | |
85 | | | <dt><a name="see_nothing"></a>I don't see ANYTHING in the logs when using the Cacti |
86 | | | plugin.</dt> |
87 | | | |
88 | | | <dd><p>Check if this is still the case when Weathermap is the |
89 | | | only plugin. If a plugin dies completely, it takes the poller |
90 | | | and any remaining plugins with it. This appears to be a |
91 | 85 | simandl | problem with some older versions of 'Reports' in particular, where |
92 | 1 | simandl | anything listed after Reports in the plugins[] list will not |
93 | 85 | simandl | be run. </p> |
94 | 1 | simandl | </dd> |
95 | | | |
96 | | | |
97 | | | <dt><a name="nofunction"></a>I get an error message about function_exists()</dt> |
98 | | | |
99 | | | <dd><p>This is PHP telling you that a function that Weathermap requires is not available in your PHP installation. Usually, it's to do with either GD, or FreeType. It can be that you have those libraries, but not current enough versions, or versions compiled without particular options. For example, it's possible to have FreeType installed, GD installed, the php-gd module installed, but that the GD library wasn't compiled with FreeType <em>support</em> so they don't know how to talk to each other. This tends to be less of a problem on packaged systems than where you build your own libraries. </p> |
100 | 85 | simandl | <p>In 0.91 and newer, you may find the check.php to be useful when figuring out which php.ini and php version you should be looking at, and which functions might be missing - http://yourserver/plugins/weathermap/check.php for the webserver (editor/rebuild now) version, and <tt>php check.php</tt> from the command-line for the CLI (Cacti Poller/command-line tool) version. </p> |
101 | 1 | simandl | |
102 | | | </dd> |
103 | | | |
104 | | | <dt><a name="nothumb"></a>My maps don't get created/updated (or "This map hasn't been created yet")</dt> |
105 | | | |
106 | | | <dd><p>This is almost always a permissions problem. Look in your cacti.log for lines starting WEATHERMAP to see what |
107 | | | is going wrong. </p></dd> |
108 | | | |
109 | | | <dt><a name="no_overlib"></a>I've defined some <a href="config-reference.html#LINK_OVERLIBGRAPH">OVERLIBGRAPH</a> lines, but nothing appears |
110 | | | in the map HTML when I use the command-line tool.</dt> |
111 | | | |
112 | | | <dd><p>For historical reasons, the default format for <a href="config-reference.html#GLOBAL_HTMLSTYLE">HTMLSTYLE</a> |
113 | | | is 'static' which avoids javascript. To get the overlib |
114 | | | graphs to appear you need to have <a href="config-reference.html#GLOBAL_HTMLSTYLE">'HTMLSTYLE</a> overlib' near |
115 | 85 | simandl | the top of your map configuration file. </p></dd> |
116 | 1 | simandl | |
117 | 85 | simandl | <dt><a name="overliboffscreen"></a>When I use <a href="config-reference.html#LINK_OVERLIBGRAPH">OVERLIBGRAPH</a> and the pointer is near the right side of the screen, the floating graph disappears off the side of the screen...</dt> |
118 | | | <dd><p>If you set <a href="config-reference.html#LINK_OVERLIBWIDTH">OVERLIBWIDTH</a> and <a href="config-reference.html#LINK_OVERLIBHEIGHT">OVERLIBHEIGHT</a> correctly, then Weathermap can make a better guess about whether to show the map to the left or right. Be careful to set them to the correct value, or you may see strange 'flashing' graphs. The easiest way is to right-click on the graph in your browser and read the sizes from the Properties panel. </p> |
119 | | | <p>Typically one size is right for all your graphs, so this is a good example of something you can add into <a href="config-reference.html#NODE_NODE">NODE</a> DEFAULT (or <a href="config-reference.html#LINK_LINK">LINK</a> DEFAULT). </p> |
120 | | | </dd> |
121 | 1 | simandl | <dt><a name="gauges"></a>The value from my RRD data is much too big!</dt> |
122 | | | |
123 | 85 | simandl | <dd><p>Is it about 8 times too big, by any chance? Historically, Weathermap was mainly used for SNMP Interface statistics, which use bytes-per-second counters ("octet counters" in SNMP-speak). Because of this, the standard RRD datasource plugin multiplies everything by 8, to get back to bits-per-second. New in 0.9, you can get the 'raw' value from an RRD file by using <a href="targets.html#rrd">'gauge:' as a prefix</a>. </p><p>If the value is wrong by some other constant factor, you can use the 'scale:' prefix to multiply or divide by that factor - e.g divide by 1000 to turn a milliseconds value into a 'real' seconds value, or multiply by 1024 to get a kilobytes values from a megabytes one. </p></dd> |
124 | 1 | simandl | |
125 | 85 | simandl | |
126 | 1 | simandl | <dt><a name="timezone"></a>The timestamp on my map is all wrong!</dt> |
127 | | | |
128 | | | <dd><p>I have not seen this one myself, but a Chinese user has, and |
129 | | | it seems that PHP doesn't always use your system timezone correctly. The fix is to edit php.ini to change date.timezone </p></dd> |
130 | | | |
131 | | | |
132 | 85 | simandl | <dt><a name="gdbug"></a>Weathermap just dies without warning on my Debian/Ubuntu system<br/>OR... I get a blank screen in the editor when I add a node<br />OR... I get a segmentation fault when Weathermap runs</dt> |
133 | 1 | simandl | |
134 | | | <dd><p> It's a GD bug. It's documented <a href="http://bugs.libgd.org/4">here</a>, and the reason it mainly affects Debian is that Debian links to the system GD (version 2.0.33) not the built-in PHP one (2.0.28ish). For whatever reason, the problems aren't present in the PHP GD library, which has a different alpha-blending implementation as far as I can see from the docs. </p> |
135 | 85 | simandl | <p>The bugs are apparently fixed in GD 2.0.34, which has been released and is in Debian unstable. Users report that upgrading to the version of libgd2-xpm from unstable will fix this problem if you can't wait, or recompile PHP to use it's own GD library. </p> |
136 | | | <p>Since 0.95, there is a small program supplied with Weathermap to test for this problem. Run <code>php check-gdbug.pgp</code> in the weathermap directory to see if it really is this problem that affects you. </p> |
137 | | | <p>There is more information about fixing this issue for Debian Etch (and perhaps also Ubuntu Edgy) in <a href="http://forums.cacti.net/viewtopic.php?t=21517">this Cacti Forum thread</a>. </p> |
138 | 1 | simandl | </dd> |
139 | | | <dt><a name="icons"></a>Where can I find some icons to use with Weathermap? Why |
140 | | | don't you have any supplied with it?</dt> |
141 | | | |
142 | | | <dd><p> |
143 | | | There are plenty of sources online. A good google search |
144 | | | would be 'visio network icons'. Some to get you started: |
145 | | | |
146 | | | <ul> |
147 | | | <li><a href= |
148 | | | "http://www.cisco.com/web/about/ac50/ac47/2.html">Cisco's |
149 | | | distinctive icons</a> in a number of formats, and I have converted a |
150 | | | set of these into <a href="http://wotsit.thingy.com/haj/cacti/">PNG with transparency</a>, too.</li> |
151 | | | |
152 | | | <li><a href="http://www.nagiosexchange.org/">Nagios |
153 | | | Exchange</a> has icons for network maps</li> |
154 | | | |
155 | | | <li>For your own use only, you could use the ones that |
156 | | | come with MS Visio. Obviously these can't be |
157 | | | redistributed!</li> |
158 | | | </ul>As for the second part, I can't draw, and I don't know |
159 | | | of any freely distributable icons. Feel free to draw some |
160 | 85 | simandl | for me, and make them open source. </p> |
161 | 1 | simandl | </dd> |
162 | | | |
163 | | | <dt><a name="logo"></a>How can I embed an image (like my company's logo) in my |
164 | | | maps? I don't want to have to create a special |
165 | | | background...</dt> |
166 | | | |
167 | | | <dd><p>You can create a <a href="config-reference.html#NODE_NODE">NODE</a> with no links and no label, but |
168 | | | with an <a href="config-reference.html#NODE_ICON">ICON.</a> The <a href="config-reference.html#NODE_ICON">ICON</a> is your logo. You can also use this to |
169 | | | embed images from somewhere else - even dynamically produced |
170 | | | ones - how about MRTG graphs or RRD stripgraphs embedded in |
171 | 85 | simandl | your map? </p></dd> |
172 | 1 | simandl | |
173 | | | <dt><a name="curves"></a>I need to have a link that isn't just a straight |
174 | | | line...how can I do this?</dt> |
175 | | | |
176 | | | <dd><p> |
177 | | | You can use the <a href= |
178 | | | "config-reference.html#LINK_VIA">VIA</a> keyword to make a |
179 | | | link go around corners.: |
180 | | | |
181 | | | <div class="shell"> |
182 | | | <pre> |
183 | | | <a href="config-reference.html#LINK_LINK">LINK</a> bendylink |
184 | | | <a href="config-reference.html#LINK_NODES">NODES</a> node1 node2 |
185 | | | <a href="config-reference.html#LINK_VIA">VIA</a> 200 300 |
186 | | | <a href="config-reference.html#LINK_VIA">VIA</a> 360 240 |
187 | | | </pre> |
188 | 85 | simandl | </div> </p> |
189 | 1 | simandl | </dd> |
190 | | | |
191 | | | <dt><a name="parallel"></a>I need to have more than one link from node A to node B, |
192 | | | but they just overlap...how can I do this?</dt> |
193 | | | |
194 | 85 | simandl | <dd><p>See <a href="http://www.network-weathermap.com/articles/parallel">this article</a> for more about parallel links. </p> |
195 | 1 | simandl | </dd> |
196 | | | |
197 | | | <dt><a name="aggregate"></a>I still have two links, but I use MLPPP, and I want to |
198 | | | see a single link on the map for both physical lines.</dt> |
199 | | | |
200 | | | <dd> |
201 | 85 | simandl | <p>See <a href="http://www.network-weathermap.com/articles/parallel">this article</a> for more about parallel and aggregated links. </p> |
202 | 1 | simandl | </dd> |
203 | | | |
204 | | | <dt><a name="editor_requests"></a>When will you make the editor work like |
205 | | | <em>XYZ</em>?</dt> |
206 | | | |
207 | | | <dd><p>Adding the editor in 0.7 has made adding a new core |
208 | | | weathermap into something that needs more consideration. |
209 | | | Anything that dramatically changes how you make a map (like |
210 | | | the <a href="config-reference.html#LINK_LINK">LINK</a> DEFAULT and <a href="config-reference.html#NODE_NODE">NODE</a> DEFAULT changes for 0.7) should |
211 | | | mean a similarly big change in the editor. All the options |
212 | | | should really be editable from the editor too. In reality, |
213 | | | just getting the editor to run smoothly on more than one |
214 | | | browser is sometimes painful, let alone re-tooling it to add |
215 | | | new features. With that all said, there very likely will be a |
216 | | | new version of the editor in 0.9, with drag & drop |
217 | | | editing, and (more) complete support for all the new features |
218 | | | since 0.6 (which is the version that the editor really was |
219 | | | written for - it was written before I added new 0.7 features. |
220 | 85 | simandl | D'oh!). </p></dd> |
221 | 1 | simandl | |
222 | | | <dt><a name="feature_requests"></a>Will you extend weathermap to do <em>XYZ</em>?</dt> |
223 | | | |
224 | | | <dd><p>It depends. I have an internal idea of what I want |
225 | | | weathermap to be like. I don't want it to feel (too much) |
226 | | | like a small program with everyone's wishlist bolted on |
227 | | | afterwards. If it seems like something that a number of |
228 | | | people could use, and doesn't dramatically change the |
229 | | | direction of the program (it won't get <a href= |
230 | | | "http://en.wikipedia.org/wiki/Zawinski's_Law_of_Software_Envelopment" |
231 | | | title="jwz's law of software envelopment">mail-reading |
232 | | | capability</a> anytime soon), then it stands a better chance. |
233 | | | Things that take dozens of parameters to adjust something |
234 | | | very subtle are less likely. Ultimately, it is a GPLed |
235 | | | program though, so <i>you</i> can <i>always</i> add your own |
236 | | | features! I try to keep a todo list on the website for |
237 | | | current work-in-progress. Obviously, things that <i>I</i> |
238 | 85 | simandl | want are <i>always</i> sensible and useful<tt>:-)</tt> . </p> |
239 | 1 | simandl | |
240 | 85 | simandl | <p>In the past, people have paid to have features added. I have a day job which pays for my food and my mortgage, so this isn't |
241 | | | <em>always</em> a possibility, but it sometimes is. If it's a good idea, then I'll probably add it anyway, but if it's something |
242 | | | special to you, or that you want in a particular timescale, then maybe we can talk! </p> |
243 | | | </dd> |
244 | | | |
245 | 1 | simandl | <dt><a name="repayme"></a>How can I possibly repay you for making my life and work |
246 | | | so much easier?</dt> |
247 | | | |
248 | | | <dd><p>Actually, this one isn't very frequent. If you do find |
249 | | | yourself asking it, feel free to <a href="http://www.network-weathermap.com/support/donate">make a donation, or send a gift,</a> |
250 | | | though. However, I do like to <a href="http://www.network-weathermap.com/contact">hear from users</a> anyway - it's nice to |
251 | 85 | simandl | know that people do use this thing. </p></dd> |
252 | 1 | simandl | </dl> |
253 | | | </div> |
254 | | | </body> |
255 | | | </html> |