Go Back   EQEmulator Home > EQEmulator Forums > Support > Support::Windows Servers

Support::Windows Servers Support forum for Windows EQEMu users.

Reply
 
Thread Tools Display Modes
  #1  
Old 04-26-2007, 09:57 PM
vafe
Fire Beetle
 
Join Date: Dec 2006
Posts: 11
Default Problems with opcode's

Not sure what the problem is. Unpatched out of the box titanium. This went on for at least 30 pages. editied down for example.

Code:
[04.27. - 06:20:26] [WORLD__CLIENT] New connection from 00.000.000.000:000
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: First opcode 0x7752 did not match expected 0x2792
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: Tried patch 6.2_world, and it did not match.
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: First opcode 0x7752 did not match expected 0x4dd0
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: Tried patch Titanium_world, and it did not match.
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: First opcode 0x7752 did not match expected 0x2154
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: Tried patch Live_world, and it did not match.
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: First opcode 0x7752 did not match expected 0x7772
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: Tried patch Live_zone, and it did not match.
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: First opcode 0x7752 did not match expected 0x2792
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: Tried patch 6.2_world, and it did not match.
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: First opcode 0x7752 did not match expected 0x4dd0
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: Tried patch Titanium_world, and it did not match.
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: First opcode 0x7752 did not match expected 0x2154
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: Tried patch Live_world, and it did not match.
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: First opcode 0x7752 did not match expected 0x7772
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: Tried patch Live_zone, and it did not match.
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: First opcode 0x7752 did not match expected 0x2792
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: Tried patch 6.2_world, and it did not match.
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: First opcode 0x7752 did not match expected 0x4dd0
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: Tried patch Titanium_world, and it did not match.
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: First opcode 0x7752 did not match expected 0x2154
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: Tried patch Live_world, and it did not match.
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: First opcode 0x7752 did not match expected 0x7772
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: Tried patch Live_zone, and it did not match.
[04.27. - 06:20:26] [NET__IDENT_TRACE] 00.000.000.000:000: First opcode matched 0x7213 and length matched 68
[04.27. - 06:20:26] [NET__IDENTIFY] Identified stream 00.000.000.000:000 with signature Titanium_zone
[04.27. - 06:20:26] [WORLD__CLIENT] New client from 00.000.000.000:000
Reply With Quote
  #2  
Old 04-26-2007, 10:46 PM
Angelox
AX Classic Developer
 
Join Date: May 2006
Location: filler
Posts: 2,049
Default

I think 00.000.000.000 is supposed to be a (legal) IP, and :000 a port - Looks like that's not working.
I don't know what you're doing but I guess minilogin and a client from the same machine?
if so then for example 127.0.0.1:129 would look more normal or 192.168.2.102:129. The opcodes are working fine, that's what they are supposed to do.
Reply With Quote
  #3  
Old 04-26-2007, 11:54 PM
vafe
Fire Beetle
 
Join Date: Dec 2006
Posts: 11
Default

I apologize. Figured you guys would notice that right off the bat as and edit. Anyways I changed those to 0's myself. The ip is fine, what im concerned with is the 30 pages of it not finding the correct patch or whatever. I was wondering what was causing the lag from me clicking the OK button on the server select to get the load screen to take me to char select.
Reply With Quote
  #4  
Old 04-27-2007, 02:14 AM
techguy84's Avatar
techguy84
Discordant
 
Join Date: Apr 2007
Location: Somewhere Safe
Posts: 453
Default

I get that error myself all the time. I ignore it as it goes right on through after only saying it once. Not sure what your problem is. Can you provide the following:

Eqemu_config.xml

What version of Mysql, Emulator, are you running. What database are your using. What guide did you follow to set up the server.

Did you exract all the files perfectly, or were there errors.

Also, if your using the Minilogin, lets see your Loginserver.ini file

I thought you had this server going though, Nhauk's PVP or something like that. I remember you said you were running a 5x xp rate but had to change it.
Reply With Quote
  #5  
Old 05-10-2007, 11:46 PM
Lamec
Fire Beetle
 
