openDCIM
openDCIM is an open source application for DataCenter Infrastructure Management.
See also
hpacucli
hpacucli
allows control of the RAID array controllers on HP servers.
Installation on CentOS
- Download RPM from HP's website (free account required).
Install, e.g:
yum install hpacucli-9.40-12.0.x86_64.rpm
Usage
Status of All Controllers
To display the status of all RAID controllers:
hpacucli ctrl all show status
Example output:
Smart Array P410i in Slot 0 (Embedded)
Controller Status: OK
Cache Status: OK
Battery/Capacitor Status: OK
Configuration of All Controllers
To display the configuration of all RAID controllers:
hpacucli ctrl all show config
Example output:
Smart Array P410i in Slot 0 (Embedded) (sn: 5001438001AD7D90)
array A (SAS, Unused Space: 0 MB)
logicaldrive 1 (136.7 GB, RAID 1, OK)
physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 146 GB, OK)
physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SAS, 146 GB, OK)
SEP (Vendor ID PMCSIERA, Model SRC 8x6G) 250 (WWID: 5123432101AB8D8F)
Status of Logical Drives
To display the status of all logical drives on a specific controller:
hpacucli ctrl slot=0 ld all show status
Example output:
logicaldrive 1 (136.7 GB, 1): OK
Status of all physical drives
To display the status of all physical drives on a specific controller:
hpacucli ctrl slot=0 pd all show status
Example output:
physicaldrive 1I:1:1 (port 1I:box 1:bay 1, 146 GB): OK
physicaldrive 1I:1:2 (port 1I:box 1:bay 2, 146 GB): OK
See Also
Champions of Regnum
Champions of Regnum is a free-to-play MMORPG, available for Linux, Windows and MAC OS X.
See also
Motion
Motion is a program that runs as a service, monitors the input from cameras, and detects whether or not there is motion. It can then record that input to video or to consecutive screenshots.
See also
Skip one record on MySQL replication slave
MySQL replication can break for a wide multitude of reasons. The
following is a quick and dirty way to resume replication, if the error
that appears in the output of SHOW SLAVE STATUS\G
indicates that
replication stopped at a specific record.
It is a dirty way, because immediately after using it the database on the slave becomes different from that on the master by one record. If you can live with that, the skip-one method can help you quickly put the slave back in track.
On the MySQL CLI:
mysql> STOP SLAVE;
mysql> SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1;
mysql> START SLAVE;
mysql> SHOW SLAVE STATUS\G
Hopefully your replication will resume after this, and the value of
your Seconds_Behind_Master
will quickly be depleted.