Probable I/O race condition detected while copying memory.

[Jeff Lauterette]

Started tonight on all my tags and BOTH my tag managers.  I think its not on my end but the URL is showing local (NAT URL)

Manual update workng

Probable I/O race condition detected while copying memory. The I/O package is not thread safe by default. In multithreaded applications, a stream must be accessed in a thread-safe way, such as a thread-safe wrapper returned by TextReader's or TextWriter's Synchronized methods. This also applies to classes like StreamWriter and StreamReader., URL attempted to call: http://172.16.1.210:17594/update?tmgr_mac=F8D5FFF99A5A&name={0}&tagid={1}&temp={2}&hum={3}&lux={4}&ts={5}&batv={6}&signaldBm={7}&txpwr={8}

dont know how to stop the errors.  power cycle the tag manager does not work.  And I doubt BOTH tag managers are bad.

[Zhiheng Cao]

We were doing database index rebuild this weekend which may have been causing interruptions for up to 1 hour.  Did this error go away now? 

--
You received this message because you are subscribed to the Google Groups "Wireless Sensor Tags" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wireless-sensor-...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/wireless-sensor-tags/e21f53a6-db83-41d7-811a-9edeff99d75dn%40googlegroups.com.

[Jimbo Automates]

Yes it went away. 

Please send out a notification when you think this may happen. It caused a lot of emails.

To view this discussion visit https://groups.google.com/d/msgid/wireless-sensor-tags/CAOM4i20hhKe0FE9S%3DS4vU3qFDxu3wu67MhWC-yS%2BKeZ4Zd4mjA%40mail.gmail.com.

[Jimbo Automates]

It's happening again.

[Jeff Lauterette]

Yep agreed.  Same problem as last Saturday!!!!

[Tom Beauchamp]

I/O race condition errors again :(

[Jeff Lauterette]

This is back!!! Every 3-4 months.  Different gateways, devices, and device types. 

[Jimbo Automates]

Yes I'm seeing it as well...

---------- Forwarded message ---------

From: Wireless Sensor Tags <notifi...@wirelesstag.net>

Date: Thu, Mar 27, 2025, 8:42 PM

Subject: Could not call URL for 'Lake Kitchen Fridge 2' at event update due to following error

URL: Lake Kitchen Fridge 2

Probable I/O race condition detected while copying memory. The I/O package is not thread safe by default. In multithreaded applications, a stream must be accessed in a thread-safe way, such as a thread-safe wrapper returned by TextReader's or TextWriter's Synchronized methods. This also applies to classes like StreamWriter and StreamReader., URL attempted to call: http://192.168.2.66:23503/update?tmgr_mac=A74D112FF58D&name={0}&tagid={1}&temp={2}&hum={3}&lux={4}&ts={5}&batv={6}&signaldBm={7}&txpwr={8}

Sent at: 3/27/2025 7:42:35 PM.

You are receiving this email because you asked to be notified about Tag events. You can click this link to stop emails like this to be sent to your email address (unsubscribe), or re-subscribe/unblock.

© CAO GADGETS, LLC. 50 Tesla, Irvine, CA 92618

To view this discussion visit https://groups.google.com/d/msgid/wireless-sensor-tags/2e515b6e-c11f-4e31-a398-66093fc5650fn%40googlegroups.com.

[Glyn Hughes]

I’ve had 218 of these notifications/emails between midnight and now 6am in the morning!

But my biggest problem by far is the abysmal battery life.

I’m using branded Energizer CR2032 and after getting so fed up after spending so much money every few weeks ended up disregarding my complete Wireless Tag system.

Decided to give it one more chance so replaced all the flat batteries on 1st December and the tags started showing out of range/low battery levels by 22nd February so a lifespan of only 52 days so less than 3 months.

As I type this 50% of my Tags are out of range due to low battery levels.

Thanks & kind regards,

-=Glyn=-

Sent from my iPhone

On 28 Mar 2025, at 03:45, Jimbo Automates <jimbo.a...@gmail.com> wrote:



To view this discussion visit https://groups.google.com/d/msgid/wireless-sensor-tags/CAB_njDUCnhdFMgZ6Yg%2BzZrLk6R5KgxZoxqtAgtUtVne%3D0nF6Zw%40mail.gmail.com.

[Jeff Lauterette]

The first time this happened I spent hours trying to figure it out.  From rebooting the gateways to rebooting my router, 

Now after multiple times I know its on their end.   Mine did stop an hour ago.  Lets hope its fixed

But I wish this did not happen every 3-4 months.

[Jeff Lauterette]

Seems to have stopped for now