From time to time I have had my site lock up with a MySQL error "Too many connections".

The site is not particularly busy and it seems odd that these issues suddenly started quite recently.

My hosting company indicates that every time a logged in user hits any node an update query like the one below runs:

UPDATE history SET timestamp=12934838097 WHERE uid=1 and nid=9

They say that this update takes a long time and other queries reading from that table then get hung up. These queries queue up, forming too many connections.

I have no custom code so am wondering what is causing these updates. I have absolutely no reason to track when each user hit each page and will happily turn it off IF I can find it!

Thanks for any tips on where to look.

Comments

gbrands’s picture

I think it might be the 'database logging' module found in core.

paulcoghlan’s picture

Many thanks, I have disabled this and will monitor...