Join Date: Apr 2007
Posts: 16
Default

Quote:
Originally Posted by techguy84
I get that error myself all the time. I ignore it as it goes right on through after only saying it once. Not sure what your problem is. Can you provide the following:

Eqemu_config.xml

What version of Mysql, Emulator, are you running. What database are your using. What guide did you follow to set up the server.

Did you exract all the files perfectly, or were there errors.

Also, if your using the Minilogin, lets see your Loginserver.ini file

I thought you had this server going though, Nhauk's PVP or something like that. I remember you said you were running a 5x xp rate but had to change it.

I'm getting this error quite a bit, and have been able to narrow it down some. This seems to happen after someone gets "dumped" from the server (not exactly sure why they're getting dumped, but I have some ideas..) Then, then try to log back in, and this op code spins wildly through trying to log them back in (0x7752) and doesn't match, for whatever reason (I looked this up, says it's OP_AckPacket, not sure what that means...) If I reboot the server, problem goes away, if they log on a different char, no problems there... But if they try to log that client back on, spam the 7752s.

Some times, it gets "unhung", meaning it's spins off the bad opcode messages until it sees the good code 0x7213, then it goes about its business. I've had this spin for hundreds of lines of opcode messages within a single minute... So, it's trying real hard to do something (I'm guessing disconnect them?)

Now, into why this is happening (again, a guess, but we're narrowing it down.)

My setup is like this: Network->my machine (and server)->internet modem (using windows ICS for the internal folks to share my connection to the outside...) It seems, if someone from the internal network encounters people coming in from the outside (the internet some where...) It's crashing both of them, and putting them into some weird state on the server (no zone id, etc..) Yet, not disconnecting them, and not letting them log back in (bad opcode 0x7752, over and over...)

I'm not sure if this is only occuring if two people from the internal network encounter someone from the outside (though I'm sure that's one case where it is hanging) or if they encounter anyone (no need for two of us to be in the zone...)

So, example: I'm in the bazaar, and Fred (from some outside ip) is there with me. Someone else on my internal network (say Gomer) zones to the bazaar, and both Fred and Gomer lock up and can't get back in (now Gomer might be able to get back in, but Fred is screwed...) And I get to watch and wonder why they're both locked up and can't get back in (or at least Fred can't for sure...) Once again, if I restart the server, Fred is un-screwed.. As long as he doesn't see Gomer... LOL


I'd sure like to fix this, but I guess we can avoid internal network people "seeing" external network people... (he's a builder for heaven's sake, he needs access...)

But, to relate it to the topic, I don't think the 0x7752 is being handled correctly, it shouldn't put 500k of bad opcode messages into the log file in a matter of 2 minutes (for one client) before the client finally gives up and goes to play on another server...
Reply With Quote
  #6  
Old 05-13-2007, 08:42 AM
CrabClaw's Avatar
CrabClaw
Hill Giant
 
Join Date: Jun 2006
Location: Plane of Knowledge
Posts: 191
Default

Hmm, a couple thoughts, if one guy is log-ing out the other, check their IP's in the databases account table. They might have the same one, also make sure none of the account values are 127.0.0.1 that will cause problems too.
Reply With Quote
  #7  
Old 05-13-2007, 02:00 PM
Lamec
Fire Beetle
 
Join Date: Apr 2007
Posts: 16
Default

Thanks for the suggestion. Since it's not the mini login, the ip addresses in the account table aren't used. The users on the interneral network all have 198.0.x.x addresses, and they're all unique. So, I don't think that's it.

And if they don't go into the same zone as someone on an external ip, everything is ok =\ oddly enough..

Thanks for pondering it at least
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

   

All times are GMT -4. The time now is 03:13 AM.


 

Everquest is a registered trademark of Daybreak Game Company LLC.
EQEmulator is not associated or affiliated in any way with Daybreak Game Company LLC.
Except where otherwise noted, this site is licensed under a Creative Commons License.
       
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Template by Bluepearl Design and vBulletin Templates - Ver3.3