I restarted one pool that was using a lot of memory and should not have been, it is responding better now, cpu load is a bit high now due to the backup running but the server is working much better overall.
Start at 3am but mssql5 is taking longer than usual recently.
I am not seeing any issue on either right now however.
Actually, just checking win7 it is goign fast then slow, then fast, so it is not mssql5, it is win7. Will assign someone to watch it for abusing domain today, sounds like someone may have some misbehaving code.
I might have to get you to change a major site of mine on Win7 to a different server - or is it just the pool that’s slowing down?
I just got a few script timeouts on this site which is a major client of mine, and I’d like to not have this happen on this app. It’s an ecommerce site and I can tell by the logs that PayPal IPN is getting script timeouts as well when it posts back to the site’s IPN script. From the log:
2007-04-02 14:04:41 POST /paypalipn.asp - ASP_0113|Script_timed_out
So this is getting a bit bothersome. What are my options here?
Downtime is not anything really, as the DNs and site stays both servers for 24 hours, so even dns cache going to old will still work.
You said you need asp.net 2 anyway, so its the best bet to move before it is urgently needed.
I have formally notified Jodo that that domain sends bulk emails to site members - will I have to do so again once it’s moved to the new server?
[edit] It’s worth mentioning that this level of support for “elective surgery” is much appreciated and separates Jodo from the run of the mill providers out there.
Just a quick update to say the changeover went smooth as silk, even though that account was a bit “unusual” - special settings etc. I didn’t have to adjust a thing. Well done and thank you! mwah!