[Freedombox-discuss] uwsgi service masked, radicale not working, bepasty seems ok.

[A. F. Cano]

On Thu, Apr 02, 2026 at 01:41:01PM -0700, Sunil Mohan Adapa wrote:
> ...
Thanks for the explanation of the new way of doing things.

> To debug your problem, please run the following commands:
> 
> systemctl status uwsgi-app at bepasty-freedombox.socket
> systemctl status uwsgi-app at radicale.socket
> 
> Also, you can view the logs with
> 
> journalctl -u uwsgi-app at bepasty-freedombox.socket -u
> uwsgi-app at bepasty-freedombox.service
> journalctl -u uwsgi-app at radicale.socket -u uwsgi-app at radicale.service

Ok, after
$ sudo  systemctl start uwsgi-app at radicale.socket
all tests pass for radicale.  The phone app just updated, so everything
seems to be back to normal.

However, bepasty is another story.  Even after stopping and starting it
I get

Apr 03 14:13:00 fbx systemd[1]: uwsgi-app at bepasty-freedombox.socket: Socket service uwsgi-app at bepasty-freedombox.service already active, refusing.
Apr 03 14:13:00 fbx systemd[1]: Failed to listen on uwsgi-app at bepasty-freedombox.socket - Socket for uWSGI app bepasty-freedombox.

I'll wait until the issue described in salsa is resolved.

Thsnks.

Augustine