[Help]Dead pets

[Jack Sparrow]

Hello all , i have a problem with my server
today the server was working fine , and many players were composing ... after like a hour i found every one telling me that when they open the universal boxs they get dead unis with 1 loyalty , tryed to hatch random pets and the same problem
what is the fix for that ?
also how that happened because the server was working fine and i didnt touch the db today ...

[~Sword~Stalker~[PM]]

u sure u didnt change ur Starlev. from DB >?
\

[~WARNING~]

i believe running the cq_grade query to update the old uni's should fix this

[Jack Sparrow]

Originally Posted by ~Sword~Stalker~[PM]

u sure u didnt change ur Starlev. from DB >?
\

No i didnt touch the db today ...

Originally Posted by UnbeatenRs2

i believe running the cq_grade query to update the old uni's should fix this

itis not only the unis , i have this problem with all the pets

[Jack Sparrow]

ugh i rolled back my cq-grade but didnt work , rolled back cq-monstertype but didnt work , rolled back cq-itemtype but didnt work and rolled back cq-eudemon and it worked!

but i still cant find the problem because i didnt touch this table only onc before a week...

[Eurion]

Just a question, how do you do your maints? Do you manually close down your npc,msg, and acct servers? Or do you use a program to do it for you?


From what you said, it sounds like your cq_eudemon table got corrupted. This can happen for a few reasons. The main one is when the msg server doesn't get closed properly.

[Jack Sparrow]

Originally Posted by Eurion

Just a question, how do you do your maints? Do you manually close down your npc,msg, and acct servers? Or do you use a program to do it for you?


From what you said, it sounds like your cq_eudemon table got corrupted. This can happen for a few reasons. The main one is when the msg server doesn't get closed properly.

i login my pm char to do /kickoutall
then close the acc/npc/msgervers

[Eurion]

Ok doing that should be fine. If it happens again what you can try is.

Right click on the cq_eudemon table, choose maintain tables -> repair tables -> quick. It will analyze the table to see if there are any errors. Most times it will save you from having to roll back.

[Jack Sparrow]

Originally Posted by Eurion

Ok doing that should be fine. If it happens again what you can try is.

Right click on the cq_eudemon table, choose maintain tables -> repair tables -> quick. It will analyze the table to see if there are any errors. Most times it will save you from having to roll back.

still the same and now itis even worse all the pets are gone

[Eurion]

What I would do is this, limit who has access to your db. Many of us have been messing with the Eo files for a while, and I have to say, I've yet to see where tables just corrupt themselves.

I typically don't get involved with anything related to pets, but this sounds like someone is editing something and not knowing what they're doing. If repairing the table didn't work, then you're stuck and will have no choice but to revert back to a date before this started happening. Sorry I can't be of much help, I've always been lazy when it comes to learning about pet tables.

[Jack Sparrow]

Originally Posted by Eurion

What I would do is this, limit who has access to your db. Many of us have been messing with the Eo files for a while, and I have to say, I've yet to see where tables just corrupt themselves.

I typically don't get involved with anything related to pets, but this sounds like someone is editing something and not knowing what they're doing. If repairing the table didn't work, then you're stuck and will have no choice but to revert back to a date before this started happening. Sorry I can't be of much help, I've always been lazy when it comes to learning about pet tables.

iam the only one who have axx to the db and i didnt do any thing wrong in this table , i will roll back it and hope this will not happen again
any ways thanx Eurion

[DeadHackerz]

so did it solved now?

[Jack Sparrow]

Originally Posted by DeadHackerz

so did it solved now?

Yeah rolled back the cq-monster to the last back up , hope it will not happen again because the db bug it self somtimes