Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Weird MYSQL Text / Error While Installing
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Weird MYSQL Text / Error While Installing

Hey guys, long time no see.

I've had this problem trying to install MYSQL on this Debian 7 64 bit for hours now.

My steps of installation: (I used this for some guidance.) --

  1. Reinstalled a fresh Debian 7, 64 through SolusVM:

  2. Setup SSH Keys, done.

  3. Login, run apt-get update, done.

  4. run apt-get install mysql-server and then this:

I don't understand why there are q's, x's, k's and l's all over the screen. I've never seen this before.

Anyways, I type in my password and press enter (does the same if I leave it blank as well) and then I get:

I checked the MYSQL logs, but they are empty. Am I missing to do something?

Comments

  • FVPSFVPS Member
    edited February 2016

    Ignore the l q x u letters. They don't break anything. Just looks hideous. To get rid of it you need to setup locales correctly on the VPS and tell your SSH client to use UTF8.

    http://superuser.com/questions/264363/how-can-i-use-utf-8-on-linux-from-windows-7-via-putty

    The last time I installed MySQL on Debian 7 I've had the same idiotic issues. I opened another session during the installation and it turned out that when it attempts to set the password the MySQL server wasn't even running.

    So

    because of a communication problem with the MySQL server

    hits the nail on the head.

    I set the password after the package was installed with that error using

    https://support.rackspace.com/how-to/mysql-resetting-a-lost-mysql-root-password/

    Thanked by 1Dillybob
  • DillybobDillybob Member
    edited February 2016

    @FVPS said:
    Ignore the l q x u letters. They don't break anything. Just looks hideous. To get rid of it you need to setup locales correctly on the VPS and tell your SSH client to use UTF8.

    http://superuser.com/questions/264363/how-can-i-use-utf-8-on-linux-from-windows-7-via-putty

    The last time I installed MySQL on Debian 7 I've had the same idiotic issues. I opened another session during the installation and it turned out that when it attempts to set the password the MySQL server wasn't even running.

    So
    https://support.rackspace.com/how-to/mysql-resetting-a-lost-mysql-root-password/

    Aww okay.

    Hmm. weird, following that tut, and I cannot even get into mysql's safe mode.

    root@testwebsocket:~# mysqld_safe --skip-grant-tables & [1] 8574 root@testwebsocket:~# 160214 15:31:12 mysqld_safe Logging to syslog. 160214 15:31:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 160214 15:31:12 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended mysql -uroot ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) [1]+ Done mysqld_safe --skip-grant-tables root@testwebsocket:~#

    This is really weird because I was using Debian 7 64 bit on a different host 4-5 months ago and never, ever ran into these mysql problems. Do you think it could be a host issue? Although, not sure what it would be, but just a thought.

    Edit: Pastebin of syslog after running these commands: http://pastebin.com/3uDigEuV If that helps

  • Install ncurses packages, common Debian issue and most likely a minimal template

    Thanked by 1Dillybob
  • FVPSFVPS Member
    edited February 2016

    mysqld: InnoDB: Error: pthread_create returned 11

    Looks like you maybe don't have enough free resources to even start MySQL with its current default my.cnf configuration.

    Similar case http://www.linux.org/threads/cannot-set-up-innodb-support-in-mysql-due-to-pthread_create-returned-11-error.6530/

    I believe the user @postcd even has an account here.

    Optimize the configuration or try to stop as many services as possible to free up resources.

    Edit: Actually that is why MySQL was not running when I tried to install it. I replaced my.cnf with a optimized version that is not even using InnoDB: http://pastebin.com/QzUyFuxj

    Thanked by 1Dillybob
  • DillybobDillybob Member
    edited February 2016

    @FVPS said:
    Edit: Actually that is why MySQL was not running when I tried to install it. I replaced my.cnf with a optimized version that is not even using InnoDB: http://pastebin.com/QzUyFuxj

    Oh, wow, changing the buffer size fixed it! Looks like I will get this error on the default installation, and then just have to change the my.cnf and re-start mysql and I should be fine? ( Assuming I am installing it on a LEB). Thanks for your help, I was stuck for hours on this.

  • @Dillybob said:
    Looks like I will get this error on the default installation, and then just have to change the my.cnf and re-start mysql and I should be fine?

    Yes, it's about like that.

    It helps on low resource machines because with this configuration MySQL only uses a few MB RAM instead of the crazy amounts of 100 - 200 MB idle with InnoDB and higher rates for other settings.

    Thanked by 1Dillybob
Sign In or Register to comment.