locked
"Error getting detailed results from a client" RRS feed

  • Question

  • I have (8) Win XP SP3 32-bit clients, the SMB/CIFS server is Windows 2008 R2 x64, and the controller is a Win XP SP3 32-bit machine.

    Here is my truncated output from fsct run on the controller. Any idea why this is happening, “Error getting detailed results from a client” message?"


    C:\fsct>fsct run controller /server fsct-winsrv /password xxxxxxxxxx /volumes "E:" /clients "fsctxp-01 fsctxp-02 fsctxp-03 fsctxp-04 fsctxp-05 fsctxp-06 fsctxp-07 fsctxp-08" /min_users 1 /max_users 8 /step 1 /duration 600 /workload HomeFolders /verbose debug 

     

    server's name: fsct-winsrv

    server's password: xxxxxxxxxx

    volumes: E:

    clients' names: fsctxp-01 fsctxp-02 fsctxp-03 fsctxp-04 fsctxp-05 fsctxp-06 fsctxp-07 fsctxp-08

    min users: 1

    max users: 8

    sweep step: 1

    test's duration: 600

    workload to use: HomeFolders

    Starting the controller.

    Removing directory: results.

    Directory results removed.

     

    Test is initializing.

    Adding client fsctxp-01 to a list of clients.

    Adding client fsctxp-02 to a list of clients.

    Adding client fsctxp-03 to a list of clients.

    Adding client fsctxp-04 to a list of clients.

    Adding client fsctxp-05 to a list of clients.

    Adding client fsctxp-06 to a list of clients.

    Adding client fsctxp-07 to a list of clients.

    Adding client fsctxp-08 to a list of clients.

    Copying profile files.

    Connecting to clients.

    Connecting to client: fsctxp-01.

    Client's fsctxp-01 ip is: 10.100.1.215.

    Connecting to client: fsctxp-02.

    Client's fsctxp-02 ip is: 10.100.1.216.

    Connecting to client: fsctxp-03.

    Client's fsctxp-03 ip is: 10.100.1.217.

    Connecting to client: fsctxp-04.

    Client's fsctxp-04 ip is: 10.100.2.218.

    Connecting to client: fsctxp-05.

    Client's fsctxp-05 ip is: 10.100.1.219.

    Connecting to client: fsctxp-06.

    Client's fsctxp-06 ip is: 10.100.1.220.

    Connecting to client: fsctxp-07.

    Client's fsctxp-07 ip is: 10.100.1.221.

    Connecting to client: fsctxp-08.

    Client's fsctxp-08 ip is: 10.100.1.222.

    Sending setup information to clients.

    Running the test (workload: HomeFolders).

    Starting adaptive iteration.

    Running iteration for 600 seconds with 1 users [warmup: 30s].

    Sending iteration data to clients.

    Client: fsctxp-01 Time: 600 number of users: 0.

    Client: fsctxp-02 Time: 600 number of users: 0.

    Client: fsctxp-03 Time: 600 number of users: 0.

    Client: fsctxp-04 Time: 600 number of users: 0.

    Client: fsctxp-05 Time: 600 number of users: 0.

    Client: fsctxp-06 Time: 600 number of users: 0.

    Client: fsctxp-07 Time: 600 number of users: 0.

    Client: fsctxp-08 Time: 600 number of users: 1.

    Waiting for clients.

    Performance Counter thread started for fsctxp-02

    Performance Counter thread started for fsctxp-06

    Performance Counter thread started for fsctxp-01

    Performance Counter thread started for fsct-winsrv

    Performance Counter thread started for fsctxp-07

    Performance Counter thread started for fsctxp-03

    Performance Counter thread started for fsctxp-08

    Performance Counter thread started for fsctxp-05

    Performance Counter thread started for fsctxp-04

    Sending a 'start' signal to clients.

    Starting performance counters.

    Performance counters started.

    Waiting for the end of the iteration.

    Waiting for client fsctxp-01 to send results.

    Client: fsctxp-01 run: 0 delayed: 0.

    Client fsctxp-01 finished its work.

    Waiting for client fsctxp-02 to send results.

    Client: fsctxp-02 run: 0 delayed: 0.

    Client fsctxp-02 finished its work.

    Waiting for client fsctxp-03 to send results.

    Client: fsctxp-03 run: 0 delayed: 0.

    Client fsctxp-03 finished its work.

    Waiting for client fsctxp-04 to send results.

    Client: fsctxp-04 run: 0 delayed: 0.

    Client fsctxp-04 finished its work.

    Waiting for client fsctxp-05 to send results.

    Client: fsctxp-05 run: 0 delayed: 0.

    Client fsctxp-05 finished its work.

    Waiting for client fsctxp-06 to send results.

    Client: fsctxp-06 run: 0 delayed: 0.

    Client fsctxp-06 finished its work.

    Waiting for client fsctxp-07 to send results.

    Client: fsctxp-07 run: 0 delayed: 0.

    Client fsctxp-07 finished its work.

    Waiting for client fsctxp-08 to send results.

    Client: fsctxp-08 run: 1 delayed: 0.

    delayed scenarios: 0 run scenarios: 1 elapsed time: 4640ms.

    Waiting for client fsctxp-08 to send results.

    Client: fsctxp-08 run: 3 delayed: 0.

    delayed scenarios: 0 run scenarios: 3 elapsed time: 9297ms.

    Waiting for client fsctxp-08 to send results.

    ……

    delayed scenarios: 0 run scenarios: 59 elapsed time: 629687ms.

    Waiting for client fsctxp-08 to send results.

    Client: fsctxp-08 run: 59 delayed: 0.

    Client fsctxp-08 finished its work.

    delayed scenarios: 0 run scenarios: 59 elapsed time: 630687ms.

    All clients finished their work.

    Stopping performance counters.

    Performance counters stopped.

    Sending a 'stop' signal to clients.

    Sending 'stop' command to fsctxp-01.

    Sending 'stop' command to fsctxp-02.

    Sending 'stop' command to fsctxp-03.

    Sending 'stop' command to fsctxp-04.

    Sending 'stop' command to fsctxp-05.

    Sending 'stop' command to fsctxp-06.

    Sending 'stop' command to fsctxp-07.

    Sending 'stop' command to fsctxp-08.

    Collecting iteration results.

    Waiting for client fsctxp-01 to send detailed results.

    Error getting detailed results from a client.

    Closing network connection

     

    Wednesday, February 17, 2010 1:47 AM

Answers

  • FSCT controller sends "stop" command at the end of each test duration. The controller will wait for the client to finish up on the tasks. In our own testing, we have seen issues with Xp client hang up on calls to the active directory randomly. Using win 7 or Vista client will not have this issue.
    Thursday, February 18, 2010 5:50 PM