3,250
edits
Changes
Jump to navigation
Jump to search
Line 4:
Line 4: + + + Line 10:
Line 13: − + + + + − yum --enablerepo=stephdl install smeserver-raidstatus + + + − You will then need to activate the database changes etc.+ − The 'official' way is to perform + + + − + + + − + Line 30:
Line 42: + + + + + + + + Line 35:
Line 55: − Not yet a component in bugzilla, please raise a bug in the unknown section. + + + + + + + + +
→Installation
==Maintainer==
==Maintainer==
[mailto:stephdl@de-labrusse.fr[[User:stephdl|Stephane de Labrusse aka stephdl]]]<br />
[mailto:stephdl@de-labrusse.fr[[User:stephdl|Stephane de Labrusse aka stephdl]]]<br />
===Version===
{{#smeversion: smeserver-raidstatus }}
[[Version::contrib9|stephdl]][[Has SME9::true| ]]
=== Description ===
=== Description ===
=== Installation ===
=== Installation ===
This contrib is currently held in the [[stephdl]] repository, so the following commands will install on your SME Server.
<tabs container><tab name="For SME 10">
yum --enablerepo=smecontribs install smeserver-raidstatus
</tab><tab name="For SME 9">
This contrib is currently held in an external non default repository. You must first configure the stephdl repository on your SME server by following the steps here [[stephdl]] (if not already configured).
You can check the repo status as follows
db yum_repositories show stephdl
If you receive no output then the repo is not configured on your SME server.
Then run the following commands to install the Raidstatus contrib on your SME Server.<br />
'''for sme8 or sme9'''
yum --enablerepo=stephdl install smeserver-raidstatus
Then activate the database changes as follows:
signal-event post-upgrade; signal-event reboot
signal-event post-upgrade; signal-event reboot
or if you do not want to restart the server
or if you do not want to restart the server, simply do
signal-event console-save
signal-event console-save
</tab>
</tabs>
Go to the Server Manager and check the status of raid
Go to the Server Manager and check the status of raid
In case of your raid is desynchronized, please check our documentation http://wiki.contribs.org/Raid:Manual_Rebuild.
In case the raid is unsynchronized, please check the documentation at http://wiki.contribs.org/Raid:Manual_Rebuild.
=== Usage ===
=== Usage ===
GREEN : All is Ok, you can return to work
GREEN : All is Ok, you can return to work
====mailto====
This contribs send a mail every sunday with the status of each array of your software raid. The recipient is admin but you can change this by a db command
config setprop raidstatus mailto "foo@foo.com"
or if you need several recipients
config setprop raidstatus mailto "foo@foo.com foo@foo.be foo@foo.fr"
=== Uninstall ===
=== Uninstall ===
yum remove smeserver-raidstatus
yum remove smeserver-raidstatus
=== Bugs ===
=== Bugs ===
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title= bugzilla}}
and select the smeserver-openvpn-bridge component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-raidstatus|title=this link}}
{{#bugzilla:columns=id,product,version,status,summary |sort=id |order=desc |component=smeserver-raidstatus|noresultsmessage="No open bugs found."}}
===Changelog===
Only versions released in smecontrib are listed here.
{{#smechangelog: smeserver-raidstatus}}
[[Category: Contrib]]
[[Category: Contrib]]