[kronolith] wunderground daily email alert
bennettj at thebennetthome.com
bennettj at thebennetthome.com
Thu Feb 25 03:53:38 UTC 2016
-------- Original message --------From: Michael J Rubinsky <mrubinsk at horde.org> Date: 2/18/2016 12:18 PM (GMT-06:00) To: kronolith at lists.horde.org Subject: Re: [kronolith] wunderground daily email alert
Quoting John H. Bennett III <bennettj at thebennetthome.com>:
> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>
>> Quoting John H. Bennett III <bennettj at thebennetthome.com>:
>>
>>> Quoting "John H. Bennett III" <bennettj at thebennetthome.com>:
>>>
>>>> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>>>>
>>>>> Quoting John H. Bennett III <bennettj at thebennetthome.com>:
>>>>>
>>>>>> Hello all,
>>>>>>
>>>>>> Since upgrading to the latest horde stable versions, I am
>>>>>> getting the below email everyday. I do have the weather
>>>>>> configured to show up on my calendar, and also to show in the
>>>>>> portal. Did something change with the behavior? I am working
>>>>>> on trying to downgrade to the previous version of kronolith and
>>>>>> see if these emails stop.
>>>>>
>>>>>
>>>>> Do you have caching enabled?
>>>>>
>>>>>
>>>>>> I could use some hints on how to downgrade a horde application
>>>>>> using pear.
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Your wunderground API key (my key) exceeded its allotted usage
>>>>>> today by making 12 calls within a minute but the limit is 10.
>>>>>>
>>>>>> We used one of your raindrops instead of disabling the key for
>>>>>> the remainder of the day. You now have 29 remaining raindrops.
>>>>>>
>>>>>> We check usage for 24-hour periods based on U.S. Eastern Time.
>>>>>>
>>>>>> The plan you are registered for is Stratus - Developer,
>>>>>> granting you 500 calls per day with 10 calls per minute limit.
>>>>>> To upgrade your plan go to:
>>>>>> http://www.wunderground.com/weather/api/d/ecb7f558afdd63e3/edit.html
>>>>>>
>>>>>> Details: exceededrate: maxrate: 12 (of 10)
>>>>>> Time: Tue, Feb 09, 2016 00:30 EST
>>>>>>
>>>>>> Thank you,
>>>>>> wunderground.com API Team
>>>>>>
>>>>>> This is an automatically generated email; it cannot be replied
>>>>>> to. For Documentation review read through:
>>>>>> http://www.wunderground.com/weather/api/d/documentation.html
>>>>>> For Developer questions and forms post in our Community here:
>>>>>> http://www.wunderground.com/weather/api/d/community.html
>>>>>> For Technical Support submit a ticket here:
>>>>>> http://wuhelp.wunderground.com/index.php?_m=tickets&_a=submit&step=1&departmentid=32
>>>>>>
>>>>>> --
>>>>>> wunderground.com | 300 Interstate North Parkway, Atlanta, GA 30339
>>>>>>
>>>>>> Thank you,
>>>>>>
>>>>>> John
>>>>>>
>>>>>> --
>>>>>> kronolith mailing list
>>>>>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>>>>>> To unsubscribe, mail: kronolith-unsubscribe at lists.horde.org
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> mike
>>>>> The Horde Project
>>>>> http://www.horde.org
>>>>> https://www.facebook.com/hordeproject
>>>>> https://www.twitter.com/hordeproject
>>>>
>>>>
>>>> Here is what I have for anything with cache:
>>>>
>>>> $conf['session']['cache_limiter'] = 'nocache';
>>>> $conf['share']['cache'] = false;
>>>> $conf['cache']['default_lifetime'] = 1800;
>>>> $conf['cache']['params']['dir'] = '/tmp/';
>>>> $conf['cache']['params']['sub'] = 0;
>>>> $conf['cache']['driver'] = 'File';
>>>> $conf['cache']['use_memorycache'] = '';
>>>> $conf['cachecssparams']['url_version_param'] = true;
>>>> $conf['cachecss'] = false;
>>>> $conf['cachejsparams']['url_version_param'] = true;
>>>> $conf['cachejs'] = false;
>>>> $conf['cachethemes'] = false;
>>>>
>>>>
>>>> I didn't get the message today, so possibly my key had been
>>>> compromised. I'll keep monitoring.
>>>>
>>>> From the other response, I wouldn't try to downgrade my
>>>> production server until I tested it on a test server, and was
>>>> comfortable with the process and results.
>>>>
>>>> Thank you,
>>>>
>>>> John
>>>
>>> Spoke too soon, I am still getting them. Instead of downgrading
>>> Kronolith, I downgraded Horde_Service_Weather to 2.3.1 Thursday
>>> night, and I haven't gotten any more notices. Looking at the
>>> changes, could this change be causing my issues,
>>> https://github.com/horde/horde/commit/22c3705bfe731acfa365a443f813bf676642dac7?
>>
>>
>> No, that commit doesn't cause any request to be sent, it only
>> changes/fixes how information already obtained from wunderground is
>> used.
>>
>> You can place some Horde::debug() statements in
>> Horde_Service_Weather_WeatherUnderground::_makeRequest() to find
>> out exactly what requests are being sent, and why they are not
>> coming from the cache.
>>
>> --
>> mike
>> The Horde Project
>> http://www.horde.org
>> https://www.facebook.com/hordeproject
>> https://www.twitter.com/hordeproject
>
>
> I would like to do what you've asked, to see if it's just an issue
> I'm seeing, or a larger issue, but I need a little more help. In
> Horde/Service/Weather/WeatherUnderground.php, there are 6 lines that
> contain makeRequest. Which ones should I add it to, or am I looking
> at the wrong file? Should it be added above or below the lines?
Do something like this:
Horde::debug($url);
Immediately after the $cachekey = md5(.....) line (line 405 locally).
And then:
Horde::debug('Not cached');
Inside the if statement (after line 408).
The results will be in your temp directory in a file named
horde_debug.txt. It will show every URL that is being requested and
"Not cached" will be shown for those that were actually sent to
wunderground. Depending on your options, you will see something like 2
requests per portal block load and should only see the same url hit
wunderground's API once per cache expire interval.
Note that thinks like auto-completing the location in the portal page
can send quite a number of requests depending on how fast you type and
select the choice.
> No one else has reported seeing the same behavior, but I can't
> believe I'm the only one using this feature.
I use wunderground on my personal install and don't receive any alerts
unless I'm actively testing features when I might change locations
frequently.
> For now, I've switched to WWO, so I can stop violating WU's policy.
> When you let me know how I need to implement the debugging, then I
> will switch back.
>
> Also, I'm up to date on everything, as of today.
>
> Thank you again, and for your patience,
>
> John
>
> --
> kronolith mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: kronolith-unsubscribe at lists.horde.org
--
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject
--
kronolith mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: kronolith-unsubscribe at lists.horde.org
Well, I'm no longer receiving these daily alerts, so I don't know what the issue was, or what caused it.
Thank you again for trying to help me,
John
More information about the kronolith
mailing list