Bukkit

NOTE: If you supply copies of your .yml or console log files, please use pastebin, dropbox, or other service and provide link, instead of copy/paste of the file into this report. Thanks!

What Version of OnTime and Bukkit are you using?
OnTime: Version: 3.8.6
Bukkit: CB 1.6.2 #2821

What storage option are you using? (YML or MYSQL) ?
MySQL I think

What permissions plugin are you using? (Groupmanager, PEX,bPermissions, etc.)
Permissions Bukkit

Please provide a link to a copy of your plugins/OnTime/config.yml:
http://pastebin.com/fXEkELHp

What steps will reproduce the problem?
1. I'm not even sure? Install
2. Wait a few days
3. Check Ontime Top

What is the expected output? What do you see instead?
I expected Ontime Top to generate a reasonable output into the display, instead it's showing information for the week from a week or two ago.

Do you have an console log of what happened?
No, but I have this? http://pastebin.com/vgMerpLj

Are you having a "rewards" problem? Please provide a link to a copy of your /plugins/OnTime/rewards.yml :
Not sure, with the Ontime Top being all funny when issuing the commands, not sure if the "top playtime for the week" is working
http://pastebin.com/6dFxF5yr

Did you turn on OnTime logging (/ontime logfile enable 1)? If so, provide a link to that file too.
I don't think I did? I've given the only error log I've got in the folder here, and anything else that I thought might relate to this issue.

Please provide any additional information below.
I seem to have a lot of "Daily Report" files in plugins/Ontime as well, is this normal? Will they delete themselves after a while?
Here is a screenshot of what we are seeing ingame. http://tinypic.com/r/2wogl5y/5

So I find out I'm using YML for storage, not MySQL... My bad. I wanted to switch though, but I get internal errors when trying to use the command... >.>

Sorry for the long delay in my response, but I have been out of town and got back just today. I needed to check some things on your ticket with the code, so I couldn't make a quick assessment while away.

It looks like you have several different things going on here. The original ticket item about the "top weekly" looks like OnTime did not roll over at the start of the week on 8/4. Since another Sunday has passed, is it still showing data accumulating from 8/4, or did it roll over on 8/11?

For the messages in the OnTime_ERROR.txt file, you have more there then I expect to see, but it is not related to your "top" issue. I may want to look into this further and ask you for some more data, but I don't think that problem is harmful, but it does concern me some. (Lets take care of this one last)

Can you please show the errors you are getting when you try to do the data conversion, so I can figure out what is going on there?

@Edge209: Go

That's quite alright, I figured you were busy and would get to my ticket when you could. ^.^

As far as ontime not rolling over on the new week, I don't believe it has even still. I'm still getting play-times of 5 days in a week that's only on it's a third day. :\

And as far as asking for any and all information I might have available, you're more than welcome to demand every file I have multiple times if it helps. XD I wasn't sure what was a problem with what so I figured I'd give you everything just in-case.

As for attempting the Database Conversion, here is the error that comes up into console: http://pastebin.com/0jpPUXb0

@sakura_blades: Go

Regarding the MySQL issues. Do you have a database already set up and are only adding an OnTime table? Or is the first MySQL DB you are using for plugins?

Can you share your updated OnTime/config.yml so I can see how you have the DB set up?

@Edge209: Go

Obviously I set mysql to "true" when attempting to export the data over from YML, but in this paste it's set to "false" as I switch it back after a failed attempt to convert.

http://pastebin.com/GgdFEF9R

I have a MySQL database set up with at least two or three other plugins already hooked into it, so I know the database is working as these other plugins are doing fine. I've double, triple and quadruple checked to make sure that the information for the database is correct in the Config. I've compared it to the other plugins hooked into it too, so I know it's not the database information. :\

If I recall, I had issues converting with my last server too and just continued to use YML for Ontime. But I see you have a new plugin that works with it, OnSign? And I'd love to be able to use it but I'd like them both to work with MySQL even it's not required they both do...

Ok, I'm going to ask you to collect some data for both the MySQL and Weekly rollover at the same time.

First I'd like you to set up your OnTime logging with the following commands:

/ontime console enable 1

