Migration from RAID1 to RAID5 turned out to be many times easier than I thought 🙄 In general they are 5 simple little wait steps and 1 a beer for courage.
For me, the system has been created RAID array md0 in which they participate 2 sda and sdb disk. I will add a 3rd sdc to them to create RAID5 from 3 disk. In general, this acrobatics is for the scientific purpose of a virtual I have not yet tested it in a real environment, but I don't expect dramas on a real machine when the time comes.
We create the same file system layout as on our other disks – sfdisk -d /dev/sdb | sfdisk /dev/sdc
We are upgrading our current RAID5 array – mdadm –grow /dev/md0 –level=5
We add the new disk to the array – mdadm –manage /dev/md0 –add /dev/sdc . Here comes the thin point that the array is still RAID1 and will not start syncing because our new drive is spare
The most important moment sdc becomes active and synchronization begins – mdadm –grow /dev/md0 –raid-devices=3 . Good time to open your beer if it is not done 😉 Do not interrupt the process under any circumstances!!!
After the synchronization is over, it has to resize the partition because the loss of space in RAID1 is 1 / n and in RAID5 is 1-1 / n
The biggest bonus is that there is no need to restart the system or remove and create additional arrays.
We are preparing a new hosting service and during the tests when trying to connect between WHMCS and Cloudmin we had the following error
CURL Error: 7 – couldn’t connect to host
Fun, I immediately check the connection between the machines where the WHMCS and the Cloudmin are, everything works. I'm checking the 10000th port and it's open and I have access to it 🙄 . Fun!
I'm doing a quick cloudmin server
tcpdump -i br0 host WHMCS_IP
and for mine (not very big) amazement I see that trying to connect to the 80's or 443 (if SSL is enabled) ports without asking me for one. By default, webmin and cloudmin, which is an application to the former, run on SSL 10000 port. Because this stupid system is IonCube encrypted, you can't edit your code to fix Indian nonsense, so you have to take a radical approach.. Before leaving the system, I replace the destination port with iptables
where you replace cloudmin_ip with the IP of your cloudmin installation. After this small manipulation, the connection between WHMCS and Cloudmin took place, but the module still has other problems besides this 😆
In general, for a year of using WHMCS I am extremely disappointed with it – it is quite wooden, support team support is slow, the documentation of the code and various other things diverge from reality, quite a lot of bugs and is quite wooden. If I knew it was so bad I would prefer to use it with a reset license instead of giving 300$ for something that works somehow!