*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
We are having very strage problem on FreeBSD server( version 5.1 ) which uses mysql 4.0.18 on it.Since yesterday we are getting so many errors of mysql_num_rows () function which says that the argument is invaild.
The problem is more severe .We have repaired the error but it keeps coming on and on .This happens Coz anything is added or deleted from table gives rise to error.
Here is whatb my /var/lib/mysql/server.err file says:
040705 06:56:47 mysqld started
040705 6:56:48 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 43952
InnoDB: Doing recovery: scanned up to log sequence number 0 43952
040705 6:56:48 InnoDB: Flushing modified pages from the buffer pool...
040705 6:56:48 InnoDB: Started
/usr/local/libexec/mysqld: ready for connections.
Version: '4.0.13' socket: '/tmp/mysql.sock' port: 3306
040706 2:55:32 Note: Found 212 of 213 rows when repairing './trafficg_trafficq/trafficg_login'
040706 4:13:41 /usr/local/libexec/mysqld: Normal shutdown
040706 04:13:43 mysqld ended
And this my error_log says:
[Fri Jul 2 16:43:34 2004] [error] PHP Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/trafficq/public_html/topbar.php on line 155
[Fri Jul 2 16:43:34 2004] [error] PHP Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/autosurf/public_html/member.php on line 118
[Fri Jul 2 16:43:39 2004] [error] PHP Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/autosurf/public_html/topbar.php on line 16
AND SO ON....
there are at least 10000 lines of same type...
What is problem?
CAn anybody help!!
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
It seems like the DB thinks there are actually more rows than it can find. If the automatic DB check doesn't work, you might have to do more drastic check/repair work. I believe there are some tools that ship with MySQL for this, but I do not have experience using them. Basically your DB seems to be corrupt.