> [2011/07/01-09:51:35 - 29593] [CBPOLICYD] WARNING: Failed to connect
> to database: Error connecting to database: Can't connect to loc
>
> al MySQL server through socket '/var/lib/mysql/mysql.sock' (2) (29593)
>
> [2011/07/01-09:51:35 - 29420] [CBPOLICYD] WARNING: Client in BYPASS
> mode due to DB connection failure!
>
> [2011/07/01-09:51:35 - 29420] [CBPOLICYD] NOTICE: Client still in
> BYPASS mode, 20s left till next reconnect
>
> [2011/07/01-09:51:35 - 29625] [CBPOLICYD] WARNING: Failed to connect
> to database: Error connecting to database: Can't connect to loc
>
> al MySQL server through socket '/var/lib/mysql/mysql.sock' (2) (29625)
>
> [2011/07/01-09:51:36 - 29418] [CBPOLICYD] WARNING: Client in BYPASS
> mode due to DB connection failure!
>
> [2011/07/01-09:51:36 - 29418] [CBPOLICYD] NOTICE: Client still in
> BYPASS mode, 19s left till next reconnect
>
> [2011/07/01-09:51:36 - 7630] [CORE] NOTICE: 2011/07/01-09:51:36 Server
> closing!
>
> Does anyone know how I can A) avoid this from happening and B) detect
> it so that I can notify myself/restart policyd?
>
====
You can use monit to monitor mysql so if mysql goes down, monit restarts
it and sends you a mail (if configured to do so) with a notification.
====
Hmm, MySQL never stopped running, actually.
To correct this issue all I had to do was restart policyd.
very strange.
-Drew
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users
