With the messages below from meshconfig-agent.log one cannot get a clear understanding on where to look for the problem, unless it can be deduced from the MaDDash. Like in our case with the missing nuttcp support on the RRZE server.
Please consider: the participants and the test type.
2017/02/17 16:45:20 (11288) WARN> perfsonar_meshconfig_agent:381 main:: - Problem adding test, continuing with rest of config: 422 UNPROCESSABLE ENTITY: Unable to complete request: Couldn't find a tool in common among the participants.
2017/02/17 16:45:20 (11288) WARN> perfsonar_meshconfig_agent:381 main:: - Problem adding test, continuing with rest of config: 422 UNPROCESSABLE ENTITY: Unable to complete request: Couldn't find a tool in common among the participants.
2017/02/17 16:45:20 (11288) WARN> perfsonar_meshconfig_agent:381 main:: - Problem adding test, continuing with rest of config: 422 UNPROCESSABLE ENTITY: Unable to complete request: Couldn't find a tool in common among the participants.
2017/02/17 16:45:20 (11288) WARN> perfsonar_meshconfig_agent:381 main:: - Problem adding test, continuing with rest of config: 422 UNPROCESSABLE ENTITY: Unable to complete request: Couldn't find a tool in common among the participants.
Hi Andy,
With the messages below from meshconfig-agent.log one cannot get a clear understanding on where to look for the problem, unless it can be deduced from the MaDDash. Like in our case with the missing nuttcp support on the RRZE server. Please consider: the participants and the test type.