Your website does not appear in the Apache configuration file


#1

how can I fix this.

I have all my wordpress files on my ftp. youarethescene.net

My website is youarethescene.net
But, i recently bought yats.cd

so, now yats.cd works, with the files from youarethescene.net

Now, I’m getting wicked bad laggy, and a lot of connection errors. I was about to submit a ticket… But this showed

Now, i actually deleted “htacess_ff” off my ftp from youarethescene.net folder

Seems to be working a tad better, still getting errors, and connection drops.

Wondering, if anyone can give me a hand… I know nothing about server side problems.

Thanks
-Dave


#2

I suspect there are a lot of people with the same issue, my sites are all effected as well and whats worse is I cannot access by ftp which would allow me to change the permissions to 644 and correct the apache issue.

I submitted a trouble ticket at 8am this morning but have had no answer yet.


#3

Looks like your server is down (or on it’s way down) Dave.


#4

Well I never had any problems. before when i was using youarethescene.net but ever since i bought the .cd domain. and directing the files to the yats.cd domain, it’s been slow, laggy and stuff… I don’t know why. I had the htaccess on youarethescene.net folder well in it… I have it on my desktop the file. but deleted it in the youarethescene.net folder…

Got any suggestions as to how i can fix this?


#5

After seeing those errors in your panel screenshot, I’d urge you to send in a ticket to Support (if you haven’t already). Would pay to link them to your screenshot too, just in case the respondent glosses over the errors in the check you did.


#6

Yes, i did send it to them I’m still waiting… I was actually on google.com last night trying to find how to do .htaccess like linking domains. I thought i could fix the slow ness. now i fucked up. and all i get is internal errors yats.cd and I don’t know what to do now!![hr]
NOW WHAT THE HELL DO I DO!!! I CANT GET INTO WORDPRESS ANYWAYS!@!!

"Hello!

I’m sorry that you are encountering these issues. It would appear that
the sites that are running under your user “yats” are occasionally
hitting our shared server’s memory limits. This is why your site is
seemingly slow, and the 500 errors are directly related as well. Here is
an excerpt from the log kept by our Process Watcher, the daemon that is
killing your troublesome php5.cgi processes:

Sat Mar 17 18:03:00 2012 procwatch3 INFO: PID 1844 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Sat Mar 17 18:03:00 2012 procwatch3 INFO: PID 1846 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Sat Mar 17 18:03:10 2012 procwatch3 INFO: PID 1756 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Sat Mar 17 18:03:10 2012 procwatch3 INFO: PID 1634 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Sat Mar 17 18:05:11 2012 procwatch3 INFO: PID 1897 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Sat Mar 17 18:05:51 2012 procwatch3 INFO: PID 2742 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Sat Mar 17 18:07:32 2012 procwatch3 INFO: PID 2914 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Sat Mar 17 18:11:54 2012 procwatch3 INFO: PID 1896 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Sat Mar 17 18:17:06 2012 procwatch3 INFO: PID 4764 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Sat Mar 17 18:18:47 2012 procwatch3 INFO: PID 1896 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Sat Mar 17 18:18:47 2012 procwatch3 INFO: PID 1895 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Sat Mar 17 18:18:47 2012 procwatch3 INFO: PID 6737 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Sat Mar 17 18:18:57 2012 procwatch3 INFO: PID 4764 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Sat Mar 17 18:19:47 2012 procwatch3 INFO: PID 6740 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Sat Mar 17 18:21:08 2012 procwatch3 INFO: PID 6739 (php5.cgi)
yats:pg1672408 - killed for uid ram total exceeds limit

Procwatch is a daemon that runs constantly on shared servers to monitor
the usage of RAM/CPU and execution time so that no single user can use an
inappropriately high percentage of the shared resources and impact the
overall health of the server or the server’s ability to serve all users’
pages.

Now, it’s important to get these errors fixed to keep your sites running
with optimum speed, as well as keep our servers happy. Unfortunately it
can often be a bit of a trial-and-error procedure, but I will provide as
much information as I can to aide you in this process.

Firstly, it should be noted that any sites running under your user can
contribute to the problems you are encountering. For example, if site A
is running processes that are taking up 85% of your individual limit, and
site B tries to run a concurrent process that takes up 20% of the memory
cap, site B will have it’s process killed since it is the one that took
you above your limits, even though site A’s script is the obvious memory
hog… For this reason, it’s important to keep all of your user’s sites
optimized and running smoothly.

