rilex

I know, I'm a slacker -- I said I'd get a tutorial out there. I'm going to update the relase version first and then do a document. As I said in my PM though, this doesn't support Apache since it requires .NET 3.5 (plus, I'm not an Apache guy myself!).

Build 22992 now includes an AJAX Rich Text Editor from www.codeplex.com/rte for the Message of the Day as well as the Terms of Service, so you can have colored text/smilies instead of plain text. Review the commit notes for various changes.

FYI the latest update, 22978, enables downloading images from the web when there is a missing ItemID entry in the lookup_itemfilename table. Read the SVN commit notes.

You can use telnet to connect to smtp ...

I guess my question was, is RA using the telnet protocol or something home-brewed?

Is the RA just a standard telnet server application, or something else entirely?

I've confirmed that MicroManager supports 3.0.9 without any issues, as long as you've set it up to use the 3.0.3 (0.13) setting in Setup.aspx. Also, as of rev 22918, we are no longer using the ASP.NET Session State service. That service can be disabled in services.msc (unless you have other ASP.NET apps using it, of course). This means some changes to the web.config, specifically the sections marked in bold: <system.web> <sessionState mode="InProc" cookieless="AutoDetect" timeout="2880"/> <authentication mode="Forms"> <forms loginUrl="Login.aspx" name="MICROMANAGER" protection="All" path="/" timeout="1440" slidingExpiration="true" defaultUrl="~/Default.aspx"/> </authentication>

It cannot be done with the current architecture of MaNGOS. Good luck on writing it!

One particular player (two different accounts, same client machine) logs in and crashes the server Revision: * * 7252 0b3748bf5f75c34695f9ed1b9cfb929f1d2d3aef Date 9:2:2009. Time 16:29 //===================================================== *** Hardware *** Processor: Intel(R) Pentium(R) III CPU - S 1400MHz Number Of Processors: 2 Physical Memory: 3997184 KB (Available: 3333772 KB) Commit Charge Limit: 4194303 KB *** Operation System *** Microsoft Windows Server 2003 Enterprise Edition Service Pack 2 (Version 5.2, Build 3790) //===================================================== Exception code: C0000005 ACCESS_VIOLATION Fault address: 00850A87 01:0044FA87 C:\\Mangos\\mangosd.exe Registers: EAX:0000004B EBX:03F69140 ECX:00000000 EDX:00000000 ESI:00000000 EDI:00000000 CS:EIP:001B:00850A87 SS:ESP:0023:04DFEECC EBP:04DFEEDC DS:0023 ES:0023 FS:003B GS:0000 Flags:00010246 Call stack: Address Frame Function SourceFile 00850A87 00000000 ?GetFloatDefault@Config@@QAEMPBDM@Z+977 006802FB 00000000 ?_setMoveData@?$FleeingMovementGenerator@VPlayer@@@@AAE_NAAVPlayer@@@Z+F2DB 0067A57F 00000000 ?_setMoveData@?$FleeingMovementGenerator@VPlayer@@@@AAE_NAAVPlayer@@@Z+955F 00828C37 00000000 ?HandleCastSpellOpcode@WorldSession@@QAEXAAVWorldPacket@@@Z+2E7 005F7196 00000000 ?Update@WorldSession@@QAE_NI@Z+176 006214B4 00000000 ?ReadMovementInfo@WorldSession@@QAEXAAVWorldPacket@@PAUMovementInfo@@@Z+28774 0061D320 00000000 ?ReadMovementInfo@WorldSession@@QAEXAAVWorldPacket@@PAUMovementInfo@@@Z+245E0 0043890F 00000000 ?getSource@?$Reference@V?$GridRefManager@VCorpse@@@@VCorpse@@@@QBEPAVCorpse@@XZ+209DF 008A1635 00000000 ?step@barGoLink@@QAEXXZ+1BA45 008A1A93 00000000 ?step@barGoLink@@QAEXXZ+1BEA3 008A5B47 00000000 ?step@barGoLink@@QAEXXZ+1FF57 78543433 00000000 _endthreadex+44 785434C7 00000000 _endthreadex+D8 77E64829 00000000 GetModuleHandleA+DF Call stack: Address Frame Function SourceFile 7C8285EC 00000000 KiFastSystemCallRet+0 77F65EDB 00000000 LookupPrivilegeValueW+114 77F65F82 00000000 LookupPrivilegeValueW+1BB 77FB75AF 00000000 StartServiceCtrlDispatcherA+93 0085063C 00000000 ?GetFloatDefault@Config@@QAEMPBDM@Z+52C 0043368B 00000000 ?getSource@?$Reference@V?$GridRefManager@VCorpse@@@@VCorpse@@@@QBEPAVCorpse@@XZ+1B75B 004390BB 00000000 ?getSource@?$Reference@V?$GridRefManager@VCorpse@@@@VCorpse@@@@QBEPAVCorpse@@XZ+2118B 77E6F23B 00000000 ProcessIdToSessionId+209 Call stack: Address Frame Function SourceFile 7C8285EC 00000000 KiFastSystemCallRet+0 77E61C8D 00000000 WaitForSingleObject+12 Call stack: Address Frame Function SourceFile 7C8285EC 00000000 KiFastSystemCallRet+0 77E61C8D 00000000 WaitForSingleObject+12 008A555E 00000000 ?step@barGoLink@@QAEXXZ+1F96E 008A1230 00000000 ?step@barGoLink@@QAEXXZ+1B640 008A03AC 00000000 ?step@barGoLink@@QAEXXZ+1A7BC 008884C0 00000000 ?step@barGoLink@@QAEXXZ+28D0 008A1635 00000000 ?step@barGoLink@@QAEXXZ+1BA45 008A1A93 00000000 ?step@barGoLink@@QAEXXZ+1BEA3 008A5B47 00000000 ?step@barGoLink@@QAEXXZ+1FF57 78543433 00000000 _endthreadex+44 785434C7 00000000 _endthreadex+D8 77E64829 00000000 GetModuleHandleA+DF Call stack: Address Frame Function SourceFile 7C8285EC 00000000 KiFastSystemCallRet+0 77E61C8D 00000000 WaitForSingleObject+12 008A555E 00000000 ?step@barGoLink@@QAEXXZ+1F96E 008A1230 00000000 ?step@barGoLink@@QAEXXZ+1B640 008A03AC 00000000 ?step@barGoLink@@QAEXXZ+1A7BC 008884C0 00000000 ?step@barGoLink@@QAEXXZ+28D0 008A1635 00000000 ?step@barGoLink@@QAEXXZ+1BA45 008A1A93 00000000 ?step@barGoLink@@QAEXXZ+1BEA3 008A5B47 00000000 ?step@barGoLink@@QAEXXZ+1FF57 78543433 00000000 _endthreadex+44 785434C7 00000000 _endthreadex+D8 77E64829 00000000 GetModuleHandleA+DF Call stack: Address Frame Function SourceFile 7C8285EC 00000000 KiFastSystemCallRet+0 77E61C8D 00000000 WaitForSingleObject+12 008A555E 00000000 ?step@barGoLink@@QAEXXZ+1F96E 008A1230 00000000 ?step@barGoLink@@QAEXXZ+1B640 008A03AC 00000000 ?step@barGoLink@@QAEXXZ+1A7BC 008884C0 00000000 ?step@barGoLink@@QAEXXZ+28D0 008A1635 00000000 ?step@barGoLink@@QAEXXZ+1BA45 008A1A93 00000000 ?step@barGoLink@@QAEXXZ+1BEA3 008A5B47 00000000 ?step@barGoLink@@QAEXXZ+1FF57 78543433 00000000 _endthreadex+44 785434C7 00000000 _endthreadex+D8 77E64829 00000000 GetModuleHandleA+DF Call stack: Address Frame Function SourceFile 7C8285EC 00000000 KiFastSystemCallRet+0 04DFDF24 00000000 0000:00000000 FF50D845 FFFFFFFF 0000:00000000 Call stack: Address Frame Function SourceFile 7C8285EC 00000000 KiFastSystemCallRet+0 77E61C8D 00000000 WaitForSingleObject+12 008A555E 00000000 ?step@barGoLink@@QAEXXZ+1F96E 008A1230 00000000 ?step@barGoLink@@QAEXXZ+1B640 008A03AC 00000000 ?step@barGoLink@@QAEXXZ+1A7BC 00434528 00000000 ?getSource@?$Reference@V?$GridRefManager@VCorpse@@@@VCorpse@@@@QBEPAVCorpse@@XZ+1C5F8 008A1635 00000000 ?step@barGoLink@@QAEXXZ+1BA45 008A1A93 00000000 ?step@barGoLink@@QAEXXZ+1BEA3 008A5B47 00000000 ?step@barGoLink@@QAEXXZ+1FF57 78543433 00000000 _endthreadex+44 785434C7 00000000 _endthreadex+D8 77E64829 00000000 GetModuleHandleA+DF Call stack: Address Frame Function SourceFile 7C8285EC 00000000 KiFastSystemCallRet+0 77E61C8D 00000000 WaitForSingleObject+12 008A555E 00000000 ?step@barGoLink@@QAEXXZ+1F96E 008A1230 00000000 ?step@barGoLink@@QAEXXZ+1B640 008A03AC 00000000 ?step@barGoLink@@QAEXXZ+1A7BC 0043414B 00000000 ?getSource@?$Reference@V?$GridRefManager@VCorpse@@@@VCorpse@@@@QBEPAVCorpse@@XZ+1C21B 008A1635 00000000 ?step@barGoLink@@QAEXXZ+1BA45 008A1A93 00000000 ?step@barGoLink@@QAEXXZ+1BEA3 008A5B47 00000000 ?step@barGoLink@@QAEXXZ+1FF57 78543433 00000000 _endthreadex+44 785434C7 00000000 _endthreadex+D8 77E64829 00000000 GetModuleHandleA+DF Call stack: Address Frame Function SourceFile 7C8285EC 00000000 KiFastSystemCallRet+0 71B21A03 00000000 0001:00000A03 C:\\WINDOWS\\system32\\MSWSOCK.dll 71C0283C 00000000 select+A1 10014AE5 00000000 ?wait_for_multiple_events@?$ACE_Select_Reactor_T@V?$ACE_Reactor_Token_T@VACE_Token@@@@@@MAEHAAVACE_Select_Reactor_Handle_Set@@PAVACE_Time_Value@@@Z+115 FFFFFFFF FFFFFFFF 0000:00000000 Call stack: Address Frame Function SourceFile 7C8285EC 00000000 KiFastSystemCallRet+0 71B21A03 00000000 0001:00000A03 C:\\WINDOWS\\system32\\MSWSOCK.dll 71C0283C 00000000 select+A1 10014AE5 00000000 ?wait_for_multiple_events@?$ACE_Select_Reactor_T@V?$ACE_Reactor_Token_T@VACE_Token@@@@@@MAEHAAVACE_Select_Reactor_Handle_Set@@PAVACE_Time_Value@@@Z+115 FFFFFFFF FFFFFFFF 0000:00000000 ======================== Local Variables And Parameters Call stack: Address Frame Function SourceFile 00850A87 00000000 ?GetFloatDefault@Config@@QAEMPBDM@Z+977 006802FB 00000000 ?_setMoveData@?$FleeingMovementGenerator@VPlayer@@@@AAE_NAAVPlayer@@@Z+F2DB 0067A57F 00000000 ?_setMoveData@?$FleeingMovementGenerator@VPlayer@@@@AAE_NAAVPlayer@@@Z+955F 00828C37 00000000 ?HandleCastSpellOpcode@WorldSession@@QAEXAAVWorldPacket@@@Z+2E7 005F7196 00000000 ?Update@WorldSession@@QAE_NI@Z+176 006214B4 00000000 ?ReadMovementInfo@WorldSession@@QAEXAAVWorldPacket@@PAUMovementInfo@@@Z+28774 0061D320 00000000 ?ReadMovementInfo@WorldSession@@QAEXAAVWorldPacket@@PAUMovementInfo@@@Z+245E0 0043890F 00000000 ?getSource@?$Reference@V?$GridRefManager@VCorpse@@@@VCorpse@@@@QBEPAVCorpse@@XZ+209DF 008A1635 00000000 ?step@barGoLink@@QAEXXZ+1BA45 008A1A93 00000000 ?step@barGoLink@@QAEXXZ+1BEA3 008A5B47 00000000 ?step@barGoLink@@QAEXXZ+1FF57 78543433 00000000 _endthreadex+44 785434C7 00000000 _endthreadex+D8 77E64829 00000000 GetModuleHandleA+DF ========================

Hmm, okay that doesn't work quite as I intended. When hitting stop from services.msc, the process begins to start again (?). In otherwords, if I check the log file, it re-uses the same log file. ...the service itself stops (and reflects that), and the process will stop a few seconds later (10 to 15 or so) and the log file will be cut off while loading a certain table. Kind of strange.

Ok, I must be blind. Where is the loop?

Is there a thread in mangosd that make sure it is still running? I'm trying to look into adding Windows Service support back to mangosd, as right now it is effectively broken since you cannot gracefully stop mangosd. If there is a thread that says "while not shutting down, do nothing (or, run a select query from our db, etc.)", support for stopping the service can probably be entered back in.

We've done this with microManager.

Would it be possible to implement non-exclusive read access to the logs? Currently StreamReader is unable to parse log files in use by MaNGOS due to MaNGOS holding exlusive read locks.

According to the help in the console, if you set the unban value to a negative, it is a permanent ban. However, if I do a -1 or -1d (which is the proper format here? Either?), it sets the same time as the ban time. I'm assuming MaNGOS does a comparison with the ban time and unban time, and if they're the same, that is a perm ban? Is this correct? EDIT: Duh, nevermind...I see it says "permanently banned". Sorry

Dual 2.4.3 and 3.0.3 support should be completed as of SVN rev 21217.

We're using ASP.NET 3.5 features, so it would not run on Linux with the Apache ASP.NET module. You can run it on a remote Win2000/XP/2003/Vista/2008 box, though. The Service Control page won't do anything for you (since under Linux you're using daemons and not Windows Services). If you have Samba set up, you can use the Mangos Configuration page edit your Mangos .conf files remotely. Always best to host Mangos on your web server on seperate boxes

We've decided to support both 2.4.3 and 3.0.3 within the same branch. SVN 21077 contains two new tables for the micromanager database that need to be imported. The configuration table was also updated with a SQL query in SVN 21074 to support this. The default value is to support 3.0.3 (expansion = 2). This can be changed in Setup.aspx. There is still some SQL queries to un-hard code the values from, but the Characters.aspx page is fully working with the new dynamic queries. There is also some work to do to enforce what patch level a user may select when creating or modifying their account.

We now support Patch revision 3.0.3 with WOTLK as of SVN revision 20903!

Ok, thanks!

In the Mangos source, is there a complete listing of zones along with the ID?

Could you implement that? Pretty please? With .NET we can just look at the file properties of the exe then.

That is only good if the current source happens to be on the server where Mangos is running.

Would it be possible for each exe, on startup, to insert a value into a table within the world db (a new table would be required)? Could just make an UPDATE statement upon startup that would fill in the revision number which is stored in the exe (as we can see from the log file).

Yep, this would be a web app extracting the revision information, so there would need to be some interface hook into doing so.