The following NEW packages will be installed:
acl python3-argcomplete python3-bottle python3-certifi python3-chardet
python3-dnspython python3-gevent python3-gevent-websocket python3-greenlet
python3-idna python3-jinja2 python3-ldap python3-markupsafe
python3-miniupnpc python3-openssl python3-packaging python3-psutil
python3-publicsuffix python3-pyasn1 python3-pyasn1-modules python3-pyparsing
python3-requests python3-toml python3-tz python3-urllib3 python3-yaml
The following packages will be upgraded:
moulinette ssowat yunohost yunohost-admin
4 upgraded, 26 newly installed, 0 to remove and 0 not upgraded.
Need to get 10.7 MB/10.7 MB of archives.
Setting up yunohost (4.2.0) …
Installing new version of config file /etc/bash_completion.d/yunohost …
Regenerating configuration, this might take a while…
The configuration file ‘/etc/cron.d/yunohost-dyndns’ is now managed by YunoHost (category yunohost).
Configuration updated for ‘yunohost’
The configuration file ‘/etc/ssh/sshd_config’ has been manually modified and will not be updated
Configuration updated for ‘apt’
Configuration updated for ‘nginx’
Configuration updated for ‘dnsmasq’
The configuration file ‘/etc/fail2ban/jail.conf’ has been manually modified and will not be updated
ERROR 1045 (28000): Access denied for user ‘root’@‘localhost’ (using password: NO)
Launching migrations…
No migrations to run
Re-diagnosing server health…
Found 1 significant issue(s) related to Base system!
Everything looks good for Internet connectivity! (+ 1 ignored issue(s))
Everything looks good for DNS records!
Everything looks good for Ports exposure!
Everything looks good for Web!
verything looks good for Services status check!
Everything looks good for System resources!
Everything looks good for System configurations! (+ 2 ignored issue(s))
To see the issues found, you can go to the Diagnosis section of the webadmin, or run ‘yunohost diagnosis show --issues’ from the command-line.
(Reading database … 55608 files and directories currently installed.)
Preparing to unpack …/yunohost-admin_4.2.0_all.deb …
Unpacking yunohost-admin (4.2.0) over (4.1.4) …
Setting up yunohost-admin (4.2.0) …
Processing triggers for systemd (241-7~deb10u6+rpi1) …
Processing triggers for man-db (2.8.5-2) …
Done!
YunoHost package upgrade completed.
Press [Enter] to get the command line back
Il y a une ligne qui me pose question : c’est grave ?
ERROR 1045 (28000): Access denied for user ‘root’@‘localhost’ (using password: NO)
La seule chose que j’ai faite pour le moment est de naviguer dans -la nouvelle- interface web sans problème.
J’ai aussi lancé un diagnostic qui m’a bien relevé, tout en les gardant ignorées, les “anomalies” que j’avais précédemment ignorées suite au “tweak” volontaire.
Si tu te connecte en root (ou bien depuis admin, puis deviens root avec sudo su) : est que la commande mysql (sans argument) ouvre bien un shell, ou est-ce que tu as la même erreur ?
admin@:~$ sudo su
root@:/home/admin# mysql
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 15
Server version: 10.3.27-MariaDB-0+deb10u1 Raspbian 10
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.
MariaDB [(none)]>
When I try to access the services in the webadmin I get this error.
I don’t remember which of my actions led to such a disaster (I remember trying to remove Movim service with CLI…)
I am upgrading to 4.2.1. This message was not shown at the top of the page as it was the case before:
The special upgrade will continue in the background. Please don’t start any other actions on your server for the next ~10 minutes (depending on hardware speed). After this, you may have to re-log in to the webadmin. The upgrade log will be available in Tools → Log (in the webadmin) or using ‘yunohost log list’ (from the command-line).
The message was hidden on the buttom and only visible when clicking on the message thet yunohost is upgrading.
Hi,
Just upgraded my server from 4.2.0 to 4.2.1 and I get 500 errors on the portal and every application.
I have this recurring error in the nginx -error.log:
2021/04/10 15:02:12 [error] 853#853: *466 lua entry thread aborted: runtime error: /usr/share/ssowat/access.lua:296: bad argument #1 to 'pairs' (table expected, got nil)
stack traceback:
coroutine 0:
[C]: in function 'pairs'
/usr/share/ssowat/access.lua:296: in function </usr/share/ssowat/access.lua:1>, client: 192.168.1.254, server: <domain>, request: "GET /ynhtheme/custom_overlay.css HTTP/2.0", host: "monin.net", referrer: "https://<domain>/"
All systemd services are running OK, yet I also lost the possibility to log on my XMPP account via Pidgin (“Vous voulez un chiffrement, mais il n’est pas disponible sur ce serveur”).
Could you please point me to where to look for more hints?
Thanks!
This is a super obscure message but i know from experience that it’s related to a bad certificate … Are you aware of anything related to /etc/yunohost/certs/yunohost.org/crt.pem or key.pem ?
Edit: hmpf in fact propagating the change is not that trivial … you need to do :
# Validate the new slapd config
# To do so, we have to use the .ldif to generate the config directory
# so we use a temporary directory slapd_new.d
rm -Rf /etc/ldap/slapd_new.d
mkdir /etc/ldap/slapd_new.d
slapadd -n0 -l /etc/ldap/slapd.ldif -F /etc/ldap/slapd_new.d/ 2>&1 \
| grep -v "none elapsed\|Closing DB" || true
# Actual validation (-Q is for quiet, -u is for dry-run)
slaptest -Q -u -F /etc/ldap/slapd_new.d
# "Commit" / apply the new config (meaning we delete the old one and replace
# it with the new one)
rm -Rf /etc/ldap/slapd.d
mv /etc/ldap/slapd_new.d /etc/ldap/slapd.d
chown -R openldap:openldap /etc/ldap/slapd.d/
service slapd force-reload
