View Issue Details

IDProjectCategoryView StatusLast Update
0010717Talerdeployment and operationspublic2025-12-12 00:58
ReporterFlorian Dold Assigned Tovecirex  
PriorityhighSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0010717: weblate does not send emails anymore
DescriptionThere's something broken with our weblate setup, emails for changing passwords aren't sent anymore.
TagsNo tags attached.

Relationships

related to 0010715 closedsebasjm translation string is not in sync with weblate 
child of 0010630 closedvecirex Set my.taler-ops.ch live [done in principle by this morning: still solving deps; work parallelized] 

Activities

vecirex

2025-12-05 18:01

manager   ~0026790

See infra chat: no weblate-notify worker can be found running, last sign of mail sent: Nov 17; more permissions needed on that server to attempt try-restart and then restart the celery-weblate.service systemd unit which should incite all needed workers when started; they can be seen here:

weblate@firefly:/etc/systemd/system$ cat /etc/default/celery-weblate | grep queues
CELERYD_OPTS="--beat:celery --queues:celery=celery --prefetch-multiplier:celery=4 \
    --queues:notify=notify --prefetch-multiplier:notify=10 \
    --queues:memory=memory --prefetch-multiplier:memory=10 \
    --queues:translate=translate --prefetch-multiplier:translate=4 \
    --concurrency:backup=1 --queues:backup=backup --prefetch-multiplier:backup=2"
weblate@firefly:/etc/systemd/system$

vecirex

2025-12-05 18:02

manager   ~0026791

I increased prio on this ticket as we need weblate functional to progress with 0010630.

Florian Dold

2025-12-08 12:28

manager   ~0026816

@vecirex: I've restarted the service (a few days ago) and e-mails seem to be working again.

Do we know *why* it stopped working?

vecirex

2025-12-09 12:07

manager   ~0026838

Nice, thanks: @stefan confirms it to work for all things needed, so closing this.

And:
No, I couldn't find any sensible log info (at least not with the $USER I have).

But yeah, as said above: if this happens again, we should investigate; I could just see that resource consumption was quite high (up to 12G of RAM) at some point in time, acc. to systemctl's status info.

vecirex

2025-12-09 12:07

manager   ~0026839

Closing, but we can reopen if it happens again.

Issue History

Date Modified Username Field Change
2025-12-04 11:19 Florian Dold New Issue
2025-12-04 11:19 Florian Dold Status new => assigned
2025-12-04 11:19 Florian Dold Assigned To => vecirex
2025-12-04 15:42 sebasjm Relationship added related to 0010715
2025-12-05 18:01 vecirex Assigned To vecirex => Florian Dold
2025-12-05 18:01 vecirex Priority normal => high
2025-12-05 18:01 vecirex Status assigned => feedback
2025-12-05 18:01 vecirex Note Added: 0026790
2025-12-05 18:02 vecirex Note Added: 0026791
2025-12-05 18:06 sebasjm Relationship added related to 0010630
2025-12-08 12:28 Florian Dold Note Added: 0026816
2025-12-08 12:28 Florian Dold Assigned To Florian Dold => vecirex
2025-12-09 12:07 vecirex Note Added: 0026838
2025-12-09 12:07 vecirex Status feedback => closed
2025-12-09 12:07 vecirex Resolution open => fixed
2025-12-09 12:07 vecirex Note Added: 0026839
2025-12-12 00:58 vecirex Relationship replaced child of 0010630