|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Stop making mediocre tutorials.The best tutorials are video! Camtasia Studio makes it easy to create engaging, buzz-building screen videos at any size, in any popular format. Download the free trial!
|
|
#1
|
|||
|
|||
|
Hi,
I had some difficulties reaching devshed.com over the last few days. It took "years" for a site to build and sometimes ie informed me that the server was unreachable. Did anybody experience similar problems? Is the server overloaded or anything? How many people per day are there using devshed.com anyway? Must be a lot... |
|
#2
|
||||
|
||||
|
Getting it all the time recently... just have to sit and wait I suppose.
|
|
#3
|
|||
|
|||
|
I was wondering wether devshed.com suffered from a dDos-Attack or something...
![]() |
|
#4
|
||||
|
||||
|
Unlikely, but you never know...
![]() |
|
#5
|
|||
|
|||
|
for me (access from germany) it sometimes will time-out and sometimes just take a minute or two.
i think it is quite after lunch-time in your country that the pages take forever to load ![]()
__________________
-- Manuel Hirsch - Linux, FreeBSD, programming, administration articles, tutorials and more. |
|
#6
|
|||
|
|||
|
>> Getting it all the time recently
Yes, and it's been like that for over a month. Although infowest.com slightly misconfigured the DNS of devshed.com, but it's not a DNS problem because accessing forums.devshed.com via its IP (216.190.27.198) makes no difference. |
|
#7
|
||||
|
||||
|
Server bandwidth overload?
|
|
#8
|
|||
|
|||
|
Probably not a bandwidth problem. During that period telneting to port 80 connects right thru to the greeting banner, after sending appropriate HTTP request, it waits forever for the server reply. So likely it's a web server misconfiguration.
|
|
#9
|
||||
|
||||
|
Zope's been getting a bit overloaded lately. We have an Apache proxy sitting in front of Zope, so that why there is a connection, but Zope wasn't replying to the proxy's requests in a convenient amount of time.
We've just upgraded the server DevShed is hosted on, so we shouldn't be having these problems anymore, at least not for a while. Sorry for the inconvenience.
__________________
Lucas Marshall |
|
#10
|
|||
|
|||
|
thank you
i really enjoy this board! |
|
#11
|
|||
|
|||
|
i can't get in till about 4pm gmt most days, which really annoys me.
Regards Kal |
|
#12
|
|||
|
|||
|
...could not connect the whole weekend since friday evening.
and the one time i could on sunday (a few minutes only though) there was not a single new post ![]() maybe this helps in tracking down the problem. |
|
#13
|
|||
|
|||
|
I'd have to say that DevShed isn't providing a strong reason via example to use Zope.
__________________
FSBO (For Sale By Owner) Realty |
|
#14
|
|||
|
|||
|
Maybe there was a webserver misconfiguration, but Ouch!! Look at this traceroute I just ran:
traceroute to forums.devshed.com (216.190.27.198), 30 hops max, 40 byte packets 1 dsl-xx-xx-xxx-xxx.telocity.com (xx.xx.xxx.xxx) 1.234 ms 1.165 ms 1.151 ms 2 * * route-xx-xx-xxx-x.telocity.com (xx.xx.xxx.x) 12.327 ms 3 216.227.80.124 (216.227.80.124) 15.142 ms 216.227.80.92 (216.227.80.92) 14.388 ms 14.163 ms 4 ge-1-2-0-50.core1.mia.tlct.net (216.227.80.129) 14.178 ms 14.229 ms ge-1-2-0-50.core2.mia.tlct.net (216.227.80.130) 12.934 ms 5 ae0-5.core2.mia.tlct.net (216.227.126.62) 13.456 ms 12.743 ms so-1-0-1.core1.was.tlct.net (216.227.126.217) 41.044 ms 6 so-1-0-1.core1.was.tlct.net (216.227.126.217) 38.348 ms ge-0-0-0.border1.was.tlct.net (216.227.126.109) 38.364 ms 39.129 ms 7 ge-0-0-0.border1.was.tlct.net (216.227.126.109) 39.031 ms mae-east-atm-eli.net (198.32.187.57) 43.028 ms 40.388 ms 8 p7-0.cr02.mcln.eli.net (207.173.114.129) 41.008 ms 41.167 ms mae-east-atm-eli.net (198.32.187.57) 39.291 ms 9 p7-0.cr02.mcln.eli.net (207.173.114.129) 42.326 ms 42.811 ms srp2-0.cr01.mcln.eli.net (208.186.20.145) 40.554 ms 10 p10-0.cr02.chcg.eli.net (207.173.115.89) 57.953 ms srp2-0.cr01.mcln.eli.net (208.186.20.145) 41.608 ms p10-0.cr02.chcg.eli.net (207.173.115.89) 59.389 ms 11 srp2-0.cr01.chcg.eli.net (208.186.20.81) 57.915 ms 58.203 ms 57.503 ms 12 srp2-0.cr01.chcg.eli.net (208.186.20.81) 57.499 ms p10-0.cr02.slkc.eli.net (207.173.115.53) 110.676 ms 109.912 ms 13 srp0-0-0.gw01.slkc.eli.net (208.186.20.53) 110.978 ms 109.919 ms 110.976 ms 14 gw-cust-INFOWEST-COM.slkc.eli.net (209.210.57.154) 139.773 ms srp0-0-0.gw01.slkc.eli.net (208.186.20.53) 109.695 ms 108.932 ms 15 * gw-cust-INFOWEST-COM.slkc.eli.net (209.210.57.154) 150.714 ms * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *
__________________
The real n-tier system: FreeBSD -> PostgreSQL -> [any_language] -> Apache -> Mozilla/XUL Amazon wishlist -- rycamor (at) gmail.com |
|
#15
|
|||
|
|||
|
Yep.. I couldn't access it either...
![]()
__________________
K1 |