Lot Posted September 30, 2010 Report Share Posted September 30, 2010 (edited) My TT character, LotTT, finally ran in to the blank wall of the manufacturing terminal while trying to access device recipes. Analyzed a batch of vendor sold devices which raised the total of device recipes known from 339 up to 357. Recipes for devices could be accessed with the total at 339. By default I used the UDP packet optimization option. The proxy logs a bunch of OP code zero errors and then tries to recover by skipping the whole sequence. I tried enabling and disabling the UDP packet optimization option and the prototype packet re-ordering option to no joy. Below are some log excerpts sorry cannot indicate which options were used with each excerpt. Ah well, it seems like this issue has been around for some time now yet not many encounter it. If I can provide any other information to help figure out the problem, I will. Not sure what else to hope for really. 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:40 ERROR: Continuation opcode found as normal packet sequence. Attempting to recover by skipping whole sequence. 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:40 ERROR: Continuation opcode found as normal packet sequence. Attempting to recover by skipping whole sequence. 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:03 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:04 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:05 Bad opcode through to Proxy: 0x2074 Length: 0x6e75 30/09/10 23:57:40 ERROR: Continuation opcode found as normal packet sequence. Attempting to recover by skipping whole sequence. Edited October 8, 2010 by Dakynos used spoiler for code list Link to comment Share on other sites More sharing options...
Lannister Posted October 1, 2010 Report Share Posted October 1, 2010 Lott, Sorry to hear it - mine seems to be working again with the new launcher. Did you try both the options on the new loader? Link to comment Share on other sites More sharing options...
Lot Posted October 2, 2010 Author Report Share Posted October 2, 2010 Did you try both the options on the new loader? Yes, I have. Generally what happens is the proxy spews out op code errors on to the log and uses up a lot of virtual memory. And usually when the proxy bloats up it eventually crashes. I try again every now and then to load the device list in the manufacturing terminal to see if anything is different. If it were just packet loss then randomly every now and then the devices would load. It might be useful to be able to specify into the launcher a path MTU e.g. 1400 or whatever. WTB net7proxy source code for debugging PST Link to comment Share on other sites More sharing options...
Lot Posted October 11, 2010 Author Report Share Posted October 11, 2010 Tried again this morning to access device recipes on my TT, LotTT. Packet optimization (1500 UDP) - Tried twice both times proxy crashed. Without packet optimization or prototype re-ordering options set (500 UDP) - Tried once, firewall showed traffic for a minute or so and then traffic stopped, proxy log showed an op code error, exited my TT from terminal and tried to quit to desktop, client did not respond. Killed client. It may be purely incidental -- the server right at that moment either got restarted or ... crashed. Uhm I won't try accessing device recipes again for the time being. NB. Device recipe count is now 362. Link to comment Share on other sites More sharing options...
Lot Posted October 12, 2010 Author Report Share Posted October 12, 2010 It may be purely incidental -- the server right at that moment either got restarted or ... crashed. Uhm I won't try accessing device recipes again for the time being. I thought yesterday was just a weird coincidence and I had tried before the September content push to download devices without options set on the launcher and it didn't seem to cause anything bad to happen except no recipes being displayed in the terminal. On a whim this morning I tried the launcher again without options and logged into my TT and went to try to show device recipes in the manufacturing terminal. Traffic for a while, traffic stopped, proxy log op code error, client didn't respond to quit to desktop, killed client. And the server died right at that moment. Once might have been a coincidence but twice ... err wtf. Link to comment Share on other sites More sharing options...
Lannister Posted October 12, 2010 Report Share Posted October 12, 2010 And the server died right at that moment. Once might have been a coincidence but twice ... err wtf. So its your fault the servers down? I guess you could keep crashing the server until the pay attention, but perhaps opening a ticket would be better. Link to comment Share on other sites More sharing options...
Lot Posted October 13, 2010 Author Report Share Posted October 13, 2010 So its your fault the servers down? I guess you could keep crashing the server until the pay attention, but perhaps opening a ticket would be better. I did bug report it after starting this thread. Between bug reporting it and now there has been a content push -- before the content push when I tested downloading devices the server definitely didn't crash. It seems to be more than just coincidence that the two times I've tested downloading devices since the content push each test ended right the moment the server crashed. Would be nice to know one way or another if it was indeed connected. My scout / backup device builder is building up a nice catalog of devices. My TT is still accumulating device recipes and may reach the 400th before long. I estimate there is in excess of 600 devices to map in total. Link to comment Share on other sites More sharing options...
C Del[IS] Posted October 13, 2010 Report Share Posted October 13, 2010 If loading your device list is crashing the server, keep doing it. If this really is the source of a crashbug, we want to find the problem and fix it. Link to comment Share on other sites More sharing options...
Lot Posted October 13, 2010 Author Report Share Posted October 13, 2010 If loading your device list is crashing the server, keep doing it. If this really is the source of a crashbug, we want to find the problem and fix it. Alright ... *holds a gun and points it at the server* if you're certain C Del!!! *Pulls trigger* Link to comment Share on other sites More sharing options...
Lot Posted October 13, 2010 Author Report Share Posted October 13, 2010 Wow, I can see devices again in the manufacturing terminal - 386/387 of them. Tried without options on the launcher to begin with -- which I thought was crashing the server when I tried to download device recipes -- and I was very surprised to see device recipes again. Then I tried again without options and it worked again. And then I tried with packet optimization (my preferred option) and that worked too. Was something fixed? I've gained 30ish more recipes but I don't think gaining more recipes could fix the problems. Glad to see my device recipes again. Glad to have NOT crashed the server. Link to comment Share on other sites More sharing options...
C Del[IS] Posted October 13, 2010 Report Share Posted October 13, 2010 Wow, I can see devices again in the manufacturing terminal - 386/387 of them. Tried without options on the launcher to begin with -- which I thought was crashing the server when I tried to download device recipes -- and I was very surprised to see device recipes again. Then I tried again without options and it worked again. And then I tried with packet optimization (my preferred option) and that worked too. Was something fixed? I've gained 30ish more recipes but I don't think gaining more recipes could fix the problems. Glad to see my device recipes again. Glad to have NOT crashed the server. Huh. Maybe is was fixed. I know Tienbau has been working on solutions to our lag problems; maybe he fixed this along the way. Link to comment Share on other sites More sharing options...
Recommended Posts