Author Topic: Supervisor Crash  (Read 2960 times)

rhagen

  • Full Member
  • ***
  • Posts: 18
Supervisor Crash
« on: December 20, 2010, 06:13:53 PM »
Had a supervisor crash requiring a reboot. The two errors I've found so far are  
1) MySQL "cant open and lock privilege tables".
2) Supervisor logs show a recurring  "ERROR: caught exception in child. "

Rebooting brought the supervisor back online and its been running well since then. Neither error have manifested again since the reboot.

Wondering if there are any hints or tips on how I can prevent this from happening again? How do I parse these errors?
« Last Edit: December 20, 2010, 07:37:20 PM by rhagen »

shinya

  • Administrator
  • *****
  • Posts: 231
Re: Supervisor Crash
« Reply #1 on: December 22, 2010, 12:03:12 AM »
Hi rhagen,

What is your supervisor platform (OS), and your supervisor version (output from "qbping" on a command line)?

Please email support@pipelinefx.com the above info, along with your mysqld error log file and supelog (both zipped). Please also mention this forum thread.

Thanks!
-shinya.