RedHat4找不到网卡和mysql启动不了解决方案-tutorial mysql-php.cn

本文记录了一次RedHat AS release4上出现找不到网卡和mysql启动不了解决方案并解决问题的过程 0.机器环境: [root@xxhost ~]# lsb_release -a LSB Version: :core-3.0-ia32:core-3.0-noarch:graphics-3.0-ia32:graphics-3.0-noarch Distributor ID: RedHatEnt

本文记录了一次RedHat AS release4上出现找不到网卡和mysql启动不了解决方案并解决问题的过程

0.机器环境:

[root@xxhost ~]# lsb_release -a
LSB Version:    :core-3.0-ia32:core-3.0-noarch:graphics-3.0-ia32:graphics-3.0-noarch
Distributor ID: RedHatEnterpriseAS
Description:    Red Hat Enterprise Linux AS release 4 (Nahant Update 4)
Release:        4
Codename:       NahantUpdate4

[root@xxhost ~]# mysql --version
mysql Ver 14.14 Distrib 5.1.55, for pc-linux-gnu (i686) using EditLine wrapper

问题描述：

1.开机不能联网，找不到网卡eth0和eth1，只能找到lo网卡

service network start:

Bringing up interface eth0: e1000 device eth0 does not seem to be present, delaying initialization.

解决方案：

在communities.vmware.com看到一个老外说，他在遇到这个问题时说：“What I found was that my modules.dep and modules.alias were empty,which live in /lib/modules/`uname-r`/”。这让我想起了,下午我在编一个模块时，执行过depmod，这是会改变modules.dep和modules.alias。到/lib/modules/`uname-r`/一看，果然，里面只有与我的模块有关的依赖信息。看来，这是由于我以错误的方式执行了depmod命令造成的。可能是由于在向安装好的php中添加新模块的时候编译了openssl和curl,而这个过程有可能改变了modules.dep

看来是系统模块的依赖关系信息丢失了，启动时网卡驱动等模块无法加载。所以，如果想用modprobe向系统加自己的模块时，应将your_module.ko拷入/lib/modules/`uname -r`/，然后depmod -a 。最后，modprobyour_module。

在/lib/modules/内核版本号/ 执行depmod 重新生成modules.dep和modules.alias

http://blog.chinaunix.net/uid-20750677-id-1878255.html

2.Mysql启动不了

2.1Starting MySQL.Manager of pid-file quit without updating file.[FAILED]mysql

查看错误日志
默认的mysql错误日志是在/usr/local/mysql/data 下面 more ****.err 有下面的信息
090302 02:27:26 mysqld_safe mysqld from pid file /opt/mysql/web2.pid ended
090302 02:30:03 mysqld_safe Starting mysqld daemon with databases from /opt/mysql
090302 2:30:03 [ERROR] /usr/local/mysql/libexec/mysqld: unknown option'--skip-federated'
090302 2:30:03 [ERROR] Aborting
解决方法：
只要将/etc/my.cnf里面的 skip federated注释掉即可。

http://www.dedecms.com/knowledge/data-base/mysql/2012/1122/16854.html

2.2

mysql不能启动 Manager of pid-file quit without updating file

启动mysql失败，提示Manager of pid-file quit without updating file.错误。从网上直接搜索错误信息，感觉出错原因及解决方案都不适用于本机的情况。

本着出错要查出其原因的原则，查看了mysql的出错日志（出错日志所在路径，请根据您自己机子的实际情况查找），发现错误信息：File ‘./mysql-bin.index’ not found (Errcode: 13)，查看数据库文件，mysql-bin.index确实存在。

查看数据库文件的权限，发现全都变成了 drwx—— 2 1001 1001。突然想起之前重建过mysql用户，造成数据库文件的权限用户信息丢失。重新授权即可。

网上有不少这个原因的解释，但是都不是我想说的。我要说的原因其实很白痴：data/mysql-bin.index没有删除，data/mysql-bin.index是存放日志文件索引的文件，只删除了日志文件而没有对日志的索引文件做处理显然是不行的。

http://www.jb51.net/article/22052.htm

sudo chown -R mysql var/
sudo chgrp -R mysql var/
http://www.gagahappy.com/mysql-manager-of-pid-file-quit-without-updating-file/

http://bbs.chinaunix.net/thread-1272674-1-1.html

2.3 errcode 122 waiting for someone to free sapce

Running Centos 6.5

We have been getting these errors for a few days when mysql tries to write to the datafiles in /var/lib/mysql tree. The file names vary. There is 120Gb free in the root partion. Every thing is in root.

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/vg_myserver-lv_root 150245636 14936520 127681188 11% /
tmpfs 4030892 0 4030892 0% /dev/shm
/dev/sda1 495844 116407 353837 25% /boot

140506 16:11:28 [Warning] Disk is full writing './george_wpress/ella_commentmeta.TMD' (Errcode: 122). Waiting for someone to free space... (Expect up to 60 secs delay for server to continue after freeing disk space)

As a test I ( using dd command ) created a 5G testfile in the /var/directory without problem.

The total size of the mysql directory is around 500Mb

The fault was resovled by switching off the quota mechanism using the
quotaoff command

http://forums.mysql.com/read.php?20,613809,613852#msg-613852

2.4 MySQL is running but PID file is not found

