Registrating For Website

There are hundreds of posts on this. Fastest way to troubleshoot it is to check your server mail logs to confirm that mail is being sent or not. You may not have direct access to these logs but your web hosting supports techs can check. Also it’s always best to use an email address for sending from your own domain (eg. use someone@youarethescene. net not a gmail or other domain mail).

I used to get email in my own personal inbox, letting me know who signed up and stuff.

I checked now [email protected]
take a look at the image https://i48.tinypic.com/22xfdi.gif

I just just recently recieved an email stating that a user signed up when they went to the main link and signed up like that, I disabled my invite plugin I had also. I think I’m not getting the emails right away because of the low bandwidth i have or I need more. Cause I already new this person signed up cause, I have a welcome message plugin, and it will show the new people that signed up to be sent this welcome email.

Looks like I need a private server VPN, or a dedicated seems like I keep going over my limite, i’m on shared server so I think someone on the same server is going over or whatever also. I don’t know

Hello Dave,

I apologize for the delay in response and for the continued issues you’ve

been seeing. It appears that your user “yats” is going over the

memory limits on the server, and you’re running into 500 Internal Server

Errors and slow loading times as a result of this. Here is one of the

logs that just occurred now as I opened all your websites on your

account:

Nov 17 08:18:40 2012 procwatch3 INFO: PID 43047 (php5.cgi) yats:pg1672408

Nov 17 08:18:40 2012 procwatch3 INFO: PID 42799 (php5.cgi) yats:pg1672408

Nov 17 08:18:40 2012 procwatch3 INFO: PID 40757 (php5.cgi) yats:pg1672408

Nov 17 08:18:40 2012 procwatch3 INFO: PID 42798 (php5.cgi) yats:pg1672408

Nov 17 08:20:00 2012 procwatch3 INFO: PID 42274 (php5.cgi) yats:pg1672408

Nov 17 08:20:00 2012 procwatch3 INFO: PID 42800 (php5.cgi) yats:pg1672408

Nov 17 08:20:00 2012 procwatch3 INFO: PID 43428 (php5.cgi) yats:pg1672408

Nov 17 08:21:11 2012 procwatch3 INFO: PID 43378 (php5.cgi) yats:pg1672408

Nov 17 08:21:31 2012 procwatch3 INFO: PID 43609 (php5.cgi) yats:pg1672408

Nov 17 08:21:41 2012 procwatch3 INFO: PID 43445 (php5.cgi) yats:pg1672408

Nov 17 08:21:41 2012 procwatch3 INFO: PID 43375 (php5.cgi) yats:pg1672408

Nov 17 08:21:41 2012 procwatch3 INFO: PID 43427 (php5.cgi) yats:pg1672408

Nov 17 08:21:41 2012 procwatch3 INFO: PID 40759 (php5.cgi) yats:pg1672408

Nov 17 08:21:41 2012 procwatch3 INFO: PID 43652 (php5.cgi) yats:pg1672408

Nov 17 08:22:31 2012 procwatch3 INFO: PID 43429 (php5.cgi) yats:pg1672408

Nov 17 08:23:01 2012 procwatch3 INFO: PID 43711 (php5.cgi) yats:pg1672408

Nov 17 08:23:01 2012 procwatch3 INFO: PID 43377 (php5.cgi) yats:pg1672408

Nov 17 08:23:01 2012 procwatch3 INFO: PID 43746 (php5.cgi) yats:pg1672408

Nov 17 08:23:01 2012 procwatch3 INFO: PID 43709 (php5.cgi) yats:pg1672408

Nov 17 08:23:01 2012 procwatch3 INFO: PID 43748 (php5.cgi) yats:pg1672408

Nov 17 08:23:11 2012 procwatch3 INFO: PID 43747 (php5.cgi) yats:pg1672408

Nov 17 08:23:21 2012 procwatch3 INFO: PID 43710 (php5.cgi) yats:pg1672408

Nov 17 08:23:21 2012 procwatch3 INFO: PID 43776 (php5.cgi) yats:pg1672408

Nov 17 08:23:21 2012 procwatch3 INFO: PID 43775 (php5.cgi) yats:pg1672408

Nov 17 08:23:21 2012 procwatch3 INFO: PID 43774 (php5.cgi) yats:pg1672408

Nov 17 08:23:21 2012 procwatch3 INFO: PID 43788 (php5.cgi) yats:pg1672408

