Re: [CentOS] How to Migrate Wordpress Website from 32-bit CentOS Linux 6.3 to 64-bit CentOS Linux 8.2 (2004)
On Mon, Aug 31, 2020 at 3:47 PM Jim Perrin wrote: > > I've moderated him (again). If this keeps up I'll see what can be done > for a more permanent solution. > I just found out he also pushed his infomercial onto the apache mailing list. > On 8/31/20 11:15, Richard wrote: > > > > > >> Date: Monday, August 31, 2020 19:04:25 +0100 > >> From: Pete Biggs > >> > >>> Why are you even posting this to a public list? Use your blog for > >>> this kind of thing. I know you have one, you post it repeatedly to > >>> random lists. > >>> > >> At least posting to a public list like this means that there is some > >> chance people will read the subsequent posts and realise the > >> quality of instructions. > >> > >> P. > >> > > > > He cross-posted this to at least three other lists (apache/httpd, > > maria-discuss and php) where these types of issues are generally out > > of scope. > > > > He has been moderated on this list, but appears to have used yet > > another email address for this posting. > > > > > > ___ > > CentOS mailing list > > CentOS@centos.org > > https://lists.centos.org/mailman/listinfo/centos > > > > -- > Jim Perrin > The CentOS Project | http://www.centos.org > twitter: @BitIntegrity | GPG Key: FA09AD77 > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to Migrate Wordpress Website from 32-bit CentOS Linux 6.3 to 64-bit CentOS Linux 8.2 (2004)
I've moderated him (again). If this keeps up I'll see what can be done for a more permanent solution. On 8/31/20 11:15, Richard wrote: Date: Monday, August 31, 2020 19:04:25 +0100 From: Pete Biggs Why are you even posting this to a public list? Use your blog for this kind of thing. I know you have one, you post it repeatedly to random lists. At least posting to a public list like this means that there is some chance people will read the subsequent posts and realise the quality of instructions. P. He cross-posted this to at least three other lists (apache/httpd, maria-discuss and php) where these types of issues are generally out of scope. He has been moderated on this list, but appears to have used yet another email address for this posting. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to Migrate Wordpress Website from 32-bit CentOS Linux 6.3 to 64-bit CentOS Linux 8.2 (2004)
On Mon, Aug 31, 2020, 6:31 AM Turritopsis Dohrnii Teo En Ming < ceo-teo-en-m...@outlook.com> wrote: > Subject: How to Migrate Wordpress Website from 32-bit CentOS Linux 6.3 to > 64-bit CentOS Linux 8.2 (2004) > > ... > > Host operating system is Windows Server 2008 R2 Standard > > Host Processor: Intel Xeon CPU E5620 @ 2.40 GHz > > Host Memory: 24 GB RAM > > Old Oracle VirtualBox version is 4.1.18 > obsolete proprietary OS, obsolete hardware, obsolete VirtualBox Even if you didn't get all kind of things wrong in your instructions (see previous replies), its OFF TOPIC on this list. your Wordpress upgrade could have been simplified to... 1) install and secure new OS on new system or VM 2) install and configure mysql or mariadb from OS distribution 3) mysql dump old database, restore on new server 4) tar up old wordpress and restore on new server 5) configure old wordpress to use new database, start it up 6) run sttandard wordpress upgrade. done. but this all is standard Wordpress administration, completely off topic for CentOS lists. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to Migrate Wordpress Website from 32-bit CentOS Linux 6.3 to 64-bit CentOS Linux 8.2 (2004)
> Date: Monday, August 31, 2020 19:04:25 +0100 > From: Pete Biggs > >> Why are you even posting this to a public list? Use your blog for >> this kind of thing. I know you have one, you post it repeatedly to >> random lists. >> > At least posting to a public list like this means that there is some > chance people will read the subsequent posts and realise the > quality of instructions. > > P. > He cross-posted this to at least three other lists (apache/httpd, maria-discuss and php) where these types of issues are generally out of scope. He has been moderated on this list, but appears to have used yet another email address for this posting. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to Migrate Wordpress Website from 32-bit CentOS Linux 6.3 to 64-bit CentOS Linux 8.2 (2004)
> Why are you even posting this to a public list? Use your blog for > this kind of thing. I know you have one, you post it repeatedly to > random lists. > At least posting to a public list like this means that there is some chance people will read the subsequent posts and realise the quality of instructions. P. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to Migrate Wordpress Website from 32-bit CentOS Linux 6.3 to 64-bit CentOS Linux 8.2 (2004)
On Mon, Aug 31, 2020 at 11:35 AM Jake Shipton wrote: > 2020-08-31 (月) の 13:31 + に Turritopsis Dohrnii Teo En Ming > さんは書きました: > > > > SECTION 4 Disable SELinux (Security Enhanced Linux) > > === > > > > You MUST disable SELinux, otherwise Apache web server will not work. > > > > If you DO NOT want to disable SELinux, you must be an expert in > > SELinux to configure SELinux. > > > Don't do this. You don't need to be an expert to configure SELinux, if > you install setroubleshootd then 9 times out of 10 it will tell you how > to fix something SELinux is blocking, and when that doesn't work, > there's always DuckDuckGo if you're not sure. > > SELinux may be daunting to a newcomer, but just like Apparmor on > Debian, it's well worth reading about and learning the security > advantages it provides. > > I always advise both security methods are left enabled where a > distribution supports them. (not at the same time.) > > To make the point further, SELinux has been in the disro since 4, in 2005. If you haven't learned it yet you are far, far, behind the times. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to Migrate Wordpress Website from 32-bit CentOS Linux 6.3 to 64-bit CentOS Linux 8.2 (2004)
2020-08-31 (月) の 13:31 + に Turritopsis Dohrnii Teo En Ming さんは書きました: > > SECTION 4 Disable SELinux (Security Enhanced Linux) > === > > You MUST disable SELinux, otherwise Apache web server will not work. > > If you DO NOT want to disable SELinux, you must be an expert in > SELinux to configure SELinux. > Don't do this. You don't need to be an expert to configure SELinux, if you install setroubleshootd then 9 times out of 10 it will tell you how to fix something SELinux is blocking, and when that doesn't work, there's always DuckDuckGo if you're not sure. SELinux may be daunting to a newcomer, but just like Apparmor on Debian, it's well worth reading about and learning the security advantages it provides. I always advise both security methods are left enabled where a distribution supports them. (not at the same time.) > SECTION 5 Disable firewalld Software Firewall > = > > Because already protected by Fortigate firewall at the perimeter. > > # systemctl disable firewalld > > # reboot > > This is another big security no-no. Never disable the firewall, even if that system is behind another system. Configure the firewall correctly in all cases and have it enabled. After all, if someone breaks through your "Fortigate Firewall", your system will be wide open to anyone who gets inside. Honestly, I believe after reading this tutorial, your system would be wide open for easy attack and hijacking. Your tutorial is a little scary to read.. Just sayin... :-O. But keep studying and practising, and look deeper into the various ways to secure a system correctly, such as not installing/running things you don't need and not unnecessarily disabling things. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to Migrate Wordpress Website from 32-bit CentOS Linux 6.3 to 64-bit CentOS Linux 8.2 (2004)
On Mon, Aug 31, 2020 at 01:31:19PM +, Turritopsis Dohrnii Teo En Ming wrote> SECTION 4 Disable SELinux (Security Enhanced Linux) > === > > You MUST disable SELinux, otherwise Apache web server will not work. > > If you DO NOT want to disable SELinux, you must be an expert in SELinux to > configure SELinux. > > # nano /etc/selinux/config > > SELINUX=disabled > > # reboot Stop posting these terrible instructions to the list! This is terrible advice and should not be considered. Wordpress is such a huge vector for attacks, you need SELinux protecting your system. You don't need to be an expert, and people posting misleading information only makes more people think so. > SECTION 5 Disable firewalld Software Firewall > = > > Because already protected by Fortigate firewall at the perimeter. > > # systemctl disable firewalld > > # reboot Also terrible advice! That's just the case for your weird corner case. I looked at more of this post, and was amazed by the amount of cargo-cult apache configuration advice that's listed. mod_perl *and* mod_php? Each httpd must be huge! Why are you even posting this to a public list? Use your blog for this kind of thing. I know you have one, you post it repeatedly to random lists. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] How to Migrate Wordpress Website from 32-bit CentOS Linux 6.3 to 64-bit CentOS Linux 8.2 (2004)
Subject: How to Migrate Wordpress Website from 32-bit CentOS Linux 6.3 to 64-bit CentOS Linux 8.2 (2004) Author of this Guide: Mr. Turritopsis Dohrnii Teo En Ming (TARGETED INDIVIDUAL) Country: Singapore Date: 31 August 2020 Monday Singapore Time Type of Publication: Plain Text Document Version: 20200831.01 SECTION 1 Information Gathering Stage = Host operating system is Windows Server 2008 R2 Standard Host Processor: Intel Xeon CPU E5620 @ 2.40 GHz Host Memory: 24 GB RAM Old Oracle VirtualBox version is 4.1.18 Upgrade to Virtualbox version 6.1.12 (COMPLETED SUCCESSFULLY AFTER RESTARTING WINDOWS SERVER) Old CentOS Linux VM is version 6.3 (32-bit only) Old Apache web server version 2.2.15 Old MySQL database server version 5.1.61 Old PHP version 5.6.40 Interface eth0: AAA.BBB.CCC.3/24 (ifconfig) Gateway: AAA.BBB.CCC.2 (ip route) (Gateway is the next hop router which is also the Fortigate firewall) /etc/resolv.conf (for DNS Client): nameserver AAA.BBB.CCC.1 (This is the Windows Server with DNS Server role installed) How to login to OLD MySQL database server: mysql -u root -p Old hostname: centos63.teo-en-ming-corp.com Old Virtual Machine Settings 4 GB RAM, 2 processors, 20 GB storage, network adapter: bridged to broadcom bcm5709c NEW Virtual Machine Settings 4 GB RAM, 4 processors, 100 GB storage, network adapter: bridged to broadcom bcm5709c After using Advanced IP scanner and checking DHCP scope in Microsoft DHCP server in Windows Server, Unused IP address: AAA.BBB.CCC.4 (Use this IP address for new CentOS 8.2 Linux VM) SECTION 2 Installation of NEW CentOS 8.2 Linux Virtual Machine == New Hostname: centos82.teo-en-ming-corp.com NEW IP: AAA.BBB.CCC.4 Subnet mask: 255.255.255.0 (Class C) Gateway: AAA.BBB.CCC.2 DNS1: 8.8.8.8 Problem === CentOS 8.2 Linux 64-bit will not start and run because VirtualBox is too old (version 4.1.18). Intel Virtualization and VT-d already enabled in server BIOS previously. So running 64-bit virtual machines is not an issue. Solution After upgrading to VirtualBox 6.1.12, CentOS 8.2 Linux 64-bit is able to start and run. SECTION 3 Generate a Backup of ALL Databases in the Old VM === Reference Guide: How to backup and restore MySQL databases using the mysqldump command Link: https://www.sqlshack.com/how-to-backup-and-restore-mysql-databases-using-the-mysqldump-command/ Reference Guide: How to Show Users in MySQL using Linux Link: https://www.hostinger.com/tutorials/mysql-show-users/ # cd /root # mysqldump -u root -p --all-databases > all-databases-20200829.sql # du -h all-databases-20200829.sql 70M all-databases-20200829.sql SECTION 4 Disable SELinux (Security Enhanced Linux) === You MUST disable SELinux, otherwise Apache web server will not work. If you DO NOT want to disable SELinux, you must be an expert in SELinux to configure SELinux. # nano /etc/selinux/config SELINUX=disabled # reboot SECTION 5 Disable firewalld Software Firewall = Because already protected by Fortigate firewall at the perimeter. # systemctl disable firewalld # reboot SECTION 6 LAMP (Linux, Apache, MySQL and PHP) Installation == I will be installing Apache web server 2.4.37-21, MariaDB server 3:10.3.17-1, PHP 7.2.24-1 and OpenSSL 1:1.1.1c-15 in 64-bit CentOS Linux 8.2 (2004). Sub-Section on Installing Apache Web Server === # dnf install php php-fpm php-gd You *MUST* install php-gd, otherwise Apache Web Server cannot execute PHP scripts. # dnf install httpd # systemctl enable httpd # systemctl start httpd [root@centos82 ~]# ps -ef | grep httpd root 33214 1 0 22:03 ?00:00:00 /usr/sbin/httpd -DFOREGROUND apache 33351 33214 0 22:03 ?00:00:00 /usr/sbin/httpd -DFOREGROUND apache 33352 33214 1 22:03 ?00:00:00 /usr/sbin/httpd -DFOREGROUND apache 33355 33214 1 22:03 ?00:00:00 /usr/sbin/httpd -DFOREGROUND apache 33357 33214 0 22:03 ?00:00:00 /usr/sbin/httpd -DFOREGROUND root 363747368 0 22:03 pts/000:00:00 grep --color=auto httpd On the OLD CentOS 6.3 server: # cd /etc/httpd # tar cfvz apacheconf.tar.gz conf conf.d # mv apacheconf.tar.gz /root On the NEW CentOS 8.2 server: # cd /etc/httpd # cp -r conf conf.original # cp -r conf.d conf.d.original # scp r...@aaa.bbb.ccc.3:/root/apacheconf.tar.gz . # tar xfvz apacheconf.tar.gz On the OLD CentOS 6.3 server: # cd /var/www/html # tar cfvz websites.tar.gz * (1.4 GB) On the NEW CentOS 8.2 server: # cd /var/www/html # scp r...@aaa.bbb.ccc.3:/root/websites.tar.gz . # tar x
