Hello Frederick, On 05-ago-09, at 00:46, Frederick Reeve wrote:
> This is located at /usr/local/bin/nanoki. Not much to it really. It > starts nanoki's web server on 127.0.0.1:9454. I then put this in the > interpreter section of my information source: > > /usr/bin/screen -dmS nanoki /usr/local/bin/nanoki It doesn't need to be daemonized, actually. Since Cherokee launches the wiki, it'd make sense if it killed it on exit. Actually, that'd be the expected behaviour. > The sreen command is just used because nanoki doesn't demonize at > all so I use screen to force it (maybe I don't need to do this???). Yeah. I could not tell you for sure without some testing, although I suppose that screen is probably checking whether or not it's been launch from a tty. > This made no difference. The web server just returns a 502 when I > attempt to view proxied page. I would really like to see Cherokee > spawning this automatically is there something I am missing. Like I > said above if I start nanoki manually it works great so the rest of > the config is right. You can look at the pertinate config sections > here: > > (information source) > source!1!host = 127.0.0.1:9454 > source!1!interpreter = /usr/bin/screen -dmS nanoki /usr/local/bin/ > nanoki Try to launch the script directly. If it fails, launch cherokee from a terminal and check the "Spawning:" message it prints. In case that didn't give you any hint, CHEROKEE_TRACE would be your next best option [1]. By the way, are you launching the server as root? When you do that, it can use a different (slightly more sophisticated spawning mechanism). Cheers! 1.- http://www.cherokee-project.com/doc/dev_debug.html -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
