OpenBSD Journal

How's the new server?

Contributed by dhartmei on from the first-poll dept.

perfectly responsive 51.6% (263 votes)


faster, but still not responsive enough 5.9% (30 votes)


slower 2.7% (14 votes)


didn't notice any difference 39.8% (203 votes)


Total votes: 510

(Comments are closed)


Comments
  1. By Daniel Hartmeier (62.65.145.30) daniel@benzedrine.cx on

    If you notice any breakage, please post them below this comment. Thank you.

    Comments
    1. By Geert Hendrickx (81.244.145.232) geert.hendrickx@ua.ac.be on

      The footer still says site powered by thttpd, but the new server seems to be running Apache.

      Comments
      1. By Daniel Hartmeier (195.234.187.87) daniel@benzedrine.cx on

        Fixed, thanks. In case anyone wonders: the change from thttpd to Apache is not motivated by technical reasons (thttpd does the job perfectly), the new server is just used for other purposes as well.

        Comments
        1. By Anonymous Coward (69.197.92.190) on

          I thought thttpd serialized all cgi access, making it pretty bad for dynamic content? Last I heard the author even says not to use thttpd for cgi content, and instead run cgis on another server and use thttpd for images and other static content.

          Comments
          1. By Daniel Hartmeier (62.65.145.30) daniel@benzedrine.cx on

            With net.inet.tcp.sendspace=65536, almost all CGI-generated pages fit into the TCP send buffer, and the running time for one invocation is in the order of < 1ms, so even if 10 clients would request the CGI at the same time, serial execution wouldn't cause much delay, and had the advantage of conserving memory (the previous server had only 64MB RAM, of which only around 5 MB were free on average :).

            If you have more memory to spare, Apache (with many concurrent processes forking the CGI) should be faster when there are concurrent requests. For undeadly, that happens only when we are /.ed or when many RSS readers fetch on full hours, though.

      2. By Anonymous Coward (208.252.48.163) on

        The version of Firefox I've been using for a couple months is now saving the favicon.ico correctly in the bookmarks and Personal Toolbar, whereas before it would just show the icon in the URL bar but never save it. I wonder if it's related to the switch to Apache.

    2. By Anonymous Coward (142.166.106.52) on

      Here is a long-standing problem. Submissions like commenting voting and moderating do not work under (at least) konqueror embedded from ports (and probably konqueror proper as well -- I can't recall). These haven't worked since the site changed from deadly.org.

      On this (new) server I get an error message rather than a hang, and here it is:

      Internal Server Error

      The server encountered an internal error or misconfiguration and was unable to complete your request.

      Please contact the server administrator, you@your.address and inform them of the time the error occurred, and anything you might have done that may have caused the error.

      More information about this error may be available in the server error log.

      -------------------------------------------------------------------
      Apache/1.3.29 Server at undeadly.org Port 80

      Comments
      1. By Daniel Hartmeier (195.234.187.87) daniel@benzedrine.cx on

        Can you repeat the request and note the time (in GMT, date -u) and the client IP address I should see in the web server log?

        It's probably related to the HTTP headers the client provides, but I don't spot anything clearly related in the log.

        Comments
        1. By Anonymous Coward (142.166.106.52) on

          Sure, Here is a 'moderate' attempt which konq-e shows in the address bar as:

          http://undeadly.org/cgi?action=submit&sid=20040823084834&pid=5

          This should show up in your logs as occurring at (approximately; I rarely check the accuracy of my clock) Mon Aug 23 12:49:38 ADT 2004

          and from address: 142.166.106.52

          If you need more detail, just post it here and I'll email you.

          Comments
          1. By Anonymous Coward (142.166.106.52) on

            Sorry -- GMT -- I didn't read; You can add 3 to hour I posted... ;)

          2. By Daniel Hartmeier (195.234.187.87) daniel@benzedrine.cx on

            I see the error log entry as

            [Mon Aug 23 09:49:12 2004] [error] [client 142.166.106.52] Premature end of script headers: /htdocs/undeadly/cgi

            which indicates a bug in the cgi (see Apache Server FAQ).

            Could you run tcpdump -s 1600 -pXi <if> tcp port 80 and capture the HTTP request for a moderation attempt?

            Comments
            1. By Anonymous Coward (142.166.106.52) on

              No problem. I'll mail it to you at your benzedrine.cx address.

              Comments
              1. By Anonymous Coward (142.166.106.52) on

                A test. Yep....You fixed it. Thanks Daniel!

  2. By Bob Beck (129.128.11.43) beck@openbsd.org on

    Way better:

    traceroute to undeadly.org (129.128.5.155), 64 hops max, 40 byte packets
    1 gateway-11 (129.128.11.1) 0.320 ms 0.309 ms 0.257 ms
    2 gsb175-c4507-gsb.backbone.ualberta.ca (198.73.178.250) 0.746 ms 2.383 ms 0.811 ms
    3 anchorman.srv.ualberta.ca (129.128.5.155) 0.275 ms 0.318 ms 0.271 ms

    Of course, my desktop location in somewhat optimal :)

    Comments
    1. By grey (64.139.7.172) on

      Gee Bob, do you think you could run a traceroute to localhost from the console of the machine too? Lucky bastard (and I mean that in the most endearing BofH compliment sort of way).

      Seriously, if I haven't thanked you already - THANK YOU for providing the new hosting for undeadly. Not to say that Daniel running it on an old laptop from his work (which apparently doesn't have decent UPS's) was bad, because that sure was better than nothing. Thanks again!

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]