2019-08-13 - Re: [GRASE-Hotspot] coovachilli stuck at pending reload, vouchers do not log in no error message

Header Data

From: Tim <ti***8@gmail.com>
Message Hash: 9810ec0b3eb01b1735530f1bcd898c98fbcd058f2c8864be59897a7b1ae7f57e
Message ID: <CAESLx0Ke8-az_gxrnYcnwp5ZtrXzvyD6fa1+vU6CE6R7tcynAQ@mail.gmail.com>
Reply To: <304e6350-6187-4c2f-a136-385bfd55de7b@grasehotspot.org>
UTC Datetime: 2019-08-13 18:02:34 UTC
Raw Date: Wed, 14 Aug 2019 11:02:34 +1000

Raw message 

For future reference. There are automatic nightly backups in
/var/backups/grase/ which may help you restore the database to a working
version (if you've not already reinstalled the OS).

Regards

Tim

On Tue, 13 Aug 2019 at 19:54, honeybadger <re***r@gmail.com> wrote:

> I agree I am doing a clean install even the os its just safer that way, I
> am using grase at a hotel it takes heavy punishment but has worked without
> issues for 3 years.
>
> On Tuesday, August 13, 2019 at 11:21:55 AM UTC+2, christopher wrote:
>>
>> Hello,
>>
>> I would suggest that you import nothing from the backup, as this backup
>> really was taken at the wrong time.  The backups need to be taken after all
>> the groups/users/passwords etc have been added, and BEFORE end users are
>> allowed to use it.
>>
>> I know that is a pain, but a fresh clean install is going to be the best
>> approach.
>>
>> I have no idea why this happened, as I have had grase installed since
>> 2016, and have had a number of power cuts and have never had an issue.  The
>> setup I have here, is that the server is being used by backpackers, and it
>> gets really heavy use.
>>
>> Regards,
>>
>> Christopher.
>>
>> On Tuesday, 13 August 2019 21:14:37 UTC+12, honeybadger wrote:
>>>
>>> Christopher I really appreciate your help, but that did not work either,
>>> I am going to reload grase hotspot since I did mess around alot and then
>>> just import the groups settings and recreate the users. I have run out of
>>> time.
>>>
>>> But again I appreciate your time and effort
>>>
>>> On Tuesday, August 13, 2019 at 10:42:25 AM UTC+2, christopher wrote:
>>>>
>>>> Hello,
>>>>
>>>> I have found another link, that may also help:
>>>>
>>>>
>>>> https://www.rosehosting.com/blog/optimizing-and-repairing-mysql-databases-with-mysqlcheck/
>>>>
>>>> Take a look at option number 3.
>>>>
>>>> Regards,
>>>>
>>>> Christopher.
>>>>
>>>> On Tuesday, 13 August 2019 20:18:21 UTC+12, christopher wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> It is now getting close to the point where you are going to have to
>>>>> call it quits, and start from scratch by re-adding all usernames and
>>>>> passwords again.  I would suggest first though, that you try the steps
>>>>> outlined here:
>>>>>
>>>>>
>>>>> https://severalnines.com/blog/my-mysql-database-corrupted-what-do-i-do-now
>>>>>
>>>>> It has some things to try, but if that fails, you can literally waste
>>>>> months trying to sort things out.
>>>>>
>>>>> There is a possibility that the actual hard drive itself has been
>>>>> damaged.  If power goes off and on very quickly, then a spike can occur and
>>>>> then corruption happens.
>>>>>
>>>>> Please make sure that you are doing these repair attempts on the
>>>>> command line from the shell WITHOUT using phpmyadmin.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Christopher.
>>>>>
>>>>> On Tuesday, 13 August 2019 19:15:38 UTC+12, honeybadger wrote:
>>>>>>
>>>>>> I used the mysqlcheck -r radmin and radius command with radius it
>>>>>> just gave an ok to everything and with radmin it said the storage engine
>>>>>> for the table does not support repair
>>>>>>
>>>>>>
>>>>>> On Tuesday, August 13, 2019 at 8:38:36 AM UTC+2, honeybadger wrote:
>>>>>>>
>>>>>>> I am new to this so not quite sure how to check for corrupt table
>>>>>>> and how to fix. Maybe can you help with a view hints or links. Thank you
>>>>>>
>>>>>> --
> This mailing list is for the Grase Hotspot Project http://grasehotspot.org
> ---
> You received this message because you are subscribed to the Google Groups
> "Grase Hotspot" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gr***e@grasehotspot.org.
> To view this discussion on the web visit
> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/304e6350-6187-4c2f-a136-385bfd55de7b%40grasehotspot.org
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/304e6350-6187-4c2f-a136-385bfd55de7b%40grasehotspot.org?utm_medium=email&utm_source=footer>
> .
>

Thread