Nov 17 08:23:21 2012 procwatch3 INFO: PID 43789 (php5.cgi) yats:pg1672408

Nov 17 08:23:21 2012 procwatch3 INFO: PID 43791 (php5.cgi) yats:pg1672408

Nov 17 08:23:21 2012 procwatch3 INFO: PID 43793 (php5.cgi) yats:pg1672408

Nov 17 08:23:32 2012 procwatch3 INFO: PID 43790 (php5.cgi) yats:pg1672408

Nov 17 08:23:32 2012 procwatch3 INFO: PID 43804 (php5.cgi) yats:pg1672408

Nov 17 08:23:32 2012 procwatch3 INFO: PID 43805 (php5.cgi) yats:pg1672408

Nov 17 08:23:42 2012 procwatch3 INFO: PID 43806 (php5.cgi) yats:pg1672408

Nov 17 08:23:42 2012 procwatch3 INFO: PID 43823 (php5.cgi) yats:pg1672408

Nov 17 08:23:42 2012 procwatch3 INFO: PID 43838 (php5.cgi) yats:pg1672408

Nov 17 08:23:42 2012 procwatch3 INFO: PID 43802 (php5.cgi) yats:pg1672408

Nov 17 08:23:42 2012 procwatch3 INFO: PID 43803 (php5.cgi) yats:pg1672408

Nov 17 08:23:42 2012 procwatch3 INFO: PID 43837 (php5.cgi) yats:pg1672408

Nov 17 08:23:42 2012 procwatch3 INFO: PID 43822 (php5.cgi) yats:pg1672408

Nov 17 08:23:52 2012 procwatch3 INFO: PID 43839 (php5.cgi) yats:pg1672408

Nov 17 08:25:02 2012 procwatch3 INFO: PID 43792 (php5.cgi) yats:pg1672408

Nov 17 08:25:02 2012 procwatch3 INFO: PID 43856 (php5.cgi) yats:pg1672408

Nov 17 08:25:22 2012 procwatch3 INFO: PID 43857 (php5.cgi) yats:pg1672408

Nov 17 08:25:42 2012 procwatch3 INFO: PID 44021 (php5.cgi) yats:pg1672408

Nov 17 08:25:53 2012 procwatch3 INFO: PID 43996 (php5.cgi) yats:pg1672408

Nov 17 08:25:53 2012 procwatch3 INFO: PID 44042 (php5.cgi) yats:pg1672408

Nov 17 08:27:13 2012 procwatch3 INFO: PID 44039 (php5.cgi) yats:pg1672408

Nov 17 08:27:23 2012 procwatch3 INFO: PID 44053 (php5.cgi) yats:pg1672408

Nov 17 08:27:23 2012 procwatch3 INFO: PID 43807 (php5.cgi) yats:pg1672408

Nov 17 08:27:23 2012 procwatch3 INFO: PID 44052 (php5.cgi) yats:pg1672408

Nov 17 08:27:33 2012 procwatch3 INFO: PID 44171 (php5.cgi) yats:pg1672408

Nov 17 08:27:43 2012 procwatch3 INFO: PID 44170 (php5.cgi) yats:pg1672408

Nov 17 08:27:53 2012 procwatch3 INFO: PID 44221 (php5.cgi) yats:pg1672408

Nov 17 08:28:14 2012 procwatch3 INFO: PID 44208 (php5.cgi) yats:pg1672408

Nov 17 08:28:24 2012 procwatch3 INFO: PID 44235 (php5.cgi) yats:pg1672408

Nov 17 08:28:24 2012 procwatch3 INFO: PID 44207 (php5.cgi) yats:pg1672408

Nov 17 08:28:24 2012 procwatch3 INFO: PID 43855 (php5.cgi) yats:pg1672408

Nov 17 08:28:24 2012 procwatch3 INFO: PID 44169 (php5.cgi) yats:pg1672408

Nov 17 08:28:24 2012 procwatch3 INFO: PID 44040 (php5.cgi) yats:pg1672408

Nov 17 08:28:24 2012 procwatch3 INFO: PID 44313 (php5.cgi) yats:pg1672408

Nov 17 08:28:24 2012 procwatch3 INFO: PID 44041 (php5.cgi) yats:pg1672408

Nov 17 08:28:34 2012 procwatch3 INFO: PID 44409 (php5.cgi) yats:pg1672408

“procwatch” is a process watcher program that runs on all our shared

