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

Header Data

From: honeybadger <re***r@gmail.com>
Message Hash: 3c2e362bc180ecd2e35341ef59947ebb4d3e0bff3b8e32910ed9c3eac645a676
Message ID: <836b02a5-2613-440c-a4dc-c6e3c5d0a416@grasehotspot.org>
Reply To: <2fdc6ce3-3890-409c-8f6c-fe8669a8fbf6@grasehotspot.org>
UTC Datetime: 2019-08-12 13:38:09 UTC
Raw Date: Mon, 12 Aug 2019 13:38:09 -0700

Raw message 

I ran sudo mysqlcheck --defaults-file=/etc/mysql/debian.cnf --auto-repair 
--optimize --all-databases

It did not change anything, I think my only option is to export the groups 
and import it into a new database

On Monday, August 12, 2019 at 10:20:17 PM UTC+2, honeybadger wrote:
>
> Thank you so much for your reply, I installed phpmyadmin loged into the 
> server and backed up radius and radmin. I reloaded the entire server from 
> scratch installed grase hotspost and tested, it worked great after which I 
> dropt the default database and imported the backup.
>
> The Coovachillie is matching config is no more red pening reload however 
> the old problem of the user not being able to login is still there.
>
> If I type user name and password it says "Attemping Login" and goes back 
> to the log in screen with no error.
>
> I assume that mysql databases have been corrupted.
>
>
>
> On Monday, August 12, 2019 at 8:39:25 PM UTC+2, christopher wrote:
>>
>>  Hello, 
>>  
>> I suggest that you ssh into the server if you are able to do so remotely, 
>> and go into /var/run and see if there is a chilli.eth3.pid file in there 
>> and delete it.  Of course your eth number *may* be different, but this is 
>> the "run" number for coova chili, and deleting it will make no difference.  
>> Hello,
>>  
>> I suggest that you ssh into the server if you are able to do so remotely, 
>> and go into /var/run and see if there is a chilli.eth3.pid file in there 
>> and delete it.  Of course your eth number *may* be different, but this is 
>> the "run" number for coova chili, and deleting it will make no difference.
>>  
>> The only other thing I can think of, is that somehow or other, during the 
>> unexpected shutdown due to lack of power, there is the possibility that the 
>> mysql database has become corrupted. 
>>  
>> You will need to use mysqlcheck to see if the database itself needs to be 
>> repaired.
>>  
>> Make sure that when deleting the .pid file, that you do so as root.  If 
>> on Ubuntu itself, you will need to do sudo rm -rf chilli.ethx.pid, where 
>> "x" is the number of the network card.
>>  
>> Regards,
>>  
>> Christopher.
>>  
>> The only other thing I can think of, is that somehow or other, during the 
>> unexpected shutdown due to lack of power, there is the possibility that the 
>> mysql database has become corrupted. 
>>  
>> You will need to use mysqlcheck to see if the database itself needs to be 
>> repaired.
>>  
>> Make sure that when deleting the .pid file, that you do so as root.  If 
>> on Ubuntu itself, you will need to do sudo rm -rf chilli.ethx.pid, where 
>> "x" is the number of the network card.
>>  
>> Regards,
>>  
>> Christopher.
>>
>> On Tuesday, 13 August 2019 05:47:05 UTC+12, honeybadger wrote:
>>>
>>> Thank you daniel I am no linux guru either hope to be some day, anyway a 
>>> hard reboot did not work in fact the client tried it a few times.
>>>
>>> On Monday, August 12, 2019 at 12:33:58 AM UTC+2, Daniel Crusoe wrote:
>>>>
>>>> Hey,
>>>>
>>>>  
>>>>
>>>> I also found I had this problem, and doing a reboot the proper way 
>>>> (logging in to my server and doing a “sudo shutdown –r now” or “sudo 
>>>> reboot” ) didn’t fix the problem, what I found fixed the problem was doing 
>>>> a hard reboot (literally switch it off and back on again or just yank the 
>>>> power and plug it back in) after doing this, the system started up 
>>>> perfectly fine
>>>>
>>>>  
>>>>
>>>> Daniel Crusoe
>>>>
>>>>  
>>>>
>>>> (P.S. I am in no way a Linux guru, I tried the Coova-Chilli software 
>>>> reboot too and it didn’t work, the hard “die now” approach seems to fix 
>>>> most of my problems)  
>>>>
>>>>  
>>>>
>>>> *From:* honeybadger [mailto:re***.@gmail.com] 
>>>> *Sent:* Friday, 09 August 2019 5:08 PM
>>>> *To:* Grase Hotspot <gr***.@grasehotspot.org>
>>>> *Subject:* Re: [GRASE-Hotspot] coovachilli stuck at pending reload, 
>>>> vouchers do not log in no error message
>>>>
>>>>  
>>>>
>>>> Hi Tim,
>>>>
>>>>  
>>>>
>>>> Thank you for your reply and amazing product.
>>>>
>>>>  
>>>>
>>>> I have rebooted the server on many occasions I have also restarted the 
>>>> coova-chilli service. It just is stays at
>>>>
>>>>    - *Changes pending Coova Chilli Reload*
>>>>
>>>>
>>>> On Friday, August 9, 2019 at 12:45:07 PM UTC+2, timwhite88 wrote:
>>>>
>>>> Have you tried rebooting it again? Also try restarting the coova-chilli 
>>>> service.
>>>>
>>>>  
>>>>
>>>> Regards
>>>>
>>>>  
>>>>
>>>> Tim
>>>>
>>>>  
>>>>
>>>> On Fri, 9 Aug 2019 at 20:10, honeybadger <re***.@gmail.com> wrote:
>>>>
>>>> Hi after a power failure users are unable to login in, after typing the 
>>>> Voucher user name and password it goes to attempting to login and just 
>>>> jumps back to the login in screen with no errors. Also I noticed that Coova 
>>>> Chilli is stuck at Changes pending reload.
>>>>
>>>>  
>>>>
>>>> I hope someone can help?
>>>>
>>>> -- 
>>>> 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***.@grasehotspot.org.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/23874de0-0fe3-4bfd-b72b-4e66b0750e91%40grasehotspot.org 
>>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/23874de0-0fe3-4bfd-b72b-4e66b0750e91%40grasehotspot.org?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>> -- 
>>>> 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***.@grasehotspot.org.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/6dd4c471-46a7-43a9-8fb1-6cba7c623e91%40grasehotspot.org 
>>>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/6dd4c471-46a7-43a9-8fb1-6cba7c623e91%40grasehotspot.org?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>

Thread