Torben,
That is what i thought as well. But i have two more oacs boxes running under the same aolserver instance. Those are mirrors of the one that got the error and they have no errors at all. Thank GOD! I guess if the problem was aolserver the error would show up on them too. Or maybe not, depending on what broke in AOLServer i believe.
So, I followed you and I debugged and compared the config.tcl with the current one availlable on CVS HEAD. Everything seems fine.
I also tested some pages: static such as robots.txt and dinamic such as adp and tcl pages. Everything seems fine again.
Then, Eureka!
Dave, you gave me a good intuition. I checked access logs and compared it against the error at error.log.
i saw this line bellow repeated many times:
[10/Sep/2009:23:07:16 -0700] "GET /project-manager/fred-dispatch-development/?project%5fitem%5fid=2548 HTTP/1.1" 200 89135 "http://iurix\
.com:8090/project-manager/" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.13) Gecko/2009080315 Ubuntu/9.04 (jaunty) Firefox/3.0.13" 1.778940 "style=null\; ad_user_login=643%2c1252527899%2c1600821E2+%7b714+0+300FF92F605B71EC439DC07787D1BDF782E77C99%7d; ad_session_id=310101%2c643%2c1+%7b343+1252553651+FD87497E91F95B028350A385B39C361B8F60A20E%7d"
Their log time match and that caught my attention. So, i reinstalled project-manager and the error is gone!
Although, this error is weird to me. It means that aolserver is locked up with project-manager application.
Or even worst, pm did something bad to aolserver installation. But those are just ideas. I need to debug it
