From: Steve V. <vi...@ie...> - 2014-06-04 12:54:46
|
On Fri, May 30, 2014 at 10:18 PM, Bob Paddock <bob...@gm...> wrote: > On Fri, May 30, 2014 at 9:22 PM, Steve Vinoski <vi...@ie...> wrote: > > The errors you show have nothing to with Yaws, but rather are problems > with > > DokuWiki. > > Yes, I relize that. I was hoping there was something Yaws could do to > fix the problem, or prevent it. > > I do wonder why Yaws that is returning the "connection refused" error, > don't see how a crashed process can refuse anything? > The "connection refused" error could be coming from your server process when it isn't quite yet crashed but is heading in that direction. The default listen backlog on a TCP connection is 5, so if your FCGI server is off the tracks and isn't performing accept() calls, then Yaws could get ECONNREFUSED when attempting to connect to the server. One way to test this would be to raise the listen backlog on your FCGI server to see if the "connection refused" errors go away. > > What OS are you trying to run this on? > > Gentoo Linux. > One interesting question here is why the DokuWiki /tmp session files are causing permissions errors. Are there multiple instances of DokuWiki running that are somehow stomping on each other, or are there leftover session files in /tmp from some other instance? Are permissions on /tmp correct? --steve |