Partner and Community Forums
Issue with app pool and included files
Last post Jan 03, 2020 12:50 AM by JuanMdP
Dec 29, 2019 10:33 PM|JuanMdP|LINK
We've a server running Windows Server 2008 R2 with IIS + PHP 5.5. It's been running for the past two years with one or two issues here and there but unrelated to what started happening two days ago: site will throw file missing errors even though they exist.
"Fix" is to restart the app pool, then files are found again. Anyone knows what could be causing this~?
Nothing has changed nor has been installed on the server; checking PHP error logs doesn't show me that other errors are happening at the time files cease to be found. I'm wary that maybe something physical could be at play here but since the issue is so
silly and obscure, I haven't found any information online; any kind of pointers or insight would be greatly appreciated~.
Dec 29, 2019 10:39 PM|lextm|LINK
Enable FRT to learn more https://docs.microsoft.com/en-us/iis/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis
The important hint is to learn which part of the PHP pipeline throws the errors, as that determines what to do next,
BTW, PHP 5.5 is long dead, and Windows Server 2008 R2 also reaches end of life. So staying on them is clearly not a good choice today.
Dec 29, 2019 10:44 PM|JuanMdP|LINK
FRT has been enabled all along and hasn't registered anything at the times it happened. I realize both WS2008 and PHP are dated but it's not like migrating everything comes cheap; that's 9 out of 10 not an answer when companies and institutions have other
Dec 30, 2019 07:34 AM|lextm|LINK
FRT has been enabled all along and hasn't registered anything at the times it happened
Create another site and test if FRT works for that one. You really need FRT to work so as to collect enough data to analyze.
Also in the worst case, show us the error page that files cannot be found. The exact screen shot contains much more information than you thought.
Jan 03, 2020 12:50 AM|JuanMdP|LINK
FTR works because it's picking up errors; say, I force a 500 or a call a page that doesn't exist, I'll get the respective FTR files. That said.. I think I misunderstood what's going on. Years ago I had the issue described in my OOP but reading the PHP error
log I can see that the issue is always the same: connection to the database fails to be established. I thought maybe, like it happened years ago, it was missing a file and that file could've had the DB connection info.
However, with other tests I see this isn't the case. Connection to a SQL server drops and unless the App Pool is restarted, it can't be established again. What I can't figure out is why? I mean, this is something that's been running for years and there've
been no changes made to the DB configuration. I've read some articles online where people experienced this (though using Asp.Net) but no clear cause as to why this would happen. Again, all the more baffling given that the app remains the same and so the config.
But in a nutshell, the issue is different: it's related to the connection. Should I close this thread and post on a different section of the forum or is it ok to keep this here?