Could not call URL

[Jimbo Automates]

Just started getting this error from all my tags. What causes this?

---------- Forwarded message ---------
From: Wireless Sensor Tags <notifi...@wirelesstag.net>
Date: Sat, Oct 26, 2024, 6:38 PM
Subject: Could not call URL for 'Bar Fridge' at event update due to following error

URL: Bar Fridge

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.86.88:29739/update?tmgr_mac=6B24C795B80E&name={0}&tagid={1}&temp={2}&hum={3}&lux={4}&ts={5}&batv={6}&signaldBm={7}&txpwr={8}

[CKurtis]

All my tags doing the same.  Must be something on the server side?

Sent from my iPhone

On Oct 26, 2024, at 9:52 PM, Jimbo Automates <jimbo.a...@gmail.com> wrote:



--
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/CAB_njDULGoMcTW5vLyqtZOwVM%3Dm57ycdrcLL52D6tq-tNS1YSA%40mail.gmail.com.

[Brian Powell]

We saw this a few years ago, and I believe it’s an indication that the WirelessTag server that processes these requests needs to rebooted. It could be caused by new code that’s been deployed, but could also be caused by problems with the existing code (such as a slow resource leak).

I’ve received several similar notifications in the last 90 minutes or so.

Brian

On Oct 26, 2024, at 9:52 PM, Jimbo Automates <jimbo.a...@gmail.com> wrote:



--

[Jeff Lauterette]

Hey Jimbo.  Actually know you!!!    I just put in the same subject here in G groups.  All of mine doing it based upon their call frequency.  NOT API related,

Should we put in tickets?

[Jimbo Automates]

Hey Jeff,  yes we saw this one time before and as Brian mentioned, it's an issue with their service.

To view this discussion visit https://groups.google.com/d/msgid/wireless-sensor-tags/f45f37fb-ab2e-444c-9574-0e60d2d5bc69n%40googlegroups.com.

[Jeff Lauterette]

but should we all put in support tickets or have one person do it?