146
edits
Tech WG/Ops Diary: Difference between revisions
add link to Tech WG main page
(add link to Tech WG main page) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Up to [[Part Of::Tech_WG]] | |||
== 22-12-16 Upgrading Linode Ram == | == 22-12-16 Upgrading Linode Ram == | ||
| Line 225: | Line 227: | ||
(The vulnerability in question) https://github.com/mastodon/mastodon/security/advisories/GHSA-3fjr-858r-92rw | (The vulnerability in question) https://github.com/mastodon/mastodon/security/advisories/GHSA-3fjr-858r-92rw | ||
== 24-02-14 == | |||
{{Message | |||
|Author=sneakers.the.rat | |||
|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024 | |||
|Date Sent=24-02-17 22:16:31 | |||
|Channel=techwg-ops | |||
|Text=[[Tech WG/Ops Diary#24-02-14]] - Patching two more security bugs thread! | |||
|Link=https://discord.com/channels/1049136631065628772/1052452072806686751/1208537492802904064 | |||
}} | |||
== 24-04-17 Elastic Search issues == | |||
Manisha: Saw a warning in the admin panel: | |||
<code> Could not connect to Elasticsearch. Please check that it is running, or disable full-text search </code> | |||
Checked ES status via root | |||
<code> service elasticsearch status</code> | |||
It showed [https://discord.com/channels/1049136631065628772/1049184335514828860/1230219622293438514 status Failed]. | |||
Restarted ES | |||
<code> service elasticsearch restart</code> | |||
Status returned to [https://discord.com/channels/1049136631065628772/1049184335514828860/1230219711543902328 active]. | |||
Had to wait a tiny bit before [https://discord.com/channels/1049136631065628772/1049184335514828860/1230220033481773087 the warning in the admin panel] disappeared. | |||
== 24-04-30 Sidekiq scheduler queue issues == | |||
Manisha: Noticed this warning about sidekiq [[File:Sidekiq issues.png|frameless]] | |||
And saw that we were hitting our swap limits. | |||
Restarted services. Sidekiq status is active but we are still near our swap limits and the sidqkiq warning in the admin panel hasn't gone away. [https://discord.com/channels/1049136631065628772/1049184335514828860/1235046062171885568 Link to discussion on the technical-wg channel]. | |||
[https://github.com/mastodon/mastodon/issues/20710#issuecomment-1329680431 Maybe this github discussion would help?] but on checking the sidekiq dashboard, while the no. of processed requests did plummet today, I do see sidekiq running. The warning about the scheduler queue(s) is puzzling as there are scheduled jobs in the sidekiq container! hmmm | |||
Something is definitely up. sidekiq's status is <code> active (exited)</code>. I restarted ES and that helped free up swap but restarting sideqik isn't helping and the warning isn't going away :( | |||
Jonny: we are sorta always at the limit of RAM and swap, cost of the ES service. disk is full! cron job likely not working | |||
Manisha: ran this <code> RAILS_ENV=production /home/mastodon/live/bin/tootctl media remove --remove-headers</code> as mastodon user. It freed up 10.5 GB and the sidekiq warning went away! :) | |||