Search stopped indexing and I don't know why #27968
Replies: 4 comments 2 replies
-
okay I did more digging and I'm seeing this:
the document IDs change but the time field doesn't, and that's certainly an interesting time and I have no idea what to do about that so... ideas? |
Beta Was this translation helpful? Give feedback.
-
Michael asked to open an issue so I did: https://mastodon.murkworks.net/@moira/111432882956209704 Issue is here: But now it's clearly a duplicate of this: But I don't know how to find and remove the posts with the invalid date. Help? |
Beta Was this translation helpful? Give feedback.
-
You can fix this directly by correcting the date on the bad post. From your Mastodon server, in the For the tags: Credit to @rrgeorge on these instructions. |
Beta Was this translation helpful? Give feedback.
-
thank you very much! in case it's of interest this is the offending post: [#<Status:0x00007f6c3c4c47f8 📌 Hilo fijado: Recomendaciones musicales chidas created_at: Thu, 07 Nov 11968 17:22:13.599000000 UTC +00:00, updated_at: Sat, 28 Oct 2023 15:09:07.728736000 UTC +00:00, in_reply_to_id: nil, reblog_of_id: nil, url: "https://mk.itzti.li/notes/9la79fmeadxw63t4", sensitive: false, visibility: "public", spoiler_text: "", reply: false, language: nil, conversation_id: 8112423, local: false, account_id: 111313267981205598, application_id: nil, in_reply_to_account_id: nil, poll_id: nil, deleted_at: nil, edited_at: nil, trendable: nil, ordered_media_attachment_ids: nil>] |
Beta Was this translation helpful? Give feedback.
-
Hi! Running 4.2.1 on debian, up to date in general.
Full-text search has been working great and is still working - but it stopped adding anything to the search database late on October 28th or very early October 29th. Nothing's in syslog, elasticsearch (v 7.17.15, pulled from https://artifacts.elastic.co/packages/7.x/apt stable InRelease) says it's happy and running fine, there's nothing in syslog, last entry in elasticsearch.log is that cluster health status is green (after a restart), but I am seeing a whole lot of this in sidekiq:
Chewy::ImportFailed: Import failed for
TagsIndex
with: Index errors: `{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse field [last_status_at] of type [date] in document withAnybody know what might be up with this? I've done a lot of searching without finding anything so...
Beta Was this translation helpful? Give feedback.
All reactions