Re: Mysql Processes

2005-10-25 Thread Gleb Paharenko
Hello.



Run ps -axm on the second server, and normally you should see a lot of

mysqld threads.



Edward David wrote:

 I just joined this list so I am hoping that this question is relevant to

 this group.

 I am running Linux AS4 Enterprise Server.

 I am running Mysql  Ver 14.7 Distrib 4.1.12, for pc-linux-gnu (i686)

 using readline 4.3

 With Client version 3.23.49.

 When I go and do a ps -ax I see 18 mysqld processes running.

 When I look at the pid file I only see one Process ID Number.

 

 When I look at another server that is running mysql that we do not have

 access to the cnf file

 I only see two processes running.

 Can anyone explain why this is happening and if it is normal.

 

 ---

 Edward David

 Sr. Systems Analyst

 University of Calgary

 Information Resources

 Information Technology Service

 ---

 

 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   ___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Mysql Processes

2005-10-24 Thread Edward David
I just joined this list so I am hoping that this question is relevant to 
this group.

I am running Linux AS4 Enterprise Server.
I am running Mysql  Ver 14.7 Distrib 4.1.12, for pc-linux-gnu (i686) 
using readline 4.3

With Client version 3.23.49.
When I go and do a ps -ax I see 18 mysqld processes running.
When I look at the pid file I only see one Process ID Number.

When I look at another server that is running mysql that we do not have 
access to the cnf file

I only see two processes running.
Can anyone explain why this is happening and if it is normal.

---
Edward David
Sr. Systems Analyst
University of Calgary
Information Resources
Information Technology Service
---


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Too many Mysql processes at startup after upgrade to 4.1.14

2005-09-16 Thread Gleb Paharenko
Hello.



What is SHOW PROCESSLIST reporting when the server is reaching the

max_connections limit?









Kishore Jalleda [EMAIL PROTECTED] wrote:

Hi All,

 Last night I upgraded our Master server to 4.1.14 standard log from 4.0.17, 

I upgraded the slave a week ago and the replication was working perfectly, 

once I upgraded and started mysql, it started fine without any errors but 

the server was steadily creating mysql processes at the rate of like 20/sec 

until it reached the Max_connections limit set at 800, while it was doing 

this it was serving the web clients only randomly , also the load was very 

very low neither was it taking up any memory, it was just creating processes 

, I remember seeing this behaviour even earlier with 4.0.17 when the server 

just started but after a certain point the no of processes return to normal.

 So I had to switch back to 4.0.x, and it works perfectly fine, Also I did 

not dump the databases just zipped the old datadir and unzipped it into the 

new datadir, anybody else experience this behaviour at startup( I am aware 

that once the server is back online it is flooded with requests), the OS is 

Redhat 7.3, the server currently does 200-400 qps quiet comfortably .

 Any help would be appreciated, let me know if you need more info

 Kishore Jalleda



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   ___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Too many Mysql processes at startup after upgrade to 4.1.14

2005-09-16 Thread Chris Allen
I don't know if this is relevant to you - but I had exactly
the same experience when upgrading to MySQL v4.1. It turned out
that MySQL was trying to do reverse DNS lookups before authenticating
the connecting hosts - and was failing slowly on each because the database
machine didn't have external net access.

Adding all the local machines to /etc/hosts solved the problem
immediately.

Chris Allen.



On Fri, Sep 16, 2005 at 01:30:34PM +0300, Gleb Paharenko wrote:
 Hello.
 
 
 
 What is SHOW PROCESSLIST reporting when the server is reaching the
 
 max_connections limit?
 
 
 
 
 
 
 
 
 
 Kishore Jalleda [EMAIL PROTECTED] wrote:
 
 Hi All,
 
  Last night I upgraded our Master server to 4.1.14 standard log from 4.0.17, 
 
 I upgraded the slave a week ago and the replication was working perfectly, 
 
 once I upgraded and started mysql, it started fine without any errors but 
 
 the server was steadily creating mysql processes at the rate of like 20/sec 
 
 until it reached the Max_connections limit set at 800, while it was doing 
 
 this it was serving the web clients only randomly , also the load was very 
 
 very low neither was it taking up any memory, it was just creating processes 
 
 , I remember seeing this behaviour even earlier with 4.0.17 when the server 
 
 just started but after a certain point the no of processes return to normal.
 
  So I had to switch back to 4.0.x, and it works perfectly fine, Also I did 
 
 not dump the databases just zipped the old datadir and unzipped it into the 
 
 new datadir, anybody else experience this behaviour at startup( I am aware 
 
 that once the server is back online it is flooded with requests), the OS is 
 
 Redhat 7.3, the server currently does 200-400 qps quiet comfortably .
 
  Any help would be appreciated, let me know if you need more info
 
  Kishore Jalleda
 
 
 
 -- 
 For technical support contracts, goto https://order.mysql.com/?ref=ensita
 This email is sponsored by Ensita.NET http://www.ensita.net/
__  ___ ___   __
   /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
  / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
 /_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
___/   www.mysql.com
 
 
 
 
 -- 
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
 

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Too many Mysql processes at startup after upgrade to 4.1.14

2005-09-16 Thread Kishore Jalleda
Hi, 
 Unfortunately I dint check SHOW PROCESSLIST as I was overwhelmed with the 
state of the server and had to bring back the old version online, but the 
reverse DNS lookups could be the reason, but surprisingly it was infact 
serving some client requests
, also is there a way to stop mysql from doing reverse DNS lookups ..
Thanks 
Kishore Jalleda 
 On 9/16/05, Chris Allen [EMAIL PROTECTED] wrote: 
 
 I don't know if this is relevant to you - but I had exactly
 the same experience when upgrading to MySQL v4.1. It turned out
 that MySQL was trying to do reverse DNS lookups before authenticating
 the connecting hosts - and was failing slowly on each because the database
 machine didn't have external net access.
 
 Adding all the local machines to /etc/hosts solved the problem
 immediately.
 
 Chris Allen.
 
 
 
 On Fri, Sep 16, 2005 at 01:30:34PM +0300, Gleb Paharenko wrote:
  Hello.
 
 
 
  What is SHOW PROCESSLIST reporting when the server is reaching the
 
  max_connections limit?
 
 
 
 
 
 
 
 
 
  Kishore Jalleda [EMAIL PROTECTED] wrote:
 
  Hi All,
 
   Last night I upgraded our Master server to 4.1.14 standard log from 
 4.0.17,
 
  I upgraded the slave a week ago and the replication was working 
 perfectly,
 
  once I upgraded and started mysql, it started fine without any errors 
 but
 
  the server was steadily creating mysql processes at the rate of like 
 20/sec
 
  until it reached the Max_connections limit set at 800, while it was 
 doing
 
  this it was serving the web clients only randomly , also the load was 
 very
 
  very low neither was it taking up any memory, it was just creating 
 processes
 
  , I remember seeing this behaviour even earlier with 4.0.17 when the 
 server
 
  just started but after a certain point the no of processes return to 
 normal.
 
   So I had to switch back to 4.0.x, and it works perfectly fine, Also I 
 did
 
  not dump the databases just zipped the old datadir and unzipped it into 
 the
 
  new datadir, anybody else experience this behaviour at startup( I am 
 aware
 
  that once the server is back online it is flooded with requests), the 
 OS is
 
  Redhat 7.3, the server currently does 200-400 qps quiet comfortably .
 
   Any help would be appreciated, let me know if you need more info
 
   Kishore Jalleda
 
 
 
  --
  For technical support contracts, goto 
 https://order.mysql.com/?ref=ensita
  This email is sponsored by Ensita.NET http://www.ensita.net/
  __ ___ ___  __
  / |/ /_ __/ __/ __ \/ / Gleb Paharenko
  / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED]
  /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
  ___/ www.mysql.com http://www.mysql.com
 
 
 
 
  --
  MySQL General Mailing List
  For list archives: http://lists.mysql.com/mysql
  To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
 
 
 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
 



Too many Mysql processes at startup after upgrade to 4.1.14

2005-09-15 Thread Kishore Jalleda
Hi All,
 Last night I upgraded our Master server to 4.1.14 standard log from 4.0.17, 
I upgraded the slave a week ago and the replication was working perfectly, 
once I upgraded and started mysql, it started fine without any errors but 
the server was steadily creating mysql processes at the rate of like 20/sec 
until it reached the Max_connections limit set at 800, while it was doing 
this it was serving the web clients only randomly , also the load was very 
very low neither was it taking up any memory, it was just creating processes 
, I remember seeing this behaviour even earlier with 4.0.17 when the server 
just started but after a certain point the no of processes return to normal.
 So I had to switch back to 4.0.x, and it works perfectly fine, Also I did 
not dump the databases just zipped the old datadir and unzipped it into the 
new datadir, anybody else experience this behaviour at startup( I am aware 
that once the server is back online it is flooded with requests), the OS is 
Redhat 7.3, the server currently does 200-400 qps quiet comfortably .
 Any help would be appreciated, let me know if you need more info
 Kishore Jalleda


