Return-Path: X-Original-To: apmail-openjpa-users-archive@minotaur.apache.org Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AB1B1E1A6 for ; Fri, 14 Dec 2012 07:52:55 +0000 (UTC) Received: (qmail 22387 invoked by uid 500); 14 Dec 2012 07:52:55 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 22350 invoked by uid 500); 14 Dec 2012 07:52:54 -0000 Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@openjpa.apache.org Delivered-To: mailing list users@openjpa.apache.org Received: (qmail 22296 invoked by uid 99); 14 Dec 2012 07:52:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Dec 2012 07:52:53 +0000 X-ASF-Spam-Status: No, hits=0.3 required=5.0 tests=FREEMAIL_REPLY,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of alcarola@gmail.com designates 209.85.217.174 as permitted sender) Received: from [209.85.217.174] (HELO mail-lb0-f174.google.com) (209.85.217.174) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Dec 2012 07:52:46 +0000 Received: by mail-lb0-f174.google.com with SMTP id gi11so2629826lbb.33 for ; Thu, 13 Dec 2012 23:52:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=/RLROGXRxCAumE08lvoshpv9scQmryVLDeBSkSHxNt0=; b=irpNlFj9l8Euo3FKdL/FMHtiVJx8ZTJTv9Cy0ht6jjbhFJPfY+Oc9KJkaXvulHCLGm 9cCrUrp4hcgOd1r6mETK1m6MNb9dab876lrKuGDqvYLn0fYjLS8crANThRnI3eHNM+71 BrpFj/N7rvuYXvLpmAeQyVPCq+nnYyelZAQEDzpA5G6XSoIXSb4zHRu5WJAmYN9GKx6e WrDXXstH+41Tlp6K/+UTe/B/x7Qg3n/19MwfrVFv4h7lriFFxlPoevsfhS3iq7qDN0TJ QICYG3AJtYi018GGa80sgGdIXbT49AZVgxFMQgZt4tzPPxtKN5Ck+ndHNXcwuHXilLWq pRSw== Received: by 10.152.124.83 with SMTP id mg19mr1766623lab.6.1355471545694; Thu, 13 Dec 2012 23:52:25 -0800 (PST) Received: from aa-eduroam-148-023.abo.fi (aa-eduroam-148-023.abo.fi. [130.232.148.23]) by mx.google.com with ESMTPS id ne2sm1476379lab.10.2012.12.13.23.52.23 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Dec 2012 23:52:24 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1085) Subject: Re: MySQL timeouts? From: Mikael Kurula In-Reply-To: Date: Fri, 14 Dec 2012 09:52:22 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: users@openjpa.apache.org X-Mailer: Apple Mail (2.1085) X-Virus-Checked: Checked by ClamAV on apache.org Hi! Thanks for the suggestion. I didn't manage to get the time stamps in = (I'm a mathematician, not a sysadmin) and I find it unlikely the server = has gone down. MySQL is on the same server as OpenMeetings and AFAIK we = have nagios watchdogging it, probably also with ping. Friendly greetings, Mikael On 2012.14.12, at 06:45, seba.wagner@gmail.com wrote: > Yes that is what I meant Mikael. >=20 > In the server on demo.openmeetings.de those config variables are = exactly > the same: > mysql> SHOW GLOBAL VARIABLES LIKE "wait_timeout"; > +---------------+-------+ > | Variable_name | Value | > +---------------+-------+ > | wait_timeout | 28800 | > +---------------+-------+ > 1 row in set (0.00 sec) >=20 > mysql> SHOW VARIABLES LIKE "wait_timeout"; > +---------------+-------+ > | Variable_name | Value | > +---------------+-------+ > | wait_timeout | 28800 | > +---------------+-------+ > 1 row in set (0.01 sec) >=20 > mysql> >=20 >=20 > Another reason might be that the host in general is not available. >=20 > You could for example test this by doing a (nasty) small ping script = that > runs "demon-like". >=20 > For example: > nohup ping -c 100000000000000 web.de & >=20 > it will write all ping results to a file called nohup.out. > And you can check the output in real-time using: > tail -f nohup.out >=20 > with some more "shell kung-fu" I guess you could also add the date = part in > front of every ping result. >=20 > Then you let run the script overnight. >=20 > And tomorrow morning when you see in your openmeetings log file =3D> = there > was a db connection lost, you see in the openmeetings log what time = exactly > the connection lost was >=20 > And then you check the output of your ping protocol in the nohup.out = if > there was any host issue (especially around that date/time of course). >=20 > Sebastian >=20 >=20 > 2012/12/13 Mikael Kurula >=20 >> 2880 >=20 >=20 >=20 >=20 > --=20 > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > seba.wagner@gmail.com