Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

StorMan


StorMan provides a number of files containing important information for troubleshooting and for diagnosis.

To ensure the best possible support in case of problems, you are recommended to recreate the problem after setting the highest debug level on the StorMan server for the duration of recreation process by StorMan CLI:

storparam -debug 5

More detailed logging information you may get using the parameters -debugcom and –traceworker of the StorMan CLI storparam.

All these settings are also available on the WebUI.

Please use the StorMan CLI to provide the current configuration data:

stormandb -dump

Afterwards, collect the following files and transmit them to your support organization:

  1. The StorMan logging files with format stormanTraceyyyy-mm-dd in the ./log directory for the day(s) concerned.

  2. The StorMan logging files with format stormanTraceExtendedyyyy-mm-dd in the ./log directory. These files contain very detailed informations about all activities of StorMan in the last hour.
  3. The configuration file of the StorMan server smserver.ini in the ./config directory.

  4. The saved StorMan database files AddData.sql and AddTables.sql (created by stormandb –dump) in the ./backup directory.

These files are located in the /var/opt/SMAWstor/StorMan directory for Linux environments and in the C:\Programme\Fujitsu\StorMan directory for Windows environments.

Additional support for Linux (including M2000)

On Linux platforms and on M2000 you may also get all diagnostic information as a g-zipped tar archive by using the StorMan CLI


storadmin getlogs

On M2000 you need user role service or administrator.

The resulting file is located at:

  • /var/opt/SMAWstor/StorMan/log/stormanLogs_<uname>_YYYY.MM.DD_HHMMSS.tar.gz for M2000 and Linux


Please note that storadmin getlogs automatically removes previously created diagnostic information (zipped tar archive) before collecting diagnostic information. Therefor previously created StorMan log files should be saved if needed, before calling storadmin getlogs.

To remove all log files use (this should be done after saving the results to save disk space)

storadmin remlogs

On the WebUI you may create the diagnostic information and download it directly to your local server.

StorMan writes eventually occurring cores to the following directories:

  • Windows: <installation directory>\log

  • Linux: /var/opt/SMAWstor/StorMan/log, only if no other directory or program is specified in /proc/sys/kernel/core_pattern

  • M2000: in the globally specified diectory /var/crash/core/storman