I'm still trying to find a solution to this issue and I am running out
of ideas. When I do a show processlist; I get a bunch of the following
connections.
| 223 | rduser | rdmusic:51230 | Rivendell | Query | 7 |
Waiting for table level lock | delete from STACK_SCHED_CODES where
STACK_LINES_ID=116264 | 0.000 |
| 235 | rduser | rd-master1:56636 | Rivendell | Query | 5 |
Waiting for table level lock | delete from STACK_SCHED_CODES where
STACK_LINES_ID=90376 | 0.000 |
| 253 | rduser | rdmusic:51264 | Rivendell | Query | 3 |
Waiting for table level lock | delete from STACK_SCHED_CODES where
STACK_LINES_ID=77455 | 0.000 |
| 265 | rduser | rdproduction2:56130 | Rivendell | Query | 1 |
Waiting for table level lock | delete from STACK_SCHED_CODES where
STACK_LINES_ID=70139 | 0.000 |
| 275 | rduser | rdproduction1:49354 | Rivendell | Query | 7 |
Waiting for table level lock | delete from STACK_SCHED_CODES where
STACK_LINES_ID=63939 | 0.000 |
| 286 | rduser | rd-master1:56686 | Rivendell | Query | 8 |
Waiting for table level lock | delete from STACK_SCHED_CODES where
STACK_LINES_ID=59351 | 0.000 |
| 294 | rduser | rdproduction1:49770 | Rivendell | Query | 2 |
Waiting for table level lock | delete from STACK_SCHED_CODES where
STACK_LINES_ID=55784 | 0.000 |
| 308 | rduser | rdproduction2:57262 | Rivendell | Query | 5 |
Waiting for table level lock | delete from STACK_SCHED_CODES where
STACK_LINES_ID=52225 | 0.000 |
| 325 | rduser | rd-master1:56732 | Rivendell | Query | 8 |
Waiting for table level lock | delete from STACK_SCHED_CODES where
STACK_LINES_ID=49433 | 0.000 |
The number of these connections keeps increasing every day until I hit
the maximum number of connections and then I have to reboot all
machines. I have tried killing them, but they just come back instantly
with another process ID. Rebooting a client will kill the connections
from that client, but they will continue to slowly increase again. Can
anyone please point me in the right direction as to what may be causing
this?
Thanks
On 2019-09-18 6:15 p.m., Jamie Dominey wrote:
Hi,
I have developed an issue since upgrading to v3. Basically what is
happening is that the number of current database connections keeps
increasing until it hits the maximum connections, and any currently
open Rivendell programs will keep running, but nothing new will open
until a currently running program is closed or everything is
restarted. It takes 4 or 5 days from a restart to hit the maximum
which I believe is 151.
I tried a second server, but that didn't make a difference. Ran the
database check which fixed a few problems, but didn't solve the issue.
Nothing has changed other that the update which I did using the posted
method. This is on CentOS 7 and everything was installed using the
scripts.
This is what I am currently seeing and 3 of the machines currently
have no open Rivendell applications. The number climbs by about 30
connections a day.
[rd@rdserver ~]$ mysql -NBe 'show global status like
"Threads_connected";' | cut -f2
95
[rd@rdserver ~]$ mysql -u root -p -e"show processlist;"|awk '{print
$3}'|awk -F":" '{print $1}'|sort|uniq -c
Enter password:
1 Host
22 localhost
15 rd-master1
20 rdmusic
18 rdproduction1
20 rdproduction2
[rd@rdserver ~]$
Any help would be greatly appreciated.
Thanks
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
