> > Please set log_warnings at 2 if you want the warnings for connection > aborted due to errors or timeout. >
ok done > > What is your wait_timeout server option set to? If it's too low and the > connection is idle, it will be closed by the server. But generally, the > application should properly handle the loss of connection. I think it is the default wait_timeout | 28800 > > > I added log_warnings = 9 > > and see a lot of these : > > mysqld: 2023-11-13 13:53:34 438 [Warning] Aborted connection 438 to > db: 'xxxxx' user: 'xxxx' host: 'xxxxx' (CLOSE_CONNECTION) > > Why is this a warning? This is already generated by simple > mysqli_connect with mysqli_close. > > > > > how to debug this? > > > > > > > > Ever since I switched from the default included centos mariadb to > your > > > repo. The web applications are getting ~1 once a week connection > refused > > or > > > so. I have already scheduled a cron job to restart your server. > But still > > > that is not enough. > > > > > > In the previous 10 years or so I never had such issue nor do I > have such > > > issues with postgresql. > > > > > > Nothing is in the log file, only the restart. Should such things > not be > > > logged by default? How to configure that issues resulting in > refusing > > > access or being unable to give access are logged? > > > > > > > > > > _______________________________________________ > > discuss mailing list -- [email protected] > <mailto:[email protected]> > > To unsubscribe send an email to [email protected] > <mailto:[email protected]> > _______________________________________________ > discuss mailing list -- [email protected] > <mailto:[email protected]> > To unsubscribe send an email to [email protected] > <mailto:[email protected]> > _______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
