From: Benjamin N. <bjn...@gm...> - 2008-02-12 14:32:02
|
Hi I've implemented a web application using yaws, and I've deployed it on a VM with a hosting company. It's in the final beta testing phase, so it's available publicly, but I haven't announced it to anyone. Everything seems to be running fine, but last week (and again when I checked today), it looks like the server is suddenly not responding when I go to http://www.<mydomain>/. But then I tried explicitly accessing http://www.<mydomain>/index.yaws and it worked, and subsequent requests to the root then started working again. There's nothing strange in report.log, but in localhost.access I spotted: 66.249.65.97 - - [12/Feb/2008:04:59:45 +0000] "GET /robots.txt HTTP/1.1" 404 253 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" 66.249.65.97 - - [12/Feb/2008:04:59:45 +0000] "GET / HTTP/1.1" 200 10418 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" Which at the moment is the only anomaly that I can suspect for this behaviour. Alternatively it could be something on the VM that's been set up by the hosting company that I don't know about, but what that might be I have no idea. Versions: Yaws: 1.73 Erlang: 5.6 Ubuntu: 6.06 Any help much appeciated! Thanks Benjamin -- Benjamin Nortier e: bjn...@gm... c: +44 (0)778 946 1959 msn: bjn...@ma... gtalk: bjn...@gm... |
From: Claes W. <kl...@ta...> - 2008-02-12 18:14:44
|
Benjamin Nortier wrote: > Hi > > I've implemented a web application using yaws, and I've deployed it on > a VM with a hosting company. It's in the final beta testing phase, so > it's available publicly, but I haven't announced it to anyone. > > Everything seems to be running fine, but last week (and again when I > checked today), it looks like the server is suddenly not responding > when I go to http://www.<mydomain>/. Odd, > > But then I tried explicitly accessing http://www.<mydomain>/index.yaws > and it worked, and subsequent requests to the root then started > working again. > Odd again, No clue. > There's nothing strange in report.log, but in localhost.access I spotted: > > 66.249.65.97 - - [12/Feb/2008:04:59:45 +0000] "GET /robots.txt > HTTP/1.1" 404 253 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; > +http://www.google.com/bot.html)" > 66.249.65.97 - - [12/Feb/2008:04:59:45 +0000] "GET / HTTP/1.1" 200 > 10418 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; > +http://www.google.com/bot.html)" > Well this seems to indicate some major weirdness, how on earth did googlebot access a server called localhost. What's your yaws.conf, and especially the entry for localhost. Why wouldyou even want a localhost entry on a proper internet www server. /klacke > Benjamin > |
From: Benjamin N. <bjn...@gm...> - 2008-02-12 18:50:12
|
Hi Thanks for your reply! On Feb 12, 2008 6:14 PM, Claes Wikstrom <kl...@ta...> wrote: > Benjamin Nortier wrote: > > Hi > > > > I've implemented a web application using yaws, and I've deployed it on > > a VM with a hosting company. It's in the final beta testing phase, so > > it's available publicly, but I haven't announced it to anyone. > > > > Everything seems to be running fine, but last week (and again when I > > checked today), it looks like the server is suddenly not responding > > when I go to http://www.<mydomain>/. > > Odd, > > > > > But then I tried explicitly accessing http://www.<mydomain>/index.yaws > > and it worked, and subsequent requests to the root then started > > working again. > > > > Odd again, > > No clue. > > > There's nothing strange in report.log, but in localhost.access I spotted: > > > > 66.249.65.97 - - [12/Feb/2008:04:59:45 +0000] "GET /robots.txt > > HTTP/1.1" 404 253 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; > > +http://www.google.com/bot.html)" > > 66.249.65.97 - - [12/Feb/2008:04:59:45 +0000] "GET / HTTP/1.1" 200 > > 10418 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; > > +http://www.google.com/bot.html)" > > > > > Well this seems to indicate some major weirdness, how on earth > did googlebot access a server called localhost. What's your yaws.conf, > and especially the entry for localhost. > Why wouldyou even want a localhost entry on a proper internet > www server. > Hmmm, that's definitely a mistake. The server entry in yaws.conf read <server localhost> port = 80 listen = 0.0.0.0 docroot = ... </server> I've updated it to the correct hostname. The access log now has the correct hostname. If I define an entry as "localhost", does that not mean that it should not be accessible from outside at all? Or is it because it's being hosted on a virtual machine? Sorry if these are such newby questions... Benjamin > > > /klacke > > > Benjamin > > > > -- Benjamin Nortier e: bjn...@gm... c: +44 (0)778 946 1959 msn: bjn...@ma... gtalk: bjn...@gm... |