2013-10-29 - Re: [GRASE-Hotspot] Radacct crashed
Header Data
From: Timothy White <ti***8@gmail.com>
Message Hash: 104d0b1899fd86db6a79a6e223071ad2693b9f9caae3471565a77b7661e05d69
Message ID: <CAESLx0+X1vtEvrpQzQm_5849eQecq2MWPN+o+rDu=mUtptOanw@mail.gmail.com>
Reply To: <51DF015F.2060200@radez.hr>
UTC Datetime: 2013-10-29 22:58:36 UTC
Raw Date: Wed, 30 Oct 2013 15:58:36 +1000
Raw message
Interesting.
One of the keys is just a key, the other is a unique key. Having both won't
hurt. I believe what must have happened is initially just the key was
there, but then I wanted the unique constraint, and so added it. I don't
think it should have ever had both keys, but it's not hurting it.
I believe it's been in the database code since the first BZR commit, so it
dates back a long way.
Tim
On Fri, Jul 12, 2013 at 5:02 AM, Drazen <dr***a@radez.hr> wrote:
> Just when decided to put new server in production, discovered that
> radacct crashed. Couldnt open "users" or "sessions" pages.
> This is Admin log:
> "FATAL: Get All User radacct details Query failed: [mdb2_error:
> message="MDB2 Error: unknown error" code=-1 mode=return level=notice
> prefix="" info="_doQuery: [Error message: Could not execute statement]
> [Last executed query: SELECT UserName,
> SUM(radacct.AcctInputOctets)+SUM(radacct.AcctOutputOctets) AS
> AcctTotalOctets, SUM(AcctSessionTime) AS AcctSessionTime, MAX(AcctStopTime)
> AS LastLogout FROM radacct GROUP BY UserName] [Native code: 1194] [Native
> message: *Table 'radacct' is marked as crashed and should be repaired*]
> "]"
>
> Then I had to install phpmyadmin, and saw that 'radacct' table was marked
> "crashed" and reparation needed.
> Funy thing what I discover there was two keys in radacct table:
> AcctUniqueId and AcctUniqueId_2, both indexed on AcctUniqueId collumn
> 'unique'.
> Even phpMyAdmin recomends to remove one key.
>
> After repairing table, 'Users' and 'Sessions' pages worked normally, but
> double key still exist there.
> Have no clue how that happened and should I delete one key?
>
> Regards
> Drazen
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Grase-hotspot mailing list
> Gr***t@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/grase-hotspot
>
>
Thread
- Return to July 2013
- Return to October 2013
- Return to November 2013
-
Return to December 2013
- Return to “jb <be***s@yahoo.com>”
- Return to “Drazen <dr***a@radez.hr>”
-
Return to “Timothy White <ti***8@gmail.com>”
- 2013-07-11 (Thu, 11 Jul 2013 21:02:55 +0200) - [GRASE-Hotspot] Radacct crashed - Drazen <dr***a@radez.hr>
- 2013-10-29 (Wed, 30 Oct 2013 15:58:36 +1000) - Re: [GRASE-Hotspot] Radacct crashed - Timothy White <ti***8@gmail.com>
- 2013-11-25 (Mon, 25 Nov 2013 17:00:06 -0800) - Re: [GRASE-Hotspot] Radacct crashed - jb <be***s@yahoo.com>
- 2013-11-27 (Wed, 27 Nov 2013 18:30:21 +1000) - Re: [GRASE-Hotspot] Radacct crashed - Timothy White <ti***8@gmail.com>
- 2013-11-27 (Wed, 27 Nov 2013 00:33:00 -0800) - Re: [GRASE-Hotspot] Radacct crashed - jb <be***s@yahoo.com>
- 2013-12-07 (Sun, 08 Dec 2013 16:19:15 +1000) - Re: [GRASE-Hotspot] Radacct crashed - Timothy White <ti***8@gmail.com>
- 2013-11-27 (Wed, 27 Nov 2013 00:33:00 -0800) - Re: [GRASE-Hotspot] Radacct crashed - jb <be***s@yahoo.com>
- 2013-11-27 (Wed, 27 Nov 2013 18:30:21 +1000) - Re: [GRASE-Hotspot] Radacct crashed - Timothy White <ti***8@gmail.com>
- 2013-11-25 (Mon, 25 Nov 2013 17:00:06 -0800) - Re: [GRASE-Hotspot] Radacct crashed - jb <be***s@yahoo.com>
- 2013-10-29 (Wed, 30 Oct 2013 15:58:36 +1000) - Re: [GRASE-Hotspot] Radacct crashed - Timothy White <ti***8@gmail.com>