Week 36 2024 routine

[kiwixbot]

Check nodes free space

df -h / && df -h /data

• create a report in issue comment

Nodes system upgrades

apt update && apt upgrade

• run systematically the upgrade on bastion, stats, services, storage, demo nodes
• check for and apply important security upgrade on worker nodes asap (imager-worker, ondemand, sisyphus)

(regular workers updates are done separately on a monthly basis for worker nodes to not impact production)

Backups

• Ensure all borg repositories are being updated

k8s cluster

• Check Pod errors

k get pods -A -o wide|grep Error

• Check Pod restarts

k get pods -A -o wide | pyp -i 'print("\n".join([line for line in l if re.split(r"\s+", line)[4] != "0"]))'

• Check if k8s should/could be upgraded

curl -s -H "X-Auth-Token: $SCW_SECRET_KEY" https://api.scaleway.com/k8s/v1/regions/fr-par/clusters/$KIWIX_PROD_CLUSTER | jq ".version,.upgrade_available"
curl -s -H "X-Auth-Token: $SCW_SECRET_KEY" https://api.scaleway.com/k8s/v1/regions/fr-par/versions | jq ".versions[].name"

• Upgrade k8s if applicable/possible

Stats

matomo - stats.kiwix.org

• Ensure download.kiwix.org stats are being recorded
• Check whether matomo should be upgraded

Grafana

• Alert list is normal
• Zimfarm dashboard is normal
• Jobs durations dashboard is normal
• There is no abnormal behaviors on cluster resources consumption
• All mdadm RAID arrays are OK (check all instances in the top left combobox)

Projects

• UptimeRobot has no alert
• zimit backlog is reasonable
• Cloud Code Signing Certificate usage is OK (look for Unused Signings under END ENTITY CERTIFICATES): we have 1,200 per year (August to August)
• Analyze zimit failed tasks
• PRs awaiting your review

Security

• Analyze/merge dependabot PRs

Note: this is an automatic reminder intended for the assignee(s).

[rgaudin]

Storage

Machine	Filesystem	Size	Used	Avail	Use%	Use change
bastion	/	37G	14G	22G	40%	-
stats	/	233G	108G	113G	49%	-1G
services	/	456G	309G	124G	72%	+5G
storage	/	33T	18T	14T	58%	-
imager-worker	/	1.9T	452G	1.4T	26%	don't care
sisyphus	/	233G	20G	201G	10%	don't care
ondemand	/	25G	9.7G	14G	42%	don't care
ondemand	/data	216G	206M	205G	1%	don't care
mirrors-qa	/	38G	3.6G	33G	10%	-
demo	/data	1.8T	923G	740G	56%	don't care

Misc

• a number of errors due to September 1st incident #242 : periodic tasks depending on online services
• many restarts due to September 1st incident #242: all of zim namespace, the drives, nautilus-api, matomo-db, zimit-api and zimfarm watcher
• zimfarm dashboard is still out Zimfarm dashboard broken #238
• first working library-gen after incident took 2.5h ; back to normal after
• storage server's md1 is syncing (which is OK) but it seems to be way behind. I doubt this much new data had been written recently.

Now looks at 7d

@benoit74 any explanation for this (we dropped to 0 on 2024-9-01 at 00:40)? Is it possible that one disk was changed without us being informed? Or the raid system decided to rewrite all fropm scratch to recover from some erro?

• Unused Signings: 1045

[rgaudin]

root@k8s-storage-node:~# cat /etc/cron.d/mdadm
#
# cron.d/mdadm -- schedules periodic redundancy checks of MD devices
#
# Copyright © martin f. krafft <[email protected]>
# distributed under the terms of the Artistic Licence 2.0
#

# By default, run at 00:57 on every Sunday, but do nothing unless the day of
# the month is less than or equal to 7. Thus, only run on the first Sunday of
# each month. crontab(5) sucks, unfortunately, in this regard; therefore this
# hack (see #380425).
57 0 * * 0 root if [ -x /usr/share/mdadm/checkarray ] && [ $(date +\%d) -le 7 ]; then /usr/share/mdadm/checkarray --cron --all --idle --quiet; fi

[rgaudin]

zimit

• pipe is empty
• (1) x ERR_INVALID_AUTH_CREDENTIALS
• (1) x ERR_INVALID_RESPONSE
• (1) x Some websites are raising HTTP2 errors on sisyphus worker openzim/zimit#329
• (3) x ValueError: Title is too long
• (5) x LookupError: unknown encoding: unicode openzim/warc2zim#331 iso, ISO-8895-1, U, 3DUTF-8
• (1) x ERR_NAME_NOT_RESOLVED
• (1) x net::ERR_CONNECTION_REFUSED
• (4) x Navigation timeout of 90000 ms exceeded
• (1) x Invalid UTF-8 (surrogates) sent to libzim openzim/warc2zim#382
• (1) x Unable to get new page, browser likely crashed
• (5) x memory consumption (exit code 137) openzim/warc2zim#383
• (2) x Execution context was destroyed webrecorder/browsertrix-crawler#655
• (1) x incorrect waitUntil value (2)
• (1) x Invalid seed specified