Stackscript, Manual Installation... neither worked.
-
J Y
MemberI'm plagued with this error:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)Took my time doing manual install of everything on the Ubuntu/Nginx guide...then finally decided to burn it down and restart with the script. Doesn't matter what I do. I get this error.
Posted 1 year ago # -
sounds like mysql isn't starting, JY .. you tried:-
sudo /etc/init.d/mysql stop
sudo /etc/init.d/mysql startPosted 1 year ago # -
J Y
Memberuser@server~ $ sudo /etc/init.d/mysql stop [sudo] password for user: Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service mysql stop Since the script you are attempting to invoke has been converted to an Upstart job, you may also use the stop(8) utility, e.g. stop mysqlThen the next logical step:
user@server~ $ service mysql stop exec: 129: stop: not found user@server~ $ service mysql start exec: 129: start: not foundDoing a remove & purge of mysql-server got it working again. But only until a server reboot.
I'm tearing my hair out.
Posted 1 year ago # -
i can replicate this error but not with mysql being down.
what about:-
sudo stop/start/restart mysql
and what does this say (most importantly, after a reboot) ..
ps aux|grep mysql
this looks buggy and I wonder if it isn't to do with a change in syntax and perhaps not great liaison between devs from 10.04/upstart/mysql
but if you have problems with mysql being down, JY, I'd advise either ditching for Debian 5 (possibly the same issue tho) else swapping for 8.04.
Posted 1 year ago # -
J Y
MemberThe stackscript I'm using says it's for 10.04. And I'm using 10.04...
I've now switched to another VPS provider thinking that was the issue. And am experiencing the exact same things.
Has this guide actually worked for anyone? I'm ready to embrace shared hosting again.
Posted 1 year ago # -
Simon
MemberI had a similar problem, and discovered that my VPS image (Ubuntu 10.0.4) came with PHP/MySQL/Apache all included. I found I had to completely (and I mean completely!) remove all traces of them before the scripts worked. I also had to remove the section in the script that setup the repositories (no idea why).
It was worth sticking with - my VPS runs along at a blistering speed compared to my old Plesk VPS and even more so compared to my shared hosting.
Try re-imaging your VPS and typing each of these lines:
dpkg --get-selections | grep php dpkg --get-selections | grep sql dpkg --get-selections | grep apacheThey will show you if you already have the packages installed. If anything comes up, use this to get rid of them all:
aptitude purge package-name(Keep going until all have gone)
Once I'd done all that then deleted the section about the repositories, then run the stackscript all worked fine.
Posted 1 year ago # -
@JY .. sorry to hear, what provider are you with, adn which were you with?
If the stack isn't working with your VPS' setup, run through the guide instead which the script is based on.
@Simon .. VPS providers should primarily offer a range of bare-bones distribution launches (Ubuntu/debian/Redhat etc). The whole point of a VPS, after all, is that we can decide what we want to install on top of the OS. It sounds as though you have elected a LEMP install, although what exactly is included should be clear in your VPS docs.
Posted 1 year ago # -
who is it Simon? .. I try to keep a log of who does what. (Am very surprised they don't offer a bare-bones option.)
Posted 1 year ago #
Reply
You must log in to post.
Want HTML?
a blockquote code em strong ul ol liPlace code between backticks `codeHere`
You've got it.