FlexHub Forum

DC ping not look hub

DC ping not look hub
« on: March 10, 2013, 19:36:54 »
The hub didn't send any message for more than 10 seconds and this exceeded the default internal Timeout. This may happen because of a problem with the hubsoft. For more information please contact our support by sending a Ticket from "DashBoard" menu or email us to
this is new hub 1409 i have problem ping hub

Re: DC ping not look hub
« Reply #1 on: March 10, 2013, 20:48:05 »
do you have any logs of how far it got, any error messages?

/1d

Re: DC ping not look hub
« Reply #2 on: June 08, 2013, 11:06:29 »
I have the same problem.
log message from dchublist.com

0.5042 <> Socket created
0.5043 <> Connected
0.6912 >> $Lock EXTENDEDPROTOCOL_FLEXHUB_MULTIPROTOCOL_ZZQJ Pk=version0.2
0.6917 << $Supports BotINFO NoGetINFO|$Key �Ҁ��A ѱ�@01���ρбϡ���ё ѱ�@01P/%DCN000%/��|
0.6918 >> $ValidateNick dchublist|$BotINFO DcHublistPinger|
0.6922 >> $HubName Megalan_BG
0.9879 >> $Supports BotINFO NoGetINFO
1.2893 >> $Hello dchublist
1.2896 << $Version 1,0091|$GetNickList|$MyINFO $ALL dchublist DcHublistPinger<++ V:0.761,M:A,H:0/0/1,S:5>$ $Cable1$admin@dchublist.com$163353712394$|
1.2899 >> $HubINFO Megalan_BG$megalan.no-ip.org:411$=== Forgotten Megalan Users ===$2000$2147483648$2$100$FlexHubBeta 0.2$n/a
1.5900 >> $HubName Megalan_BG -
1.5904 >> $MyINFO $ALL FlexBot FlexHub Security$ $$$0$
1.5908 >> $MyINFO $ALL [Megalan]Scarface [NMDC] <ApexDC++ V:1.5.6,M:A,H:8/1/1,S:20>$ $50$Kyle@mail.bg$272681892725$
1.5911 >> $MyINFO $ALL dchublist [NMDC] DcHublistPinger<++ V:0.761,M:A,H:0/0/1,S:5>$ $Cable1$admin@dchublist.com$163353712394$
1.5914 >> $OpList FlexBot$$[Megalan]Scarface$$
1.5916 >> <FlexBot> FlexHub Beta 0.2 svn: 1417 - Made by Daywalker, FlipFlop and en_dator.
1.5969 >> <FlexBot>
                Welcome to megalan.no-ip.org:411

   ********************************************************************************
      General Hub information
   ********************************************************************************
 bla bla bla

11.5981 <> Hub checked in 12 seconds
11.9065 !! New address is not online or cannot be resolved
11.9392 <> Disconnecting
11.9393 <> Done stats for megalan.no-ip.info:411 - 78.90.223.109:411

log message from Feed.log
[08/06/2013 11:43:07] <FlexBot> Pinger detected from IP: 64.31.32.183 with name: dchublist                                            is kicking because:

What is wrong?
10x in advance.

Re: DC ping not look hub
« Reply #3 on: June 08, 2013, 18:07:02 »
when i renamed name of the hub from .org to .info message - New address is not online or cannot be resolved - disappeared./I forgot to do it/ ???
But error message "The hub didn't send any message for more than 10 seconds and this exceeded the default internal Timeout........"is still there.

Is that a problem?

Re: DC ping not look hub
« Reply #4 on: June 25, 2013, 23:20:35 »
That message doesn't come from Flexhub, the hub wont send any messages unless it needs to, so why the pinger complains about that I don't know.

As far as I can tell the hub does what it is supposed to, you need to make sure that the addy you have registered on the pinger does resolve to the correct ip, not sure there is much else that can be done unless dchublist admin can show that Flex does something wrong.

I see both dchublist and hublist.eu ping my hub without problems so I think everything is ok.