|
|
| Author |
Message |
cards
none
Joined: 10 Dec 2003
Posts: 4
|
 Posted: Apr 21, 2009 8:10pm Post subject: Network delisted, not sure why |
 |
|
According to the page, our network shows connection timeout. This doesn't seem to affect any of our users, and our DNS is up working fine. I tried emailing to have it reactivated without a reply after 5 days. Could someone please reactivate it, as I don't believe we are the ones with the issue.
Network: 420-mafia
DNS pool: irc.420-mafia.org
my Email: cards@420-mafia.org |
|
| Back to top |
|
 |
PingBad
Post Whore
Joined: 05 Feb 2005
Posts: 3027
Location: New Zealand
|
| Posted: Apr 21, 2009 9:16pm Post subject: |
|
|
tried looking at the network page of the network in question - the reason the bots aren't connecting to your network is because they can't get thru to it: | SearchIRC crawler wrote: | NOTE: This network does not appear to be currently indexed by SearchIRC. Possible reasons include: Network has been disbanded, SearchIRC index robots have been banned, SearchIRC index robots have been unable to connect to the network, or the network was recently added and has yet to undergo the nightly update process.
The last error received from the network was:
socket_connect() failed: Connection timed out to irc.420-mafia.net |
|
|
| Back to top |
|
|
bsd20
none
Joined: 05 Jul 2004
Posts: 4
Location: Massachusetts, USA
|
| Posted: Apr 22, 2009 9:58am Post subject: we know they couldn't |
|
|
We know they couldn't, we had a DNS issue that caused issues for about a week. The issues have since been corrected over a week ago to date, and we haven't seen any scrawl bots. Please put the network back active at your earliest convenience. Thanks. 
Bryan
(BSD)
420-Mafia IRC Network
Owner & Director of Network Operations |
|
| Back to top |
|
|
bsd20
none
Joined: 05 Jul 2004
Posts: 4
Location: Massachusetts, USA
|
| Posted: Apr 22, 2009 2:27pm Post subject: |
|
|
| Just as an FYI - we had irc.420-mafia.net listed for searchirc, and that is functioning. So when we say .org .net, its all the same, .com .net all point to .org. |
|
| Back to top |
|
|
PingBad
Post Whore
Joined: 05 Feb 2005
Posts: 3027
Location: New Zealand
|
| Posted: Apr 22, 2009 9:25pm Post subject: |
|
|
the network is considered still actively indexed if it experiences connection issues such as this. Only after trying for a week will scrawl decide the network isn't coming back and deactivate it accordingly.
As gleaned from the staff network modification pages: | Quote: | | Network name: 420-mafia Active1_Index Successful connection. |
|
|
| Back to top |
|
|
cards
none
Joined: 10 Dec 2003
Posts: 4
|
| Posted: May 06, 2009 3:13pm Post subject: |
|
|
| Yet Again, your bot cannot connect to us. Apparently wherever you host your bot, keeps nulling servers at our data center's, or you have some major backbone issues. In either event, we are now down to having 2 servers active in our pool out of 5, for the simple reason that your bot can't seem to connect to anything anymore. Now it looks like we will have to go down to one if you can't connect to 1 of the 2. This is rediculous. Move the bot to a more reliable connection somewhere other than Florida, as we have clients all over the world, and they can all connect to every server just fine.... |
|
| Back to top |
|
|
katsklaw
Guru
Joined: 28 Jun 2004
Posts: 1614
Location: Somewhere you're not.
|
| Posted: May 06, 2009 4:09pm Post subject: |
|
|
| cards wrote: | | Yet Again, your bot cannot connect to us. Apparently wherever you host your bot, keeps nulling servers at our data center's, or you have some major backbone issues. In either event, we are now down to having 2 servers active in our pool out of 5, for the simple reason that your bot can't seem to connect to anything anymore. Now it looks like we will have to go down to one if you can't connect to 1 of the 2. This is rediculous. Move the bot to a more reliable connection somewhere other than Florida, as we have clients all over the world, and they can all connect to every server just fine.... |
Please keep in mind that SIRC indexes thousands of networks, it's very likely that some of them are on the same peer if not the same datacenter and no one else has complained. If it was truely an issue with SIRC, then hundreds of people would have the same problem.
Since there hasn't been a flood of complaints from other networks and the fact that searchirc indexes more networks than you have users, it is safe to assume that the problem is closer to your end.
What's really ridiculous is you think a single bot can affect servers across several data centers simply by trying to connect using a 20 year old protocol and a few TCP packets. In fact, the very same protocol that all the other networks seem to accept. |
|
| Back to top |
|
|
Trixar_za
Eleet
Joined: 10 Dec 2006
Posts: 624
Location: South Africa
|
| Posted: May 06, 2009 4:56pm Post subject: |
|
|
| cards wrote: | | Yet Again, your bot cannot connect to us. Apparently wherever you host your bot, keeps nulling servers at our data center's, or you have some major backbone issues. In either event, we are now down to having 2 servers active in our pool out of 5, for the simple reason that your bot can't seem to connect to anything anymore. Now it looks like we will have to go down to one if you can't connect to 1 of the 2. This is rediculous. Move the bot to a more reliable connection somewhere other than Florida, as we have clients all over the world, and they can all connect to every server just fine.... |
I'll add my own experience here, I have found certain hosts which closes ports (normally 6667) for international users, and some users from certain American states, ISP's, countries, etc. Some seemed to be found in to be using broad based blacklisted IP or host ranges which is blocked by the by the Services Provider. I think this is what is happening here. To simplify it a bit for you, I'll paraphrase from the RFC on netiquette in saying, that if your experiencing issues, and it seems that you are the only ones experiencing it, then 9/10 it's on YOUR END.
SIRC uses port 6667, and their host is easy to obtain, contact your datacenter(s) or hosting company(s) and ASK them if their blocking this host via a BROAD ranged block or if 6667 really IS open completely, or secured in some way. If you are the host, then check your settings, sometimes it can be something as simple as a blacklisting error or as complex as not having port forwarding open on that port! Also check your round ribbon and how it's setup, make sure ALL the IP's are synced to the correct hosts, that it IS possible to connect to that IP using port 6667 (Ask somebody OUTSIDE of your state, possible Florida, or country to try and connect to it.) and that you have no dead routes.
By doing the above you'll be eliminating any possibility that it may be on your end, and no, international users connecting to any of these servers may be incidental or they may just be using a DIFFERENT port to connect, besides 6667. Anyway, I hope that you can solve this problem, or at least get some closer to why it's happening. |
|
| Back to top |
|
|
Jason
SearchIRC Developer
Joined: 03 May 2003
Posts: 1484
Location: Tampa, FL
|
| Posted: May 06, 2009 7:02pm Post subject: |
|
|
There's no firewalls in place to block any traffic on my end. The robot has no reason to not connect.
PS: Thanks for the laugh :) I'll get right on moving to Alaska so I can get out of the hell hole that is Florida |
|
| Back to top |
|
|
Darkhaven
none
Joined: 14 Dec 2008
Posts: 31
|
| Posted: May 06, 2009 9:05pm Post subject: |
|
|
| I agree with Trixar_za, I’ve experienced this very issue on my networks and found my ISP to the culprit. Do a little more investigation on your side and eliminate all possible reasons as 9 out 0f 10 the problem is stemming from your side. |
|
| Back to top |
|
|
cards
none
Joined: 10 Dec 2003
Posts: 4
|
| Posted: May 08, 2009 2:40pm Post subject: |
|
|
What's really funny is, we use the Same company for all of our servers. 2 Weeks ago, your bot could not connect to our server's in Canada and France. YOUR OWN REPRESENTATIVE said it was an issue on your end on why it couldn't reach out of US servers. Now it has trouble connecting to servers in the US. We are relisted now, and no changes have been made on our end whatsoever. So it seems as though there is a problem somewhere in the line, and after tracing from a server in Flordia, it appears it is Cognet, not any of our DC's.
Would it really kill you to have multiple bots throughout the country, instead of basing it all out of one, excuse my language, sh***y data center on a half a**ed backbone... |
|
| Back to top |
|
|
Trixar_za
Eleet
Joined: 10 Dec 2006
Posts: 624
Location: South Africa
|
| Posted: May 08, 2009 3:44pm Post subject: |
|
|
| cards wrote: | What's really funny is, we use the Same company for all of our servers. 2 Weeks ago, your bot could not connect to our server's in Canada and France. YOUR OWN REPRESENTATIVE said it was an issue on your end on why it couldn't reach out of US servers. Now it has trouble connecting to servers in the US. We are relisted now, and no changes have been made on our end whatsoever. So it seems as though there is a problem somewhere in the line, and after tracing from a server in Flordia, it appears it is Cognet, not any of our DC's.
Would it really kill you to have multiple bots throughout the country, instead of basing it all out of one, excuse my language, sh***y data center on a half a**ed backbone... |
Interesting, ALL with the SAME hosting company, you say? Problem magically fixed itself, you say? Happened to ONLY YOU, you say?
I take it by your half-arshed response that you didn't even do ANY checking with your hosting company, who may in the mean time have fixed the issues with those said servers, which would also magically solve this problem for you, since you say it's different servers with the same company - it means different servers around the world, with different people taking care of the box and each of those servers can be setup different from all the others and changed independently of the others too.
You still with me? Since you didn't ask them if they were doing any maintenance or anything, it means you have NO idea if they DID or DIDN'T fix your issue by accident. Dude, seriously stop trying to blame SIRC for YOUR issue. If the bots connects properly to 1000+ Networks, hosted by 1000+ different hosting companies from around the world, and doesn't connect well to yours... then IT'S AT YOUR END... |
|
| Back to top |
|
|
PingBad
Post Whore
Joined: 05 Feb 2005
Posts: 3027
Location: New Zealand
|
| Posted: May 08, 2009 6:03pm Post subject: |
|
|
the "YOUR REPRESENTATIVE" cards points to is me. However I do not believe I stated it was sirc's fault; | Code: | [16:03] { + - digilante } anyway, all the issue seems to be is that a peering link between searchirc's servers in florida and your network's roundrobin seems to be down
[16:03] { ~ - BSD } are we the only ones affected?
[16:03] { + - digilante } there is absolutely nothing you nor searchirc can do with regards to that
[16:04] { + - digilante } pretty much
[16:04] { ~ - BSD } weird
[16:04] { + - digilante } the only real solution is to just wait it out
[16:05] { ~ - BSD } it must be a partial nulling
[16:05] { + - digilante } or a dead link
[16:05] { ~ - cards } backbone issue
[16:05] { + - digilante } precisely, cards
[16:06] { ~ - BSD } weird thought that it wouldn't be able to connect ever
[16:06] { ~ - cards } maybe i'll change our dns to my hosting temporarily
[16:06] { ~ - BSD } we have server in france, Cali, Michigan, and somewhere else
[16:06] { ~ - cards } cause it's hosted in Texas
[16:06] { ~ - cards } Chicago
[16:07] { ~ - BSD } you would think one of them scrawl would get a chance to connect to
[16:07] { + - digilante } oh, and for what it's worth... a server in cali, michigan, chicago and france isn't "Across the earth"
[16:07] { ~ - BSD } i know
[16:08] { ~ - BSD } do you know if it keeps getting same ip from the round robin
[16:08] { ~ - BSD } just a thought
[16:08] { & - Thanach } nah, we'd need aussie land, japan, india, italy, and antartica... then we'd be world-wide :-p
[16:08] { ~ - BSD } lol
[16:08] { + - digilante } what i'd suggest doing (if only temporarily) is to tracert from your servers back to sirc
[16:08] { + - digilante } any traces that can't get thru would equate temporarily moving those servers into a different round robin
[16:09] { + - digilante } Thanach - japan bans IRC from it's shores
[16:09] { ~ - BSD } lol
[16:09] { ~ - BSD } well we ran
[16:09] { ~ - BSD } just-ping.com
[16:09] { ~ - cards } is it that sirc can't see our round robin, or get's an ip from RR and can't reach the server?
[16:09] { ~ - BSD } to test ping each of our servers ips from all over the place
[16:10] { & - Thanach } hmmm well then... siberia?
[16:10] { + - digilante } sirc resolves the round robin fine (otherwise the error would be "Can't resolve <address>" instead of "Connection timeout to <address>"
[16:11] { ~ - cards } could timeout trying to get an ip...
[16:11] { ~ - cards } i dunno how your system's work
[16:11] { + - digilante } BSD, from my home I can't access my own website, yet if I rdp into one of work's servers which are a mere 100KM away from me physically, I can get at my own site from there
[16:11] { + - digilante } so a ping from one location may not necessarily mean a ping from another would work
[16:12] { ~ - BSD } yea
[16:12] { ~ - BSD } tracert would show where the failure is |
|
|
| Back to top |
|
|
Jason
SearchIRC Developer
Joined: 03 May 2003
Posts: 1484
Location: Tampa, FL
|
| Posted: May 08, 2009 8:04pm Post subject: |
|
|
Any legit issue on the site will be easy to spot because multiple complaints will be made.
Since only you appear to have this issue, you might want to not be so quick in calling me out.
HOWEVER, we work our best to make everyone happy. If you aren't satisfied with our service, please let me know and I'll issue a full refund of the purchase price :) |
|
| Back to top |
|
|
katsklaw
Guru
Joined: 28 Jun 2004
Posts: 1614
Location: Somewhere you're not.
|
| Posted: May 08, 2009 8:06pm Post subject: |
|
|
| Jason wrote: | Any legit issue on the site will be easy to spot because multiple complaints will be made.
Since only you appear to have this issue, you might want to not be so quick in calling me out.
HOWEVER, we work our best to make everyone happy. If you aren't satisfied with our service, please let me know and I'll issue a full refund of the purchase price |
If I complain twice as much can I have twice my money back? ;P .. hehehe |
|
| Back to top |
|
|
|
|
| |
Register
Log in
