<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Failed to create graph with error code 1 - 2.0-RC3 (i386) built on Thu Jun 23]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">There is a problem displaying some!!! of the graphs in RRD.</p>
<p dir="auto">Version 2.0-RC3 (i386)<br />
built on Thu Jun 23 13:05:26 EDT 2011<br />
CPU Type Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz</p>
<p dir="auto"><img src="http://s4.postimage.org/eqdmk8t1q/pfsensegraph2.gif" alt="" class=" img-fluid img-markdown" /></p>
<p dir="auto"><img src="http://s4.postimage.org/eqd9by13i/pfsensegraph.gif" alt="" class=" img-fluid img-markdown" /></p>
<p dir="auto">Can I clear this error? The error manifested after this problem <a href="http://forum.pfsense.org/index.php/topic,38093.0.html" target="_blank" rel="noopener noreferrer nofollow ugc">http://forum.pfsense.org/index.php/topic,38093.0.html</a><br />
After updating pfsense to latest build the error is still there.</p>
<p dir="auto">Tnx!</p>
]]></description><link>https://forum.netgate.com/topic/34799/failed-to-create-graph-with-error-code-1-2-0-rc3-i386-built-on-thu-jun-23</link><generator>RSS for Node</generator><lastBuildDate>Sat, 14 Mar 2026 09:49:51 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/34799.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 24 Jun 2011 04:06:49 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Failed to create graph with error code 1 - 2.0-RC3 (i386) built on Thu Jun 23 on Wed, 20 Jul 2011 18:59:13 GMT]]></title><description><![CDATA[<p dir="auto">ok updated to the latest build and cleared the graphs with the new button.</p>
<p dir="auto">this has resulted in all the graphs working except the quality graphs</p>
<p dir="auto">I was also getting the following errors:<br />
php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: No DS called 'inpass' in '/var/db/rrd/wan-traffic.rrd'/usr/bin/nice -n20 /usr/local/bin/rrdtool graph /tmp/wan-traffic.rrd-month.png –start 1308421501 --end 1311186301 --vertical-label "bits/sec" --color SHADEA#eeeeee --color SHADEB#eeeeee --title "<code>hostname</code> - WAN :: Traffic - 1 month - 1 hour average" --height 200 --width 620 DEF:wan-in_bytes_pass=/var/db/rrd/wan-traffic.rrd:inpass:AVERAGE DEF:wan-out_bytes_pass=/var/db/rrd/wan-traffic.rrd:outpass:AVERAGE DEF:wan-in_bytes_block=/var/db/rrd/wan-traffic.rrd:inblock:AVERAGE DEF:wan-out_bytes_block=/var/db/rrd/wan-traffic.rrd:outblock:AVERAGE CDEF:"wan-in_bits_pass=wan-in_bytes_pass,8,<em>" CDEF:"wan-out_bits_pass=wan-out_bytes_pass,8,</em>" CDEF:"wan-in_bits_block=wan-in_bytes_block,8,<em>" CDEF:"wan-out_bits_block=wan-out_bytes_block,8,</em>" CDEF:"wan-in_bytes=wan-in_bytes_pass,wan-in_bytes_block,+" CDEF:"wan-out_bytes=wan-out_bytes_pass,wan-out_bytes_block,</p>
<p dir="auto">but now Jul 20 19:57:16 apinger: Error while feeding rrdtool: Broken pipe</p>
]]></description><link>https://forum.netgate.com/post/288061</link><guid isPermaLink="true">https://forum.netgate.com/post/288061</guid><dc:creator><![CDATA[rikrobson]]></dc:creator><pubDate>Wed, 20 Jul 2011 18:59:13 GMT</pubDate></item><item><title><![CDATA[Reply to Failed to create graph with error code 1 - 2.0-RC3 (i386) built on Thu Jun 23 on Tue, 28 Jun 2011 13:24:02 GMT]]></title><description><![CDATA[<p dir="auto">That depends on what the error is. If if's something minor, it may be something that's been fixed on a newer snapshot than you have. If it's something bigger, you may just need to remove your RRD files and start over with the graphs. I just added a button to the RRD settings page yesterday that will reset the RRD data.</p>
]]></description><link>https://forum.netgate.com/post/284946</link><guid isPermaLink="true">https://forum.netgate.com/post/284946</guid><dc:creator><![CDATA[jimp]]></dc:creator><pubDate>Tue, 28 Jun 2011 13:24:02 GMT</pubDate></item></channel></rss>