Difference between revisions of "Smeadmin"
Unnilennium (talk | contribs) |
Unnilennium (talk | contribs) |
||
Line 7: | Line 7: | ||
=== Version === | === Version === | ||
− | {{ #smeversion: smeserver-sme9admin}} | + | {{#smeversion: smeserver-sme9admin}} |
=== Maintainer === | === Maintainer === | ||
− | [mailto:tests@pialasse.com[[User:Unnilennium|Unnilennium | + | [mailto:tests@pialasse.com][[User:Unnilennium|Unnilennium]] |
− | [mailto:daniel@firewall-services.com[[User:VIP-ire|Daniel B. | + | [mailto:daniel@firewall-services.com][[User:VIP-ire|Daniel B.]] from [http://www.firewall-services.com Firewall Services] |
[mailto:stephdl@de-labrusse.fr stephdl] Stéphane de Labrusse AKA [[User:stephdl|Stephdl]]<br /> | [mailto:stephdl@de-labrusse.fr stephdl] Stéphane de Labrusse AKA [[User:stephdl|Stephdl]]<br /> | ||
Line 70: | Line 70: | ||
After reboot disabled IMAP will be set automatically to enabled and access to localhost. | After reboot disabled IMAP will be set automatically to enabled and access to localhost. | ||
+ | |||
+ | ==== CRITICAL - md0 [U_] has 1 of 2 devices active (active=sda1 failed=none spare=none) ==== | ||
+ | Any sme9 installation will have a raid 1 boot partition. If you want to avoid to see this warning you can do the following: | ||
+ | |||
+ | <syntaxhighlight lang="bash"> | ||
+ | mdadm --grow /dev/md0 --raid-devices=1 --force | ||
+ | </syntaxhighlight> | ||
===Troubleshoot section=== | ===Troubleshoot section=== | ||
Line 104: | Line 111: | ||
===Changelog=== | ===Changelog=== | ||
Only released version in smecontrib are listed here. | Only released version in smecontrib are listed here. | ||
− | {{ #smechangelog: smeserver-sme9admin }} | + | {{#smechangelog: smeserver-sme9admin }} |
---- | ---- | ||
[[Category: Contrib]] | [[Category: Contrib]] | ||
[[Category: Administration:Monitoring]] | [[Category: Administration:Monitoring]] |
Revision as of 21:28, 12 February 2018
sme9admin for SME Server
for a sme 7 version check sme7admin
for a sme 8 version check sme8admin
Version
Maintainer
[2]Daniel B. from Firewall Services
stephdl Stéphane de Labrusse AKA Stephdl
Description
- sme9admin is a graphical monitor, alert raising, and services supervision tool for your SME 9 Server.
- It adds a headline + several subpages to the server-manager.
Installation
yum install smeserver-sme9admin --enablerepo=smecontribs
then
signal-event sme9admin-update
or if you want to restart your server
signal-event post-upgrade; signal-event reboot
Sensor detection
Detect the sensors on your mainboard, (run as root)
/usr/sbin/sensors-detect
For my mainboard, I just hit enter for all questions, which then uses the defaults which can be seen as CAPs. You will need to follow the instructions in order to add the detected sensors in rc.local to have them loaded on reboot.
see lm-sensors wiki and more particularly lm-sensors device
Check installed versions
yum info installed smeserver-sme9admin yum info installed sysstat yum info installed hddtemp yum info installed perl-rrdtool yum info installed rrdtool
Uninstall
yum remove smeserver-sme9admin
Additional information
If you connect to the SMEserver console by Putty ssh-client (or similar) you can copy and paste the commands (very convenient).
Good luck /Per
Known Problems
du -s and CPU
The du -s option allows you to have detailed information on the use of your hard drive. Unfortunately with the high volume of data in recent huge drives and/or with older slower CPUs, you should NOT use this option unless you want to see constant high CPU utilization, as this command will be launched every 5 minutes.
disabling IMAP
Disabling IMAP will fails webmail authentication. As a result, disabling IMAP will only work until new reboot or some event to be trigger. This will also make webmail fails until next reboot.
After reboot disabled IMAP will be set automatically to enabled and access to localhost.
CRITICAL - md0 [U_] has 1 of 2 devices active (active=sda1 failed=none spare=none)
Any sme9 installation will have a raid 1 boot partition. If you want to avoid to see this warning you can do the following:
mdadm --grow /dev/md0 --raid-devices=1 --force
Troubleshoot section
Here some tricks and tips to understand what is occurring if you have problem with sme9admin
- look what sysstat can collect
/usr/lib/sa/sadc 1 2 > sadc.bout sar -A -n DEV -f sadc.bout
- look what sadf has stocked (sadf is a human readable file)
less /var/log/sarXX
XX is a number adapt it.
- look if sensors are working
sensors
sensors need to be activated first
sensors-detect
press 'enter' for all questions and reboot
- look if hddtemp is working
hddtemp /dev/sda
- rdd files
all rdd files are in /var/lib/sme9admin, which are binary files. If you want to look the dump to see what it contains
rrdtool dump /var/lib/sme9admin/sensors.rrd > /tmp/sensors.xml less /tmp/sensors.xml
You have to do it for each file.rrd
- Logs of sme9admin
less /var/log/sme9admin.log
Bugs
Please raise bugs under the SME-Contribs section in bugzilla and select the smeserver-sme9admin component or use this link .
Below is an overview of the current issues for this contrib:
Changelog
Only released version in smecontrib are listed here.