Bukkit

INFO {popSignData} SQL Error: Column 'uuid' not found.
INFO No OnSigns defined.

What Version of OnSign and Bukkit are you using?
OnSign:v2.0
Bukkit:spigot 1.8.1

Please provide any additional information below.
depending on what you put the refreshrate to is when you will see this in console
i updated to 2.0 get this so i deleted all files including config restarted the server nothing so i added mysql info and restart now getting this again

what can i do to get rid of this console spam

sorry about the doble post it said i wasnt able to post so i clicked the button agin and it worked

I need a little bit more information. Can you edit your config.yml to enable more detailed console logging:

# Enable logging of OnSign Activity, mainly for debug purposes
logEnable: true
#
 
AND

#
# Level of detail in the console during stratup etc. (3 = least detail; 1= most detail)
consoleLevel: 1

And then restart your server and provide to me the output you see in the console from OnSign during the startup?

Thanks.

do apologise about the lack of detail before i hope this can help

This server is running CraftBukkit version git-Spigot-c46583f-e6f9fd4 (MC: 1.8) (Implementing API version 1.8-R0.1-SNAPSHOT)

http://pastebin.com/7KpGYpGv

update

i stopped the server exported MySQL onsign-data and deleted it restarted the server only with No OnSigns defined. joined ther server and created a sign with no problems the No OnSigns defined went away

now getting a new thing

http://pastebin.com/QRJmWAp1

Thanks for the extra data it helped, but also is generating more questions.

1. I've found and have fix for the original 'uuid' not found issue.

2. For your "new thing", I see a couple of issues in the log, so I have some requests:

A) At the top of your log, there is a message "[15:52:51] [Server thread/INFO]: [ONSIGN] {extractColor} string was null.", this is indicating that something is missing or corrupt in your OnSign/config.yml. Can you post a link to a copy of that file for me to see?

B) For the sign that failed and was auto deleted, can you tell me exactly what you tried to put on each of the lines of the sign?

Thanks.

thank you for the help that really help alot

if you check in the first pastebin i sent you here http://pastebin.com/7KpGYpGv you can find the missing parts from the config on line 139 refer, 155 referCount, and 157 noData those 3 where missing and might be from converting from running v1.3.0 on 1.7.10 to v2.0.0 on 1.8.1 just an idea not to sure my self but i made a backup of the original file deleted it and restated the server making a new config loaded both side by side to find missing parts

and for the missing sign multiverse didn't fully remove a world that had signs i put all my plugins in debug and full all log mode that i could. finding multiverse trying to load a world not there no more i fully removed it and no more error

still getting uuid error if i try to use the old tables in mysql db but not if i load a new table with a different name and remake all the signs

at this time i have made all new signs and gonna stick with the new table in mysql and have no more problems

i hope this help you and may help more when or these problems reapers

plus i use all your plugins and refer others to use and help out

@Jonny42G: Go

I now have an fix for the config.yml upgrade issue, which you were right about. So thanks again for the good details.

You are right to use just use the new DB, because until I get out the v2.0.1, the 'uuid' issue will persist with your old database. I'm sorry you had to re-create everything.

Based on what you said about multiverse, it means that OnSign was handling the removed world properly, so no issue there either.

V2.0.1 will be up shortly. I will then be closing this ticket.

Sounds great im glad to help and dont worry it was just 25 signs just a bunch of % and scribbles and thanks again

I'm using OnSign v2.0.1 and getting the same issue as Jonny42G. Same server log, error messages, and everything.

I'd really appreciate help with this issue, as all of our OnSign signs are completely unusable due to this bug, even the reward signs.