2019-08-12 - 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: 96a3051ad5bf4c3766bb3df262e7d51ba4fcd30eb603cd1b46ce0adbb7fc2f86
Message ID: <4b433ff0-40b0-4552-83a6-77c122aabcd0@grasehotspot.org>
Reply To: <ba3ab7b3-7205-4053-a56e-fb0896f98c54@grasehotspot.org>
UTC Datetime: 2019-08-12 11:39:25 UTC
Raw Date: Mon, 12 Aug 2019 11:39:25 -0700

Raw message 

 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