EVE Technology Lab

Based on my post from yesterday I decided to start putting together a little guide to help people when trying to troubleshoot Yapeal. I don't know how useful it might be for people so ideas and feedback on how to improve it are welcome. Also like to hear ideas for how to continue on or does it need to continue? Anyway here the link:
https://github.com/Dragonrun1/yapeal/wiki/Troubleshooting-Tips

Tiberius Zol - Thanks for report on WalletTransactions problem I started issue for it.
https://github.com/Dragonrun1/yapeal/issues/33

I'm still looking at the other thing with Starbase but let's try one thing that might help on getting a little more complete log message for all you POSes. It looks as though corpStarbaseList for ownerID = 98067338 wasn't expired at the time you took that log so let's 'force' all the Starbase stuff to need refreshing at the same time. This may work better for you if you temporarily stop any crontabs etc and run Yapeal manually.

• Go into the utilCachedUntil table and delete all the StarbaseList and StarbaseDetails rows.
• You can also optional delete the cache files for them in cache/corp/ but Yapeal should use or replace them as needed.
• You might also find truncating the log/yapeal.log file useful.
• Now run Yapeal manually on CLI with something like 'php bin\yapeal.php'.

Once it finishes take a look once again at the tables that didn't seem to be updating and see if they changed also look at your log and see if it now shows anything different like trying to add the other POS that is missing. If you can Pastebin the section from the new log so I can compare it with to old one that would be great as well.

Tiberius Zol - I've been looking at stuff for last couple days and just not seeing anything but I just pushed an update that will add into the XML via processing instruction a json copy of the arguments used when retrieving it from the API server which might help one of us figure out why you're have problems. I did setup a new test POS myself and everything seems to be working fine with the APIs. Try the update and clear the cachedUntil table and the FS cache and see if the XML with the new info makes a difference because without something more to work with not sure what I can do to help you

OK..deleted all entries in StarbaseList, StarbaseDetail and Fuel, deleted starbase entries in cachedUntil and Cache also.
runned yapeal manually..
- all entrys in starbaseList seem to be ok
- theres only one entry in starbaseDetail (should be one for each pos i think?)
- posFuel have only entry for this entry...

as a sidenote.. this pos entry is for the first entry in starbaseList. seems really a loop problem?!
as my interpretation yapeal read the first entry in starbase list.. this work as it should be.. but after it, it doesn't go to the next entry in starbaseList.

Tiberius Zol - Give the update to DatabaseDetails a try and see if it fixes your issue.
https://github.com/Dragonrun1/yapeal/issues/35

Hello,

following steps to install and start to use yapeal but it looks like the wiki is obsolete and concern old yapeal version.

I am in the step where testing yapeal ... but ... no yeapeal.php in install base dir ...

So now what to test and start please ?

ps: installed from git repo

All this two files completed already. Install and config done, database populated.

I just need a start point on how uses api functions and how I can play with it.

There's nothing that introduce the use of the api if the wiki became for old versions.

I'm not a php dev at the origin, but a developer anyway.

Thanks for any information.

I'll try this.

The data imported depends of the api access masks selected on EvE Create Api Page ?

Thanks for help.

Looks like yes, some corp data inserted using yapeal.php.

Now it's all about php code to build my function using database data.

Thanks again !

shouldn't be that hard.. fetch all from the table where refTypeID=10 (should be player donation)

Hi all I just pushed something I've been working on for last couple weeks. I finished up the database updater system. You can try it out by running

'php bin\yc D:U'

It should be able to update any databases that have been manually updated to at least have the blueprint API tables. Note just like with install you may need additional privileges above what the normal Yapeal user needs. Something that's different with the update compared to the install is it uses MYSQL procedure so make sure the user you run it as can create, delete, and use them. Also as always make sure you have a current backup of your database before using it.

Just a little bit about how the updates work. The command starts out by grabbing your settings from config/yapeal.yaml. You can tell it to use a different config file you if you want or override any of the settings using command line options. The command then checks the current version of the database in the utilDatabaseVersion table if it exists and compares that to the sql files in bin/sql/updates/ directory. It will apply any of the sql files that have a version (name) greater then the current database version. They are applied in order and the utilDatabaseVersion table is updated. On the first run you will get a warning message about 'Could NOT get database version ...' which you can ignore as the table should be added for you automatically so you don't see the message again. I decided to use a date-timestamp for the versions vs something else like plain numbers which you might have seen during development. All but the first one are based on when I did commits to git with database updates but in the future they'll be based on when I do create the update sql on my development machine since I wouldn't have commit dates before doing the actual commits like I did this time.

Anyway hope this new tool makes it easier for everybody when updating Yapeal. As always you can ask any questions you have here and if you find a bug make sure to create the issue on GitHub.

Thank you for using Yapeal.