Loading...
Loading...
Repeated error seen in collecting log for VPlex Collector as below: WARNING -- [2018-03-26 08:02:00 SAST] -- TableDataset::execute(): Found a table line without the expected columns length (193 vs 151): director-1-2-B,2018-03-26 06:01:59,1522044119085,25654,149,146,24479,8851,9218,9420,9371,0,772,319,24156,0,0,no data,no data,580,255,0,0,0,0,no data,no data,1531,1624,0,0,0,0,no data,no data,24814,4022,0,0,0,0,0,0,0,0,0,0,0,0,0,0,580,255,0,0,0,0,0,0,0,0,0,0,0,0,no data,no data,0,0,0,0,0,0,0,0,531,335,0,0,0,0,0,0,1096,11158,47,541,160,1264,162923,4823209,1608,87015,6354978,421,0,936.968,0,0,2127.966,0.0,0,6,0,0,1475.533,107,177,855,244,0.8,630,53485,793,80,951,943,682,0.2,3,723,17.8,1420,1851,3292,1993,0,0,0,0,107,174,133,226,2409,12793,7210,11633,0,38149,1.86,0,0,1389,34045,50428,0,599,62,0,28,20,1383,0,0,0,0,0,54909,640,0,0,0,0,28.2,0,744,791,0,1.86,0,354,2837,0,145,0,0,28542,0.0,0,0,0,659.554,876.568,0.0,20,20,17,1,3,1,2,1 with context CKM00xxxx-CKM00xxxx (CLUSTER1-VPLEX0): {vplex.id=VPLEX-CKM00xxxx-CKM00xxxx, cluster1.collectionHost=xxxx, cluster1.password={97B1F5CB472C25B01630BF86446CCFB909A2B9DAC09B836AE0EC2675C102BB444362BF28851EB57E23F248764A19F2A0}, cluster1.host=xx.xx.xx.xx, cluster1.username=service, cluster1.serialnb=CKM00xxxx, POLLING_COUNTER=1637, type=Metro, cluster1.collectionInstance=emc-vplex_2} WARNING -- [2018-03-26 08:02:00 SAST] -- TableDataset::execute(): Found a table line without the expected columns length (193 vs 151): director-1-3-B,2018-03-26 06:01:34,1522044094085,226,193,212,273,6331,4309,3994,6317,0,20.8,159,6844,0,0,no data,no data,107,58,0,0,0,0,no data,no data,296,82,0,0,0,0,no data,no data,363,113,0,0,0,0,0,0,0,0,0,0,0,0,0,0,107,58,0,0,0,0,0,0,0,0,0,0,0,0,no data,no data,0,0,0,0,0,0,0,0,64.4,48,0,0,0,0,0,0,10683,1648,7,535,178,669,61073,1712572,543,8742,3526974,172,0,395.413,0,0,1539.063,0.0,0,1.2,0,0,1544.0,132,1.2,160,308,289,0,7,1082,88.9,0,694,587,49.4,0,0.6,78,1379,1138,1554,1588,0,0,0,0,82.2,1.2,159,230,1469,9.6,2687,16568,0,14006,1.67,0,0,176,20734,864,0,31.2,62,0,25.2,10,601,0,0,0,0,0,1378,473,0,0,0,0,25.2,0,128,144,0,1.67,0,33,216,0,2,0,0,320,0.0,0,0,0,796.891,1177.501,0.0,9,10,10,0,1,2,1,0 with context CKM00xxxx-CKM00xxxx (CLUSTER1-VPLEX0): {vplex.id=VPLEX-CKM00xxxx-CKM00xxxx, cluster1.collectionHost=xxxx, cluster1.password={97B1F5CB472C25B01630BF86446CCFB909A2B9DAC09B836AE0EC2675C102BB444362BF28851EB57E23F248764A19F2A0}, cluster1.host=xx.xx.xx.xx, cluster1.username=service, cluster1.serialnb=CKM00xxxx, POLLING_COUNTER=1637, type=Metro, cluster1.collectionInstance=emc-vplex_2}
Director logs for cluster 2 are present in cluster 1 with a header containing 150 fields of old data and a header field containing 192. When log in to VPlex at location "/home/service# ./get-director-data.py," the new log has a column length of 192 fields whereas old logs had 150 fields. Ran directory listing of "/var/log/VPlex/cli/" It showed the logs for old date: director-2-1-A,2015-10-02 director-2-2-B,2015-10-02 director-2-3-A,2015-10-02 director-2-4-A,2015-10-02 director-2-2-A,2015-10-02 director-2-3-B,2015-10-02 director-2-1-B,2015-10-02 director-2-4-B,2015-10-02 These old logs had the column length of 150.
Deleted the director logs in "/var/log/VPlex/cli/" for old date where the data contains 150 field. The new data contains 192 fields.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.