No capacity and perf data captured for DataDomain (DD860)

ravikum_hp

Hello Stor2rrd Team,

After discovering the DD860 in Stor2rrd, I can see only configuration and Health status of DD. Capacity and Perf data are not captured even after a week time.

DD860 OS version is 5.4 and Stor2rrd version is 2.20

Below are the errors in log file and same are repeating every 5 mins.

**** Invalid argument: "ddboost". Valid strings are: nfs, cifs, repl, net, iostat, sysstat.

Sat Feb 10 16:10:05 2018: command failed: system show stats view nfs cifs repl ddboost net interval 150 count 3 /storage/stor2rrd/bin/datadomainperf.pl:3586 :

Sat Feb 10 16:10:11 2018: command failed: mtree show performance /data/col1/Tesco1 last 1hours /storage/stor2rrd/bin/datadomainperf.pl:3611 :

Sat Feb 10 16:10:12 2018: command failed: mtree show performance /data/col1/aftd last 1hours /storage/stor2rrd/bin/datadomainperf.pl:3611 :

Sat Feb 10 16:10:12 2018: command failed: mtree show performance /data/col1/backup last 1hours /storage/stor2rrd/bin/datadomainperf.pl:3611 :

Sat Feb 10 16:10:13 2018: command failed: mtree show performance /data/col1/myppnwkrho01 last 1hours /storage/stor2rrd/bin/datadomainperf.pl:3611 :

**** Invalid number: "custom-view".

Sat Feb 10 16:10:14 2018: command failed: system show performance custom-view throughput protocol cache-miss latency compression utilization duration 10 min interval 5

min /storage/stor2rrd/bin/datadomainperf.pl:3611 :

Sat Feb 10 16:10:22 2018: File not exist /storage/stor2rrd/data/MYPPNWKRHO03/IOSTATS/05/perf_stat.txt: No such file or directory/storage/stor2rrd/bin/datadomainperf.pl:

3661 : No such file or directory

Use of uninitialized value $timestamp in subtraction (-) at /storage/stor2rrd/bin/datadomainperf.pl line 2626.

Use of uninitialized value $timestamp_end in localtime at /storage/stor2rrd/bin/datadomainperf.pl line 3750.

Use of uninitialized value $timestamp_end in localtime at /storage/stor2rrd/bin/datadomainperf.pl line 3751.

Sat Feb 10 16:10:22 2018: File not exist /storage/stor2rrd/data/MYPPNWKRHO03/IOSTATS/05/system_stat.txt: /storage/stor2rrd/bin/datadomainperf.pl:3661 :

Use of uninitialized value $timestamp in subtraction (-) at /storage/stor2rrd/bin/datadomainperf.pl line 612.

Use of uninitialized value $timestamp_end in localtime at /storage/stor2rrd/bin/datadomainperf.pl line 3750.

Use of uninitialized value $timestamp_end in localtime at /storage/stor2rrd/bin/datadomainperf.pl line 3751.

Use of uninitialized value $timestamp in subtraction (-) at /storage/stor2rrd/bin/datadomainperf.pl line 241.

Use of uninitialized value $timestamp_end in localtime at /storage/stor2rrd/bin/datadomainperf.pl line 3750.

Use of uninitialized value $timestamp_end in localtime at /storage/stor2rrd/bin/datadomainperf.pl line 3751.

Use of uninitialized value $timestamp in subtraction (-) at /storage/stor2rrd/bin/datadomainperf.pl line 453.

Use of uninitialized value $timestamp_end in localtime at /storage/stor2rrd/bin/datadomainperf.pl line 3750.

Use of uninitialized value $timestamp_end in localtime at /storage/stor2rrd/bin/datadomainperf.pl line 3751.

**** Invalid argument: "ddboost". Valid strings are: nfs, cifs, repl, net, iostat, sysstat.

Lukas

Hello,

Send us logs pls.
Note a short problem description in the text field of the upload form.

cd /home/stor2rrd/stor2rrd # or where is your STOR2RRD working dir
ps -ef |egrep "2rrd" > tmp/ps_log.txt
tar cvhf logs.tar logs etc tmp/*txt data/MYPPNWKRHO03/IOSTATS/*
gzip -9 logs.tar

Send us logs.tar.gz via https://upload.stor2rrd.com
You might even attach screenshots when it helps in understanding of the issue.


Thank you

ravikum_hp

Hello Lukas,
Uploaded the logs. Can you review them?
Thanks

Pavel

Hi,

you have older firmware version 5.4 which does not recognize some command parameters we expect (we actually support 5.5+)
We will fix that during next week.

fmacor

Has this been solved? I'm running into the same issue with the same DD OS rel

fmacor

STOR2RRD v2.31-1

Pavel

Hi,

unfortunatelly appeared that v5.4 is quite different and implementation effort would be very high.

We have gave it up, it is not priority for us. Supported are 5.5+