mysql processes

2003-11-07 Thread Hugh Beaumont
Hi List,

I've searched the archives and the web many times in the past for answers to the 
following
questions but never really got a complete understanding of what is going on. Hopefully 
someone on
the list will be able to take the time to set me straight.

I have a typical php + mysql + linux setup. Today I noticed a high load, and checked 
things out
with:

mysql% show processlist;

it showed 6 processes running:

[ I'll skip all the ascii output since it usually ends up garbled]

6 rows in set (0.00 sec)


however if I do:

 ps axuw | grep mysql | wc -l

I get:

 28

What is going on here? 

Do I have 28 mysqld's waiting around for requests and just 6 actually processes 
running?

Is there any way to regulate this - something similiar to apache's max_clients, min 
spare server,
max spare servers, etc?

We often have mysql just totally melt down a server - someone will run a bit query and 
then all
the others start to back-up. We then end up with a ton of queries trying run at once, 
the load
goes to 50 or even 100(!).

How can I stop this? Any tips at all on regulating the use of mysql - this is an ISP 
server so it
is very hard to make sure that all usrs are running sensible and well-constructed 
database
schema's.

I have tried to contact mysql for consulting but their beginning prices are too high 
for our
modest budget. Does anyone else know of ways to get some help if no one on the list is 
able to
advise?

Thanks!


__
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: mysql processes

2003-11-07 Thread Gabriel Ricard
On Friday, November 7, 2003, at 01:21  PM, Hugh Beaumont wrote:

Hi List,

I've searched the archives and the web many times in the past for 
answers to the following
questions but never really got a complete understanding of what is 
going on. Hopefully someone on
the list will be able to take the time to set me straight.

I have a typical php + mysql + linux setup. Today I noticed a high 
load, and checked things out
with:

mysql% show processlist;

it showed 6 processes running:

[ I'll skip all the ascii output since it usually ends up garbled]

6 rows in set (0.00 sec)

however if I do:

 ps axuw | grep mysql | wc -l

I get:

 28

What is going on here?
Looks like your OS has threads in user space as processes rather than 
in kernel space.


Do I have 28 mysqld's waiting around for requests and just 6 actually 
processes running?
You have one mysqld with 28 threads waiting for requests, only 6 are 
actually processing requests.

Is there any way to regulate this - something similiar to apache's 
max_clients, min spare server,
max spare servers, etc?
I don't recall any way to limit the number of threads created, but 
there is a way to limit the number of threads that are handling delayed 
inserts - max_delayed_threads and thread_cache_size will tell mysql how 
many threads to keep around waiting for something to do. in your case, 
since the threads are in user space, they tend to be more expensive to 
create, so if your mysql server is busy, you may want to leave a bunch 
waiting around to process requests.

Be aware that the following variables are per-thread, and if they are 
set high, will consume a lot of RAM:

read_buffer (was record_buffer)
record_rnd_buffer
sort_buffer

We often have mysql just totally melt down a server - someone will run 
a bit query and then all
the others start to back-up. We then end up with a ton of queries 
trying run at once, the load
goes to 50 or even 100(!).
How many users  databases are there on this server? Is the server 
dedicated to just MySQL? What kinda hardware is it running on?

- Gabriel

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


large mysql processes

2003-08-28 Thread sanjay gupta
Hi all,
  I am using Mysql-4.0.12 on my 7.1 redhat. every thing is
working fine but when i give command

 #ps -ae
it shows various process including mysqld_safe and mysql . the mysqld
process are eleven in number with respective pids on my machine . I want to
know why there are large number of mysql  processes are running becasue  it
should show only  single  mysqld process.

any idea 

sanjay



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: large mysql processes

2003-08-28 Thread Chris Nolan
Welcome to the world of Linux!

You see, even though I love Linux to death, LinuxThreads are a bit 
inferior to what everyone else has in their
OS of choice (If Xavier reads this, please don't kill me or submit some 
kernel patch that will get even with me. :-) ).

LinuxThreads essentially are processes - you get the advantage of 
threads (shared address space and intra-process concurrency)
but each thread appears as a process.

RedHat 9.0 ships with NPTL - a newer thread implementation that acts 
properly.

Regards,

Chris

P.S - Be thankful you're running Linux - at least we have kernel-space 
threads. The poor people
forced to run SCO's inferior products quite often have to put up with 
user-space threads.

sanjay gupta wrote:

Hi all,
 I am using Mysql-4.0.12 on my 7.1 redhat. every thing is
working fine but when i give command
#ps -ae
it shows various process including mysqld_safe and mysql . the mysqld
process are eleven in number with respective pids on my machine . I want to
know why there are large number of mysql  processes are running becasue  it
should show only  single  mysqld process.
any idea 

sanjay



 



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


MySQL processes not showing.

2003-08-18 Thread Fagyal, Csongor
Hi,

I have a P4 server with RedHat 8.0 running on the lates stable kernel. I 
also have MySQL 3.23.54 installed.

My problem is that when I do a 'ps aux', I only see one mysql process:  
mysql  916  0.0  0.3 38616 3936 ?S17:39   0:02 
/usr/sbin/mysqld --defaults-file=/etc/my.cnf --basedir=/ 
--datadir=/var/lib/mys
(root   881  0.0  0.0  42844 ?S17:39   0:00 /bin/sh 
/usr/bin/safe_mysqld --defaults-file=/etc/my.cnf)

Or:
ps aux|grep mysql
mysql  916  0.0  0.3 38752 3936 ?S17:39   0:02 
/usr/sbin/mysqld

But if I do a 'fuser 3306/tcp', I get a
3306/tcp:  916   918   919  1127  1128  4774  5348  6042  
6083  6214  9113  9123  9424  9445  9448  9819  9909  9984  9992  9994 
10088 10095 10096 10112 10127 10228 10240

So basically I have some missing mysql processes. But if I know a pid, I 
can ps it, like this:
ps 1128
PID TTY  STAT   TIME COMMAND
1128 ?S  0:00 /usr/sbin/mysqld --defaults-file=/etc/my.cnf 
--basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/ 

Is this normal? Or maybe the system switched to threads when I was not 
watching :-), so that is why I only see one process??

Please advise!

Regards,
- Csongor Fagyal
ps: Being paranoid I have also run the lates chkrootkit... but it says 
my system is clean.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Re: MySQL processes not showing.

2003-08-18 Thread Fagyal, Csongor
All right, you can disregard this :-) I was too quick to post it to the 
list... those _are_ threads, the kernel upgrade must have introduced 
them :-). Sorry for the bandwidth!

But other than that, something off-topic: on the very same server I have 
found that I cannot issue the 'su' command, because it just locks up. 
All I can see is ('ps aux' after 'su -l www'):

root 11613  0.0  0.0  4096  996 pts/0S20:42   0:00 su -l www
www  11647  0.0  0.0  3408  476 pts/0T20:42   0:00 stty erase ?
and su... hangs.

What is this any who called stty???

Any ideas?

Thanx,
- Cs.
Hi,

I have a P4 server with RedHat 8.0 running on the lates stable kernel. 
I also have MySQL 3.23.54 installed.

My problem is that when I do a 'ps aux', I only see one mysql 
process:  mysql  916  0.0  0.3 38616 3936 ?S17:39   
0:02 /usr/sbin/mysqld --defaults-file=/etc/my.cnf --basedir=/ 
--datadir=/var/lib/mys
(root   881  0.0  0.0  42844 ?S17:39   0:00 
/bin/sh /usr/bin/safe_mysqld --defaults-file=/etc/my.cnf)

Or:
ps aux|grep mysql
mysql  916  0.0  0.3 38752 3936 ?S17:39   0:02 
/usr/sbin/mysqld

But if I do a 'fuser 3306/tcp', I get a
3306/tcp:  916   918   919  1127  1128  4774  5348  6042  
6083  6214  9113  9123  9424  9445  9448  9819  9909  9984  9992  9994 
10088 10095 10096 10112 10127 10228 10240

So basically I have some missing mysql processes. But if I know a pid, 
I can ps it, like this:
ps 1128
PID TTY  STAT   TIME COMMAND
1128 ?S  0:00 /usr/sbin/mysqld --defaults-file=/etc/my.cnf 
--basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/ 


Is this normal? Or maybe the system switched to threads when I was not 
watching :-), so that is why I only see one process??

Please advise!

Regards,
- Csongor Fagyal
ps: Being paranoid I have also run the lates chkrootkit... but it says 
my system is clean.



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Re: URGENT problem with mysql processes

2003-06-27 Thread Keith Bussey
Neither of these two machines send the request.

I have 12 webservers, which send the requests.
I have 5 database servers, 1 master(for updates/inserts/deletes) and 4
slaves(for selects).

Machine A below was the current Master DB server, however it is old and was
being replaced by machine B


-- 
Keith Bussey

Wisol, Inc.
Chief Technology Manager
(514) 398-9994 ext.225


