Hello,
Sorry, I was wrong. Looks like the timeout already happens in xCAT/rinv and the
gui just reports it. What to some respect is good - now this is a purely
xCAT/hardware issue. The GUI isn't involved any more.
Kind regards
Heiner
/var/log/xcat/command.log:
[Date] 2020-03-25 15:03:46
[ClientType] cli
[Request]rinv * all
[Response]
***: Error: timeout
[NumberNodes] 1
[ElapsedTime] 97.085 s
GUI:
HW_INVENTORY * 2020-03-25 15:03:26 681436ms failed CmdRunTask.doExecute
nas12io04b-i: Error executing rinv command. Exit code = 1; Command output =
; Command error =***: [**]: Error: timeout
On 25.03.20, 16:35, "Billich Heinrich Rainer (ID SD)"
wrote:
Hello,
I did ask about this timeouts when the gui runs HW_INVENTORY before. Now I
would like to know what the exact timeout value in the gui code is and if we
can change it. I want to argue: If a xCat command takes X seconds but the GUI
code timeouts after Y we know the command will fail if X > Y, hence we need to
increase Y unless we can reduce X ...
It's this function which raises the timeout:
at com.ibm.fscc.ras.xcat.InventoryAndStateHelper.runRemoteInventory
If we can't fix the long execution time for the time being, can we raise
the timeout value? I know this most likely is a Firmware issue with little
endian power systems, but we won't update some more time.
Thank you,
Heiner
debug: Running 'xcat.sh rinv '10.250.***' '*' 'all' ' on node localhost
err: com.ibm.fscc.common.exceptions.FsccException: Error executing rinv
command. Exit code = 1; Command output = ; Command error = *: []:
Error: timeout
at
com.ibm.fscc.ras.xcat.InventoryAndStateHelper.runRemoteInventory(InventoryAndStateHelper.java:92)
at
com.ibm.fscc.ras.xcat.InventoryAndStateHelper.buildHardwareInventory(InventoryAndStateHelper.java:175)
at
com.ibm.fscc.ras.xcat.InventoryRefreshTask.inner_run(InventoryRefreshTask.java:94)
at
com.ibm.fscc.ras.xcat.InventoryRefreshTask.run(InventoryRefreshTask.java:72)
at
com.ibm.fscc.common.newscheduler.RefreshTaskExecutor.executeRefreshTask(RefreshTaskExecutor.java:227)
at
com.ibm.fscc.common.newscheduler.RefreshTaskExecutor.executeRefreshTask(RefreshTaskExecutor.java:199)
at
com.ibm.fscc.common.newscheduler.RefreshTaskIds.execute(RefreshTaskIds.java:482)
at
com.ibm.fscc.newcli.commands.task.CmdRunTask.doExecute(CmdRunTask.java:80)
at
com.ibm.fscc.newcli.internal.AbstractCliCommand.execute(AbstractCliCommand.java:156)
at
com.ibm.fscc.cli.CliProtocol.processNewStyleCommand(CliProtocol.java:470)
at com.ibm.fscc.cli.CliProtocol.processRequest(CliProtocol.java:456)
at com.ibm.fscc.cli.CliServer$CliClientServer.run(CliServer.java:97)
...
debug: Running 'mmsysmonc event 'gui' 'xcat_nodelist_ok' -i' ***-i' '
on node localhost
err: ***-i: Error executing rinv command. Exit code = 1; Command output = ;
Command error = nas12io04b: [***]: Error: timeout
,*** -i: Error executing rinv command. Exit code = 1; Command output = ;
Command error =***: [***]: Error: timeout
err: com.ibm.fscc.cli.CommandException: EFSSG1150C Running specified task
was unsuccessful.
at
com.ibm.fscc.cli.CommandException.createCommandException(CommandException.java:117)
at
com.ibm.fscc.newcli.commands.task.CmdRunTask.doExecute(CmdRunTask.java:84)
at
com.ibm.fscc.newcli.internal.AbstractCliCommand.execute(AbstractCliCommand.java:156)
at
com.ibm.fscc.cli.CliProtocol.processNewStyleCommand(CliProtocol.java:470)
at com.ibm.fscc.cli.CliProtocol.processRequest(CliProtocol.java:456)
at com.ibm.fscc.cli.CliServer$CliClientServer.run(CliServer.java:97)
EFSSG1150C Running specified task was unsuccessful.
--
===
Heinrich Billich
ETH Zürich
Informatikdienste
Tel.: +41 44 632 72 56
heinrich.bill...@id.ethz.ch
___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss