Scheduled Task Error

[DeadMan...]

This has happened on 2 sites over the last couple of days.
I go to my site and find this:

Code Select Expand

Yesterday at 09:21:03 PM
Guest
https://www.mydomain.com/index.php?https://www.mydomain.com/
/Sources/ScheduledTasks.php (Line 1109)

Type of error: Database
Error message
Database Error: Data too long for column 'data' at row 1
The only task set up for that time:

Code Select Expand

Fetch Simple Machines files
Retrieves javascript files containing notifications of updates and other information.
Today at 09:21:00 PM
Starting at 21:21, repeating every 1 day(s)
Just tried to do a run now on the Fetch Simple Machines files on clean test site:

Code Select Expand

Database Error
Data too long for column 'data' at row 1
File: /Sources/ScheduledTasks.php
Line: 1109

[Julius_2000]

I can confirm. This happened to us as well a day ago.

[Kindred]

That's due to some server bumps here. We're fixing some stuff in the stack

[Louis]

good to know I can happily ignore these errors then (at least for the time being)

[Steve]

Problem resolved @DeadMan... ?

[DeadMan...]

Problem resolved @DeadMan... ?

Unknown. I'm on my phone and I had turned off the Fetch in the scheduled tasks list. Will turn it back on later today and see what happens.

Have they fixed the server stack issue yet?

[Steve]

I believe they have so when you have time could you let us know if the problem persists even after turning the Fetch task back on?

[CRM 114]

The problem still exists here with the active task "Fetch Simple Machines files" (today 2023-04-25, 03:00 CEST).

[DeadMan...]

The problem still exists here with the active task "Fetch Simple Machines files" (today 2023-04-25, 03:00 CEST).

You might have to wait until the next run, or do like I did and do a run now for it.

I believe they have so when you have time could you let us know if the problem persists even after turning the Fetch task back on?

After turning back on and doing a run now, it seems to be fixed.

[CRM 114]

You might have to wait until the next run, or do like I did and do a run now for it.
...
After turning back on and doing a run now, it seems to be fixed.

That worked fine. Thanks and thumbs up!

[gkawa]

I don't know if this helps. I'm having the same problem (quotes here, it doesn't seem to be a problem) but it only happens once daily with one query from Bing. And that could be just a coincidence because we don't have much traffic from users at that time.
The URL varies, once it requested an ics from the Calendar, the others are posts. I don't think it's relevant. It happens always in the first minutes of the day (our time, GMT -3). It's weird because Bing has been querying our site nonstop all day long since April 10th, and all the other queries don't trigger this error.
One detail I noticed in this case, the query timestamp is 23:58:11 (GMT-3, 00:58:11 GMT-4 in the log) and the error was recorded at 00:03:12. It's a long time to serve a page. And the result was normal, 200, so the file was served.
Another one I checked was answered between the second, 00:03:07, but it responded with a 500. The same URL has been queried many times over the day by Bing and all the others were answered normally.

My guess (and it's a long shot) is that I have a process running at that time that somehow blocks or delays the DB for SMF. Sometimes it happens before the request is answered and sometimes after when the ScheduledTask script is running.

[DeadMan...]

@gkawa
If you had read the thread and did as I last posted, you'd likely notice that the issue is fixed.