Website in question:
http://redbirdled.com/ (very apparent)
So RedBirdLED mainly loads fine but hangs many other times if I leave it alone and try to load a new page. The only way to get it to load is to try and load it again and it immediately loads after that. This is not a client issue as many people are reporting the problem. I've tried a few things such as idle-timeout and weird stuff with IIS already but it didn't help.
Overall the thing I am getting is that if I try to load something, it will wait and simply timeout from waiting. However if I press the button again immediately it is very likely to instantly load without issue. What is going on and is there any way I can trace the issue?
I'm going to assume it has little to do with idling unless it is possible to idle within 10 seconds... This issue is random at times. I don't understand what is happening.
Visit http://sole-revival.com/ and let me know if there are any issues. For me personally, the website runs PERFECTLY and without issue. That's the weirdest part. Some pools hang and some don't? I have never modified these pools from the default setting until tonight as I try to resolve the issue.
I'm using IIS 8.0 on Win Server 2012.
Related
I am new in share point. I just made some static site and host it on server, its was working fine. due to some reason I change my server location now this site is responding very slow. I did not get any root cause why its happening, even there is 5 more share point sites all are working very slow. May be there is some configuration problem please help me to fix it
Sounds like IIS is rebuilding the cache. This happens whenever the server is rebooted, or sharepoint is loaded in a new/different web server. Typically the speed increases after a few minutes as everything gets cached.
What #marten said is correct.. its takes time for distributed cache service to kick in for new server. also check if there is any app pool/IIS recycling schedule is applied on new server.
I'm making an app in the Cloud9 IDE using Node.js with the Express.js framework. Something very odd is happening to a specific .ejs file where if I try to update it (like typing some mumbo jumbo in an h1 tag and then saving and restarting the server), it NEVER gets reflected in the browser no matter what I do. For example, if I delete my jumbotron, save, restart the server, and then refresh the browser, I still see the same page with the jumbotron. I also tried deleting this entire file and then restarting the server and I still see the page and it doesn't break my application which is bizarre. All other .ejs files are fine and I can see the changes that I make.
I've spent about 4 hours trying to figure this out and no one else seems to have my specific issue. I tried clearing my browser cache, using different browsers, logging in/out from Cloud9, creating a new database, going back to older versions of my code, etc. and nothing seems to be working. I'm not even sure what code to post on here since my entire app is about 2000 lines of code so far. Does anyone have any suggestions because this is really frustrating.
I have a webAPI deployed on window azure, till last week I was able to run the WebAPI and debug but all of a sudden when I run the web application I get the below message.
Role instances are taking longer than expected to start. Do you want
to continue waiting?
And I tried to enable disable caching(default caching is disable) and also cleared the local storage but still the same issue persist, its happening in not only my machine but also on other dev machine as well. Could it be because of automatic software updates related to emulator or other SW or any other issue?
Happened withh me today. I ran into an issue of the Azure emulator not working. The roles were going in a continuous loop of Running, Busy and Suspended.
Initially I thought it might be due to some code I had changed ď. However, it turned out that a recent Windows update had caused this issue.
After spending a frustrating amount of time un-installing the recent updates one by one, I found the miscreant.
For Fix please un-install the Security Update KB3126593 (https://support.microsoft.com/en-us/kb/3126593).
While searching for the particular update, make sure you type âKB3126593â in the search bar. Typing 3126593 will not work.
I'm currently developing a web application running locally on IIS 10 with coldfusion 9.
I have a problem right now, caused by SSL I think. Since it's a backoffice, it has to be https, so I used our company certificate to install it locally on my computer and I linked it to the website I'm developing. The problem is whenever I use the https connection, all the pages are loaded twice (it isn't visible, but for instance when I submit a form, the data are inserted twice in the database).
I manage, with luck, to solve this issue by changing the SSL parameters "client certificates" from ignore to accept but when I do that, from time to time (like 1 out of 3) the page that I want to load takes forever (like 30s) and as I can see, uses 100% of the CPU.
It doesn't come from my code (I think) because when I navigate with http, I have none of the problem listed above.
Does anyone have an idea with this is happening and how to solve it ?
Thanks in advance ! If you need any further information, ask and I'll try to give it to you !
I've now installed Coldfusion 11 and with that the issue is not happening anymore. So I'm pretty sure it's a compatibility answer.
I have a suite of tests for our website using Sahi. These tests are automated and feed into our Jenkins build system.
The tests run on a dedicated PC that is used for nothing else. It has Sahi plus all the browsers installed. The Jenkins server makes a remote call to the testing PC to run the tests. Due to the time it takes to run all the tests, this functional test suite is run overnight.
For several months this system was all working beautifully. But suddenly one day a few weeks ago I came into the office and found that all the tests had failed. they haven't worked since. As far as I know, nothing significant has changed (we obviously keep the browser versions up-to-date, but I don't think the failure co-incided with any updates; Sahi itself hasn't had an update since last year)
I've done some work to find out what's happening:
Sahi uses a proxy as part of it's browser control magic, and I believe that this proxy is the source of the problem. But I can't work out how or why.
When the browser under Sahi's control loads the page to be tested, it seems none of the HTTP requests are succeeding. The raw page content is shown (I think because it's cached), but none of the styles, graphics or scripts (except those already cached by the browser). Furthermore, the Sahi script then tries to click on a button to proceed through the test, but the browser fails to load anything. Sahi waits for a bit, but eventually the script times out and the test fails.
I can replicate this on the affected PC when running Sahi manually. It happens on any site, and in all browsers. However it doesn't happen on my own desktop PC, which has the same versions of all the relevant software installed. And of course, it worked fine in the past on the test box.
I have tried uninstalling Sahi and the browsers, and re-installing from scratch. This has not made any difference. (I appreciate that uninstalling often doesn't actually delete everything, so perhaps there's more I could do here?)
I'm really hoping someone can help me here, because I'm unsure what else to try.
Many thanks in advance.
Since it happens on all browsers, it looks like a firewall setting may be preventing access to port 9999. Turn off the firewall and check. If you see any exceptions on the Sahi console, you could post that too.
I wasn't able to get to the bottom of this. I suspect it was something blocking the Sahi proxy from working, but I couldn't find the culprit.
I'd wasted too much time on it, and the machine it was running on wasn't being used for anything else anyway, so my final solution to this was to re-install the OS from scratch.
This has solved the problem. It hasn't helped me understand why it happened, but as long as it's working, eh?
Thank you to everyone who stopped by.