View previous topic :: View next topic |
Author |
Message |
RTAdams89 -
Joined: 06 Nov 2005 Posts: 102
|
Posted: Fri Nov 17, 2006 5:21 am Post subject: PHP is causing Abyss to freeze (I think) |
|
|
The last fee days Abyss has sporadically been freezing (no access to the hosted files or the Abyss web interface). The only way to fix the problem is to restart the abyss service. It just happened again, so I pulled the traffic and fastcgi(for PHP) log files. Fortunately I just cleared them both, so there were only a handful of entrees. Anyhow, here is the traffic log:
Quote: | 192.168.1.101 - - [16/Nov/2006:21:08:01 -0700] "GET /adams/homepage/index.php HTTP/1.1" 200 4590
192.168.1.101 - - [16/Nov/2006:21:08:01 -0700] "GET /adams/homepage/search.js HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:08:01 -0700] "GET /adams/homepage/liveclock.js HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:08:01 -0700] "GET /adams/homepage/logo.gif HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET / HTTP/1.1" 301 52
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET /personal/index.html HTTP/1.1" 200 2720
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET /personal/layout/sample.css HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET /personal/layout/bg.gif HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET /personal/layout/containerBg.gif HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET /personal/layout/signature.gif HTTP/1.1" 200 2119
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET /personal/layout/welcome.gif HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET /personal/layout/aboutsite.gif HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET /personal/layout/aboutme.gif HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET /personal/layout/findingyourway.gif HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET /personal/layout/news.gif HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET /personal/layout/randomimg/rotate.php HTTP/1.1" 200 196461
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET /personal/layout/archives.gif HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET /personal/layout/links.gif HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:09:02 -0700] "GET /adams/ HTTP/1.1" 302 37
192.168.1.104 - - [16/Nov/2006:21:12:18 -0700] "GET /adams/homepage/index.php HTTP/1.1" 200 4590
192.168.1.104 - - [16/Nov/2006:21:12:18 -0700] "GET /adams/homepage/search.js HTTP/1.1" 304 0
192.168.1.104 - - [16/Nov/2006:21:12:19 -0700] "GET /adams/homepage/liveclock.js HTTP/1.1" 304 0
192.168.1.104 - - [16/Nov/2006:21:12:19 -0700] "GET /adams/homepage/logo.gif HTTP/1.1" 304 0
192.168.1.104 - - [16/Nov/2006:21:12:19 -0700] "GET /adams/homepage/rss2html.php?XMLFILE=http://feeds.feedburner.com/brainyquote/QUOTEBR&TEMPLATE=http://192.168.1.102/adams/homepage/quote-template.html&MAXITEMS=1 HTTP/1.1" 200 0
192.168.1.101 - - [16/Nov/2006:21:14:58 -0700] "GET /adams/homepage/index.php HTTP/1.1" 200 4590
192.168.1.101 - - [16/Nov/2006:21:14:58 -0700] "GET /adams/homepage/search.js HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:14:58 -0700] "GET /adams/homepage/liveclock.js HTTP/1.1" 304 0
192.168.1.101 - - [16/Nov/2006:21:14:58 -0700] "GET /adams/homepage/logo.gif HTTP/1.1" 304 0
|
And here is the fastcgi log:
Quote: | 16/Nov/2006:21:08:01 -0700 SUID: 0 PUID: 0 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
16/Nov/2006:21:08:01 -0700 SUID: 0 PUID: 0 RUID: 0 URI: timeout-header2!
16/Nov/2006:21:08:01 -0700 SUID: 1 PUID: 1 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
16/Nov/2006:21:08:01 -0700 SUID: 1 PUID: 1 RUID: 0 URI: timeout-header2!
16/Nov/2006:21:08:01 -0700 SUID: 2 PUID: 2 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
16/Nov/2006:21:08:01 -0700 SUID: 2 PUID: 2 RUID: 0 URI: timeout-header2!
16/Nov/2006:21:09:02 -0700 SUID: 0 PUID: 0 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
16/Nov/2006:21:09:02 -0700 SUID: 0 PUID: 0 RUID: 0 URI: timeout-header2!
16/Nov/2006:21:09:10 -0700 SUID: 1 PUID: 1 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
16/Nov/2006:21:09:10 -0700 SUID: 1 PUID: 1 RUID: 0 URI: timeout-header2!
16/Nov/2006:21:12:18 -0700 SUID: 2 PUID: 2 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
16/Nov/2006:21:12:18 -0700 SUID: 2 PUID: 2 RUID: 0 URI: timeout-header2!
16/Nov/2006:21:12:19 -0700 SUID: 3 PUID: 3 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
16/Nov/2006:21:12:19 -0700 SUID: 3 PUID: 3 RUID: 0 URI: timeout-header2!
16/Nov/2006:21:13:27 -0700 SUID: 0 PUID: 0 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
16/Nov/2006:21:13:27 -0700 SUID: 0 PUID: 0 RUID: 0 URI: timeout-header2!
16/Nov/2006:21:14:58 -0700 SUID: 1 PUID: 1 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
16/Nov/2006:21:14:58 -0700 SUID: 1 PUID: 1 RUID: 0 URI: timeout-header2!
|
As you can see, all the requests in the traffic log result in an error in the fastcgi log. All the errors are the same:
Quote: | Reading 0 bytes failed = The process cannot access the file because it is being used by another process. |
Yet the files being requested are all different. Any ideas what is going on / what to do. The only things I can think of doing recently was installing the latest PHP a while ago....
Of an here is a little background on the server:
Windows XP home
Abyss X1 latest version running as a service
PHP 5.2 set u pas fastcgi in Abyss. |
|
Back to top |
|
|
aprelium -
Joined: 22 Mar 2002 Posts: 6800
|
Posted: Fri Nov 17, 2006 1:05 pm Post subject: Re: PHP is causing Abyss to freeze (I think) |
|
|
RTAdams89,
We have fixed this problem (which does not occur always) in the coming version. Meanwhile, we suggest that you configure PHP to use the CGI interface instead of FastCGI. _________________ Support Team
Aprelium - http://www.aprelium.com |
|
Back to top |
|
|
RTAdams89 -
Joined: 06 Nov 2005 Posts: 102
|
Posted: Fri Nov 17, 2006 2:22 pm Post subject: |
|
|
Ok, I did that immediately after I posted my message. It wasn't helping at first, but at a reboot (which presumable ended some of the PHP processes still running) it seems OK now. |
|
Back to top |
|
|
RTAdams89 -
Joined: 06 Nov 2005 Posts: 102
|
Posted: Wed Jan 10, 2007 10:02 pm Post subject: |
|
|
I just updated to the new abyss version 2.4 and re enabled FastCGI. It no longer freezes, and everything seems OK, but i still get the following in the fastcgi log:
Quote: | 10/Jan/2007:13:56:02 -0700 SUID: 0 PUID: 0 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
10/Jan/2007:13:56:02 -0700 SUID: 0 PUID: 0 RUID: 0 URI: timeout-header2!
10/Jan/2007:13:56:02 -0700 SUID: 1 PUID: 1 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
10/Jan/2007:13:56:02 -0700 SUID: 1 PUID: 1 RUID: 0 URI: timeout-header2!
10/Jan/2007:13:56:02 -0700 SUID: 2 PUID: 2 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
10/Jan/2007:13:56:02 -0700 SUID: 2 PUID: 2 RUID: 0 URI: timeout-header2!
10/Jan/2007:13:56:02 -0700 SUID: 3 PUID: 3 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
10/Jan/2007:13:56:02 -0700 SUID: 3 PUID: 3 RUID: 0 URI: timeout-header2!
10/Jan/2007:13:56:02 -0700 SUID: 4 PUID: 4 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
10/Jan/2007:13:56:02 -0700 SUID: 4 PUID: 4 RUID: 0 URI: timeout-header2!
10/Jan/2007:13:57:40 -0700 SUID: 5 PUID: 5 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
10/Jan/2007:13:57:40 -0700 SUID: 5 PUID: 5 RUID: 0 URI: timeout-header2!
10/Jan/2007:14:00:42 -0700 SUID: 6 PUID: 6 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
10/Jan/2007:14:00:42 -0700 SUID: 6 PUID: 6 RUID: 0 URI: timeout-header2!
10/Jan/2007:14:00:42 -0700 SUID: 7 PUID: 7 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
10/Jan/2007:14:00:42 -0700 SUID: 7 PUID: 7 RUID: 0 URI: timeout-header2!
10/Jan/2007:14:00:43 -0700 SUID: 8 PUID: 8 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
10/Jan/2007:14:00:43 -0700 SUID: 8 PUID: 8 RUID: 0 URI: timeout-header2!
10/Jan/2007:14:00:43 -0700 SUID: 9 PUID: 9 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
10/Jan/2007:14:00:43 -0700 SUID: 9 PUID: 9 RUID: 0 URI: timeout-header2!
10/Jan/2007:14:00:43 -0700 SUID: 10 PUID: 10 RUID: 0 URI: Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
10/Jan/2007:14:00:43 -0700 SUID: 10 PUID: 10 RUID: 0 URI: timeout-header2!
|
Any thoughts? |
|
Back to top |
|
|
admin Site Admin
Joined: 03 Mar 2002 Posts: 1295
|
Posted: Wed Jan 10, 2007 10:14 pm Post subject: |
|
|
RTAdams89,
Thank you for the update.
The reported error is caused by PHP which does not usually "behave" as expected when started in FastCGI mode (there is a negotiation between the Web server and the FastCGI application that takes place at the startup of a FastCGI application, but PHP sometimes refuses to answer all the Web server queries about its capabilities hence the error).
This is not a major error and Abyss Web Server tolerates it. But it's reported by Abyss Web Server if you turn debugging to "Errors only". _________________ Follow @abyssws on Twitter
Subscribe to our newsletter
_________________
Forum Administrator
Aprelium - https://aprelium.com |
|
Back to top |
|
|
RTAdams89 -
Joined: 06 Nov 2005 Posts: 102
|
Posted: Wed Jan 10, 2007 10:38 pm Post subject: |
|
|
So, these messages are essentially normal and the underlying issue will present no issues for me? Are there plans to block this error from being reported in the future, or will my log keep growing with "false" errors? |
|
Back to top |
|
|
aprelium -
Joined: 22 Mar 2002 Posts: 6800
|
Posted: Thu Jan 11, 2007 3:01 pm Post subject: |
|
|
RTAdams89,
We confirm that there are no issues with that message. We'll offer an option to remove it in the next version. _________________ Support Team
Aprelium - http://www.aprelium.com |
|
Back to top |
|
|
|