Jump to content

Ashoat

Chief Financial Officer
  • Posts

    6,455
  • Joined

  • Last visited

  • Days Won

    37

Everything posted by Ashoat

  1. Looks like it's active and the nameservers are pointed. I'm going to close this thread now.
  2. Open a new thread please... if it's always occurring, it's probably a issue specific to you. I'm going to close this thread now.
  3. I'm hoping to finish the coding work I need to do to upgrade our infrastructure to support multiple servers by the end of this month, and then I can send Charlie in. I'm still not sure how we're splitting him up, though.
  4. Tom_K: Okay... but you'll eventually need to point your nameserver records to HelioHost. Please wait until "Server Load" under "Service Status" in your cPanel is below 4, and then try adding the domain again once. You will have to wait 24 hours after adding your domain for it to become active.
  5. Yeah we're having problems every early morning (GMT -8). It's server-wide. I'm never awake in the morning so I haven't actually managed to check. I guess I'll do it Sunday?
  6. Yeah, we just had some trouble with BIND. As for the morning stuff... we have high load every morning for some reason and I'm never awake so I haven't actually managed to check why it's happening.
  7. grohe43: Please wait until "Server Load" under "Service Status" in your cPanel is below 4, and then try adding the domain again once. You will have to wait 24 hours after adding your domain for it to become active. Tom_K: The nameservers on that domain aren't pointed to HelioHost.
  8. Oops... I made some changes to the account management scripts earlier today, and looks like those changes broke the renew script. I've fixed the problem and I went ahead and renewed your account for you, so you should be good to go.
  9. It's just the "webdisk" (WebDAV), actually. The others don't require constantly-running processes. And WebDAV shouldn't really require that many processes, anyways... so let me know if it keeps on being a problem.
  10. Okay, I registered the domain. It should be active as soon as it propagates. It's not set to auto-renew, so make sure you start a topic in a year to tell me to renew it if you want me to renew it.
  11. That sure is a lot, but monitoring MySQL's PROCESSLIST I don't see anything out of the ordinary.
  12. Okay, so I figured out the problem with the help of the cPanel techs. We have a resource limit in place for the maximum amount of processes a user is allowed to run, and there were a couple of processes running under your username for WebDAV. I've killed those processes... please let me know if these problems start coming up again (in which case I'll just modify the resource limit).
  13. Reist: your problem seems differently... I've noticed high load during nighttimes as well. Stevie (our server) seems to consistently have problems during the late night, when I am unable to take a look at what's going on. It's sort of annoying... b_ing: I've submitted the support request. I'll keep you updated on this thread.
  14. This might be the result of a directory move I did this month... I'll leave it 'til October and I'll check then.
  15. So... everything is working now?
  16. I'll need to reset your password temporarily during this process. Is that okay?
  17. So I've looked around for a couple of hours and I honestly have no idea why this is happening. There is no information in error_log, suphp_log, or local error_logs. Your VirtualHost entry seems completely sound, and I can execute raw PHP under your username just fine. My suspicion is that this problem has something to do with suPHP (as no entry for your scripts show up in suphp_log, which is abnormal). However, I have no way of identifying why that is. At this point, I have two options. I'll leave the decision up to you. 1) Escalate this issue up to cPanel tech support and have them figure it out. This will probably take about two days. 2) We can try deleting your account and then you can create it again. If this issue is localized (which is what I suspect), the problem should be fixed.
  18. Where is your test script located on disk?
  19. Problem with the CGI scripts you're running is that you have a you U+FEFF character at the beginning. Here, read this Wikipedia page. I've had this problem before and it's not easy to deal with in Windows. If you're running a 32-bit version, the command-line text editor in cmd (I think it's just "edit") can see the U+FEFF character, but most text editors just don't display it. Alternately, if you're running Linux or Mac OS X or something, you can open the file up in vim and just remove that character.
×
×
  • Create New...