Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok. First of all I would like to mention that I have just registered on this site and I will like to apologize if I may have used the wrong section or so, but I feel like this is the place where I could get the most help as fast as possible.
Now I would like to give out some information about my server and what is going on with it.
- My dedicated server is hosted at OVH in Quebec if I'm correct
- On my server I run a minecraft server, Teamspeak3 server and a website running SMF (SimpleMachines Forum) + I got to setup a Mysql server which I use both for the website and for the Minecraft server
- Now this is my first time that I was setting up and working in the Linux enviroment, even though I don't have much knowledge in scripting and proggraming either way and I just did most of the work following tutorials so everything could work.
But looks like always something has to go wrong :/
And here is my website which has been down for some time now, cause I really do not know how to fix it. http://mc.brutalcraft.org
However the Minecraft server is still working.
I know I probably sound like a joke and your best advice for me from most of you would probably be to just give up cause I don't know what the f* I'm doing, but there's actually a great community I have created in this "more than a year" lasting Minecraft server and I would really like to keep it going and running.
Once again apologizes if I'm asking for too much help here, but I'm lost and stuck at the point where I really need somebody else more experienced with me to help me solve this issues. I do not know if this is the best website to post about this kind of issues, but I definetly feel like it's worth trying, cause hey, can't get much worse.
If you have any questions or if you would like me to execute some commands for you and tell you the results go ahead.
At first glance I'd say you should either attach storage or re-distribute space as your /home partition apparently doesn't require that much free space:
Quote:
Originally Posted by wumpyc
Code:
Filesystem Size Used Avail Use% Mounted on
/dev/md3 91G 21G 66G 24% /home
Quote:
Originally Posted by wumpyc
Code:
17G /var/lib
What does this return?:
Code:
du -mhs /var/lib/*
*Depending on what's in /var/lib we might be able to re-attach a subdirectory in /home to temporarily alleviate disk space problems but that won't address the problem in the structurally and long run.
At first glance I'd say you should either attach storage or re-distribute space as your /home partition apparently doesn't require that much free space:
What does this return?:
Code:
du -mhs /var/lib/*
*Depending on what's in /var/lib we might be able to re-attach a subdirectory in /home to temporarily alleviate disk space problems but that won't address the problem in the structurally and long run.
*First ensure you have backups off site (like you should with valuable data).
0) Stop the web server and the MySQL service
1) Ensure nothing is accessing the source directory or stop those services first:
Code:
lsof -Pwln -a +D/var/lib/mysql
2) Copy the source database directory to the /home partition:
3) Move the original database directory out of the way:
Code:
mv /var/lib/mysql /var/lib/mysql_old
4) Create a mount point and mount the destination there:
Code:
mkdir /var/lib/mysql && mount --bind /home/mysql /var/lib/mysql
5) Start the web server and the MySQL service and check their log files for any errors
6) If no errors are logged and the web site is working then adjust /etc/fstab to reflect the changes:
140216 15:39:38 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140216 15:39:38 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
140216 15:39:38 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140216 15:39:38 [Note] Plugin 'FEDERATED' is disabled.
/usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist
140216 15:39:38 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
140216 15:39:38 InnoDB: The InnoDB memory heap is disabled
140216 15:39:38 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140216 15:39:38 InnoDB: Compressed tables use zlib 1.2.8
140216 15:39:38 InnoDB: Using Linux native AIO
140216 15:39:38 InnoDB: Initializing buffer pool, size = 128.0M
140216 15:39:38 InnoDB: Completed initialization of buffer pool
140216 15:39:38 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name ./ibdata1
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.
140216 15:39:38 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
140216 15:44:54 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140216 15:44:54 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
140216 15:44:54 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140216 15:44:54 [Note] Plugin 'FEDERATED' is disabled.
/usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist
140216 15:44:54 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
140216 15:44:54 InnoDB: The InnoDB memory heap is disabled
140216 15:44:54 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140216 15:44:54 InnoDB: Compressed tables use zlib 1.2.8
140216 15:44:54 InnoDB: Using Linux native AIO
140216 15:44:54 InnoDB: Initializing buffer pool, size = 128.0M
140216 15:44:54 InnoDB: Completed initialization of buffer pool
140216 15:44:54 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name ./ibdata1
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.
140216 15:44:54 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
[code]140216 15:39:38 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name ./ibdata1
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.[code]
140216 17:20:45 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140216 17:20:45 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
140216 17:20:45 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
140216 17:20:45 [Note] Plugin 'FEDERATED' is disabled.
140216 17:20:45 InnoDB: The InnoDB memory heap is disabled
140216 17:20:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140216 17:20:45 InnoDB: Compressed tables use zlib 1.2.8
140216 17:20:45 InnoDB: Using Linux native AIO
140216 17:20:45 InnoDB: Initializing buffer pool, size = 128.0M
140216 17:20:45 InnoDB: Completed initialization of buffer pool
140216 17:20:45 InnoDB: highest supported file format is Barracuda.
140216 17:20:45 InnoDB: Waiting for the background threads to start
140216 17:20:46 InnoDB: 5.5.34 started; log sequence number 24779282639
140216 17:20:46 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
140216 17:20:46 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140216 17:20:46 [Note] Server socket created on IP: '0.0.0.0'.
140216 17:20:46 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
140216 17:20:46 [ERROR] Do you already have another mysqld server running on port: 3306 ?
140216 17:20:46 [ERROR] Aborting
Please don't use [QUOTE]text[/QUOTE] but [CODE]text[/CODE] tags for log lines.
Quote:
Originally Posted by wumpyc
Code:
140216 17:20:46 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
140216 17:20:46 [ERROR] Do you already have another mysqld server running on port: 3306 ?
It literally tells you what to check for. So stop the service then
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.