Quoting Nils Valentin [EMAIL PROTECTED]:

 Hi Keith,
 
 soory now I got confused. Which machine is sending the requests (client) and
 
 which machine is the mysql server (server). Do you use php or something like
 
 this (webinterface) on the client ?
 
 If yes, than my suggestions below apply.
 If no than I we will have to think the next step.
 
 Best regards
 
 Nils Valentin
 Tokyo/Japan
 
 
 
 2003年 6月 27日 金曜日 11:29、Keith Bussey さんは書きました:
  Ok but that's not what I meant.
 
  I'll try to explain better.
 
  Machine A: IP = 192.168.1.71
  Machine B: IP = 192.168.1.79
 
  1) Scripts goto 192.168.1.71 - Everything is OK
  2) Changed scripts to 192.168.1.79 - Site works at first, but processes
  pile up until server is killed
  3) Halt machine B
  4) Give machine A IP 192.168.1.79 (so now it has 2 IPs)
  5) Problem persists even though it's a different machine, site works but
  then processes pile up and kill machine
  6) Change scripts to use 192.168.1.71 again
  7) Site works fine
 
 
  What I don't get is why do processes run normally with IP 192.168.1.71,
 but
  NOT with IP 192.168.1.79 even when they are on the same machine ?
 
  --
  Keith Bussey
 
  Wisol, Inc.
  Chief Technology Manager
  (514) 398-9994 ext.225
 
  Quoting Nils Valentin [EMAIL PROTECTED]:
   Hi Keith,
  
   The wrong IP address could only avoid a client to connect to the
 database
   server.
  
   If you have the TCP/IP address specified in /etc/php.ini or for
   phpmyadmin in
  
   config.inc.php or which ever tool you use than of course it will try to
   connect to this IP address.
  
   Best regards
  
   Nils Valentin
   Tokto/Japan
  
   2003年 6月 27日 金曜日 11:02、Keith Bussey 
 さんは書きました:
Hrmmmeaning if I do id mysql, that information (group etc..) ?
   
I've halted that server and moved everything back to my original
 server
  
   for
  
now, I had too much downtime. I did notice something else interesting
though:
   
The old mahcine's IP is 192.168.1.71
New machine's IP is 192.168.1.79
   
Now that it's halted, instead of changing the IP back to .71 in my
pages/scripts I added .79 to the .71 machine so it has both
   
Now that machine experienced the exact same problem. Switching my code
to use .71 again however, and no problems.
   
Could somehow there be a problem with the IP address 192.168.1.79?? It
seems very strange, however tomorrow I will try putting the .71 on the
new machine and see if it works or not
  
   --
   ---
   Valentin Nils
   Internet Technology
  
E-Mail: [EMAIL PROTECTED]
URL: http://www.knowd.co.jp
Personal URL: http://www.knowd.co.jp/staff/nils
  
  
   --
   MySQL General Mailing List
   For list archives: http://lists.mysql.com/mysql
   To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
 
 -- 
 ---
 Valentin Nils
 Internet Technology
 
  E-Mail: [EMAIL PROTECTED]
  URL: http://www.knowd.co.jp
  Personal URL: http://www.knowd.co.jp/staff/nils
 
 

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: URGENT problem with mysql processes

2003-06-27 Thread Nils Valentin
When you said you modified the scripts, are these the scripts on the 12 
webservers (mysql clients) ?

If not, then these mysql clients (webservers) would still be wanting to send 
to IP addres 192.168.1.71 as configured for php or in your client.

Best regards

Nils Valentin
Tokyo/Japan


2003 6 27  14:58Keith Bussey :
 Neither of these two machines send the request.

 I have 12 webservers, which send the requests.
 I have 5 database servers, 1 master(for updates/inserts/deletes) and 4
 slaves(for selects).

 Machine A below was the current Master DB server, however it is old and was
 being replaced by machine B


 --
 Keith Bussey

 Wisol, Inc.
 Chief Technology Manager
 (514) 398-9994 ext.225

 Quoting Nils Valentin [EMAIL PROTECTED]:
  Hi Keith,
 
  soory now I got confused. Which machine is sending the requests (client)
  and
 
  which machine is the mysql server (server). Do you use php or something
  like
 
  this (webinterface) on the client ?
 
  If yes, than my suggestions below apply.
  If no than I we will have to think the next step.
 
  Best regards
 
  Nils Valentin
  Tokyo/Japan
 
  2003 6 27  11:29Keith Bussey 
:
   Ok but that's not what I meant.
  
   I'll try to explain better.
  
   Machine A: IP = 192.168.1.71
   Machine B: IP = 192.168.1.79
  
   1) Scripts goto 192.168.1.71 - Everything is OK
   2) Changed scripts to 192.168.1.79 - Site works at first, but processes
   pile up until server is killed
   3) Halt machine B
   4) Give machine A IP 192.168.1.79 (so now it has 2 IPs)
   5) Problem persists even though it's a different machine, site works
   but then processes pile up and kill machine
   6) Change scripts to use 192.168.1.71 again
   7) Site works fine
  
  
   What I don't get is why do processes run normally with IP 192.168.1.71,
 
  but
 
   NOT with IP 192.168.1.79 even when they are on the same machine ?
  
   --
   Keith Bussey
  
   Wisol, Inc.
   Chief Technology Manager
   (514) 398-9994 ext.225
  
   Quoting Nils Valentin [EMAIL PROTECTED]:
Hi Keith,
   
The wrong IP address could only avoid a client to connect to the
 
  database
 
server.
   
If you have the TCP/IP address specified in /etc/php.ini or for
phpmyadmin in
   
config.inc.php or which ever tool you use than of course it will try
to connect to this IP address.
   
Best regards
   
Nils Valentin
Tokto/Japan
   
2003 6 27 
 11:02Keith
Bussey
 
  :
 Hrmmmeaning if I do id mysql, that information (group etc..)
 ?

 I've halted that server and moved everything back to my original
 
  server
 
for
   
 now, I had too much downtime. I did notice something else
 interesting though:

 The old mahcine's IP is 192.168.1.71
 New machine's IP is 192.168.1.79

 Now that it's halted, instead of changing the IP back to .71 in my
 pages/scripts I added .79 to the .71 machine so it has both

 Now that machine experienced the exact same problem. Switching my
 code to use .71 again however, and no problems.

 Could somehow there be a problem with the IP address 192.168.1.79??
 It seems very strange, however tomorrow I will try putting the .71
 on the new machine and see if it works or not
   
--
---
Valentin Nils
Internet Technology
   
 E-Mail: [EMAIL PROTECTED]
 URL: http://www.knowd.co.jp
 Personal URL: http://www.knowd.co.jp/staff/nils
   
   
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:   
http://lists.mysql.com/[EMAIL PROTECTED]
 
  --
  ---
  Valentin Nils
  Internet Technology
 
   E-Mail: [EMAIL PROTECTED]
   URL: http://www.knowd.co.jp
   Personal URL: http://www.knowd.co.jp/staff/nils

-- 
---
Valentin Nils
Internet Technology

 E-Mail: [EMAIL PROTECTED]
 URL: http://www.knowd.co.jp
 Personal URL: http://www.knowd.co.jp/staff/nils


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: URGENT problem with mysql processes

2003-06-27 Thread Nils Valentin
Hi Keith,

from your last e-mail I understand now finally that we are talking about 
replication here. Would have been a short cut to mention it in your first 
e-mail.

The failed login attempts couldn't be from your slaves trying to login, but 
you havent set them up on the master yet ?

Just a guess, so.

2003 6 27  09:05Keith Bussey :
 | 106 | unauthenticated user | 192.168.1.59:1925 | NULL | Connect | NULL |
 | login NULL
 |
 | 115 | unauthenticated user | 192.168.1.53:2041 | NULL | Connect | NULL |
 | login NULL
 |
 | 118 | unauthenticated user | 192.168.1.56:4172 | NULL | Connect | NULL |
 | login NULL
 |
 | 119 | unauthenticated user | 192.168.1.56:4173 | NULL | Connect | NULL |
 | login NULL

Best regards

Nils Valentin
Tokyo/Japan

-- 
---
Valentin Nils
Internet Technology

 E-Mail: [EMAIL PROTECTED]
 URL: http://www.knowd.co.jp
 Personal URL: http://www.knowd.co.jp/staff/nils


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: URGENT problem with mysql processes

2003-06-27 Thread Dominicus Donny
If it is the replication problem...::
Check the replication account on the master server:
...[EMAIL PROTECTED] identified by ...
...[EMAIL PROTECTED] identified by ...
...[EMAIL PROTECTED] identified by ...
...
...[EMAIL PROTECTED] identified by ...

or perhaps simply set to
...replication_account@% identified by ...

make sure the account has access to the specified db.tables, too.

Me fail English? That's unpossible
###___Archon___###

