- This topic has 5 replies, 4 voices, and was last updated 4 years, 5 months ago by
.
-
Posts
-
Hi!
Today I upgraded our WMS server from 1.2.1HF to 1.4. I ran the installer, copied our keystore back into the Tomcat folder and all seemed well. There is some intermittent slowness and I took a look at stratus.log and it is filling up with WARN messages very quick. Log is turning over every 2-5 minutes. A lot of this in the logs, followed by Java exception info.
2019-05-30 17:38:01,095 [ERROR] myScheduler-42 <com.wyse.stratus.server.cache.QueueLockCache::read,67> Unable to read from cache. Timeout waiting for value
2019-05-30 17:38:01,095 [ERROR] myScheduler-42 <com.wyse.stratus.server.dao.QueueLockDaoImpl::getQueueLockByType,70> Unable to read from cache.Timeout waiting for value
2019-05-30 17:38:01,095 [INFO] myScheduler-42 <com.wyse.stratus.server.dao.QueueLockDaoImpl::getQueueLockByType,77> UpdateParentCommandQueue not found in cache, adding to cache.
2019-05-30 17:38:01,209 [WARN] https-openssl-nio-443-exec-255 <com.wyse.stratus.server.cache.CacheableItem::get,65> Cache exeception :
net.spy.memcached.OperationTimeoutException: Timeout waiting for valueAppreciate if anyone can suggest next steps on addressing this.
Thanks!
Update: I have opened a ticket with DELL. Post-upgrade, I see Tomcat9 service taking as much as 3+GB memory on the server. Clients are not getting updated config policy from WMS. I am not able to view device details in the WMS console. If any of this turns out to be something that could happen to others, I will continue to share details here.
Got my issues fixed today! It’s been a long week because WMS was pretty broken post-upgrade. Clients started losing their Wifi profiles as a result of this issue, still not sure why that was but not having config policy flow for a week was not great.
Anyhow, the problem was that Tomcat wasn’t able to connect to the memcached service. I’m not really sure what broke this since I don’t have an older implementation of WMS to check and it doesn’t look like the 1.4 upgrade should have changed anything with memcached but I had to explicitly specify the port for memcached to listen on in the properties of the memcached service to get it to listen properly for connections.
The registry key for this is HKLM\SYSTEM\CurrentControlSet\Services\memcached\ImagePath
Old value: <path to executable> -d runservice -l <server name> -U 0
New value: <path to executable> -d runservice -l <server name> -U 0 -p 11211
Would definitely be interested to hear from others on if they have had problems moving to 1.4 and also, if you haven’t, can you share this registry value so I can see what it should have been pre-upgrade?
Thanks!
Hi MoPositive,
I updated to WMS 1.4 this week and also had issues concerning memcached.
The log file shows a lot of warnings:
2019-08-20 07:36:31.359 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms_QueueLockCache_3. 2019-08-20 07:36:31.406 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms:globalType:. 2019-08-20 07:36:31.406 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms:globalType:. 2019-08-20 07:36:31.406 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms_QueueLockCache_29. 2019-08-20 07:36:31.421 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms:globalType:. 2019-08-20 07:36:31.421 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms:globalType:. 2019-08-20 07:36:31.437 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms_QueueLockCache_30. 2019-08-20 07:36:31.515 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms:globalType:. 2019-08-20 07:36:31.531 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms:globalType:. 2019-08-20 07:36:31.531 WARN net.spy.memcached.MemcachedConnection: Could not redistribute to another node, retrying primary node for wms:globalType:.After seeing your post I checked the registry:
Old value was: <path to executable> -d runservice -p 11211 -l <server name> -U 0
As you can see, the port number is already specified. However, it didn’t work. So I just changed the order of the string to:
<path to executable> -d runservice -l <server name> -U 0 -p 11211
Oddly enough, after restarting the memcached-service, everything works fine.
Thanks a lot for pointing me in the right direction!
Thanks for the tip… it helped me a lot… !!!
Having the same issue here.
We started with WMS1.1 updated to 1.2 and now to 1.4.
Error:
<com.wyse.stratus.server.cache.QueueLockCache::read,67> Unable to read from cache. Timeout waiting for value
<com.wyse.stratus.server.dao.QueueLockDaoImpl::getQueueLockByType,70> Unable to read from cache.Timeout waiting for value
<com.wyse.stratus.server.dao.QueueLockDaoImpl::getQueueLockByType,77> TenantEventCounterQueue not found in cache, adding to cache.
<com.wyse.stratus.server.dao.QueueLockDaoImpl::getQueueLockByType,77> DeviceCheckinQueue1 not found in cache, adding to cache.ImagePath is also without Port:
“Path to memcached exe” -d runservice -l SERVERNAME -U 0
But changing it to “Path to memcached exe” -d runservice -l SERVERNAME -U 0 -p 11211 and restarting the service doesnt work for us. The error is still the same. As Memcached seems not to have any logfile im not able to check the other side.
The Thin Clients took very long to boot and the webinterface is very slow but it seems to work somehow.
Are there any additional hints or do we need to reinstall it?
regards
- You must be logged in to reply to this topic.