Wordpress on Vultr 768
-
Just a bit of browsing I find this. You do actually seem to be out of memory, try adding
performance_schema = offto the [mysqld] section of my.cnf
-
@momurda said in Wordpress on Vultr 768:
Just a bit of browsing I find this. You do actually seem to be out of memory, try adding
performance_schema = offto the [mysqld] section of my.cnf
No go. Same result, same errors
-
Oh look, I fixed it!
(throws hands up and reinstalls.) -
Just don't forget to feed it... water it... say nurturing things to it.
-
Ah I forgot you put it in recovery mode. Turning that off might have fixed it, but if youre going to NIFO then that is ok too. Also when doing the reinstall make sure your permissions are right.
-
Wait, it works now? Or you reinstalled? Or both?
-
@scottalanmiller said in Wordpress on Vultr 768:
Wait, it works now? Or you reinstalled? Or both?
Sounds like both.
-
Think he means he fixed it by 'throwing hands up' and reinstalling. DOes the reinstall work though?
-
I "fixed it" by reinstalling. Now I'm in the process of setting up LAMP and then Wordpress again.
-
@fuznutz04 said in Wordpress on Vultr 768:
I "fixed it" by reinstalling. Now I'm in the process of setting up LAMP and then Wordpress again.
Gotcha
-
It's the old "Take that!" & nuke it from orbit ploy. Works every time.
-
@dafyre Exactly. Didn't want to waste any more time on it, especially since it was still in testing/setup stages.
-
@fuznutz04 said in Wordpress on Vultr 768:
@dafyre Exactly. Didn't want to waste any more time on it, especially since it was still in testing/setup stages.
Makes sense.
-
@scottalanmiller said in Wordpress on Vultr 768:
@thwr said in Wordpress on Vultr 768:
Most Wordpress sites only have like 128 MB, maybe 256 MB.
I doubt that most do, as it's effectively impossible for many years to even get VPS that small. Rackspace minimum is 512MB and DO/Vultr is like 768MB.
I wasn't sure what he got at that point. Wordpress runs "fine" on 128MB, but that does not take into account what the operating system, Apache/Nginx and MySQL need.
A VM with Wordpress and a full webserver/database server stack should probably have like 512 MB at least.
-
@thwr said in Wordpress on Vultr 768:
I wasn't sure what he got at that point. Wordpress runs "fine" on 128MB, but that does not take into account what the operating system, Apache/Nginx and MySQL need.
It should run fine on 16MB then
-
@thwr said in Wordpress on Vultr 768:
A VM with Wordpress and a full webserver/database server stack should probably have like 512 MB at least.
For any real use, yeah. We have it working on 256MB, but it sucks.
-
@scottalanmiller said in Wordpress on Vultr 768:
@thwr said in Wordpress on Vultr 768:
A VM with Wordpress and a full webserver/database server stack should probably have like 512 MB at least.
For any real use, yeah. We have it working on 256MB, but it sucks.
Probably due to Wordpress. Someone once said: "That's the most frustrating piece of code I've ever seen". Don't have the link anymore...
-
@thwr said in Wordpress on Vultr 768:
@scottalanmiller said in Wordpress on Vultr 768:
@thwr said in Wordpress on Vultr 768:
A VM with Wordpress and a full webserver/database server stack should probably have like 512 MB at least.
For any real use, yeah. We have it working on 256MB, but it sucks.
Probably due to Wordpress. Someone once said: "That's the most frustrating piece of code I've ever seen". Don't have the link anymore...
No, it's because MariaDB and Apache like a bit of room to breathe. Then PHP needs some overhead, too.
-
@scottalanmiller said in Wordpress on Vultr 768:
@thwr said in Wordpress on Vultr 768:
@scottalanmiller said in Wordpress on Vultr 768:
@thwr said in Wordpress on Vultr 768:
A VM with Wordpress and a full webserver/database server stack should probably have like 512 MB at least.
For any real use, yeah. We have it working on 256MB, but it sucks.
Probably due to Wordpress. Someone once said: "That's the most frustrating piece of code I've ever seen". Don't have the link anymore...
No, it's because MariaDB and Apache like a bit of room to breathe. Then PHP needs some overhead, too.
That was a joke...
-
So reinstalling CentOS7, then installing the LAMP stack, followed by Wordpress, seems to have solved my issues. No issues like I was having earlier. Also, I have much more available memory than what i had previously. Strange problem.
