EVE Technology Lab

Hello,


I'm very excited about the databasing possibilities(never done databasing before), and have just finished the install of the latest Yapeal with Mysql 5.1.63, php-3.5.12 VC9 version, and Apache 2.2.29(also VC9 compatible...just mentioning for info), and when running the 'createMySQLTables.php' , got the following:




Failed to execute schema for account
Failed to execute schema for char
Failed to execute schema for corp
Failed to execute schema for eve
Failed to execute schema for map
Failed to execute schema for server
Failed to execute schema for server
There were problems during processing please check any error messages from above and correct.


Is this because my database's head is completely empty as far as data goes? ..because it did create 115 rows of table.



Thanks!
Lotso

Hi everybody,
Thought it was time to let people know I'm still working on Yapeal etc. Development has slowed as other projects have been the priority lately but I'm still working on Yapeal from time to time as well. What has me especially doing an update now is something I read in another thread that got me to thinking about something in Yapeal. Historically Yapeal has had most of the API sections turned off do to many reasons like logs filling up with error messages when no characters/corporations were added to the utilRegistered* tables plus other issues but since none of those issues exist anymore I've decided to change the default so all sections are on by default going forward. This should also help many people when they first are trying out Yapeal since one of the more common questions is why their stuff doesn't work after adding data to the utilRegistered* tables. I'm not going to change which APIs are active in each section from the current defaults so you may still need to make those changes yourself in the masks.

There are a few other minor changes as well in the new version but they are mostly just comment updates.

version 12.155.1909

Look at utilCachedUntil table to see when it will next try to get the API.

Think that's cause by changes CCP has been making for unified innovatory so you might try reporting it to them.

I Sorry to hear it's running without an errors for you If it ever does have some errors you might try looking in log/ directory since that's where they get put.

Shouldn't ever do that but also remember it expects to be ran every minute from a crontab or scheduled task.

Sorry about that but maybe you should slow down just a little and try a little reading and things might be easier for you.

i'm using the standard yapeal.php for updateing the database.

BTW have you tried read the stuff in the Wiki a lot of your questions are answered there.

As always make sure you've backed up your data before trying to update it. To try figuring out what part of the SQL isn't working look in the cache/ADOdb/ directory and try running the SQL files you'll find there starting with util.sql. you can either run them directly with MySQL on the command line or through PhpMyAdmin. You can also look at the SQL in the files to have some idea what has changed but often the best way to find the differences is to run the script on a new empty DB and compare it with your current one.

As a general warning for everyone it's important to keep up with the current versions on Yapeal because though usually the individual updates rarely break anything and can be done automatically by the scripts upgrading over several versions can be more than they can handle and you'll end up having to do part of it manually.

Thanks for letting me know last I'd checked CCP limited all names to 32 characters but I guess maybe they've changed that now. I'm wondering one thing with that name did it use any non-English characters by chance?

Sounds just like they have lifted the length limit I'll update Yapeal and push it out the next time I get a chance.

Your errors would seem to be your MySQL not being able to keep up or something. as both of your examples are for tables that only do small inserts. I'd check you MySQL config and make sure it's optimized for the system you have it running on.

I got that length error again on a different table this time but just to show the Corp Name

Also, still getting those MySQL errors

Any way of finding out which query is causing the error so I can debug further?

@Lluerssen
First that's a very old tread from when they regularly reset the refIDs which no longer happens also if you pay attention Yapeal will include both records since ownerID, refID are used as the primary key so if you aren't seeing both of them in the Db it might be the query you are using to find them. If I understand right when you did a search you did end up seeing them both. In the char table ownerID is sent to the charID and in the corp one it's the corpID. The only time there can be a problem is when a char buys from their own sell order or the same for the corp. You still have a record but which one you'll get (buy or sell) can be random and due to no guarantee from the API on record ordering can change each time it's received

@Gilgamoth
I'll try to update all of the name columns to be longer and push it out over the next couple of days.

Probably the best thing to do for the charSkillQueue error is to look at the XML and see what might be strange about it that causes the error. Also look for other errors just above it in the logs that start with either 'Row was missing required fields ...' or 'Row has extra unknown fields ...' which should give you some idea what's going wrong.

Thanks Dragon, i've found my problem, activeAPIMask change for character at some time, and it just stopped quering -.- :D

Hello Dragonaire,

I have been using Yapeal since more than a year now. Great software!

I recently had some problems with "Operations being to slow". The 12 Bytes per 10s thing. After that I noticed I haven't updated since half a year and quickly changed that.

Since 3 days, the cronjob running Yapeal doesn't output anything, but there are no log files and no updates in the database.

I double-checked my config files (including new logger).

After running checkForRequirements (again via cronjob, damn it webhosting package), it finally gave me the hint that i need PHP 5.2.8. Sadly i only have 5.2.6 and i don't know if i can tell my provider to upgrade it. Is it really needed? And if so, is that the reason why yapeal stopped working without saying anything?^^.

It really drove me crazy the last days...

Greetings

Mikokoel

Edit: Nevermind, fixed it