On Jul 27, 2015, at 11:06 AM, Michal Tomaszewski <Michal.Tomaszewski@cca.pl> wrote:
When database is going down server hangs on first processed request and stops processing any further requests. There is no connection timeout nor any other timeout to database request.
That may happen, especially when the client library for the back-end database locks.
Yes, but there was a timeout and process was not locked indefinitely. Other requests were processed properly. In 3.0.9 it hangs all the processing.
In freeradius 2.x when database was not available server responded with Reject until database was on. In freeradius 3.0.9 server stops responding to any requests, even when database comes up.
Hmm... that's bad.
Fri Jul 24 17:44:34 2015 : Debug: rlm_redis (redis): Reconnecting (3)
Fri Jul 24 17:44:34 2015 : Error: rlm_redis (redis): Problems with redisConnect('10.113.13.245', 6379), Connection refused
That's the problem code. It's something Arran changed recently...
I've made the same test when sql server is down: Mon Jul 27 17:25:02 2015 : Debug: (2) sql: Executing select query: SELECT id, username, attribute, value, op FROM radius_radcheck WHERE username = 'test8' AND (hotspot_id is null OR hotspot_id = '0' ) ORDER BY id Mon Jul 27 17:25:02 2015 : Debug: rlm_sql_mysql: Socket destructor called, closing socket Mon Jul 27 17:25:02 2015 : Debug: rlm_sql (sql): Reconnecting (0) Mon Jul 27 17:25:02 2015 : Debug: rlm_sql_mysql: Starting connect to MySQL server Mon Jul 27 17:25:02 2015 : Error: rlm_sql_mysql: Couldn't connect to MySQL server stage-user@127.0.0.1:stage_main Mon Jul 27 17:25:02 2015 : Error: rlm_sql_mysql: MySQL error: Can't connect to MySQL server on '127.0.0.1' (111) Mon Jul 27 17:25:02 2015 : Debug: rlm_sql_mysql: Socket destructor called, closing socket And from this point freeradius is not processing any further requests nor there are no any further information on debug screen. Radclient has a timeout: no response from server for ID XXX socket N In freeradius 2.x the processing ended with the message SQL_DOWN following by an access-reject and server did not hang. ________________________________________ Uwaga: Treść niniejszej wiadomości może być poufna i objęta zakazem jej ujawniania. Jeśli czytelnik tej wiadomości nie jest jej zamierzonym adresatem, pracownikiem lub pośrednikiem upoważnionym do jej przekazania adresatowi, informujemy że wszelkie rozprowadzanie, rozpowszechnianie lub powielanie niniejszej wiadomości jest zabronione. Jeśli otrzymałeś tę wiadomość omyłkowo, proszę bezzwłocznie odesłać ją nadawcy, a samą wiadomość usunąć z komputera. Dziękujemy. ________________________________ Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.If you have received this communication in error, please notify the sender immediately by replying to the message and deleting it from your computer. Thank you. ________________________________