No need to keep open any longer since the issue itself is no longer persisting.

Will do by end of week

@RhinosF1: progress on IR?

Only IR left

Sysadmins: Use https://graylog.miraheze.org/search?q=NOT+mediawiki_exception_file%3A%5C%2Fsrv%5C%2Fmediawiki%5C%2Fw%5C%2Fextensions%5C%2FCargo%5C%2F%2A+AND+mediawiki_exception_class%3AJobQueueError&rangetype=relative&streams=5f8c6fd446640840f104b0ba&relative=7200 and https://graylog.miraheze.org/search?q=mediawiki_host%3Ajobrunner%2A&rangetype=relative&streams=5f8c6fd446640840f104b0ba&relative=7200 to see errors.

Much lower rate but still some. We'll continue working on it. CC @Paladox to see if they know how to get redis working again.

In T6859#135237, @Emad4ald wrote:

It has been resolved
Thanks Team

It has been resolved
Thanks Team

Looks to be out of disk space

jbr3&4:

ERR Error running script (call to f_3b56824083b7c4c3509163c7e76e00904014d92e): @user_script:4: @user_script: 4: -MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.

There's a huge rise in redis errors starting 07:12

This issue appear only for me

I'll look now

As per Omegas request, reopened the task.

I maintain DynamicPageList3 at the moment, I'll fix it tomorrow, but this being an upstream extension bug is not necessarily appropriate for this phabricator. Feel free to create an issue for this at https://github.com/Universal-Omega/DynamicPageList3/issues/new however. Thanks!

This is an error in DynamicPageList3. The error message looks like this: [1fd7cd4921c8fba999509db0] 2021-02-16 05:32:36: Fatal exception of type "TypeError" .

Published at https://meta.miraheze.org/wiki/Special:IncidentReports/36

Can you do the incident report as the primary responder?

Thanks for the add, @RhinosF1

Should be fixed now.

I apologize for the inconvenience caused by this error. I've now fixed this for you.

@Reception123 might be claiming this task.

In T6752#132830, @RhinosF1 wrote:

@Dmehus: We've seen this what feels like a million and one times before. There's a task somehwere I believe upstream.

@Paladox: can you populate the table?

@RhinosF1 Ah, okay, that's helpful. Thanks, and thanks for updating the projects.

@Dmehus: We've seen this what feels like a million and one times before. There's a task somehwere I believe upstream.

Thank you for reporting this, @Bimagv. A system administrator should run a full trace on this error and either (a) fix it locally or (b) fix it, or request for it to be fixed, upstream, as applicable, within the next day or two.

Yay! Looks like the screenshot helped. I'm glad I pushed you to look into fixing this. I think the fix you implemented was a reasonable one. Thanks! :)

Fixed with https://github.com/miraheze/DataDump/pull/17

In T6698#132195, @Dmehus wrote:

In T6698#132192, @Universal_Omega wrote:

Interesting I don't see that log entry like that.

Hrm, really? On Vector?

In T6698#132192, @Universal_Omega wrote:

Interesting I don't see that log entry like that.

Interesting I don't see that log entry like that.

@Universal_Omega I'm reopening this task because in reference to:

Closing as invalid as looking at the code there is absolutely nothing that would cause this unless you reload the page a second time, without clicking the "Refresh page" link. https://github.com/miraheze/DataDump/blob/f9dc4f686221606913c207fc94589c5f78723efc/includes/specials/SpecialDataDump.php#L80.

I can't seem to reproduce the error either.

Also from a look, this is the *only* wiki affected it seems.