Hello Everyone,
My YunoHost server
Hardware: VPS bought online (OVH)
Debian: Buster GNU/Linux 10 (Buster)
YunoHost version: 4.1.7
I have access to my server : Through SSH
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
Description of my issue
I am getting some errors after an upgrade of my yunohost server to version 4.1.7. I cannot access to my services such as gitea/synapse and calendar. It happened after the upgrade of yunohost. I also dont know if it is related to the OVH incident recently.
When I try to get some info on my services I get:
> yunohost service status
ERROR: Failed to get status information via dbus for service supervisor, systemctl didn't recognize this service ('NoSuchUnit').
avahi-daemon:
configuration: unknown
description: Allows you to reach your server using 'yunohost.local' in your local network
last_state_change: 2021-03-14 21:52:13
start_on_boot: enabled
status: running
coturn-synapse:
configuration: unknown
description: coturn
last_state_change: 2021-03-14 21:52:16
start_on_boot: enabled
status: running
dnsmasq:
configuration: valid
description: Handles domain name resolution (DNS)
last_state_change: 2021-03-14 21:52:15
start_on_boot: enabled
status: running
dovecot:
configuration: unknown
description: Allows e-mail clients to access/fetch email (via IMAP and POP3)
last_state_change: 2021-03-14 21:52:18
start_on_boot: enabled
status: running
fail2ban:
configuration: valid
description: Protects against brute-force and other kinds of attacks from the Internet
last_state_change: 2021-03-14 21:52:23
start_on_boot: enabled
status: running
gitea:
configuration: unknown
description: Gitea
last_state_change: 2021-03-15 23:34:59
start_on_boot: enabled
status: running
matrix-synapse:
configuration: unknown
description: Synapse Matrix homeserver
last_state_change: 2021-03-15 23:35:08
start_on_boot: enabled
status: auto-restart
metronome:
configuration: unknown
description: Manage XMPP instant messaging accounts
last_state_change: 2021-03-15 00:00:00
start_on_boot: enabled
status: running
mysql:
configuration: unknown
description: Stores app data (SQL database)
last_state_change: 2021-03-14 21:52:21
start_on_boot: enabled
status: running
navidrome:
configuration: unknown
description: Web-based music collection server and streamer
last_state_change: 2021-03-14 21:52:14
start_on_boot: enabled
status: running
nginx:
configuration: valid
description: Serves or provides access to all the websites hosted on your server
last_state_change: 2021-03-14 21:52:21
start_on_boot: enabled
status: running
php7.3-fpm:
configuration: valid
description: The PHP 7.3 FastCGI Process Manager
last_state_change: 2021-03-14 21:52:20
start_on_boot: enabled
status: running
postfix:
configuration: unknown
description: Used to send and receive e-mails
last_state_change: 2021-03-14 21:52:20
start_on_boot: enabled
status: running
redis-server:
configuration: unknown
description: A specialized database used for rapid data access, task queue, and communication between programs
last_state_change: 2021-03-14 21:52:15
start_on_boot: enabled
status: running
rspamd:
configuration: unknown
description: Filters spam, and other e-mail related features
last_state_change: 2021-03-14 21:52:15
start_on_boot: enabled
status: running
slapd:
configuration: valid
description: Stores users, domains and related info
last_state_change: 2021-03-14 21:52:17
start_on_boot: enabled
status: running
ssh:
configuration: valid
description: Allows you to connect remotely to your server via a terminal (SSH protocol)
last_state_change: 2021-03-14 21:52:15
start_on_boot: enabled
status: running
supervisor:
configuration: unknown
description: Error: failed to get information for this service, it doesn't exists for systemd
last_state_change: unknown
start_on_boot: unknown
status: unknown
syncthing:
configuration: unknown
description: syncthing daemon for Syncthing
last_state_change: 2021-03-14 21:52:23
start_on_boot: enabled
status: running
yunohost-api:
configuration: unknown
description: Manages interactions between the YunoHost web interface and the system
last_state_change: 2021-03-14 21:52:14
start_on_boot: enabled
status: running
yunohost-firewall:
configuration: unknown
description: Manages open and close connection ports to services
last_state_change: 2021-03-14 21:52:23
start_on_boot: enabled
status: running
When I try to restart the supervisor service I get:
> yunohost service restart supervisor
Failed to restart supervisor.service: Unit supervisor.service not found.
Warning: Could not execute the command 'systemctl restart supervisor'
Error: Failed to get status information via dbus for service supervisor, systemctl didn't recognize this service ('NoSuchUnit').
Error: Could not restart the service 'supervisor'
Recent service logs:-- Logs begin at Mon 2021-03-15 23:46:21 CET, end at Tue 2021-03-16 00:48:30 CET. --
-- No entries --
The diagnosis gives :
=================================
Base system (basesystem)
=================================
[INFO] Server hardware architecture is kvm amd64
- Server model is OpenStack Foundation OpenStack Nova
[INFO] Server is running Linux kernel 4.19.0-14-amd64
[INFO] Server is running Debian 10.8
[INFO] Server is running YunoHost 4.1.7.4 (stable)
- yunohost version: 4.1.7.4 (stable)
- yunohost-admin version: 4.1.4 (stable)
- moulinette version: 4.1.4 (stable)
- ssowat version: 4.1.3 (stable)
=================================
Internet connectivity (ip)
=================================
[SUCCESS] Domain name resolution is working!
[SUCCESS] The server is connected to the Internet through IPv4!
- Global IP: xx.xx.xx.xx
- Local IP: xx.xx.xx.xx
[WARNING] The server does not have working IPv6.
- Having a working IPv6 is not mandatory for your server to work, but it is better for the health of the Internet as a whole. IPv6 should usually be automatically configured by the system or your provider if it's available. Otherwise, you might need to configure a few things manually as explained in the documentation here: https://yunohost.org/#/ipv6. If you cannot enable IPv6 or if it seems too technical for you, you can also safely ignore this warning.
=================================
DNS records (dnsrecords)
=================================
[SUCCESS] DNS records are correctly configured for domain maindomain.tld (category basic)
[ERROR] Some DNS records are missing or incorrect for domain maindomain.tld (category mail)
- Please check the documentation at https://yunohost.org/dns_config if you need help about configuring DNS records.
- The following DNS record does not seem to follow the recommended configuration:
Type: TXT
Name: @
Current value: [u'"v=spf1 a mx -all"', u'"v=spf1 include:mx.ovh.com ~all"', u'"1|www.maindomain.tld"']
Expected value: "v=spf1 a mx -all"
[WARNING] Some DNS records are missing or incorrect for domain maindomain.tld (category xmpp)
- Please check the documentation at https://yunohost.org/dns_config if you need help about configuring DNS records.
- According to the recommended DNS configuration, you should add a DNS record with the following info.
Type: SRV
Name: _xmpp-client._tcp
Value: 0 5 5222 maindomain.tld.
- According to the recommended DNS configuration, you should add a DNS record with the following info.
Type: SRV
Name: _xmpp-server._tcp
Value: 0 5 5269 maindomain.tld.
- According to the recommended DNS configuration, you should add a DNS record with the following info.
Type: CNAME
Name: muc
Value: maindomain.tld.
- According to the recommended DNS configuration, you should add a DNS record with the following info.
Type: CNAME
Name: pubsub
Value: maindomain.tld.
- According to the recommended DNS configuration, you should add a DNS record with the following info.
Type: CNAME
Name: vjud
Value: maindomain.tld.
- According to the recommended DNS configuration, you should add a DNS record with the following info.
Type: CNAME
Name: xmpp-upload
Value: maindomain.tld.
[WARNING] Some DNS records are missing or incorrect for domain maindomain.tld (category extra)
- Please check the documentation at https://yunohost.org/dns_config if you need help about configuring DNS records.
- According to the recommended DNS configuration, you should add a DNS record with the following info.
Type: A
Name: *
Value: xx.xx.xx.xx
[SUCCESS] DNS records are correctly configured for domain git.maindomain.tld (category basic)
[SUCCESS] DNS records are correctly configured for domain domain2.tld (category basic)
[SUCCESS] DNS records are correctly configured for domain domain2.tld (category mail)
[SUCCESS] DNS records are correctly configured for domain domain2.tld (category xmpp)
[SUCCESS] DNS records are correctly configured for domain domain2.tld (category extra)
[SUCCESS] Your domains are registered and not going to expire anytime soon.
- maindomain.tld expires in 190 days.
=================================
Ports exposure (ports)
=================================
[SUCCESS] Port 22 is reachable from outside.
- Exposing this port is needed for admin features (service ssh)
[SUCCESS] Port 25 is reachable from outside.
- Exposing this port is needed for email features (service postfix)
[SUCCESS] Port 80 is reachable from outside.
- Exposing this port is needed for web features (service nginx)
[SUCCESS] Port 443 is reachable from outside.
- Exposing this port is needed for web features (service nginx)
[SUCCESS] Port 587 is reachable from outside.
- Exposing this port is needed for email features (service postfix)
[SUCCESS] Port 993 is reachable from outside.
- Exposing this port is needed for email features (service dovecot)
[SUCCESS] Port 5222 is reachable from outside.
- Exposing this port is needed for xmpp features (service metronome)
[SUCCESS] Port 5269 is reachable from outside.
- Exposing this port is needed for xmpp features (service metronome)
[SUCCESS] Port 5349 is reachable from outside.
- Exposing this port is needed for [?] features (service coturn-synapse)
[ERROR] Port 8448 is not reachable from outside.
- Exposing this port is needed for [?] features (service matrix-synapse)
- To fix this issue, you most probably need to configure port forwarding on your internet router as described in https://yunohost.org/isp_box_config
[SUCCESS] Port 22000 is reachable from outside.
- Exposing this port is needed for [?] features (service syncthing)
=================================
Web (web)
=================================
[SUCCESS] Domain maindomain.tld is reachable through HTTP from outside the local network.
[SUCCESS] Domain git.maindomain.tld is reachable through HTTP from outside the local network.
[SUCCESS] Domain domain2.tld is reachable through HTTP from outside the local network.
=================================
Email (mail)
=================================
[SUCCESS] The SMTP mail server is able to send emails (outgoing port 25 is not blocked).
[SUCCESS] The SMTP mail server is reachable from the outside and therefore is able to receive emails!
[ERROR] The reverse DNS is not correctly configured in IPv4. Some emails may fail to get delivered or may get flagged as spam.
- Current reverse DNS: 145.ip-145-239-73.eu
Expected value: maindomain.tld
- You should first try to configure the reverse DNS with maindomain.tld in your internet router interface or your hosting provider interface. (Some hosting provider may require you to send them a support ticket for this).
- Some providers won't let you configure your reverse DNS (or their feature might be broken...). If you are experiencing issues because of this, consider the following solutions:
- Some ISP provide the alternative of using a mail server relay though it implies that the relay will be able to spy on your email traffic.
- A privacy-friendly alternative is to use a VPN *with a dedicated public IP* to bypass this kind of limits. See https://yunohost.org/#/vpn_advantage
- Or it's possible to switch to a different provider
[SUCCESS] The IPs and domains used by this server do not appear to be blacklisted
[SUCCESS] 0 pending emails in the mail queues
=================================
Services status check (services)
=================================
[SUCCESS] Service avahi-daemon is running!
[SUCCESS] Service coturn-synapse is running!
[SUCCESS] Service dnsmasq is running!
[SUCCESS] Service dovecot is running!
[SUCCESS] Service fail2ban is running!
[SUCCESS] Service gitea is running!
[ERROR] Service matrix-synapse is start-pre :(
- You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart matrix-synapse' and 'yunohost service log matrix-synapse').
[SUCCESS] Service metronome is running!
[SUCCESS] Service mysql is running!
[SUCCESS] Service navidrome is running!
[SUCCESS] Service nginx is running!
[SUCCESS] Service php7.3-fpm is running!
[SUCCESS] Service postfix is running!
[SUCCESS] Service redis-server is running!
[SUCCESS] Service rspamd is running!
[SUCCESS] Service slapd is running!
[SUCCESS] Service ssh is running!
[WARNING] Service supervisor is unknown :(
- You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart supervisor' and 'yunohost service log supervisor').
[SUCCESS] Service syncthing is running!
[SUCCESS] Service yunohost-api is running!
[SUCCESS] Service yunohost-firewall is running!
=================================
System resources (systemresources)
=================================
[SUCCESS] The system still has 899 MiB (46%) RAM available out of 1.9 GiB.
[INFO] The system has no swap at all. You should consider adding at least 512 MiB of swap to avoid situations where the system runs out of memory.
- Please be careful and aware that if the server is hosting swap on an SD card or SSD storage, it may drastically reduce the life expectancy of the device`.
[SUCCESS] Storage / (on device /dev/sda1) still has 3.8 GiB (20%) space left (out of 19 GiB)!
=================================
System configurations (regenconf)
=================================
[WARNING] Configuration file /etc/nslcd.conf appears to have been manually modified.
- This is probably OK if you know what you're doing! YunoHost will stop updating this file automatically... But beware that YunoHost upgrades could contain important recommended changes. If you want to, you can inspect the differences with 'yunohost tools regen-conf nslcd --dry-run --with-diff' and force the reset to the recommended configuration with 'yunohost tools regen-conf nslcd --force'
[WARNING] Configuration file /etc/ssh/sshd_config appears to have been manually modified.
- This is probably OK if you know what you're doing! YunoHost will stop updating this file automatically... But beware that YunoHost upgrades could contain important recommended changes. If you want to, you can inspect the differences with 'yunohost tools regen-conf ssh --dry-run --with-diff' and force the reset to the recommended configuration with 'yunohost tools regen-conf ssh --force'
I tried to restart nginx and reboot server but nothing worked.
I would really like to have your thoughts about this. Thank you in advance for your help !!