- Original Message -
From: Nils Valentin [EMAIL PROTECTED]
To: Keith Bussey [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Friday, June 27, 2003 1:30 PM
Subject: Re: URGENT problem with mysql processes


Hi Keith,

from your last e-mail I understand now finally that we are talking about
replication here. Would have been a short cut to mention it in your first
e-mail.

The failed login attempts couldn't be from your slaves trying to login, but
you havent set them up on the master yet ?

Just a guess, so.

2003 6 27  09:05Keith Bussey :
 | 106 | unauthenticated user | 192.168.1.59:1925 | NULL | Connect | NULL |
 | login NULL
 |
 | 115 | unauthenticated user | 192.168.1.53:2041 | NULL | Connect | NULL |
 | login NULL
 |
 | 118 | unauthenticated user | 192.168.1.56:4172 | NULL | Connect | NULL |
 | login NULL
 |
 | 119 | unauthenticated user | 192.168.1.56:4173 | NULL | Connect | NULL |
 | login NULL

Best regards

Nils Valentin
Tokyo/Japan

--
---
Valentin Nils
Internet Technology

 E-Mail: [EMAIL PROTECTED]
 URL: http://www.knowd.co.jp
 Personal URL: http://www.knowd.co.jp/staff/nils


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: URGENT problem with mysql processes

2003-06-27 Thread Keith Bussey
No, the slaves replicate fine and I can see their entries in the processlist
normally (as their hostname), not as unauthenticated user..

-- 
Keith Bussey

Wisol, Inc.
Chief Technology Manager
(514) 398-9994 ext.225


Quoting Nils Valentin [EMAIL PROTECTED]:

 Hi Keith,
 
 from your last e-mail I understand now finally that we are talking about 
 replication here. Would have been a short cut to mention it in your first 
 e-mail.
 
 The failed login attempts couldn't be from your slaves trying to login, but 
 you havent set them up on the master yet ?
 
 Just a guess, so.
 
 2003年 6月 27日 金曜日 09:05、Keith Bussey さんは書きました:
  | 106 | unauthenticated user | 192.168.1.59:1925 | NULL | Connect | NULL |
  | login NULL
  |
  | 115 | unauthenticated user | 192.168.1.53:2041 | NULL | Connect | NULL |
  | login NULL
  |
  | 118 | unauthenticated user | 192.168.1.56:4172 | NULL | Connect | NULL |
  | login NULL
  |
  | 119 | unauthenticated user | 192.168.1.56:4173 | NULL | Connect | NULL |
  | login NULL
 
 Best regards
 
 Nils Valentin
 Tokyo/Japan
 
 -- 
 ---
 Valentin Nils
 Internet Technology
 
  E-Mail: [EMAIL PROTECTED]
  URL: http://www.knowd.co.jp
  Personal URL: http://www.knowd.co.jp/staff/nils
 
 
 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
 
 

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: URGENT problem with mysql processes

2003-06-27 Thread Keith Bussey
No, replication is fine I can see those processes as they should be. The problem
processes all come from the webservers' requests.

-- 
Keith Bussey

Wisol, Inc.
Chief Technology Manager
(514) 398-9994 ext.225


Quoting Dominicus Donny [EMAIL PROTECTED]:

 If it is the replication problem...::
 Check the replication account on the master server:
 ...[EMAIL PROTECTED] identified by ...
 ...[EMAIL PROTECTED] identified by ...
 ...[EMAIL PROTECTED] identified by ...
 ...
 ...[EMAIL PROTECTED] identified by ...
 
 or perhaps simply set to
 ...replication_account@% identified by ...
 
 make sure the account has access to the specified db.tables, too.
 
 Me fail English? That's unpossible
 ###___Archon___###
 
 - Original Message -
 From: Nils Valentin [EMAIL PROTECTED]
 To: Keith Bussey [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Sent: Friday, June 27, 2003 1:30 PM
 Subject: Re: URGENT problem with mysql processes
 
 
 Hi Keith,
 
 from your last e-mail I understand now finally that we are talking about
 replication here. Would have been a short cut to mention it in your first
 e-mail.
 
 The failed login attempts couldn't be from your slaves trying to login, but
 you havent set them up on the master yet ?
 
 Just a guess, so.
 
 2003年 6月 27日 金曜日 09:05、Keith Bussey さんは書きました:
  | 106 | unauthenticated user | 192.168.1.59:1925 | NULL | Connect | NULL |
  | login NULL
  |
  | 115 | unauthenticated user | 192.168.1.53:2041 | NULL | Connect | NULL |
  | login NULL
  |
  | 118 | unauthenticated user | 192.168.1.56:4172 | NULL | Connect | NULL |
  | login NULL
  |
  | 119 | unauthenticated user | 192.168.1.56:4173 | NULL | Connect | NULL |
  | login NULL
 
 Best regards
 
 Nils Valentin
 Tokyo/Japan
 
 --
 ---
 Valentin Nils
 Internet Technology
 
  E-Mail: [EMAIL PROTECTED]
  URL: http://www.knowd.co.jp
  Personal URL: http://www.knowd.co.jp/staff/nils
 
 
 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:
 http://lists.mysql.com/[EMAIL PROTECTED]
 
 
 -- 
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
 
 

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: URGENT problem with mysql processes

2003-06-27 Thread Keith Bussey
Quoting Nils Valentin [EMAIL PROTECTED]:

 When you said you modified the scripts, are these the scripts on the 12 
 webservers (mysql clients) ?

Yes, when I mention modifying my scripts, I mean the scripts/pages on the 12
webservers
 
 If not, then these mysql clients (webservers) would still be wanting to send
 
 to IP addres 192.168.1.71 as configured for php or in your client.
 
 Best regards
 
 Nils Valentin
 Tokyo/Japan
 
 
 2003年 6月 27日 金曜日 14:58、Keith Bussey さんは書きました:
  Neither of these two machines send the request.
 
  I have 12 webservers, which send the requests.
  I have 5 database servers, 1 master(for updates/inserts/deletes) and 4
  slaves(for selects).
 
  Machine A below was the current Master DB server, however it is old and
 was
  being replaced by machine B
 
 
  --
  Keith Bussey
 
  Wisol, Inc.
  Chief Technology Manager
  (514) 398-9994 ext.225
 
  Quoting Nils Valentin [EMAIL PROTECTED]:
   Hi Keith,
  
   soory now I got confused. Which machine is sending the requests (client)
   and
  
   which machine is the mysql server (server). Do you use php or something
   like
  
   this (webinterface) on the client ?
  
   If yes, than my suggestions below apply.
   If no than I we will have to think the next step.
  
   Best regards
  
   Nils Valentin
   Tokyo/Japan
  
   2003年 6月 27日 金曜日 11:29、Keith Bussey 
 さんは書きました:
Ok but that's not what I meant.
   
I'll try to explain better.
   
Machine A: IP = 192.168.1.71
Machine B: IP = 192.168.1.79
   
1) Scripts goto 192.168.1.71 - Everything is OK
2) Changed scripts to 192.168.1.79 - Site works at first, but
 processes
pile up until server is killed
3) Halt machine B
4) Give machine A IP 192.168.1.79 (so now it has 2 IPs)
5) Problem persists even though it's a different machine, site works
but then processes pile up and kill machine
6) Change scripts to use 192.168.1.71 again
7) Site works fine
   
   
What I don't get is why do processes run normally with IP
 192.168.1.71,
  
   but
  
NOT with IP 192.168.1.79 even when they are on the same machine ?
   
--
Keith Bussey
   
Wisol, Inc.
Chief Technology Manager
(514) 398-9994 ext.225
   
Quoting Nils Valentin [EMAIL PROTECTED]:
 Hi Keith,

 The wrong IP address could only avoid a client to connect to the
  
   database
  
 server.

 If you have the TCP/IP address specified in /etc/php.ini or for
 phpmyadmin in

 config.inc.php or which ever tool you use than of course it will try
 to connect to this IP address.

 Best regards

 Nils Valentin
 Tokto/Japan

 2003年 6月 27日
 金曜日 11:02、Keith
 Bussey
  
  

さんは書きました:
  Hrmmmeaning if I do id mysql, that information (group etc..)
  ?
 
  I've halted that server and moved everything back to my original
  
   server
  
 for

  now, I had too much downtime. I did notice something else
  interesting though:
 
  The old mahcine's IP is 192.168.1.71
  New machine's IP is 192.168.1.79
 
  Now that it's halted, instead of changing the IP back to .71 in my
  pages/scripts I added .79 to the .71 machine so it has both
 
  Now that machine experienced the exact same problem. Switching my
  code to use .71 again however, and no problems.
 
  Could somehow there be a problem with the IP address
 192.168.1.79??
  It seems very strange, however tomorrow I will try putting the .71
  on the new machine and see if it works or not

 --
 ---
 Valentin Nils
 Internet Technology

  E-Mail: [EMAIL PROTECTED]
  URL: http://www.knowd.co.jp
  Personal URL: http://www.knowd.co.jp/staff/nils


 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:   
 http://lists.mysql.com/[EMAIL PROTECTED]
  
   --
   ---
   Valentin Nils
   Internet Technology
  
