Implementing a diagnostic function would help debugging by providing useful information on Yunohost instance:
- debian version wheezy/jessie
- yunohost version
- running / non running services
- apps installed (including community app)
- server status like RAM and disk usage
- packages versions
- main domain
Some information can be personal, so we need to carefully show them to the user.
#3 Updated by opi about 1 year ago
Current status of development:
root@yunohost:/# yunohost tools diagnosis --private host: Debian 8.3 kernel: 3.16.0-62-generic packages: yunohost: 2.3.9 yunohost-admin: 2.3.4 moulinette: 2.3.4 ssowat: 2.3.0 system: disks: mapper/ubuntu--vg-root: Mounted on /host_src, 106.1GiB (10.3GiB free) memory: ram: 3.5GiB (1.4GiB free) swap: 0B (0B free) services: postfix: inactive (enabled) rspamd: inactive (enabled) nginx: running (enabled) [...] php5-fpm: running (enabled) ssh: inactive (enabled) applications: dokuwiki: Dokuwiki wordpress: Blog wallabag: Wallabag private: public_ip: IPv4: 111.222.333.444 IPv6: 2a01:1234:beef:cafe:dead:beef:cafe:dead domains: - my-yunohost.local - another-domain.com
#5 Updated by mbugeia about 1 year ago
@opi cool ! What do you think about systemctl status instead of yunohost service status ? For me systemctl give all the infos needed while the yunohost function give only a summary and sometime services (especially app specific service) are not properly reconized.