2017-01-15 - Re: [GRASE-Hotspot] accessing database and users problem

Header Data

From: George Perlington <ge***e@seeag.com>
Message Hash: 15b130dc005876e83ba69fce13b60fe9138d339b364094ebaa565cf897669513
Message ID: <CAKTB4c-r4pwEPvH6ybV5rz3no8grG7PDv7cbWSgvNcBjL78G4Q@mail.gmail.com>
Reply To: <CAESLx0KdhbxbmvnwfGjxrHPcVgxa4CSYigWo-CpTuER_gDcfTA@mail.gmail.com>
UTC Datetime: 2017-01-15 17:44:27 UTC
Raw Date: Mon, 16 Jan 2017 08:44:27 +0800

Raw message 

Hi Really i wish to hear good news on Ubunutu 16.04 . its really important .

On Sun, Jan 15, 2017 at 7:15 PM, Timothy White <ti***8@gmail.com> wrote:

> Are you using expiry dates on your batches? (The group that the batches
> are created in). Normally, with batches you want expiry's so old users are
> removed.
>
> You can also force the cron runner to remove any user that has used up all
> their time or data (for those with fixed time or data limits).
> Browse to http://graseserveraddress/radmin/grase/cron?deleteoutoftimeusers
> or http://graseserveraddress/radmin/grase/cron?deleteoutofdatausers to
> trigger that.
>
> You could also edit the CronFunctions.class.php file to change deletion of
> expired users to delete as soon as expired, instead of waiting an extra
> month.
>
> I expect with 500 new users each day, yes you'll end up with a very slow
> admin interface. If you could send me the latest backup
> from /var/backups/grase/database/, I'd love to load the database with
> that many users and try to work out how to optimise it. Just make sure you
> send it to me off list.
>
> Regards
>
> Tim
>
>
> On Sun, Jan 15, 2017 at 9:01 PM, nazanin behroozian <
> na***n@gmail.com> wrote:
>
>> Hello All :
>>
>> We have grase installed in a project which have around 500 people stable
>> people connecting everyday, and also around 500 people get daily vouchers
>> access to the hotspot as visitors.
>>
>> I have two problems and will be grateful if anyone helps me.
>>
>> 1- a few days ago my users page in admin panel has stopped working and
>> the browser does not open that page.
>>
>> 2- as I make alot of batch users and there is no option for deleting the
>> batch users group the page becomes a mess. is there a way I can delete them
>> via database, such as connecting to the phpmyadmin or anything ?
>> maybe the users has been overloaded thats why I cannot see my users page
>> anymore ??
>>
>> Thanks for your cooperation
>> regards
>> nazanin
>>
>> --
>> 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 post to this group, send email to gr***t@grasehotspot.org.
>> Visit this group at https://groups.google.com/a/gr
>> asehotspot.org/group/grase-hotspot/.
>> To view this discussion on the web visit https://groups.google.com/a/gr
>> asehotspot.org/d/msgid/grase-hotspot/CAH9wN0or3Wo5ga_ppn6MD
>> 0skGSJa9Cv2vQkaxPogw9eB6PUUgg%40mail.gmail.com
>> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAH9wN0or3Wo5ga_ppn6MD0skGSJa9Cv2vQkaxPogw9eB6PUUgg%40mail.gmail.com?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***e@grasehotspot.org.
> To post to this group, send email to gr***t@grasehotspot.org.
> Visit this group at https://groups.google.com/a/
> grasehotspot.org/group/grase-hotspot/.
> To view this discussion on the web visit https://groups.google.com/a/
> grasehotspot.org/d/msgid/grase-hotspot/CAESLx0KdhbxbmvnwfGjxrHPcVgxa4
> CSYigWo-CpTuER_gDcfTA%40mail.gmail.com
> <https://groups.google.com/a/grasehotspot.org/d/msgid/grase-hotspot/CAESLx0KdhbxbmvnwfGjxrHPcVgxa4CSYigWo-CpTuER_gDcfTA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

Thread