E-Mail: [EMAIL PROTECTED]
URL: http://www.knowd.co.jp
Personal URL: http://www.knowd.co.jp/staff/nils
 
 -- 
 ---
 Valentin Nils
 Internet Technology
 
  E-Mail: [EMAIL PROTECTED]
  URL: http://www.knowd.co.jp
  Personal URL: http://www.knowd.co.jp/staff/nils
 
 
 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
 
 

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



URGENT problem with mysql processes

2003-06-26 Thread Keith Bussey
Major problem!

I've installed mysql-standard 4.0.13 (from binary) a new DB server, it is

- quad-xeon (500mhz each cpu)
- 3 gig RAM
- Linux Redhat 7.3

When I start up mysql, processes looking like the following begin to pile up
until it kills the server:

| 106 | unauthenticated user | 192.168.1.59:1925 | NULL | Connect | NULL | login
| NULL
|
| 115 | unauthenticated user | 192.168.1.53:2041 | NULL | Connect | NULL | login
| NULL
|
| 118 | unauthenticated user | 192.168.1.56:4172 | NULL | Connect | NULL | login
| NULL
|
| 119 | unauthenticated user | 192.168.1.56:4173 | NULL | Connect | NULL | login
| NULL
|


I need to fix this immediately as my site cannot run !

Thanks in advance. I've seen this exact same situation happen to others (posted
on various boards), however never saw any solutions ;/



-- 
Keith Bussey

Wisol, Inc.
Chief Technology Manager
(514) 398-9994 ext.225




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: URGENT problem with mysql processes

2003-06-26 Thread Nils Valentin
Hi Keith,

The wrong IP address could only avoid a client to connect to the database 
server. 

If you have the TCP/IP address specified in /etc/php.ini or for phpmyadmin in 
config.inc.php or which ever tool you use than of course it will try to 
connect to this IP address.

Best regards

Nils Valentin
Tokto/Japan


2003 6 27  11:02Keith Bussey :
 Hrmmmeaning if I do id mysql, that information (group etc..) ?

 I've halted that server and moved everything back to my original server for
 now, I had too much downtime. I did notice something else interesting
 though:

 The old mahcine's IP is 192.168.1.71
 New machine's IP is 192.168.1.79

 Now that it's halted, instead of changing the IP back to .71 in my
 pages/scripts I added .79 to the .71 machine so it has both

 Now that machine experienced the exact same problem. Switching my code to
 use .71 again however, and no problems.

 Could somehow there be a problem with the IP address 192.168.1.79?? It
 seems very strange, however tomorrow I will try putting the .71 on the new
 machine and see if it works or not

-- 
---
Valentin Nils
Internet Technology

 E-Mail: [EMAIL PROTECTED]
 URL: http://www.knowd.co.jp
 Personal URL: http://www.knowd.co.jp/staff/nils


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



MySQL processes..

2002-10-20 Thread Sandeep Murphy
hi,

I have a problem with the connections and would appreicate a lot if anyone can provide 
a soln..

Our JSP application has connections to both Oracle and MySQL... In each page there are 
nearly a dozen queries executing on a MySQL db. at the begining of each page, a 
connection is opened and at the end they are close.. Ideally, if the user waits for 
the page to load completely and then hit the button Next or Cancel, the connection is 
freed..

But what happens often is that soon after entering the page, many users just click on 
Next resulting in the connection not getting closed...and soon, the no of connections 
exceed the allotted number (because they dont get freed automatically) and thus 
crashes the application..

My question is this: Is there anyway to kill the processes in MySQL (ofcourse i can do 
it manually but am talking about real time) ???

thnx for any suggestions..

sands

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: MySQL processes..

2002-10-18 Thread Niclas Hedhman
On Thursday 17 October 2002 19:33, Sandeep Murphy wrote:
 Our JSP application has connections to both Oracle and MySQL... In each
 page there are nearly a dozen queries executing on a MySQL db. at the
 begining of each page, a connection is opened and at the end they are
 close.. Ideally, if the user waits for the page to load completely and then
 hit the button Next or Cancel, the connection is freed..

 thnx for any suggestions..

Give up JSP ... Move the DB code to servlets, where you have better control.

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: MySQL processes..

2002-10-18 Thread Mark Matthews
Sandeep Murphy wrote:

hi,

I have a problem with the connections and would appreicate a lot if anyone can provide a soln..

Our JSP application has connections to both Oracle and MySQL... In each page there are nearly a dozen queries executing on a MySQL db. at the begining of each page, a connection is opened and at the end they are close.. Ideally, if the user waits for the page to load completely and then hit the button Next or Cancel, the connection is freed..

But what happens often is that soon after entering the page, many users just click on Next resulting in the connection not getting closed...and soon, the no of connections exceed the allotted number (because they dont get freed automatically) and thus crashes the application..


Wrap your code with a try/finally{} block, and in the finally block, put 
your connection.close(). It will always get called, no matter whether or 
not the user clicks next.

My question is this: Is there anyway to kill the processes in MySQL (ofcourse i can do it manually but am talking about real time) ???



mysqladmin will let you kill threads.

	-Mark
--
For technical support contracts, visit https://order.mysql.com/?ref=mmma

__  ___ ___   __
   /  |/  /_ __/ __/ __ \/ /  Mark Matthews [EMAIL PROTECTED]
  / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer - JDBC/Java
 /_/  /_/\_, /___/\___\_\___/ Flossmoor (Chicago), IL USA
___/ www.mysql.com


-
Before posting, please check:
  http://www.mysql.com/manual.php   (the manual)
  http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




RE: MySQL processes..

2002-10-18 Thread Sandeep Murphy
Hi Mark,

