Hi all, I'm not a Dev, more ops supporting SOSS that I inherited, so jumping into this pretty blind. (Any existing posts/documentation that I missed, feel free to post.)
I've got one StateServer supporting 3 environments (remote agents), it was working fine, but yesterday one Test env stopped working. Unfortunately it's being used by a proprietary framework so I don't have much visibility, but main part of error is:
'ScaleoutServiceUnavailableException'><message><![CDATA[Unable to open a connection to the local ScaleOut service. Verify the local service is started and joined
I've compared to other environments, re-deployed (known working) code, uninstalled and re-installed, rolled back OS patches, upgraded agent... Not sure where to go from here. Some questions that came up trying to figure things out:
1 - How do you verify remote client connection? On the (IIS) web servers I can open the management console, see the "Local Store" (that's not local, but on the server cluster), and see the IP's of the other environments in the remote-clients tab, but none from the the broken environment. Additionally, can use get-cache and see a couple appid/cachename pairs on the expected server hosts. On the remote agent servers, where/what is the actual process/.exe? On the server, finding the various SOSS services is easy. On the remote clients - I can't see anything in services, task manager, anything. So I have no way of restarting the agent/service without rebooting the whole OS.
2 - What's the agent < - > server compatibility story? Can I upgrade agents or server first and the other will be backward compatible? (Just enough for testing, then upgrade the rest.)
3 - The online docs (http://static.scaleoutsoftware.com/docs/soss_help/content/index.html) mention windows event logs, but there's no mention of the actual logs, esp remote agents. I finally found the soss_tlog0.txt log, which repeatedly says 'Cannot open parameters file path C:\Program Files\ScaleOut_Software\StateServer\soss_params.txt' - why is it trying to read that rather than client_params? is that by design?
4 - Additionally, we've had some issue w/ old apps not playing well with TLS 1.2 - disabling 1.0 and 1.1 on the windows level (Registry/Group Policy) breaks some things. Has anyone had issues or experience w/ this for SOSS?
I've got one StateServer supporting 3 environments (remote agents), it was working fine, but yesterday one Test env stopped working. Unfortunately it's being used by a proprietary framework so I don't have much visibility, but main part of error is:
'ScaleoutServiceUnavailableException'><message><![CDATA[Unable to open a connection to the local ScaleOut service. Verify the local service is started and joined
I've compared to other environments, re-deployed (known working) code, uninstalled and re-installed, rolled back OS patches, upgraded agent... Not sure where to go from here. Some questions that came up trying to figure things out:
1 - How do you verify remote client connection? On the (IIS) web servers I can open the management console, see the "Local Store" (that's not local, but on the server cluster), and see the IP's of the other environments in the remote-clients tab, but none from the the broken environment. Additionally, can use get-cache and see a couple appid/cachename pairs on the expected server hosts. On the remote agent servers, where/what is the actual process/.exe? On the server, finding the various SOSS services is easy. On the remote clients - I can't see anything in services, task manager, anything. So I have no way of restarting the agent/service without rebooting the whole OS.
2 - What's the agent < - > server compatibility story? Can I upgrade agents or server first and the other will be backward compatible? (Just enough for testing, then upgrade the rest.)
3 - The online docs (http://static.scaleoutsoftware.com/docs/soss_help/content/index.html) mention windows event logs, but there's no mention of the actual logs, esp remote agents. I finally found the soss_tlog0.txt log, which repeatedly says 'Cannot open parameters file path C:\Program Files\ScaleOut_Software\StateServer\soss_params.txt' - why is it trying to read that rather than client_params? is that by design?
4 - Additionally, we've had some issue w/ old apps not playing well with TLS 1.2 - disabling 1.0 and 1.1 on the windows level (Registry/Group Policy) breaks some things. Has anyone had issues or experience w/ this for SOSS?
Last edited: