A read timeout means that the scServer timed out when communicating with the scAgent. I would look out how long SnapDrive takes to create a snapshot. Probably this is longer than timeout you have set in config for SC_AGENT_TIMEOUT. You can increase the timeout by increasing value for SC_AGENT_TIMEOUT, it is in seconds.
Other things to check:
1. Under scAgent3.4.0\config\agent.conf - make sure you have this like "command: sdcli". This makes sure that the agent will allow snapdrive commands, you can also do "command: *" to allow all commands.
2. Make sure agent ping works. Open profile in GUI and go to agent settings, then click "test agent".
3. If you aren't using GUI you can simply do a telnet "telnet <host> 9090"
4. Check to make sure user running agent has permissions to run snapdrive. Remember snapdrive requires admin permissions.
Again I am guessing this is issue with SnapDrive taking a while and SC_AGENT_TIMEOUT not being enough to account for it
And you're right Keith. I've now set the SC_AGENT_TIMEOUT to 30 and now it works fine. It was set to 2 during the gui job creation. If nothing will be entered then the default of 300 sec will be used. Found that in the conf file. Maybe a hint would be helpful when useing the gui that the default value is ok and nothing should be entered. As I'm using SnapDrive for the SnapShots this will take more then 2 sec which was entered before 😉 So the default timeout is fine
Thanks for feedback and reporting back that it works
We recommend SC_AGENT_TIMEOUT=60 but 30 should be enough unless something really bad happens with SnapDrive. i have seen SnapDrive take fore than 60 seconds even but that was unix env with LOTS of file systems.
We will add a hint in GUI, i agree this would be helpful with some guidance for different configurations