Yes, the code is wrapped by a try , catch, finally block but still we r facing 
suspended connections.. :(

am using MysqlFront to administer the dbs and i can kill the suspended/delayed 
processes manually.. 

Does mysqladmin provide any other additional services??

thnx,
sands

-Original Message-
From: Mark Matthews [mailto:mark;mysql.com]
Sent: quinta-feira, 17 de Outubro de 2002 13:05
To: Sandeep Murphy
Cc: [EMAIL PROTECTED]
Subject: Re: MySQL processes..


Sandeep Murphy wrote:
 hi,
 
 I have a problem with the connections and would appreicate a lot if anyone can 
provide a soln..
 
 Our JSP application has connections to both Oracle and MySQL... In each page there 
are nearly a dozen queries executing on a MySQL db. at the begining of each page, a 
connection is opened and at the end they are close.. Ideally, if the user waits for 
the page to load completely and then hit the button Next or Cancel, the connection is 
freed..
 
 But what happens often is that soon after entering the page, many users just click 
on Next resulting in the connection not getting closed...and soon, the no of 
connections exceed the allotted number (because they dont get freed automatically) 
and thus crashes the application..

Wrap your code with a try/finally{} block, and in the finally block, put 
your connection.close(). It will always get called, no matter whether or 
not the user clicks next.

 My question is this: Is there anyway to kill the processes in MySQL (ofcourse i can 
do it manually but am talking about real time) ???


mysqladmin will let you kill threads.

-Mark
-- 
For technical support contracts, visit https://order.mysql.com/?ref=mmma

 __  ___ ___   __
/  |/  /_ __/ __/ __ \/ /  Mark Matthews [EMAIL PROTECTED]
   / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer - JDBC/Java
  /_/  /_/\_, /___/\___\_\___/ Flossmoor (Chicago), IL USA
 ___/ www.mysql.com


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Hung login mysql processes - unable to kill.

2002-05-20 Thread Reid Sutherland (mysql)

Hi everyone,

I have a rather obscure problem with hung login connections in mysql. 
 I've set the wait|interactive_timeout to 120 seconds, but it has no 
effect.\
If I attempt to `mysqladmin kill id`, the process is marked 'killed', 
but never goes away.  

Now I know the main problem is with the program I am using to create the 
connections and access the data, but I'm ignoring that right now because 
I want to deal with these stale (or hung) login processes.  And find out 
how to remove them or time them out (without restarting mysql mind you, 
if at all possible).

Here's some brief output from my `mysqladmin processlist`:

++--+---+--+-+--+---+--+
| Id | User | Host  | db   | Command | Time 
| State | Info |
++--+---+--+-+--+---+--+
| 22088  | via_httplogs | localhost |  | Connect |  
| login |  |
| 22877  | via_httplogs | localhost |  | Connect |  
| login |  |
| 23135  | via_httplogs | localhost |  | Connect |  
| login |  |
| 23226  | via_httplogs | localhost |  | Connect |  
| login |  |
| 26523  | via_httplogs | localhost |  | Connect |  
| login |  |
| 32105  | via_httplogs | localhost |  | Connect |  
| login |  |
| 32113  | via_httplogs | localhost |  | Connect |  
| login |  |
| 37098  | via_httplogs | localhost |  | Connect |  
| login |  |
| 38300  | via_httplogs | localhost |  | Connect |  
| login |  |
| 51212  | via_httplogs | localhost |  | Connect |  
| login |  |
| 89713  | via_httplogs | localhost |  | Connect |  
| login |  |
| 99008  | via_httplogs | localhost |  | Connect |  
| login |  |
| 119642 | via_httplogs | localhost | via_httplogs | Sleep   | 2
|   |  |
| 119644 | via_httplogs | localhost | via_httplogs | Sleep   | 29   
|   |  |
| 119645 | via_httplogs | localhost | via_httplogs | Sleep   | 14   
|   |  |
| 119646 | via_httplogs | localhost | via_httplogs | Sleep   | 41   
|   |  |
...

Nothing shows up in the mysql error log either.

Any ideas?

Thanks again.

-reid



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Mysql processes not dying

2001-12-28 Thread Pedro


Is there any reason for mysqld processes not dying? 

Any try to kill it result in a 'defunct' processes (accoarding to ps
aux). And what is a defunct process?

The kernel prints the message: mm: critical shortage of bounce
buffers. Any ideia what is it´s relation with Mysql? 

The machine has no special devices and has 1GB of ram.

Thanks for any help.

Pedro Furlanetto
ocarteiro.com team

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: Lots of spawning Mysql processes and one that won't die?

2001-08-15 Thread Ed Carp

Ryan Shrout ([EMAIL PROTECTED]) writes:

   PID USER PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND=
   =20
 24424 mysql 18   0  6116 6116  2196 R99.9  0.5   4:05 mysqld =

 This is after a mysqld restart -- It restarted, but didn't work because =
 this single mysqld process wouldn't die.  I even tried to kill it kill =
 24424 and it still wouldn't go away -- not letting me restart mysqld.

IT often takes several seconds for a killed mysqld process to clean up and go away.  I 
wouldn't recommend doing a kill -9, though, except as a last resort.  The fact that 
mysqld is still running means it's doing somethig, it hasn't died.

I used to have the same problem until I used hdparm to tune my drives.  Surprisingly, 
it made a *lot* of difference - I was surprised at how much it made a difference in 
how fast mysql ran.
--
Ed Carp, N7EKG  [EMAIL PROTECTED]   214/986-5870 cell phone
http://www.pobox.com/~erc

I sometimes wonder if the American people deserve to be free - they seem
so unwilling to fight to preserve the few freedoms they have left.

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: Lots of spawning Mysql processes and one that won't die?

2001-08-15 Thread Irmund Thum

 This is after a mysqld restart -- It restarted, but didn't work because
 this single mysqld process wouldn't die.  I even tried to kill it kill
 24424 and it still wouldn't go away -- not letting me restart mysqld.

 What is going on here?
kill -9 24424
i.t

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




RE: Lots of spawning Mysql processes and one that won't die?

2001-08-14 Thread Dan Haynes

Dunno if this will help or not, I'll just throw it out for consideration.

I'm just learning PHP, Javascript etc.  and tend to make a lot of mistakes in
my scripts at this point.

When I write a script that executes a binary on the Apache server (NT 4.0
SP6a) and it goes off into na-na land, I terminate the page loading under
netscape with the esc key. This leaves dead Apache child processes in the
background, one for each page load that is canceled. Any possibility you've
got some scripts running/barfing when you start up mySQL?

Regards,

  Dan Haynes


 -Original Message-
 From: Ryan Shrout [mailto:[EMAIL PROTECTED]]
 Sent: Tuesday, August 14, 2001 4:36 PM
 To: [EMAIL PROTECTED]
 Subject: Lots of spawning Mysql processes and one that won't die?


 Earlier I told you all about the mysqld problem I had with my
 dual-athlon server.

 Well, more hunting and I find this:

   6:26pm  up  4:55,  1 user,  load average: 3.05, 28.62, 26.85

 106 processes: 103 sleeping, 3 running, 0 zombie, 0 stopped

 CPU0 states: 28.4% user,  4.3% system,  0.0% nice, 66.2% idle

 CPU1 states: 79.3% user,  1.3% system,  0.0% nice, 18.2% idle

 Mem:  1026964K av,  699636K used,  327328K free,  56K shrd,
 67576K buff
 Swap: 2048248K av,   17980K used, 2030268K free
 463444K cached


   PID USER PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME
 COMMAND
 24424 mysql 18   0  6116 6116  2196 R99.9  0.5   4:05
 mysqld
 19915 apache 8   0  7316 6280  3976 S 0.5  0.6   0:02 httpd

 25881 root  11   0  1124 1124   840 R 0.5  0.1   0:00 top

   888 apache 9   0  6476 5028  2812 S 0.3  0.4   0:36 httpd

 20001 apache 9   0  7460 6424  3972 S 0.3  0.6   0:03 httpd

 20276 apache 9   0  7264 6232  3976 S 0.3  0.6   0:02 httpd

 24316 apache 8   0  5500 4460  3860 S 0.3  0.4   0:00 httpd

 24371 apache 8   0  6072 5032  3900 S 0.3  0.4   0:00 httpd

 24441 apache 9   0  5440 4400  3844 S 0.3  0.4   0:00 httpd

 24458 apache 8   0  5868 4828  3852 S 0.3  0.4   0:00 httpd

 24490 apache 8   0  5496 4456  3852 S 0.3  0.4   0:00 httpd

 24459 apache 8   0  5520 4456  3856 S 0.1  0.4   0:00 httpd

 24484 apache 8   0  5784 4672  3832 S 0.1  0.4   0:00 httpd

 24502 apache 8   0  5496 4432  3860 S 0.1  0.4   0:00 httpd

 This is after a mysqld restart -- It restarted, but didn't work
 because this single mysqld process wouldn't die.  I even tried to
 kill it kill 24424 and it still wouldn't go away -- not letting
 me restart mysqld.

 What is going on here?

 Ryan Shrout
 Owner - Amdmb.com
 http://www.amdmb.com/
 [EMAIL PROTECTED]





-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: Apache/PHP/MySQL - processes multiply until about 30, then doom

2001-05-03 Thread Gary Bickford

Thanks for the reply!, Scott!  I considered changing the number of 
allowed connections but I figured this would just defer the problem, 
as the root problem was the increasing number of connections.

Last night I went through the entire website looking for code that 
used mysql_pconnect() in PHP, which provides 'persistent' 
connections.  I had thought before that I had caught all of these but 
found another 40 or so files that had either been missed or magically 
appeared.  I converted all those to standard mysql_connect() calls 
and ran a stress test all night - using wget to fetch 1000 pages as 
fast as possible from a neighboring machine, over and over.

On the server I have a loop running like this:

   N=1; while [ $N -ge 1 ]; do ps aux|grep mysql |wc; sleep 5; done

which shows the number of mysql processes every five seconds or so.
I had run this test earlier and over two hours' time the number of 
connections increased to about 22.  After changing all the 
mysql_pconnect() calls to mysql_connect(), and leaving the wget job 
running all night (the 'at' job I set up to kill it while I was 
sleeping failed), the number of connections was still at 5.  This 
involved fetching almost 400,000 pages. 

So it appears that the increasing number of connections has to do 
with some persistent connections never being closed, although PHP 
thought they were.  Determining if this is a PHP, MySQL, Apache or 
Redhat problem is beyond my desired effort and code experience level. 
At least all parts are open source!!

Interestingly, the rate at which wget could fetch pages almost 
doubled while the server's CPU load dropped from 86% to 77%, which 
bears out the experience of some others on various PHP lists. Some 
users get dramatic improvements using mysql_pconnect(), others don't.

I will now make another pass at a couple of pages that seemed to be 
the focus of the errors that users received, to see if I can improve 
the error handling (and maybe mail myself a message!).  For now, I'm 
calling the bug worked-around.

GB

On Wednesday 02 May 2001 04:43 pm, Scott Baker opined:
 You can look into increasing the number of allowed connections that
 MySQL will accept... are you using connect or pconnect?

 At 04:23 PM 5/3/2001 -0700, Gary Bickford wrote:
 Repost - nobody has any ideas?  I've run some stress tests,
  sending several thousand page requests, and the number of mysql
  processes goes up and down but over time continues to rise.  It's
  up to about 22 now.  When it gets to about 30, every request from
  the web server will be will fail.
 
 Could some of these processes be threads that are orphaned for
  some reason (perhaps Apache continuing to expire its own
  processes?) and hang around, idle?  I speculate that there is
  some maximum number of processes and finally MySQL can't won't
  start another thread/process. GB
 
 On Tuesday 01 May 2001 05:26 pm, Gary E Bickford opined:
   I am running MySQL (3.23.27 at this point) with Apache1.3.12
   and PHP3 on a PC running Redhat 6.0.  My problem has survived
   upgrades of all components from earlier versions.
  
   Every PHP page has at least one query to a MySQL database for
   session tracking (home-rolled code, not PHPLib or anything off
   the shelf)  There are also on some pages other queries, to a
   different database, same server (same mysql).  Most of the
   latter are Phorum queries.
  
   Periodically the number of mysql instances that show up in 'ps
   auxww'1 gets to about 30 and mysql no longer listens to
   PHP/Apache. However I can still use the mysql shell with no
   problem, so MySQL is still running but can't hear anything from
   PHP.
  
   The only way to fix it is to run 'apachectl restart' or
   equivalent. 'graceful' doesn't do it.  Im not sure if
   restarting MySQL instead works.  After Apache is restarted, the
   mysql processes are down to 3 and everybody's happy again.
  
   I have been trying for months to figure out what is happening
   and how to fix it.  I had heard at one point that there was a
   problem with Redhat 5.2 kernel that caused a similar problem,
   but I upgraded that but no joy.
  
   Temporarily I have built a kluge cron job that restarts apache
   every so often, which worked as long as the server was low
   volume. But now usage is dramatically increasing due to some
   new web sites that have been installed and announced to the
   entire corporation. So the problem is triggered before the
   restart cleans up the mess. I can't have it restarting every 20
   minutes.
  
   I've also changed every instance of pconnect() to connect()
   where I can, but no difference.
  
   Can anybody tell me anything useful?  I'm supposed to come back
   with a firm fixit schedule tomorrow morning, so please email me
   directly as well as on the list - I'm afraid I'll miss it in
   the volume on the list. If I don't get this fixed very shortly
   my consulting contract with this company will no doubt begin to
   fade out

Re: Apache/PHP/MySQL - processes multiply until about 30, then doom

2001-05-03 Thread Scott Baker

That's very odd...  Technically pconnect should be a lot faster, not sure 
exactly why it's not.  The other thing you might want to look at is the 
MySQL idle timeout (or something like that).  That's how long your 
pconnects stay connected if they don't transfer any traffic.  I think it 
defaults to 30 minutes, which is probably ok.  Depending on the traffic of 
your site.

At 09:27 AM 5/4/2001 -0700, Gary Bickford wrote:
Thanks for the reply!, Scott!  I considered changing the number of
allowed connections but I figured this would just defer the problem,
as the root problem was the increasing number of connections.

Last night I went through the entire website looking for code that
used mysql_pconnect() in PHP, which provides 'persistent'
connections.  I had thought before that I had caught all of these but
found another 40 or so files that had either been missed or magically
appeared.  I converted all those to standard mysql_connect() calls
and ran a stress test all night - using wget to fetch 1000 pages as
fast as possible from a neighboring machine, over and over.

On the server I have a loop running like this:

N=1; while [ $N -ge 1 ]; do ps aux|grep mysql |wc; sleep 5; done

which shows the number of mysql processes every five seconds or so.
I had run this test earlier and over two hours' time the number of
connections increased to about 22.  After changing all the
mysql_pconnect() calls to mysql_connect(), and leaving the wget job
running all night (the 'at' job I set up to kill it while I was
sleeping failed), the number of connections was still at 5.  This
involved fetching almost 400,000 pages.

So it appears that the increasing number of connections has to do
with some persistent connections never being closed, although PHP
thought they were.  Determining if this is a PHP, MySQL, Apache or
Redhat problem is beyond my desired effort and code experience level.
At least all parts are open source!!

Interestingly, the rate at which wget could fetch pages almost
doubled while the server's CPU load dropped from 86% to 77%, which
bears out the experience of some others on various PHP lists. Some
users get dramatic improvements using mysql_pconnect(), others don't.

I will now make another pass at a couple of pages that seemed to be
the focus of the errors that users received, to see if I can improve
the error handling (and maybe mail myself a message!).  For now, I'm
calling the bug worked-around.

GB

On Wednesday 02 May 2001 04:43 pm, Scott Baker opined:
  You can look into increasing the number of allowed connections that
  MySQL will accept... are you using connect or pconnect?
 
  At 04:23 PM 5/3/2001 -0700, Gary Bickford wrote:
  Repost - nobody has any ideas?  I've run some stress tests,
   sending several thousand page requests, and the number of mysql
   processes goes up and down but over time continues to rise.  It's
   up to about 22 now.  When it gets to about 30, every request from
   the web server will be will fail.
  
  Could some of these processes be threads that are orphaned for
   some reason (perhaps Apache continuing to expire its own
   processes?) and hang around, idle?  I speculate that there is
   some maximum number of processes and finally MySQL can't won't
   start another thread/process. GB
  
  On Tuesday 01 May 2001 05:26 pm, Gary E Bickford opined:
I am running MySQL (3.23.27 at this point) with Apache1.3.12
and PHP3 on a PC running Redhat 6.0.  My problem has survived
upgrades of all components from earlier versions.
   
Every PHP page has at least one query to a MySQL database for
session tracking (home-rolled code, not PHPLib or anything off
the shelf)  There are also on some pages other queries, to a
different database, same server (same mysql).  Most of the
latter are Phorum queries.
   
Periodically the number of mysql instances that show up in 'ps
auxww'1 gets to about 30 and mysql no longer listens to
PHP/Apache. However I can still use the mysql shell with no
problem, so MySQL is still running but can't hear anything from
PHP.
   
The only way to fix it is to run 'apachectl restart' or
equivalent. 'graceful' doesn't do it.  Im not sure if
restarting MySQL instead works.  After Apache is restarted, the
mysql processes are down to 3 and everybody's happy again.
   
I have been trying for months to figure out what is happening
and how to fix it.  I had heard at one point that there was a
problem with Redhat 5.2 kernel that caused a similar problem,
but I upgraded that but no joy.
   
Temporarily I have built a kluge cron job that restarts apache
every so often, which worked as long as the server was low
volume. But now usage is dramatically increasing due to some
new web sites that have been installed and announced to the
entire corporation. So the problem is triggered before the
restart cleans up the mess. I can't have it restarting every 20

Re: Apache/PHP/MySQL - processes multiply until about 30, then doom

2001-05-03 Thread Paul DuBois

At 9:35 AM -0700 5/3/01, Scott Baker wrote:
That's very odd...  Technically pconnect should be a lot faster, not 
sure exactly why it's not.  The other thing you might want to look 
at is the MySQL idle timeout (or something like that).  That's how 
long your pconnects stay connected if they don't transfer any 
traffic.  I think it defaults to 30 minutes, which is probably ok. 
Depending on the traffic of your site.

For most databases pconnect() is faster.  But it turns out MySQL is so
fast at making connections that pconnect() doesn't give much advantage,
if any.  So regular connect() can be advantageous in terms of not leaving
as many connections open.


At 09:27 AM 5/4/2001 -0700, Gary Bickford wrote:
Thanks for the reply!, Scott!  I considered changing the number of
allowed connections but I figured this would just defer the problem,
as the root problem was the increasing number of connections.

Last night I went through the entire website looking for code that
used mysql_pconnect() in PHP, which provides 'persistent'
connections.  I had thought before that I had caught all of these but
found another 40 or so files that had either been missed or magically
appeared.  I converted all those to standard mysql_connect() calls
and ran a stress test all night - using wget to fetch 1000 pages as
fast as possible from a neighboring machine, over and over.

On the server I have a loop running like this:

N=1; while [ $N -ge 1 ]; do ps aux|grep mysql |wc; sleep 5; done

which shows the number of mysql processes every five seconds or so.
I had run this test earlier and over two hours' time the number of
connections increased to about 22.  After changing all the
mysql_pconnect() calls to mysql_connect(), and leaving the wget job
running all night (the 'at' job I set up to kill it while I was
sleeping failed), the number of connections was still at 5.  This
involved fetching almost 400,000 pages.

So it appears that the increasing number of connections has to do
with some persistent connections never being closed, although PHP
thought they were.  Determining if this is a PHP, MySQL, Apache or
Redhat problem is beyond my desired effort and code experience level.
At least all parts are open source!!

Interestingly, the rate at which wget could fetch pages almost
doubled while the server's CPU load dropped from 86% to 77%, which
bears out the experience of some others on various PHP lists. Some
users get dramatic improvements using mysql_pconnect(), others don't.

I will now make another pass at a couple of pages that seemed to be
the focus of the errors that users received, to see if I can improve
the error handling (and maybe mail myself a message!).  For now, I'm
calling the bug worked-around.

GB

On Wednesday 02 May 2001 04:43 pm, Scott Baker opined:
  You can look into increasing the number of allowed connections that
  MySQL will accept... are you using connect or pconnect?

  At 04:23 PM 5/3/2001 -0700, Gary Bickford wrote:
  Repost - nobody has any ideas?  I've run some stress tests,
   sending several thousand page requests, and the number of mysql
   processes goes up and down but over time continues to rise.  It's
   up to about 22 now.  When it gets to about 30, every request from
   the web server will be will fail.
  
  Could some of these processes be threads that are orphaned for
   some reason (perhaps Apache continuing to expire its own
   processes?) and hang around, idle?  I speculate that there is
   some maximum number of processes and finally MySQL can't won't
   start another thread/process. GB
  
  On Tuesday 01 May 2001 05:26 pm, Gary E Bickford opined:
I am running MySQL (3.23.27 at this point) with Apache1.3.12
and PHP3 on a PC running Redhat 6.0.  My problem has survived
upgrades of all components from earlier versions.
   
Every PHP page has at least one query to a MySQL database for
 session tracking (home-rolled code, not PHPLib or anything off
the shelf)  There are also on some pages other queries, to a
different database, same server (same mysql).  Most of the
latter are Phorum queries.
   
Periodically the number of mysql instances that show up in 'ps
auxww'1 gets to about 30 and mysql no longer listens to
PHP/Apache. However I can still use the mysql shell with no
problem, so MySQL is still running but can't hear anything from
PHP.
   
The only way to fix it is to run 'apachectl restart' or
equivalent. 'graceful' doesn't do it.  Im not sure if
restarting MySQL instead works.  After Apache is restarted, the
mysql processes are down to 3 and everybody's happy again.
   
I have been trying for months to figure out what is happening
and how to fix it.  I had heard at one point that there was a
problem with Redhat 5.2 kernel that caused a similar problem,
but I upgraded that but no joy.
   
Temporarily I have built a kluge cron job that restarts apache
every so often, which worked as long

Re: Apache/PHP/MySQL - processes multiply until about 30, then doom

2001-05-02 Thread Gary Bickford

Repost - nobody has any ideas?  I've run some stress tests, sending 
several thousand page requests, and the number of mysql processes 
goes up and down but over time continues to rise.  It's up to about 
22 now.  When it gets to about 30, every request from the web server 
will be will fail.

Could some of these processes be threads that are orphaned for some 
reason (perhaps Apache continuing to expire its own processes?) and 
hang around, idle?  I speculate that there is some maximum number of 
processes and finally MySQL can't won't start another thread/process.
GB

On Tuesday 01 May 2001 05:26 pm, Gary E Bickford opined:
 I am running MySQL (3.23.27 at this point) with Apache1.3.12 and
 PHP3 on a PC running Redhat 6.0.  My problem has survived upgrades
 of all components from earlier versions.

 Every PHP page has at least one query to a MySQL database for
 session tracking (home-rolled code, not PHPLib or anything off the
 shelf)  There are also on some pages other queries, to a different
 database, same server (same mysql).  Most of the latter are Phorum
 queries.

 Periodically the number of mysql instances that show up in 'ps
 auxww'1 gets to about 30 and mysql no longer listens to PHP/Apache.
  However I can still use the mysql shell with no problem, so MySQL
 is still running but can't hear anything from PHP.

 The only way to fix it is to run 'apachectl restart' or equivalent.
 'graceful' doesn't do it.  Im not sure if restarting MySQL instead
 works.  After Apache is restarted, the mysql processes are down to
 3 and everybody's happy again.

 I have been trying for months to figure out what is happening and
 how to fix it.  I had heard at one point that there was a problem
 with Redhat 5.2 kernel that caused a similar problem, but I
 upgraded that but no joy.

 Temporarily I have built a kluge cron job that restarts apache
 every so often, which worked as long as the server was low volume. 
 But now usage is dramatically increasing due to some new web sites
 that have been installed and announced to the entire corporation. 
 So the problem is triggered before the restart cleans up the mess. 
 I can't have it restarting every 20 minutes.

 I've also changed every instance of pconnect() to connect() where I
 can, but no difference.

 Can anybody tell me anything useful?  I'm supposed to come back
 with a firm fixit schedule tomorrow morning, so please email me
 directly as well as on the list - I'm afraid I'll miss it in the
 volume on the list. If I don't get this fixed very shortly my
 consulting contract with this company will no doubt begin to fade
 out!!

 Thanks in advance,
 Gary Bickford


 ---
-- Before posting, please check:
http://www.mysql.com/manual.php   (the manual)
http://lists.mysql.com/   (the list archive)

 To request this thread, e-mail [EMAIL PROTECTED]
 To unsubscribe, e-mail
 [EMAIL PROTECTED] Trouble
 unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: Apache/PHP/MySQL - processes multiply until about 30, then doom

2001-05-02 Thread Scott Baker

You can look into increasing the number of allowed connections that MySQL 
will accept... are you using connect or pconnect?

At 04:23 PM 5/3/2001 -0700, Gary Bickford wrote:
Repost - nobody has any ideas?  I've run some stress tests, sending
several thousand page requests, and the number of mysql processes
goes up and down but over time continues to rise.  It's up to about
22 now.  When it gets to about 30, every request from the web server
will be will fail.

Could some of these processes be threads that are orphaned for some
reason (perhaps Apache continuing to expire its own processes?) and
hang around, idle?  I speculate that there is some maximum number of
processes and finally MySQL can't won't start another thread/process.
GB

On Tuesday 01 May 2001 05:26 pm, Gary E Bickford opined:
  I am running MySQL (3.23.27 at this point) with Apache1.3.12 and
  PHP3 on a PC running Redhat 6.0.  My problem has survived upgrades
  of all components from earlier versions.
 
  Every PHP page has at least one query to a MySQL database for
  session tracking (home-rolled code, not PHPLib or anything off the
  shelf)  There are also on some pages other queries, to a different
  database, same server (same mysql).  Most of the latter are Phorum
  queries.
 
  Periodically the number of mysql instances that show up in 'ps
  auxww'1 gets to about 30 and mysql no longer listens to PHP/Apache.
   However I can still use the mysql shell with no problem, so MySQL
  is still running but can't hear anything from PHP.
 
  The only way to fix it is to run 'apachectl restart' or equivalent.
  'graceful' doesn't do it.  Im not sure if restarting MySQL instead
  works.  After Apache is restarted, the mysql processes are down to
  3 and everybody's happy again.
 
  I have been trying for months to figure out what is happening and
  how to fix it.  I had heard at one point that there was a problem
  with Redhat 5.2 kernel that caused a similar problem, but I
  upgraded that but no joy.
 
  Temporarily I have built a kluge cron job that restarts apache
  every so often, which worked as long as the server was low volume.
  But now usage is dramatically increasing due to some new web sites
  that have been installed and announced to the entire corporation.
  So the problem is triggered before the restart cleans up the mess.
  I can't have it restarting every 20 minutes.
 
  I've also changed every instance of pconnect() to connect() where I
  can, but no difference.
 
  Can anybody tell me anything useful?  I'm supposed to come back
  with a firm fixit schedule tomorrow morning, so please email me
  directly as well as on the list - I'm afraid I'll miss it in the
  volume on the list. If I don't get this fixed very shortly my
  consulting contract with this company will no doubt begin to fade
  out!!
 
  Thanks in advance,
  Gary Bickford
 
 
  ---
 -- Before posting, please check:
 http://www.mysql.com/manual.php   (the manual)
 http://lists.mysql.com/   (the list archive)
 
  To request this thread, e-mail [EMAIL PROTECTED]
  To unsubscribe, e-mail
  [EMAIL PROTECTED] Trouble
  unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

-
Before posting, please check:
http://www.mysql.com/manual.php   (the manual)
http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php


-
Scott Baker - Webster Internet - Network Technician
503.266.8253 - [EMAIL PROTECTED]

By working faithfully eight hours a day you may eventually get to be boss 
and work twelve hours a day. - Robert Frost, 1874 - 1963











-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Apache/PHP/MySQL - processes multiply until about 30, then doom

2001-05-01 Thread Gary E Bickford

I am running MySQL (3.23.27 at this point) with Apache1.3.12 and PHP3 on 
a PC running Redhat 6.0.  My problem has survived upgrades of all 
components from earlier versions.

Every PHP page has at least one query to a MySQL database for session 
tracking (home-rolled code, not PHPLib or anything off the shelf)  There 
are also on some pages other queries, to a different database, same 
server (same mysql).  Most of the latter are Phorum queries.

Periodically the number of mysql instances that show up in 'ps auxww'1 
gets to about 30 and mysql no longer listens to PHP/Apache.  However I 
can still use the mysql shell with no problem, so MySQL is still running 
but can't hear anything from PHP.

The only way to fix it is to run 'apachectl restart' or equivalent. 
'graceful' doesn't do it.  Im not sure if restarting MySQL instead 
works.  After Apache is restarted, the mysql processes are down to 3 and 
everybody's happy again.

I have been trying for months to figure out what is happening and how to 
fix it.  I had heard at one point that there was a problem with Redhat 
5.2 kernel that caused a similar problem, but I upgraded that but no joy.

Temporarily I have built a kluge cron job that restarts apache every so 
often, which worked as long as the server was low volume.  But now usage 
is dramatically increasing due to some new web sites that have been 
installed and announced to the entire corporation.  So the problem is 
triggered before the restart cleans up the mess.  I can't have it 
restarting every 20 minutes.

I've also changed every instance of pconnect() to connect() where I can, 
but no difference.

Can anybody tell me anything useful?  I'm supposed to come back with a 
firm fixit schedule tomorrow morning, so please email me directly as 
well as on the list - I'm afraid I'll miss it in the volume on the list. 
  If I don't get this fixed very shortly my consulting contract with 
this company will no doubt begin to fade out!!

Thanks in advance,
Gary Bickford


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php