View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001785SphereServerexecutable - genericpublic26-07-10 11:3727-07-10 17:23
Reporterumuri 
Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOSOS Version
Product Version0.56c Nightly 
Target VersionFixed in Version 
Summary0001785: Telnet thread stopped during resync, cannot resume
DescriptionWhen you resync via the telnet console, the telnet console can no longer send the second R command to wakeup from resync, using latest nightly build.

Tried all combination of network and telnet related ini settings, including ones only vaguely related, log, filter, async, and all EF flags.
 
Could not find a workable combination that allows proper resyncs via telnet.
TagsNo tags attached.
Nightly VersionNot Available
Experimental FlagsNew_Triggers, UseNetworkMulti
Option FlagsFileCommands, Buffs
Internal Build Number
Attached Files

- Relationships
related to 0001786resolvedShiryuX Prevent Telnet from resync pausing. 

-  Notes
(0000527)
umuri (reporter)
26-07-10 22:45

Umm, quick note.

This only affects the resync pause done with R, not the resync command. (Stupid me never knew a resync command was added, (51a veteran))
(0000528)
umuri (reporter)
26-07-10 23:33

Found a workaround for the issue, so i guess it can be downgraded from major to minor, since resync does technically still work.

turn on telnet packet filter in options and add:
PACKET114=f_telnet_resync_block

and

[function f_telnet_resync_block]
//Packet 114
if ( <local.0> == 072 ) && ( <local.num> == 03 )
    serv.log Resync blocked to prevent telnet from hanging the server!
    return 1
endif

Blocks R to start the resync pause, but allows resync to do the full cycle.
(0000529)
MrSugarCube (administrator)
27-07-10 17:23

There isn't really anything wrong going on here. Sphere won't process any client data received during a resync pause, so if you're going to resync from a client then (as you've already found out) you should be using the 'resync' command.

- Issue History
Date Modified Username Field Change
26-07-10 11:37 umuri New Issue
26-07-10 11:37 umuri Nightly Version => Not Available
26-07-10 11:37 umuri Experimental Flags => New_Triggers, UseNetworkMulti
26-07-10 11:37 umuri Option Flags => FileCommands, Buffs
26-07-10 22:45 umuri Note Added: 0000527
26-07-10 23:33 umuri Note Added: 0000528
27-07-10 17:23 MrSugarCube Status new => closed
27-07-10 17:23 MrSugarCube Note Added: 0000529
27-07-10 17:23 MrSugarCube Resolution open => no change required
18-08-10 22:08 ShiryuX Relationship added related to 0001786


Copyright © 2000 - 2010 MantisBT Group
Powered by Mantis Bugtracker