I waited more than 24hrs after submitting the ticket to get the 30 seconds (or multiple of 30s) delay problem, and it came back, again.
I enjoyed less than a day of normal operation.
This time, I didn’t wait to see if DreamHost catches and corrects it and submitted a ticket, right away.
I’m starting to monitor the site myself, as I don’t think DraemHost is monitoring, and I’m thinking about writing a script to submit a ticket, too.
On the server, we just need a very simple CGI, like this:
#!/bin/sh echo "" echo "Testing CGI"
Name it “test.cgi” , for example, and do “chmod 700 test.cgi”
And we can issue a command like this from any machine:
time wget http://yoursite.com/test.cgi
With the 30 second delay problem, it will take slightly more than 30 seconds.
With a script that invokes another process, it takes twice as much.
#!/bin/sh echo "" date
If you use pipe, it will take a lot longer.
#!/bin/sh echo "" ls -al |tail
If you issue more commands, the same thing.
30s for starting CGI process, and 30s each for every single process, no matter how simple it is.
#!/bin/sh echo "" date date date
It’s very unusual to get the same delay for each subprocess, and each time this problem happens, by accident.
I’d understand if it’s by design and if it’s desired to be like this.
In addition, the manner support stuffs answer to tickets about this problem is strange.
They simply say the HTTP server needed to be reset.
Then, why not monitor the server and reset it automatically when this problem happens?
It would reduce the ticket volume and the associated cost.
I don’t understand why they keep this hanging around for months.