There are quite a few things that can contribute to high memory
consumption on any given site, but I will mention the most common
causes…

Plugins - Especially third-party plugins can often be poorly written and
run up the memory consumption. I often recommend disabling all
non-critical plugins and see if the problem gets better, then enabling
them one-by-one until you are able to identify one that causes problems.

Database related overhead, or an unnecessary amount of database queries -
If you are trying to query your database for thousands of results at a
time, this can also cause issues… Try to keep all database sizes and
queries to a minimum by deleting irrelevant or old information from your
database. You might also try optimizing tables in your databases by
visiting your database through PHPMyAdmin. Simply use the “Check tables
having overhead” link located directly underneath your tables and then
"With Selected:", choose “Optimize Table”. This might reduce overhead in
your database, which is basically a lot of empty and redundant space that
can slow your queries down.

It is also possible that a spike in traffic, or a heavy run by a site
indexer (such as the GoogleBot), or even abusive hits by a given IP
address, could cause this on a short term basis, so you might want to
inspect your access logs for such activity (you can often manage this
problem by implementing a robots.txt or by blocking abusive IP addresses
with .htaccess).

You might as well want to try looking over the suggestions offered at our
wiki pages on this matter:

http://wiki.dreamhost.com/Database_Maintenance

Implementing the above suggestions more often than not will fix the
ProcWatch errors, but if you are still finding that your sites encounter
the same problems, you might want to consider moving to a VPS
(http://wiki.dreamhost.com/DreamHost_PS) or dedicated server where you
can reserve sufficient RAM for your own processes to run!

I am sorry if this news is discouraging, but I felt it was important that
you have the full benefit of knowing what is occurring here so you can
make the appropriate decision to meet your needs for this site.

If you have any other questions, or if I can help you further, please let
me know.

Thanks!

Daniel H.

DreamHost Support

"


#7

Yats,

Try and experiment of editing your yats user on panel and change the php from ‘fastcgi’ to ‘cgi’ and see if that helps.

-Bill


#8

I FIXED IT! :slight_smile: well I was messing around with google.com thru in the post title and had to do somethings with the htaccess file… I made a .ht and it didn’t show in my ftp so i made htaccess and uploaded so i had a few htacces files i found how to show hidden files thru ws_Ftp i got rid fo them files… uploaded .htaccess with the right code. now i’m working at the site again… I need to have the lines of fast.cgi in my htaccess otherwise the content of my site won’t load EVER… which is weird. I think that I HAVE TO HAVE it in there.

Anyways… I’m still having to log into my site when i’m already logged into it… I don’t know how to config yats.cd to apache. I take it I need to code the htaccess file with something. I looked online also last night on google.com was looking for “domains name directory .htaccess”

Cause… I started back in 08 with youarethescene.net thats on my ftp. i just bought yats.cd domain name from https://www.nic.cd/ now I host on dreamhost, and have domain on dreamhost, i wanted shorter domain url thats why i got yats.cd

Now, I point my files from youarethescene.net to yats.cd I run a wordpress site keep in mine.

Do I need to config my htaccess for apache so yats.cd will run…

On my ftp i have yats.cd it was made when i was making a new domain on dreamhost panel… there’s nothing in it except for 2 icons for favicon.

umm…

In my htaccess. do i need to redirect my long url, to the shorter one?

http://chanon-srithongsook.info/development-notes/change-main-domain-to-subfolder/

RewriteEngine on
2 RewriteCond %{HTTP_HOST} ^(www.)?main-domain.com$ [NC]
3 RewriteCond %{REQUEST_URI} !^/sub-folder/
4 RewriteCond %{REQUEST_FILENAME} !-f
5 RewriteCond %{REQUEST_FILENAME} !-d
6 RewriteRule ^(.*)$ /sub-folder/$1
7 RewriteCond %{HTTP_HOST} ^(www.)?main-domain.com$ [NC]
8 RewriteRule ^(/)?$ sub-folder/index.php [L]

Cause all last night i was looking for Domains name directory .htaccess
since, i wrote a topic a few days ago about having problems, and I think someone said i needed to direct my domain to the new one or something it’s way over my head and I know really nothing about this crap… I wish someone would do it for me to get it done and over with!


#9

try freelancer.com