Jump to content

herrtrigger

Members
  • Posts

    134
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Posts posted by herrtrigger

  1. Well i tried around with a value of '10'.

    It also showed up ok in the client.

    But sometimes when i would refresh the ah listed items (ingame at auctioneer), it would get stuck (looked like it kept searching forever).

    The only thing helping to get the list again was to logout-login.

    But then after some more refreshes, it got stuck again.

    This is what happened in log at those times:

    2010-06-01 21:30:13 ERROR:ERROR: Attempted to get in ByteBuffer (pos: 32 size: 46) value with size: 16
    2010-06-01 21:30:13 ERROR:WorldSession::Update ByteBufferException occured while parsing a packet (opcode: 600) from client 192.168.30.2, accountid=23.
    2010-06-01 21:30:49 ERROR:ERROR: Attempted to get in ByteBuffer (pos: 32 size: 46) value with size: 16
    2010-06-01 21:30:49 ERROR:WorldSession::Update ByteBufferException occured while parsing a packet (opcode: 600) from client 192.168.30.2, accountid=23.
    2010-06-01 21:31:11 ERROR:ERROR: Attempted to get in ByteBuffer (pos: 32 size: 46) value with size: 16
    2010-06-01 21:31:11 ERROR:WorldSession::Update ByteBufferException occured while parsing a packet (opcode: 600) from client 192.168.30.2, accountid=23.
    2010-06-01 21:32:17 ERROR:SESSION: received not allowed opcode CMSG_LFD_PLAYER_LOCK_INFO_REQUEST (0x036E)
    2010-06-01 21:32:28 ERROR:ERROR: Attempted to get in ByteBuffer (pos: 32 size: 46) value with size: 16
    2010-06-01 21:32:28 ERROR:WorldSession::Update ByteBufferException occured while parsing a packet (opcode: 600) from client 192.168.30.2, accountid=23.
    2010-06-01 21:38:08 ERROR:ERROR: Attempted to get in ByteBuffer (pos: 32 size: 46) value with size: 16
    2010-06-01 21:38:08 ERROR:WorldSession::Update ByteBufferException occured while parsing a packet (opcode: 600) from client 192.168.30.2, accountid=23.

    (i daily check logs and try to understand all errors/warnings. But i never saw those before, so i thought maybe worth mentioning)

  2. Sometimes, due to server crashes or when updating the database to newer server revisions, "trash" data can be left behind. This can include old spells, items, and pets that are no longer used or have changed IDs, instances that did not reset correctly, mail that was not properly deleted, and so forth.

    These "Character Cleaning" SQL scripts attempt to find and remove this old data. Having an accurate, up to date database is important to prevent crashes and "bugged" characters that may become unplayable due to faults in their data. Be careful which cleaning script you choose. Make sure it is for your server and database version, plus check that it uses proper procedures like creating backups in case an error is made and data needs to be restored as well as using IF EXISTS with DELETE and INSERT instead of simply using REPLACE INTO when modifying tables.

    To be safe, always make sure you run your own backup of any tables before modifying or cleaning them with any scripts or queries.

    I think they are referring to:

    http://github.com/mangos/mangos/commit/1d1ec20a02eccb9fb3fd43156146f7e71b482c19

  3. Ok, thanks for the feedback guys.

    It's good to know where it originated from, and that the mentioned querry can be executed safely. :)

    Though, a question still remains: Since mangos maintains the character DB, shouldn't this querry be added to the sql-updates?

    -The skill, like mentioned here, doesn't exist anymore at all.

    -Characters-databases not having any guids with this skill, won't be hurt with running the querry. While (older) characters-databases that do have guids with this skill, will recieve a mini cleanup with running the querry, wich can only be a good thing imho.

  4. I started using Mangos, UDB and SD2 (and eventAI/acid later) when the client was somewhere around 2.3.x.

    Think Mangos was around milestone 0.9 then if I remember correctly.

    Me and some 10-15 other accounts (family & friends) are still enjoying playing, and are very very thankfull to all that make this possible.

    I still have my very first realmd DB and character DB in use (dating +- 2 dec 2007).

    Now runing rev 9765 atm, always having applied sql updates along the way, with great care.

    (Big 'salute!' to you guys, since it shows that all realmd & characters sql-updates were/are nearly flawless! :))

    Not a single character on this server has ever had any gm-commands intervention in terms of stats/gear/spells/... .

    And core has never recieved any other patches than SD2.

    Yet is seems that some chars have some skills wich don't exist anymore.

    example:

    2010-04-26 17:45:27 ERROR:Character 79 has skill 40 that does not exist.

    After checking here:

    http://wiki.udbforums.kicks-ass.net/index.php/SkillLine.dbc

    It indeed doesn't list 'skill 40'

    (I have no idea what 'skill 40' actually was)

    Some older(<-edit) chars do have these skills though in the DB, and one guid even learned it to max skill:

    http://img690.imageshack.us/img690/425/skill40.jpg

    Small possibility I missed an sql-update along the years, or one didn't get fully applied (but I think not (and hope not)).

    Should that not be the case, adding somethin like:

    DELETE FROM character_skills where skill=40;

    to the sql-updates of the char DB might be a good idea I think.

    Let alone for the long-time users who like to keep things clean. :)

    Cheers,

    Herr_Trigger

  5. First off, this is looking awesome. So I have been trying to get it running last night, but sadly I couldn't.

    The thing preventing me from being succesfull is purely my knowledge about sql. (complete noob, yet succeeded in getting MBA and mw-enh running before)

    So after googling all night yesterday i hope somebody would be so kind to show me some direction. :)

    Thing is I just can't get the huge sql file imported. (edit: talking about "wowarmory_rc1_r50.sql")

    Importing it with sqlyog ended up in the "Line no.:7758

    Error Code: 1153 - Got a packet bigger than 'max_allowed_packet' bytes" error.

    Looking at your readme i fired up google and started searching.

    After tons of posts reading, I ended up adding these settings to the bottom of my "my.ini".

    max_allowed_packet=64M
    query_cache_size = 16M
    query_cache_limit = 2M
    max_connections=500
    wait_timeout = 90

    Restarted pc and tried again with sqlyog-> mysql crashed completely but got a lot further than before.

    So another pc restart. Opened up command line client and used:

     
    use [your database]
    source [path/to/file.sql]
    

    It started importing but after some time, again, mysql completely crashed.

    So I tried to overcome but i failed and i would really like to learn how to get it imported fine.

    Thanks in advance,

    [sCW]Hr_Trigger

  6. Awesome website. I was also looking for one, and I got my set up and everything, but when I go to post a thread for news, etc. it says "You must select a character before you can post." I've looked all over to find out the problem, and I know on the top right there's a drop down menu where you can select the character, but I do that and nothing happens.

    (Hopefully this isn't advertising, but you can try looking (http://partizans.servegame.com/))

    Posting working fine here.

    Great website btw. :)

  7. Can't compile on the latest version. 8754.

    1>------ Build started: Project: tbb, Configuration: Release Win32 ------
    1>Assembling...
    1>'ml.exe' is not recognized as an internal or external command,
    1>operable program or batch file.
    1>Project : error PRJ0019: A tool returned an error code from "Assembling..."
    1>Build log was saved at "file://f:\\games\\World_of_Warcraft_LAN\\mangos_origin\\win\\VC90\\tbb__Win32_Release\\BuildLog.htm"
    1>tbb - 1 error(s), 0 warning(s)
    2>------ Build started: Project: tbbmalloc, Configuration: Release Win32 ------
    2>Assembling...
    2>'ml.exe' is not recognized as an internal or external command,
    2>operable program or batch file.
    2>Project : error PRJ0019: A tool returned an error code from "Assembling..."
    2>Build log was saved at "file://f:\\games\\World_of_Warcraft_LAN\\mangos_origin\\win\\VC90\\tbbmalloc__Win32_Release\\BuildLog.htm"
    2>tbbmalloc - 1 error(s), 0 warning(s)
    3>------ Build started: Project: shared, Configuration: Release Win32 ------
    3>Extract revision
    3>Build log was saved at "file://f:\\games\\World_of_Warcraft_LAN\\mangos_origin\\win\\VC90\\shared__Win32_Release\\BuildLog.htm"
    3>shared - 0 error(s), 0 warning(s)
    4>------ Build started: Project: realmd, Configuration: Release Win32 ------
    4>Linking...
    4>LINK : fatal error LNK1181: cannot open input file '..\\..\\dep\\lib\\win32_release\\tbbmalloc.lib'
    4>Build log was saved at "file://f:\\games\\World_of_Warcraft_LAN\\mangos_origin\\win\\VC90\\realmd__Win32_Release\\BuildLog.htm"
    4>realmd - 1 error(s), 0 warning(s)
    5>------ Build started: Project: mangosd, Configuration: Release Win32 ------
    5>Linking...
    5>LINK : fatal error LNK1181: cannot open input file '..\\..\\dep\\lib\\win32_release\\tbbmalloc.lib'
    5>Build log was saved at "file://f:\\games\\World_of_Warcraft_LAN\\mangos_origin\\win\\VC90\\mangosd__Win32_Release\\BuildLog.htm"
    5>mangosd - 1 error(s), 0 warning(s)
    6>------ Build started: Project: script, Configuration: Release Win32 ------
    6>Linking...
    6>LINK : fatal error LNK1181: cannot open input file 'mangosd.lib'
    6>Build log was saved at "file://f:\\games\\World_of_Warcraft_LAN\\mangos_origin\\win\\VC90\\script__Win32_Release\\BuildLog.htm"
    6>script - 1 error(s), 0 warning(s)
    ========== Build: 1 succeeded, 5 failed, 7 up-to-date, 0 skipped ==========
    

    Where the heck did i go wrong?

    8745 compiled fine here, winxp 32bit, release. :)

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use