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

Header Data

From: christopher <me***e@pc-networking-services.com>
Message Hash: 1ae449312a4e63a65fd617868df021458f1b10b5126c1d117b13814b0c23a2a7
Message ID: <fbcb5efe-8326-4a53-92a1-c9aeae778c9e@grasehotspot.org>
Reply To: <c31f061a-2719-45d4-8733-80c67ad60e3e@grasehotspot.org>
UTC Datetime: 2019-08-13 02:21:55 UTC
Raw Date: Tue, 13 Aug 2019 02:21:55 -0700

Raw message 

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
>>>>
>>>>

Thread