今天vps访问速度很慢，我用/root/lnmp restart 命令给lnmp重启了一下，重启之后发觉mysql链接不上了。 ssh里面运行 service mysql restrat 出现 MySQL is running but PID file could not be found 错误。

用mysql -u root -p 命令运行mysql时出现 Can't connect to MySQL through socket mysql.sock 错误。

后来网上找到一篇不错的文章 mysql PID file not found and Can't connect to MySQL through socket mysql.sock虽然后来我是直接重启vps(reboot)解决这个问题，不过上面文章里的很多内容还是挺有用的。

记录几个以前不知道的知识：

1、grep 是查找命令可做文件内的字符串查找，使用如： ps aux | grep mysql

2、ps 命令显示所有进程跟windows系统的 tasklist 命令相似 aux 显示所有包含其他使用者的行程比如我运行 ps aux | grep mysql 命令后能够找到

–datadir=/usr/local/mysql/var–pid-file=/usr/local/mysql/var/li220-124.pid

3、kill -9 [PID] 终止进程命令通过ps 找到进程pid 然后用kill -9 [PID]终止进程(-9表示强迫进程立即停止)

4、hostname 命令显示当前主机名 uname -a 命令显示当前系统内核版本

5、service命令

通过 service mysql status 可以查看 mysql的状态。但是其他服务名称如何查找？

发现通过 ls /etc/init.d/ 目录下面可以找到各个服务名称。

6、top命令查看内存和cup使用情况

7、chown 更改属主和属主组

chown [OPTION]… [OWNER][:[GROUP]] FILE…

如：chown mysql:mysql redhat.pid 更改redhat.pid 的ownner为mysql 所属组为mysql
2.5 MySQL: mysql is not running but lock exists

A MySQL crash on Red Hat system resulted with:

/etc/init.d/mysql status

coming back with:

mysql is not running but lock exists

Solved by removing the lock file:

rm /var/lock/subsys/mysql

If this happens again it may also be necessary to remove the pid file from /var/lib/mysql
2.6
MySQL: write failed, user block limit reached

this mean that you don't have enouph space to create this backup file. check your qouta and file size

http://www.experts-exchange.com/Database/MySQL/Q_24895505.html

2.7
sda5: write failed, user block limit reached

http://forums.cpanel.net/f5/sda5-write-failed-user-block-limit-reached-49435.html

da5: write failed, user block limit reached ???

sda5 : write failed, user block limit reached ???

--------------------------------------------------------------------------------

I got write failed, user block limit reached in my server shell ....
I can not start apache and mysql because if I do that server load average goes up ti 100! in seconds..!!

Already runed /scripts/fixquotas but the problem stills.

sda5 is 50% free space....

I use RH4.

Last edited by sh4ka; 01-31-2006 at 06:05 PM.

Reply With QuoteReply With Quote

01-31-2006, 06:14 PM

nyjimbo nyjimbo is offline

Registered Member

nyjimbo's Avatar
Join DateJan 2003LocationNew YorkPosts1,123

Default

did you try to google or yahoo search:

write failed, user block limit reached

Sounds like you ran out of some kind of room either due to quotas or some other limits.

Is this a virtual server ?

"A dog has raised it’s hind leg on the age of nevermore !"
-- Rolf

Reply With QuoteReply With Quote

01-31-2006, 06:22 PM

sh4ka sh4ka is offline

Registered Member

sh4ka's Avatar
Join DateMay 2005Posts435

Default

Yes is a virtual server...
I already searched google and know the problem is with the disk quota maybe it was bad configured at the setup.. I really don't know, that's why I am asking.

On sda5 I have the / partition... including home, and the system directories. /tmp /boot are the other partitions..

root@server [~]# quota
Disk quotas for user root (uid 0): none

root@server [~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda5 71G 35G 32G 53% /
/dev/sda1 99M 11M 83M 12% /boot
/dev/sda3 1012M 36M 925M 4% /tmp
none 506M 0 506M 0% /dev/shm
/dev/sdb1 74G 20G 50G 29% /backup/cpbackup

Also the fstab is well configured for this partition:

root@server [~]# cat /etc/fstab
/dev/sda5 / ext3 defaults,usrquota 1 1

Any ideas, pleaseeeee ?

thkz!

Reply With QuoteReply With Quote

02-01-2006, 01:48 AM

madaboutlinux madaboutlinux is offline

Registered Member

Join DateJan 2005LocationEarthPosts1,052

Default

If its a VPS, the hosting company do set a Quota limit for each VPS on the main VPS server. There are Disk quotas set for each VPS to control the number of inodes a vps can use. You will have to ask your hosting company to change the quota limit for you. It seems you have reached your Hard limit. You will not be able to sort this issue at your end.

Hope this will sort out your issue.

Linux WebHosting Blog.
http://linuxhostingsupport.net/blog/
MSN :: madaboutlinux@hotmail.com

Reply With QuoteReply With Quote

02-01-2006, 05:32 AM

xerophyte xerophyte is offline

Registered Member

Join DateMar 2003LocationCanadaPosts217

Default

That error happens when you are over the quota, and you try to write to the disk.

In your case looks like one (many) of your hosted site over the quota, and when they try to write to the disk you get that error. Check site(s) which are over the quota.

hope that helps