Thanks Stephen. I didn’t expect you to deal with it during the isues, just wanted to post a reminder for when you had time.
The site has seemed faster but it seems fine for a few minutes, then it doesn’t respond for a few minutes and so on. We noticed it as did an external monitoring service that seen the site down as well. At the same time we check sites on other servers and they are fine. It always seems to be Win13. Perhaps it is the SQL Server causing issues since these are all DNN3 sites, not sure, I just know we have had a lot of problems on this server from day 1.
PS - Right now the sites seem super fast, but agian it seems to come and go.
Mark my words, one day hosts are going to only allow approved CMS’s to be used on shared systems, and only allow higher-priced accounts to use custom code. Too many irresponsible coders out there!
Thanks Stephen, hopefully this will clean things up.
We were reviewing a site with a client last night around 7-8PM EST and our sites were not very well and at times were totally timing out (perhaps you were wrokign on it or it was another internet issue), however by about 9PM it seemed to be workign really well and it is working fine this morning. I’ll keep and eye on it and let you know.
Win13 having issues again? First no sites worked, now some up but others not. Was good for a while there but now seems back to same old issue from before.
There seems to be a conspiracy.. I couldn’t FTP to Win11 earlier, but after 30 minutes it comes right again, immediately after which I get a ticket reply that says, “can’t see anything wrong..” lol
[QUOTE=antic]
There seems to be a conspiracy.. I couldn’t FTP to Win11 earlier, but after 30 minutes it comes right again, immediately after which I get a ticket reply that says, “can’t see anything wrong..” lol
[/QUOTE]
Ya that often seems to be the case, few minutes of “please wait” then it magically starts working 8)
For my outage today however I had 3 different monitoring services report it as well as the fact I couldn’t connect either so I’m pretty sire it was server issues again.
Schooner, your site was down for 10 minutes according to the monitoring that monitors once per minute, this was 4 hours and 14 minutes ago, when for some reason all pools restarted without an IISreset, I will be speaking with techs to find what happened at this time.
Oh, and about win7 and win11, we have FTP checks each minute that showed them to be fine, what error were you getting there?
Hi Stephen. FTP Explorer just didn’t want to connect to them for about 30 mins… win13 was fine, twas only 7 and 11. When I tried to connect, it just sat there, not getting any response back from the server. I could go back and forth and connect ok to 13, which is why I thought it must have been those servers? Came right after a bit, so no biggie. Always happens when one is in a rush for something.
[QUOTE=Stephen]
Schooner, your site was down for 10 minutes according to the monitoring that monitors once per minute, this was 4 hours and 14 minutes ago, when for some reason all pools restarted without an IISreset, I will be speaking with techs to find what happened at this time.
Oh, and about win7 and win11, we have FTP checks each minute that showed them to be fine, what error were you getting there?
[/QUOTE]
Thanks Stephen that sounds about right it being down for 10 minutes. We noticed since we were using the site at the time plus we got notices from all our monitoring services. This has been the only outage we noticed during work hours in some time so thigns are better overall. Only outages we see now are late each night which I am assuming is a scheduled restart or backup.
Looks like the issues are back again. Some sites on Win13 ok, other one not ?(
Manish is working on it but took some coaxing as he said it was fine at first but actually only first page would load, not subpages so appeared it was cached. Can ping site fine.
Yes it is fine NOW, after the pool was reset. It certainly wan’t when I contacted support. Hence why I said there was an issue. Please don’t imply this is an issue on our end as it was clearly the pool that caused this issue and the site was fine after this was looked into.
