Unsolved
1 Rookie
•
21 Posts
0
28
RFIDeas Badge Reader Issues Since 2308 Release
Since the 2308 ThinOS release I have been experiencing an issue where the RFIDeas Badge Readers (RDR-80582AKU) attached to our thin clients randomly stop working (both 5070 and 5470 AIO models) . The badge tap is recognized by the reader (it beeps) but the credentials are never sent to the application (Epic). The only way to get the reader working again is to completely reboot the thin client. I have opened multiple tickets with support for this and was hoping this would be fixed in the 2402 release but it's still an issue. The support tech I worked with this week did acknowledge that he's received multiple incidents from other customers regarding this issue. Curious if any others are experiencing this and can offer any guidance. This has been an ongoing issue for 9 months now so I have little confidence in support coming up with a quick solution.
buffalobound
3 Apprentice
3 Apprentice
•
712 Posts
0
April 25th, 2024 23:25
ThinOS 2405 is in closed Beta. Has your engineer had you test with the early access code for 2405 yet?
rnailor1225
1 Rookie
1 Rookie
•
21 Posts
0
April 26th, 2024 11:31
@buffalobound The Beta firmware has not been offered to me yet. I would think though if there was a fix for this issue on that code, the support person I have been working with would know that or at least be informed by engineering. I will ask about this.
buffalobound
3 Apprentice
3 Apprentice
•
712 Posts
0
April 26th, 2024 12:39
Sent you a DM. I want to look into this for you
#IWork4Dell
buffalobound
3 Apprentice
3 Apprentice
•
712 Posts
0
April 29th, 2024 14:25
Thanks for reaching out Robert. I replied to your message, hopefully, we can get this back on the right track.
CorPor
1 Rookie
1 Rookie
•
1 Message
0
May 6th, 2024 20:28
Just want you to know that you are not alone. Our environment consists of 3040s and Optiplex 3000s. Originally we were faced with an issue of intermittently not being able to badge 'out' until we restart the VM and thin client. We are now experimenting with using USB redirection without the Imprivata virtual channel and are plagued with intermittent pop-ups asking users to re-enroll their badge without the user ever having tapped their badge to begin with.
rnailor1225
1 Rookie
1 Rookie
•
21 Posts
1
May 7th, 2024 11:45
Do you have a case open with support? I've had two engineers look at my logs and didn't find anything so I took it upon myself to dig through the logs and there is definitely a memory leak type issue with the ssoManager daemon. It's clearly evident in the logs that the daemon is crashing due to memory issues and all subsequent attempts to auto restart the service also crash. Take a look at your thinos_watchdog.log and the kmessages log files and you will see the errors. Below is what is appearing in the kmessages log. Once the daemon crashes it will not restart until the device is rebooted. I believe my case is at 3rd level engineering now so hopefully this gets fixed in the next release.![]()
(edited)
rnailor1225
1 Rookie
1 Rookie
•
21 Posts
0
May 7th, 2024 11:49
Apr 17 02:32:56 kernel: <140623.835679> Out of memory - pid 700 (ssoManager_daemon): 158827 MB, will be killed.
Apr 17 02:32:56 kernel: <140623.835685> pid 700 (ssoManager_daemon), uid 0, was killed: out of swap space
Apr 17 02:32:56 kernel: <140623.861150> worker_thread.573: kevent USER EOF
Apr 17 02:42:26 kernel: <141194.106809> pid 21986 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 02:52:26 kernel: <141794.297511> pid 22063 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 03:02:26 kernel: <142394.322638> pid 22142 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 03:12:27 kernel: <142994.432922> pid 22219 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 03:22:27 kernel: <143594.591407> pid 22296 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 03:32:27 kernel: <144194.673009> pid 22389 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 03:42:27 kernel: <144794.754199> pid 22466 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 03:52:27 kernel: <145394.806862> pid 22543 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 04:02:27 kernel: <145994.806496> pid 22622 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 04:12:27 kernel: <146594.937147> pid 22699 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 04:22:27 kernel: <147194.942941> pid 22776 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 04:32:27 kernel: <147795.050858> pid 22854 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 04:42:27 kernel: <148395.067219> pid 22931 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 04:52:27 kernel: <148995.116155> pid 23008 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 05:02:27 kernel: <149595.175057> pid 23087 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 05:12:27 kernel: <150195.208713> pid 23164 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 05:22:27 kernel: <150795.375433> pid 23241 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 05:32:27 kernel: <151395.412060> pid 23319 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 05:42:28 kernel: <151995.474327> pid 23396 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 05:52:27 kernel: <152595.530315> pid 23473 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 06:02:28 kernel: <153195.543943> pid 23552 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 06:12:28 kernel: <153795.624261> pid 23629 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 06:22:28 kernel: <154395.659623> pid 23706 (ssoManager_daemon), uid 0: exited on signal 11
Apr 17 06:32:28 kernel: <154995.890176> pid 23784 (ssoManager_daemon), uid 0: exited on signal 11