zmstat-chart java.text.ParseException: Found two charts that write..

[gkchicago]

Hello, I'm trying to generate the graphs described in this article:
Server Monitoring - Zimbra :: Wiki

But am receiving the errors below. Please advise, thank you!

[zimbra@zimbra01 2009-10-26]$ zmstat-chart -c /opt/zimbra/conf/zmstat-chart.xml -s /opt/zimbra/zmstat/2009-10-26 -d /opt/zimbra/zmstat/2009-10-26/charts
java.text.ParseException: Found two charts that write zimbra01.linngroup.com_cciss_c0d0p1_part_thruput.png
        at com.zimbra.perf.chart.ChartUtil.validateChartSettings(ChartUtil.java:947)
        at com.zimbra.perf.chart.ChartUtil.getAllChartSettings(ChartUtil.java:413)
        at com.zimbra.perf.chart.ChartUtil.doit(ChartUtil.java:339)
        at com.zimbra.perf.chart.ChartUtil.main(ChartUtil.java:306)

usage: Usage: zmstat-chart -c <arg> -s <arg> -d <arg> [options]
    --aggregate-end-at <arg>     if specified, aggregate computation ends
                                 at this timestamp (MM/dd/yyyy HH:mm:ss)
    --aggregate-start-at <arg>   if specified, aggregate computation
                                 starts at this timestamp (MM/dd/yyyy HH:mm:ss)
 -c,--conf <arg>                 chart configuration xml files
 -d,--destdir <arg>              directory where the generated chart files
                                 are saved
    --end-at <arg>               if specified, ignore all samples after
                                 this timestamp (MM/dd/yyyy HH:mm:ss)
 -h,--help                       prints this usage screen
    --no-summary                 skip summary data generation
 -s,--srcdir <arg>               one or more directories where the csv
                                 files are located
    --start-at <arg>             if specified, ignore all samples before
                                 this timestamp (MM/dd/yyyy HH:mm:ss)
    --title <arg>                chart title; defaults to last directory
                                 name of --srcdir value

Config generated with:

[zimbra@zimbra01 ~]$ zmstat-chart-config > /opt/zimbra/conf/zmstat-chart.xml

It appears that the csv files are in the zmstat directory.. I also tried gunzipping them first with no change in the error message.

[zimbra@zimbra01 2009-10-26]$ ls -l /opt/zimbra/zmstat/2009-10-26/
total 1524
drwxr-x--- 2 zimbra zimbra   4096 Oct 27 15:25 charts
-rw-r----- 1 zimbra zimbra  85733 Oct 27 00:00 cpu.csv.gz
-rw-r----- 1 zimbra zimbra   8030 Oct 27 00:00 fd.csv.gz
-rw-r----- 1 zimbra zimbra  19426 Oct 27 00:00 imap.csv.gz
-rw-r----- 1 zimbra zimbra 295782 Oct 27 00:00 io-x.csv.gz
-rw-r----- 1 zimbra zimbra 151138 Oct 27 00:00 io.csv.gz
-rw-r----- 1 zimbra zimbra 137887 Oct 27 00:00 mailboxd.csv.gz
-rw-r----- 1 zimbra zimbra   3837 Oct 27 00:03 mtaqueue.csv.gz
-rw-r----- 1 zimbra zimbra 482584 Oct 27 00:00 mysql.csv.gz
-rw-r----- 1 zimbra zimbra  45053 Oct 27 00:00 pop3.csv.gz
-rw-r----- 1 zimbra zimbra  63455 Oct 27 00:00 proc.csv.gz
-rw-r----- 1 zimbra zimbra  32168 Oct 27 00:00 soap.csv.gz
-rw-r----- 1 zimbra zimbra   7334 Oct 27 00:00 threads.csv.gz
-rw-r----- 1 zimbra zimbra 182722 Oct 27 00:00 vm.csv.gz

[zimbra@zimbra01 2009-10-26]$ ls -l /opt/zimbra/zmstat/2009-10-26/charts/
total 0

[gkchicago]

Upon looking closer at the zmstat-chart.xml I realize now that it is generating something tailored to my machine. So I spotted duplicate entries for these disk devices and simply commented out the duplicates and everything has run fine.

If anyone at Zimbra interested in debugging this further to see why these duplicates appeared when running zmstat-chart-config post to this thread and I will share whatever information I can.

[phoenix]

Upon looking closer at the zmstat-chart.xml I realize now that it is generating something tailored to my machine. So I spotted duplicate entries for these disk devices and simply commented out the duplicates and everything has run fine.

If anyone at Zimbra interested in debugging this further to see why these duplicates appeared when running zmstat-chart-config post to this thread and I will share whatever information I can.

You should file a bug report - check if one already exists for this problem before filing.