By: Freddie Johnson Jr user 13 Dec 2018 at 10:14 a.m. CST

3 Responses
Freddie Johnson Jr gravatar
Team -- I'm getting Invalid Date on Cache Refresh, but the actual Cache Refresh is working fine for populating Persons and interacting with Active Directory. I also set the time of the Gluu server in which is reflected in the logs below. I've searched the community tickets and ticket #6181 does not relate to my issue as I'm not getting a server invalid server configuration error from my understanding. Here are my logs: ``` [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] ( - Removed '1' persons from target server 2018-12-12 23:37:06,821 INFO [ForkJoinPool.commonPool-worker-2] [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] ( - There are '3' entries before updating inum list 2018-12-12 23:37:06,821 INFO [ForkJoinPool.commonPool-worker-2] [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] ( - There are '2' entries after removal '1' entries 2018-12-12 23:37:06,822 INFO [ForkJoinPool.commonPool-worker-2] [gluu.oxtrust.ldap.cache.service.CacheRefreshTimer] ( - There are '2' entries after adding '0' entries ``` As you can see from the logs, the time is correct but the picture below shows Invalid.Date in the UI: Here's a picture of the time as of this morning set in the container which also matches the server as well (ignore the different time from the logs as I've updated the ticket): Looking forward to any guidance you can provide. Thanks for your time.

By Mohib Zico staff 19 Dec 2018 at 4:20 a.m. CST

Mohib Zico gravatar
It should have been fixed already. Sahil, can you please check status real quick in 3.1.5?

By Freddie Johnson Jr user 19 Dec 2018 at 5:12 p.m. CST

Freddie Johnson Jr gravatar
I think I found out the solution. I'm working in a environment where we don't have direct internet access. In order to get the RPM, I downloaded it directly from your repo and ported it over to the client side. Today, I attached our Artifactory to your repo and downloaded an update and now I have the date! Maybe an update was pushed out to your repo since I posted this question? Freddie

By Sahil Arora staff 27 Dec 2018 at 8:50 p.m. CST

Sahil Arora gravatar
Hi Freddie, We have not pushed any updates to prod repos. There was an [issue]( identified in Cache Refresh which has been fixed in 3.1.5. I am closing this ticket as original issue reported by you is resolved. Let me know if you need any further assistance. Thanks