servers. It automatically kills processes that exceed the RAM limit. RAM

is just another term for memory, the main purpose of including the

log is to assure you that I have indeed investigated the issue and so

that we can match up the time stamp and date to the problem you are

reporting.

Please understand that while you may not be hitting your disk space or

bandwidth limits, these are actually entirely different things.

If we didn’t limit the amount of memory our customers were using on the

server, then one customer could bring the system down completely if they

so desired.

I would highly recommend that you follow the steps in the following wiki

article in order to reduce your usage:

https://wiki.dreamhost.com/Slow_site_troubleshooting

https://wiki.dreamhost.com/Finding_Causes_of_Heavy_Usage

https://wiki.dreamhost.com/Fine_Tuning_Your_WordPress_Install

https://wiki.dreamhost.com/WordPress_Optimization

https://www.prelovac.com/vladimir/wordpress-optimization-guide

Also, please be aware that just because this site is the one getting

killed, it isn’t necessarily the problematic one.

For instance, if Site A is using 90% of your allotted memory usage, and

then Site B attempts to use an additional 15%, Site B will be 5% over and

will get it’s script killed.

I’d also recommend looking into any 3rd party plugins you may be running,

especially if you happen to be running WordPress, Joomla, etc. as they

can be notoriously poor at memory management.

Lastly, you may want to look into DreamHost VPS, as you will be able to

raise your memory limits to whatever limit you’d like. We offer a free

1 week trial for this as well.

https://dreamhost.com/servers/vps/

This is the link to enable VPS in your account:

https://panel.dreamhost.com/index.cgi?tree=vserver.provision&

Of course I wouldn’t recommend going through with an upgrade to

DreamHost VPS unless you’d exhausted the other options, which will

typically solve this type of issue.

Please let me know if you have further questions about any of this.

Thanks!

Gracie

Last week we had some email drama over at DreamHost, but those should all be resolved by now. Normally the memory issues wouldn’t impact your email, but in your case, it’s preventing WP from sending the email.

You’re definitely having memory issues with WP on your account, though. A couple things jumped out at me.

You have caching defined in your wp-config, but you’re not actually using any caching plugins. You also have wordpress-mu-secure-invites installed, but you’re not using Multisite, and this could cause issues.

I would go through and remove any plugins I don’t have to use to see if that helps out a little. After that, I’d install WP Super Cache and see if that helps any. Finally I’d change PHP to 5.3 Fast CGI (you can do that in your Panel, go to Domains and then Edit the domain. PHP changes are on that page.)

oh hai… thanks for getting back to me, yeah I’ve been contacting people from dreamhost, and they have been sending emails, looks like emails are going thru but still at a slow rate, cause I see who signs up when i go into my dashboard and go to welcome email, once i see that, a few hours later emails start to come over to my personal email account saying hey this person signed up, where as before it was QUICK..

How, do I get rid of the cache thing on my wp-config. I bet you if I get more memory, a VPN / Dedicated Server, I can stop using this email plugin that you guys suggested me to use correct?

The email is still running slower for web-apps right now. I don’t have an ETA right now, but I know security and mail server teams are working so hard, they had to eat their holiday party yummies at their desks.

If you log in via SSH or any file transfer app, you can edit the wp-config.php file manually, just like any file. If you’re having trouble with that, open up a ticket and we can help you out ??

looking @ my php file i delete just the first line?

// ** MySQL settings ** //
//define(‘WP_CACHE’, true); //Added by WP-Cache Manager

Well second line.

Also. where you the one that told me about my plugins I use.??

Yeah I use secure invite which is awsome, granted its for buddy press, but it does work with reg wordpress

I did have a cache plug in installed before, but got rid of it, had no idea how to work it. that’s why that line is there i’m guessing!

The // in front of the define already tells PHP it’s turned off ?? You don’t have to delete it, I was trying to point out that, while you have wp super cache installed, you’re not using it.

Since your site is giving error 500s, and other memory errors, I’d really suggest using a cache plugin. WP Super Cache is pretty easy, almost a set and forget type app.

So, I can delete those two lines from the .php file? and my site will still work correct? if I don’t want the plugin, the best thing is to get VPN / Dedicated Server??

You can remove the lines, or leave them there, they aren’t doing anything at all right now ??

VPS (VPN is something else). Either way, having caching plugins is a good idea if your site gets a lot of traffic ??