Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 5 May 2010 01:43:44 -0300 (ADT)
From:      "Marc G. Fournier" <scrappy@hub.org>
To:        Fbsd1 <fbsd1@a1poweruser.com>
Cc:        "questions@freebsd.org" <questions@freebsd.org>
Subject:   Re: Addition to BSDstats
Message-ID:  <alpine.BSF.2.00.1005050138530.85296@hub.org>
In-Reply-To: <4BE0E8B1.3000802@a1poweruser.com>
References:  <4BE03042.5010806@ipv6canada.com> <4BE0A341.1010207@a1poweruser.com> <alpine.BSF.2.00.1005042107170.85296@hub.org> <alpine.BSF.2.00.1005042135120.85296@hub.org> <4BE0E8B1.3000802@a1poweruser.com>

next in thread | previous in thread | raw e-mail | index | archive | help

can you tell me two things:

nslookup rpt.bsdstats.org

and the contents of /var/db/bsdstats

the results should have showed up instantly on the web site ... but, just 
checking the database, I do find a connection from PH  today at 2010-05-05 
03:30:12.196478 ... and the country stats does show it:

#47  	PH Philippines	 	 	1	 	 	 	2 
3

Even on the FreeBSD specific screen:

#55  	PH Philippines	1	0.03 %

If you can send me the output of /var/db/bsdstats though,I can confirm 
that it is, in fact, your host that reported ...

On Wed, 5 May 2010, Fbsd1 wrote:

> Marc G. Fournier wrote:
>> On Tue, 4 May 2010, Marc G. Fournier wrote:
>> 
>> Don't worry about it, found and fixed that bug ... it had to do with trying 
>> to masquarade behind haproxy, so it looked like all systems were coming in 
>> from Panama if they were running the newest code ... which means alot of 
>> ppl out there were running *old* code ...
>> 
>> Basically, by setting up haproxy to load balance, all IPs hitting the 
>> backend were, as mentioned before, masquaraded ... but, of course, that 
>> means that when Geo::IP trying to determine country of origin, it always 
>> reports for the country of origin of the haproxy IP (Panama) ...
>> 
>> I've fixed this ... still not recording IP, but at least the PHP script 
>> determing country basis it on the proper IP, not the haproxy IP ...
>> 
>> No changes required on the client side, as things will normalize over the 
>> course of the next month as ppl report in ...
>> 
>> If anyone on FreeBSD wishes to 'force an update':
>>
>>   /usr/local/etc/periodic/monthly/300.statistics -nodelay
>> 
>> will push it through ...
>> 
>> 
>> 
>> 
> Just did pkg_add -r bsdstats followed by
> /usr/local/etc/periodic/monthly/300.statistics -nodelay
>
> Still don't see any Freebsd systems listed for the Philippines on the 
> website.
>
> What is YOUR definition of REAL-TIME.
>

----
Marc G. Fournier                        Hub.Org Hosting Solutions S.A.
scrappy@hub.org                                     http://www.hub.org

Yahoo:yscrappy    Skype: hub.org    ICQ:7615664    MSN:scrappy@hub.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1005050138530.85296>