Huawei Ocean Stor issue

Hello,

I deployed Xormon-NG to plan the replacement of Stor2rrd and Lpar2rrd.

Four Huawei Ocean Stor device has no value. Both 5300 and both 6000.

No error for 5000 and OceanProtect x8000

In the log ~/xormon-ng/server-nest/logs/oceanstor-error.log, I found this :

2024-08-13 11:35:02: [OceanStor-Device] No data found for cmd performace_statistic/cur_statistic_data?CMO_STATISTIC_UUID=216:0&CMO_STATISTIC_DATA_ID_LIST=22,25,28,370,384,385,23,26,182,232,233,523,524,525,511,770,771,805,806,807 description : Invalid performance indicator IDs exist in the specified performance indicator list. error_code : 1073951268

2024-08-13 11:35:02: [OceanStor-Device] No data found for cmd performace_statistic/cur_statistic_data?CMO_STATISTIC_UUID=216:3&CMO_STATISTIC_DATA_ID_LIST=22,25,28,370,384,385,23,26,182,232,233,523,524,525,511,770,771,805,806,807 description : Invalid performance indicator IDs exist in the specified performance indicator list. error_code : 1073951268

2024-08-13 11:35:02: [OceanStor-Device] API command storagepool_data_info/0 failed

2024-08-13 11:35:02: [OceanStor-Device] {"data":{},"error":{"code":-1,"description":"The operation fails.","suggestion":"Try again. If the problem persists, contact technical support engineers."}}Can't use string ("") as a HASH ref while "strict refs" in use at /home/xormon/xormon-ng/server-nest/microservices/oceanstor/OCEANSTOR.pm line 1144.

Connection test is Ok for theses devices.

5300 and 6000 work fine with Stor2rrd.


Good job for the NG release, it's very pleasant.

Regards,

Frédéric.

Comments

  • Hello Frédéric,


    There was a bug:

    1. Apply this fix:

    https://download.xormon.com/patch/1.5-83-g84c83/OCEANSTOR.pm.gz


    Gunzip it and copy to this path in your Xormon application directory (755, xormon owner):

    server-nest/microservices/oceanstor/

    -rwxrwxr-x 1 xormon xormon 94667 14. Aug 07.38 OCEANSTOR.pm


    If your web browser gunzips it automatically then just rename it: mv OCEANSTOR.pm.gz OCEANSTOR.pm

    Make sure the filesize is the same as in the example above


    2.

    su -l xormon

    cd /home/xormon/xormon-ng/server-nest

    npx pm2 restart oceanstor


    3. Wait about 1 hour, then refresh xormon UI (ctrl+F5).

    Let us know

    Thank you

  • Hello Lukas,

    The fix is the same as file installed.

    xormon@xormonng:~/xormon-ng/server-nest/microservices/oceanstor$ ls -l OCEAN*

    -rwxr-xr-x 1 xormon xormon 94667 Aug 14 06:43 OCEANSTOR.pm

    -rwxr-xr-x 1 xormon xormon 94667 Aug 14 06:42 OCEANSTOR.pm.orig

    xormon@xormonng:~/xormon-ng/server-nest/microservices/oceanstor$ diff OCEANSTOR.pm OCEANSTOR.pm.orig

    xormon@xormonng:~/xormon-ng/server-nest/microservices/oceanstor$


    So, i have the same error in log file.


    Version deployed :

    XorMon 1.5.0

    Node.js v20.16.0

    Frontend 1.1-395-g9bc405e3

    Database 2.15.2

    Appliance 1.5.0


    Regards,

    Frédéric.

  • Hello Frédéric,


    I apologize. My mistake.

    1. Apply this fix:

    https://download.xormon.com/patch/1.5-100-g9e21e/OCEANSTOR.pm.gz

    Gunzip it and copy to this path in your Xormon application directory (755, xormon owner):

    server-nest/microservices/oceanstor/

    -rwxrwxr-x 1 xormon xormon 95008 14. Aug 11.03 OCEANSTOR.pm


    If your web browser gunzips it automatically then just rename it: mv OCEANSTOR.pm.gz OCEANSTOR.pm

    Make sure the filesize is the same as in the example above

    2.

    su -l xormon

    cd /home/xormon/xormon-ng/server-nest

    npx pm2 restart oceanstor


    3. Wait about 1 hour, then refresh xormon UI (ctrl+F5).


    Let us know

    Thank you

  • Thanks Lukas, it's perfect !

    Metrics appear for the missing array.

    Regards,

    Frédéric.

Sign In or Register to comment.