Weird URL calling error

[Brian Powell]

I have a tag set up to do a local URL call every five minutes.  Today at about 00:30 GMT, continuing for about half an hour, I got this error emailed to me for each call...

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.1.46/update.php?tag={0}&temp={2}&time={5}

Any idea what caused this?  Is this a server issue, or is it something local?  At about 01:10 GMT, it returned to its normal quiet self.

Brian

[JimBo CA]

I had a bunch of these yesterday as well, hasn't happened today.

--
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 on the web visit https://groups.google.com/d/msgid/wireless-sensor-tags/9526894c-a7d7-4d41-81e2-978c36c01a74n%40googlegroups.com.

[Brian Powell]

These errors have resurfaced:

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.1.46/update.php?tag={0}&temp={2}&time={5}

I'm not sure the source of the problem was ever identified when it first occurred in 2021.

[Tom Beauchamp]

I'm also getting a bunch of those exact same errors today via email while my tag manager is trying to call a local URL with the data.

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://x.x.x.x:8085/wirelessTags?name={0}&tempF=&hum={3}&batt={6}

[Alan Barnett]

I am also seeing this.

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.,

[Jim Searle]

I'm also getting a lot of these from a setup that has been running with no issues for years.  Has anyone opened a support ticket?

[Tom Beauchamp]

I opened a ticket about it now.  In the only previous ticket about it that I found, it eventually resolved itself without any response from the manufacturer.

[Gary]

Same error here earlier today and now the tags will not update. Just shows error when trying to update.

[Glyn Hughes]

Me too!

Received over 100 notifications in the last couple of hours from 20 Tags and they’re coming in thick & fast!

Have reset both my router and Tag Manager so pretty sure it’s not a local network problem…

Thanks & kind regards,
-=Glyn=-

Sent from my iPhone

[Scott]

same issue

On Friday, December 10, 2021 at 9:55:50 AM UTC-5 Brian Powell wrote:

[Brewing Brzeski]

Same issue here.  Every time temp tag updates with URL call I receive this error.  Data is actually getting through to URL target, but I am getting errors on app and via email.  Started at 6:30am Pacific.  Still happening (3 hours later).  Have reset tag manager, router, URL target etc.  No change.

[Wireless Sensor Tags]

We are investigating, maybe a couple more hours. 

[LFMc in Texas]

Ditto here. They started this morning at 8:33AM CST . I got 3 hours relief when I powered off and on the tag manager, but they keep coming back. 

[Wireless Sensor Tags]

This is probably fixed now, can you confirm? 

[Glyn Hughes]

Looks like it might be. It was almost constant until @15 minutes ago.

Thank you! 

Regards,

-=Glyn=-

Sent from my iPhone

On 3 Aug 2022, at 20:42, Wireless Sensor Tags <wireless-s...@googlegroups.com> wrote:

This is probably fixed now, can you confirm? 

--
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 on the web visit https://groups.google.com/d/msgid/wireless-sensor-tags/20f66b72-bca4-4c96-b030-59a61b254d7cn%40googlegroups.com.

[LFMc in Texas]

Has not restarted since 2:26pm CST.

[Jim Searle]

Thanks, all good here now as well.

[Brewing Brzeski]

OK here since 12:31 PST (2 hours ago).  Thanks