/ontime logfile enable 1

[MYSQL Issue]

Then while leaving "dataStorage:YML", set "MySQL.enable: true".

Then restart your server (or reload plugins) so that OnTime goes through its initialization. There should be output in your console log that OnTime generates, which states it success in accessing the MYSQL db.

[Weekly RollOVer Issue]

Next execute the following two commands:

/ ontime test yesterday
/ ontime test today

Then please post a copy of the full output of the console starting from the plugin reload, through the execution of the last two commands above.

And post a copy of the file /plugins/OnTime/OnTimeLog.txt

Thanks!

@Edge209: Go

I didn't see anything saying Ontime registered with MySQL or not... but here it is from a reload, the server log.

http://pastebin.com/h3KSyPgU

For some reason all of the console log info from OnTime is missing, and it could be related to another issue that I just fixed.

I'm going to post this later tonight, but I think this will help in working through your issues, so here is a link to a "sneak peek" at v3.8.7

https://dl.dropboxusercontent.com/u/98770053/OnTime%20v3.8.7.jar

Replace your current OnTime version with this one, and repeat the tests from my last post, and send the results. Hopefully this will tell us more, and perhaps fix the (rollover) problem even.

@Edge209: Go

Here is the server log with the new Jar.

http://pastebin.com/1w3RmFQ7

And I forgot this last time, so here is the OntimeLog.txt too

http://pastebin.com/YWguTLVu

@sakura_blades: Go

It's better but still not everything I expect to see in the console log. Please check the OnTime/config.yml and make sure that the following is set:

consoleLogLevel: 1

And make sure that MySQL is enabled.

Then also set the following in config.yml

firstDayOfWeek: 4

(The above will make today, Wednesday the start of a new week.)

Reload the plugins again, so hopefully this time we will see the right console output.

Execute the two test commands again, and OnTime should now roll over the week since we made today the start of a new week.

Again post the same console log and the OnTime logfile,

@Edge209: Go

Serverlog : http://pastebin.com/Zu6kuchW Ontime log: http://pastebin.com/sPAE8P2K Ontime config: http://pastebin.com/gBKzcfuG

That did seem to get it to rollover to today, but it's only counting anyone who's logged in since I reloaded the plugins? XD

@sakura_blades: Go

Finally a good set of data.

The mysql looks like it is setting up properly, so go ahead and again try the export to MySQL and see what happens.

It looks like the rollover did work, and yes it will only start recording going forward since the plugin thinks it rolled over at midnight. There is no way around this and we had to get it unstuck. There is no way to recover the detail of the time played this week, so unfortunately your weekly top data and rewards will be screwed up yet this week. At this point you can change your week start back to Sunday, and next Sundaywe can see if things are truly back on track.

I think you will see if you look at the indirewards.yml that a number of weekly top rewards were issued when the roll over finally happened. If you don't want those rewards to be issued you will have to disable ontime, edit that file, and then restart OnTime.

@Edge209: Go

Nah I'll leave the rewards issued alone, it's a few weeks overdue anyway. But I got notice that ontime converted successfully this time! :D

Thanks so much again Edge, as always you've been fabulous! I will set it back to reset on Sundays, and hope it keeps up with the week changes/rollovers from there.

Just to be sure, once i'm told ingame "Player data successfully exported to MySQL" I change from YML to MySQL?

@sakura_blades: Go

Yes. Just change "dataStorage: MYSQL ", and then do a reload, which can be done using "/ontime reload all".

Let me know if things seem to be working with your MySQL storage.

Also, I will leave this ticket open in the "waiting" state until we see what happens on Sunday.

This is long over-due and I see you still have this ticket open.

Everything is working as it should be, by the way.. Sorry I never responded. But I think you can close this to weed out un-needed tickets from your lists. :P

I take that back, I checked it again just now to be sure... and saw this? It seems out of order. XD

http://i41.tinypic.com/2core47.png

@sakura_blades: Go

The one guy out of order is the only one on line. The top order is based on the stored information , and then his current OnTime is added, making his total position higher than his stored position. This is different issue than the original ticket. I know it works this way, I just never got around to making it right. :p