Pages: 1 2 3 4 5 6 7 8 [9] 10 11 12 13 14 15 16 17 18 .. 18 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Dragonaire
Corax. The Big Dirty
32
|
Posted - 2012.02.15 01:50:00 -
[241] - Quote
Read INSTALL.md and just follow the instructions like a new install. You can skip to step to make the DB but when you run the one to create the tables it will update the existing one with your data in place. As always make sure you have a good backup of the DB in case something goes wrong Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
32
|
Posted - 2012.02.17 17:58:00 -
[242] - Quote
Just a quick note for everyone. All the Wiki pages have been converted, updated and moved over to SourceForge now. Check them out at https://sourceforge.net/p/yapeal/wiki/Home/ You'll also notice the Wiki tab at Google Code now redirects you to them. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Dragonaire
Corax. The Big Dirty
32
|
Posted - 2012.02.20 08:37:00 -
[243] - Quote
Ok everything for Yapeal can now be found on SourceForge.
For those of you that might have been cloning their Mercurial from Google Code you'll want to change to SourceForge as the one on Google isn't going to be updated in the future.
Also note for anyone else getting stuff from the SF site when the project was changed to SF Beta project all the URLs have changed so you'll either need to do a new clone of the project. Backup your config/ files and just wipe out your existing checkout and clone it again from the new URL. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Elojs
The Scope Gallente Federation
0
|
Posted - 2012.02.22 02:42:00 -
[244] - Quote
Hey, Dragonaire,
After finally getting hardware upgraded, I return to a variety of new things. Installing yapeal again, I'm getting errors once installed, finding an uncaught exception. Below is the text displayed from my initial run of yapeal.php.
Quote: C:\yapeal>php -f yapeal.php 2012-02-22 02:17:59.445 WARN: Insert/upsert failed for utilXmlCache File: C:\yapeal\class\YapealQueryBuilder.php(489) 2012-02-22 02:17:59.495 WARN: mysqli error: [2006: MySQL server has gone away] in EXECUTE("truncate table `eveAllianceList`")
Code: 2006 Trace: #0 C:\yapeal\ext\ADOdb\adodb.inc.php(1042): adodb_throw('mysqli', 'EXECUTE', 200 6, 'MySQL server ha...', 'truncate table ...', false, Object(ADODB_mysqli)) #1 C:\yapeal\ext\ADOdb\adodb.inc.php(1017): ADOConnection->_Execute('truncate ta ble ...', false) #2 C:\yapeal\class\api\eve\eveAllianceList.php(188): ADOConnection->Execute('tru ncate table ...') #3 C:\yapeal\class\api\AApiRequest.php(112): eveAllianceList->prepareTables() #4 C:\yapeal\class\SectionEve.php(113): AApiRequest->apiStore() #5 C:\yapeal\yapeal.php(164): SectionEve->pullXML() #6 {main} --------- END TRACE ----------
File: C:\yapeal\class\api\eve\eveAllianceList.php(195) 2012-02-22 02:17:59.497 WARN: Could not prepare eveAllianceList API tables to accept new data for 0
File: C:\yapeal\class\api\AApiRequest.php(115) 2012-02-22 02:17:59.499 FATAL: Uncaught exception in yapeal.php File: C:\yapeal\yapeal.php(183) 2012-02-22 02:17:59.500 FATAL: Failed to get ADOFieldObjects for columns in YapealQueryBuilder Trace: #0 C:\yapeal\class\api\eve\eveAllianceList.php(84): YapealQueryBuilder->__constr uct('eveAllianceList', 'mysqli://yapeal...') #1 C:\yapeal\class\api\AApiRequest.php(126): eveAllianceList->parserAPI() #2 C:\yapeal\class\SectionEve.php(113): AApiRequest->apiStore() #3 C:\yapeal\yapeal.php(164): SectionEve->pullXML() #4 {main} --------- END TRACE ----------
File: C:\yapeal\yapeal.php(184)
C:\yapeal>
What I did...
I installed my new API Key and vCode. I activated all sections in utilsections table. Then I ran the yapeal.php and received the above trace.
Do I need to correct anything? Or do you need further information? Or ...
Thanks in advance, Elojs
|
Mikokoel
Mining Industry Exile Foundation
0
|
Posted - 2012.02.22 15:54:00 -
[245] - Quote
I'm not Dragonaire, but your error reminds me of some errors I got when using yapeal.
IIRC the main error is the "MySQL server has gone away" after the "Insert/upsert failed for utilXmlCache". My guess would be that Yapeal creates to big SQL-Queries which your server can't process.
You could try to change the configuration of your server (somewhere in the my.ini), but I also think you can disable XML-Caching in the Yapeal configuration file
Hope that helps,
Mikokoel EvE API Development zap - advanced programming |
Dragonaire
Corax. The Big Dirty
33
|
Posted - 2012.02.22 17:38:00 -
[246] - Quote
Mikokoel Is right sounds like you need to change your max_allowed_packet setting for MySQL. I would say yours is set below 1M or you are trying to run an older version of Yapeal before I put in some limits to the insert/upsert size that it uses. It now limits the size to 990k which is below the normal limit. You can find the constant that sets that at the bottom of class/YapealQueryBuilder.php. If you haven't yet you should read through the Starter Guide which on the Yapeal Settings page tells you more about changing the setting for MySQL. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Elojs
The Scope Gallente Federation
0
|
Posted - 2012.02.23 01:02:00 -
[247] - Quote
Quote: IIRC the main error is the "MySQL server has gone away" after the "Insert/upsert failed for utilXmlCache". My guess would be that Yapeal creates to big SQL-Queries which your server can't process.
You could try to change the configuration of your server (somewhere in the my.ini), but I also think you can disable XML-Caching in the Yapeal configuration file
Thanks, will look into that. The server hadn't gone away after all, just was slow responding. Need to tweak some settings in the XAMPP package (PHP, MySQL)
Appreciate the input.
Quote: Mikokoel Is right sounds like you need to change your max_allowed_packet setting for MySQL. I would say yours is set below 1M or you are trying to run an older version of Yapeal before I put in some limits to the insert/upsert size that it uses. It now limits the size to 990k which is below the normal limit. You can find the constant that sets that at the bottom of class/YapealQueryBuilder.php. If you haven't yet you should read through the Starter Guide which on the Yapeal Settings page tells you more about changing the setting for MySQL.
Thanks, Dragonaire. I've read the starter guide. BTW, nice job on the Wiki. Looked through all that's there. Hoping to see it grow with Yapeal. XAMPP (which I'm using) is a non-standard install, so I have to track down the config files its using, and alter the appropriate setting in the right place. It's complicated by other sites using the XAMPP stack locally. Avoiding breaking any of them is my goal.
The main focus prompting the post was the 'untrapped' error that was reported for your review and whatever action you decide to take on it. Sorry if I didn't make that clear enough. Just responding to your request in the Yapeal Wiki.
FYI, I did have it working shorly after the post, and it's now polling for updates every hour under Task Scheduler. BTW, is the wiki postable? If so, I have a few thoughts for Windows installations to ease use. A two line command file named for some reason Yapeal.cmd to add the PHP and MySQL clients to the path, followed by the invocation of yapeal.php.
Thanks loads, Elojs (Paul) |
Satis Iqulenax
Free Imperial Vikings Monkey Circus
1
|
Posted - 2012.02.23 03:22:00 -
[248] - Quote
Elojs wrote:Thanks, Dragonaire. I've read the starter guide. BTW, nice job on the Wiki. I would be the one taking the credit for this, since I was the one making the starter guide but I also do understand the confusion since I haven't made any credit note on it, so I also don't mind that you are thanking Dragonaire
Elojs wrote: BTW, is the wiki postable? If so, I have a few thoughts for Windows installations to ease use. A two line command file named for some reason Yapeal.cmd to add the PHP and MySQL clients to the path, followed by the invocation of yapeal.php. I'm almost sure it's only the developer/commiter that can make wikies, but you are welcome to add a comment to it or send it to Dragonaire or me, then we will look thou it and add it to the guide or a new wiki if it's usefull
Kind regards Satis Committer of Yapeal for Eve API. Developer of XMLSchema. A database schema tool for PHP |
Dragonaire
Corax. The Big Dirty
33
|
Posted - 2012.02.23 04:56:00 -
[249] - Quote
You can post to the wiki but you have to be authenticated (Be signed into SourceForge) to do so. General posts like that are moderated as well but I only set it up that way because of spambots so please do add any comments or suggestion etc you have and one of us will make it visible for everyone (Once I figure out how that works anyway ) I may decided to change to just authenticated in the future but still getting use to the new system and I decided being a little bit on the paranoid side might not be a bad thing to start with
Satis Iqulenax does deserve the credit for the writing on the Starter Guide I just acted as editor on it and did the translation of the Wiki syntax during the move. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
The Magez
Quasar Buccaneers Lawful Insanity
0
|
Posted - 2012.02.23 20:19:00 -
[250] - Quote
Hello, i have this problem, i had an industry job that i cancelled ingame (Material Effiency job) and since then yapeal stopped fetching new corpIndustryJobs xml, or atleast its not putting it into database as it should, tried to truncate the table but its still not updating it, also tried to truncate another table (corpStandingsFromFactions) and that fetched fine even after truncated.
Thanks |
|
PsyKzz
Bat Country Goonswarm Federation
9
|
Posted - 2012.02.23 20:21:00 -
[251] - Quote
The Magez wrote:Hello, i have this problem, i had an industry job that i cancelled ingame (Material Effiency job) and since then yapeal stopped fetching new corpIndustryJobs xml, or atleast its not putting it into database as it should, tried to truncate the table but its still not updating it, also tried to truncate another table (corpStandingsFromFactions) and that fetched fine even after truncated.
Thanks
Truncate means to empty. It wont make a difference to how anything works. Meh. |
The Magez
Quasar Buccaneers Lawful Insanity
0
|
Posted - 2012.02.24 13:43:00 -
[252] - Quote
WARN: Deactivating Eve API: IndustryJobs for keyID: ****** as this API is no longer allowed by owner with this key File: /var/www/eve/yapeal/class/api/ACorp.php(321)
So i found that line from the logs, didnt see it when i first time looked at the logs. I take it this means i have to activate the said api again? I tried manually to access the api with that key and it worked perfectly. What possibly made that happen? I still have no other idea but the deleted job messing around with that thing somehow.
EDIT: Tried activating the corp api by using the wiki guide "Activating and deactivating APIs in a section" but still couldnt get it working. |
Dragonaire
Corax. The Big Dirty
34
|
Posted - 2012.02.24 18:07:00 -
[253] - Quote
At some point the API server thought that key had the IndustryJobs API turned off so when Yapeal was told that it unset the key and/or corp's bit so you'll need to update them not the general ones used by all of Yapeal. Look at the utilRegisteredCorporation and utilRegisteredKey tables that are related to the key that stopped working as the bitmap in activeAPIMask doesn't have the IndustryJobs bit set. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
The Magez
Quasar Buccaneers Lawful Insanity
0
|
Posted - 2012.02.25 13:30:00 -
[254] - Quote
Thanks! got it working again by updating the masks to include the industry jobs bit. |
Zaepho
Phoenix Propulsion Labs Shadow of xXDEATHXx
8
|
Posted - 2012.02.28 18:34:00 -
[255] - Quote
Dragonaire wrote:At some point the API server thought that key had the IndustryJobs API turned off so when Yapeal was told that it unset the key and/or corp's bit so you'll need to update them not the general ones used by all of Yapeal. Look at the utilRegisteredCorporation and utilRegisteredKey tables that are related to the key that stopped working as the bitmap in activeAPIMask doesn't have the IndustryJobs bit set.
Would it make sense to have a field for desired and effective bit masks? This should allow for the desired mask to cover everything you want and effective to be updated via errors and the APIKeyInfo api. Effective would be used by all of the current classes. APIKeyInfo when processed would attempt to update the effective to be as close to the Desired as possible based on what the key itself supports. |
Eduardo'o
Versatech Co. Raiden.
16
|
Posted - 2012.02.29 14:55:00 -
[256] - Quote
Dragonnaire,
I had a corp API for a character in my yapeal instance, i moved the character to another account, removed the api from the registeredKeys table and added the new api key for the accounts the character was moved to to the registeredKey instance.
The new data was picked up nicely, but the old data, belonging to the first api that I deleted keeps showing up. Is there something I forgot about when deleting the api in order to clean up the rest of the database?
Ed |
Dragonaire
Corax. The Big Dirty
35
|
Posted - 2012.02.29 17:10:00 -
[257] - Quote
Quote:Would it make sense to have a field for desired and effective bit masks? This should allow for the desired mask to cover everything you want and effective to be updated via errors and the APIKeyInfo api. Effective would be used by all of the current classes. APIKeyInfo when processed would attempt to update the effective to be as close to the Desired as possible based on what the key itself supports. Could something like that maybe be implemented? Yes, but not everyone wants the keys to change either. If you want that effect Yapeal supplies the tools for you to do so in a way that makes sense to your application. BTW you can get most of the effect you are looking for by simply setting the masks in utilSections and utilRegisteredKey to what you want and once accountAPIKeyInfo updates it will block any APIs that aren't allowed. If Yapeal tries getting an API before it updates that isn't allowed it deactivates it when the API server returns an error saying its not allowed like what was happening above. I've designed Yapeal to report error and then try to keep from repeatedly telling you there's an error or wasting time on something that doesn't work. You then as the programmer/user get to decide when whatever was causing the error has been fixed and it can try again.
Quote:The new data was picked up nicely, but the old data, belonging to the first api that I deleted keeps showing up. Is there something I forgot about when deleting the api in order to clean up the rest of the database? You didn't delete the old data from the API tables. Deleting the keys doesn't have any effect on the API tables themselves when it comes to existing data but only effects what new data may be added. Additionally when you do a character move like you did it would be a good idea to update the accountCharacters and accountKeyBridge tables manually or in your application to break the link between the key and the old account etc as how Yapeal well react in this case is not really defined. It should do the right things after accountAPIKeyInfo updates for the key but you may get a few errors until that has happened. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Drapko Nitzhonot
Abdera Logistics
4
|
Posted - 2012.03.15 12:30:00 -
[258] - Quote
Since long time ago I'm getting serveral "cron mails" per day with messages like:
Quote:curl_error: Operation too slow. Less than 10 bytes/sec transfered the last 12 seconds 2012-03-12 20:00:42.981 INFO: Operation too slow. Less than 10 bytes/sec transfered the last 12 seconds for API https://api.eveonline.com/corp/WalletTransactions.xml.aspx File: /home/drapko/doc/yapeal/class/YapealNetworkConnection.php(106) or just:
Quote:curl_error: Operation too slow. Less than 10 bytes/sec transfered the last 12 seconds As everything were updated correctly, I didn't mind, but I can't believe I can't connect so many times to API every day and I wanted to decrease email notifies. (I don't want to redirect Yapeal to /dev/null in cron)
Another issue is Yapeal stopped updating corpWalletTransactions about 10 days ago. I notice my activeAPIMask was changed from utilRegisteredKey. I haven't touch any API key or Yapeal config since last Yapeal update (January 26th), so I don't know what happend to change that key... maybe because I'm getting so many curl_error?
Thanks |
Dragonaire
Corax. The Big Dirty
35
|
Posted - 2012.03.15 16:00:00 -
[259] - Quote
Drapko Nitzhonot - You have a couple options for the too slow errors.
- B!tch at CCP because their servers aren't responding in a timely matter to API requests for some reason.
- Change the error reporting level in Yapeal to 'warning' instead of 'info' inside the config/logger.xml file.
- Change the timeout value in Yapeal to try giving them more time. You can try this by changing the last line
const TIMEOUT = 45; in ext/eac_httprequest.class.php. This probably won't help as most times when the API doesn't response in the time given it's not going to respond at all
You also need to make sure there isn't another application trying to grab the same API information as they can conflict ending up with a race condition between them and the timeout errors.
Quote:Another issue is Yapeal stopped updating corpWalletTransactions about 10 days ago. I notice my activeAPIMask was changed from utilRegisteredKey. I haven't touch any API key or Yapeal config since last Yapeal update (January 26th), so I don't know what happend to change that key... maybe because I'm getting so many curl_error? Look for a line in your logs like this WARN: Deactivating Eve API: WalletTransactions for keyID: ****** as this API is no longer allowed by owner with this key I'll bet for what ever reason that Yapeal received an API error saying the key was not valid for that API and turned it off just like happened to The Magez above on IndustryJobs and the fix is the same as I gave to fix it. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Drapko Nitzhonot
Abdera Logistics
4
|
Posted - 2012.03.15 17:43:00 -
[260] - Quote
I will change to "warn". I missed the email about deactivating eve API because I was tired about same message :P
You are right, I have the log:
Quote:2012-03-03 13:30:06.867 INFO: Deactivating Eve API: WalletTransactions for corporation XXXXXXXX as this API is no longer allowed by owner with this key File: /home/drapko/doc/yapeal/class/api/ACorp.php(301)
Thank you! |
|
Drapko Nitzhonot
Abdera Logistics
4
|
Posted - 2012.03.15 21:07:00 -
[261] - Quote
I'm still getting cron emails after changing to "warn" level:
Quote:curl_error: Operation too slow. Less than 10 bytes/sec transfered the last 12 seconds
I'm getting this even there is no updates in log/ files. |
Dragonaire
Corax. The Big Dirty
35
|
Posted - 2012.03.17 15:19:00 -
[262] - Quote
Drapko Nitzhonot wrote:I'm still getting cron emails after changing to "warn" level: Quote:curl_error: Operation too slow. Less than 10 bytes/sec transfered the last 12 seconds I'm getting this even there is no updates in log/ files. Sorry about that there seems there was some old debugging code left over in ext/eac_httprequest.curl.php which I hadn't noticed before which was directly printing out the errors on the CLI I've pushed out a change that fixes that plus a few other minor things.
I am concern though after looking more fully at the second log message you were getting that you are still running an older version as the line 106 reported in the error should be 100 instead. Make sure you are following the full instructions on how to instill and update Yapeal and not getting a mix of old and new versions etc.
version 12.077.0801 Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
Drapko Nitzhonot
Abdera Logistics
4
|
Posted - 2012.03.17 17:17:00 -
[263] - Quote
Thank you. I will install the new version |
Kush Monster
Big Tobacco
29
|
Posted - 2012.03.30 22:11:00 -
[264] - Quote
I'm sure this has been covered but your wiki goes into inserting data but it doesn't go into extracting data.
let's say I want to insert a key and then register the chars associated with that key.
How do I get a list of character id's associated with the api key?
I can do this with SQL but the point of using a library would be so that I don't have to. How to make mining enjoyable: An Autocannon, Faction Ammo, Your Mouth
|
Dragonaire
Corax. The Big Dirty
36
|
Posted - 2012.03.31 17:57:00 -
[265] - Quote
Kush Monster wrote:I'm sure this has been covered but your wiki goes into inserting data but it doesn't go into extracting data.
let's say I want to insert a key and then register the chars associated with that key.
How do I get a list of character id's associated with the api key?
I can do this with SQL but the point of using a library would be so that I don't have to. I'd suggest reading the project home page a little closer as part of the main idea with Yapeal is that the database is the API for people's applications. There are some classes in class/util/ to help manage the non-API tables that an application might need but there's no way I could ever come up with a set of classes that allow as much versatility to access the API data as what each developer can do for their own project with a simple wrapper class around the SQL queries they need.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
malaire
328
|
Posted - 2012.04.01 11:27:00 -
[266] - Quote
How do I clear the cache-directory of old files?
Running install/cacheCleaner.php from command line claims that cache was cleaned, but it wasn't. I tried running that both from yapeal and yapeal/install directory.
New to EVE? Don't forget to read: The Manual * The Wiki * The Career Options * and everything else |
Dragonaire
Corax. The Big Dirty
36
|
Posted - 2012.04.01 15:15:00 -
[267] - Quote
Check your cache settings in config/yapeal.ini as the default is 7 days so it will only clear files that are older than that. Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
malaire
330
|
Posted - 2012.04.01 15:49:00 -
[268] - Quote
Dragonaire wrote:Check your cache settings in config/yapeal.ini as the default is 7 days so it will only clear files that are older than that. I checked that. It is still 7 days but it did not delete files over 30 days old. I have only 3 accounts in yapeal, but cache is 5500 files and 400 MB.
New to EVE? Don't forget to read: The Manual * The Wiki * The Career Options * and everything else |
Gabba Cyno
11
|
Posted - 2012.04.02 15:41:00 -
[269] - Quote
Is there a reason I have to run the yapeal.php 5-7 times in a row before it actually updates my database? . |
Dragonaire
Corax. The Big Dirty
36
|
Posted - 2012.04.02 17:12:00 -
[270] - Quote
Gabba Cyno wrote:Is there a reason I have to run the yapeal.php 5-7 times in a row before it actually updates my database? I'd be checking the error logs to see what's going wrong myself. You might have to run it a couple times for it to prime the account section tables before you'll start seeing data in your char and corp section tables but I've never seen any cases where it was more than a couple as long as something isn't going wrong.
Finds camping stations from the inside much easier. Designer of Yapeal for Eve API. Check out the Yapeal PHP API library thread for more information. |
|
|
|
|
Pages: 1 2 3 4 5 6 7 8 [9] 10 11 12 13 14 15 16 17 18 .. 18 :: one page |
First page | Previous page | Next page | Last page |