MantisBT - Doomseeker
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000258Doomseeker[All Projects] Bugpublic2011-01-10 04:502018-09-29 14:49
ReporterGreg 
Assigned ToBlzut3 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformMicrosoftOSWindowsOS VersionXP/Vista/7
Product Version0.7 Beta 
Target VersionFixed in Version0.8 Beta 
Summary0000258: Unable to connect to master list.
DescriptionUsing 0.7 Beta, I am unable to connect to any servers. The servers will show on Doomseeker, however they all show <NO RESPONSE>.

Using 0.6b, I can play and connect to all active servers.
Steps To Reproduce
Additional Information[23:41:05] Starting Doomseeker. Hello World! :)
[23:41:05] Setting up data directories.
[23:41:05] Loaded plugin: "Chocolate Doom"!
[23:41:05] Loaded plugin: "Odamex"!
[23:41:05] Loaded plugin: "Skulltag"!
[23:41:05] Loaded plugin: "Vavoom"!
[23:41:05] Loaded plugin: "ZDaemon"!
[23:41:05] Initializing IP2C database.
[23:41:05] Initializing configuration file.
[23:41:05] Setting INI file: C:/Users/Owner/AppData/Roaming/.doomseeker/doomseeker.ini
[23:41:05] Ini file is: C:/Users/Owner/AppData/Roaming/.doomseeker/doomseeker.ini
[23:41:05] Initializing configuration for plugins.
[23:41:05] Initializing IRC configuration file.
[23:41:05] Setting IRC INI file: C:/Users/Owner/AppData/Roaming/.doomseeker/doomseeker-irc.ini
[23:41:05] Ini file is: C:/Users/Owner/AppData/Roaming/.doomseeker/doomseeker-irc.ini
[23:41:05] Starting refreshing thread.
[23:41:05] Preparing GUI.
[23:41:08] Total refresh process initialized!
[23:41:09] Init finished.
================================
[23:41:08] Starting IP2C parser thread.
[23:41:08] Parsing IP2C database: C:/Users/Owner/AppData/Roaming/.doomseeker/IpToCountry.csv
[23:41:09] IP2C Database read in 807 ms. Entries read: 106695
[23:41:09] IP2C Parsing thread has finished.
[23:41:09] IP2C parsing finished.
[23:41:18] Error: Master server for Odamex: Connection timeout (76.74.252.88:15000).
[23:41:18] Error: Master server for Chocolate Doom: Connection timeout (2002:5CF3:1FAF:0:0:0:0:1:2342).
[23:41:18] Error: Master server for Vavoom: Connection timeout (66.45.244.219:26001).
[23:41:18] Error: Master server for Skulltag: Connection timeout (178.79.132.45:15300).
[23:41:18] Reloading master server results from cache for Skulltag!
[23:41:18] Error: Master server for ZDaemon: Connection timeout (69.94.108.99:15300).
[23:41:24] No flag for country: CRI
[23:41:49] Finished refreshing. Servers on the list: 478 (+ 0 custom). Players: 0.
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-01-10 04:50GregNew Issue
2011-01-10 04:57GregNote Added: 0000799
2011-01-10 18:28user35Note Added: 0000801
2011-01-10 18:29user35Note Edited: 0000801bug_revision_view_page.php?bugnote_id=801#r372
2011-01-10 20:09Blzut3Note Added: 0000804
2011-01-10 20:10Blzut3Statusnew => confirmed
2011-01-11 01:17Blzut3Statusconfirmed => resolved
2011-01-11 01:17Blzut3Fixed in Version => 0.8 Beta
2011-01-11 01:17Blzut3Resolutionopen => fixed
2011-01-11 01:17Blzut3Assigned To => Blzut3
2011-01-11 01:19Blzut3Note Added: 0000807
2012-06-09 13:22Torr SamahoCategoryGeneral => Bug
2018-09-29 14:49WubTheCaptainStatusresolved => closed

Notes
(0000799)
Greg   
2011-01-10 04:57   
Tried with Router, and directly connected to modem with no success.

Rolled back a version to 0.6b and worked fine.

Tried SVN r594, even latest build wasn't connecting.

Router is Linksys Wireless-G WRT54G that has been flashed with DD-WRT.
(0000801)
user35   
2011-01-10 18:28   
(edited on: 2011-01-10 18:29)
well, my problem with doomseeker is that he cannot start! I recently downloaded skulltag again and noticed that Doomseeker.exe doesn't want to start (this happend few days ago)
I tried reistalling it, downloading doomseeker 0.6 from website and getting the same fucking error?
EDIT: yes I know, if I had problems, I was supposted to report this bug but I just put here
(0000804)
Blzut3   
2011-01-10 20:09   
The problem is the chocoalte doom master is now returning an ipv6 address. In the mean time you can disable that and Doomseeker will work fine.
(0000807)
Blzut3   
2011-01-11 01:19   
Fixed for now. Hopefully either ipv6 will start working for most people or someone will figure out the proper solution.

Apparently trying to query an ipv6 address causes the socket to reopen which was causing a bunch of problems with the way Doomseeker queries.