Hi, I have a Fossil setup running on Debian 7.8 64-bit inside OpenVZ container. I use nginx and xinetd to host my repositories. When I build Fossil from source without Tcl support - everything works fine. But when I build Fossil --with-tcl (Tcl 8.5), I can't display any repository through browser.
I couldn't find any other info than nginx complaining about wrong HTTP headers returning from "upstream" and then about connection reset by "upstream" (upstream in nginx's terminology is a cluster that nginx can proxy requests to). I build Fossil on my local Debian 7.8 64-bit Virtualbox image and then put it on VPS with the same OS version. Both have required libraries installed. The Fossil binary itself seems to be working on-site when used in command line mode. "Fossil open", "version" and "help" do what they're supposed to do. Also running "fossil server" on Virtualbox seems to work fine, as I can browse repository through it's web interface. Only xinetd + nginx seem to be not working for some reason (on both Virtualbox image and VPS) unless I switch to Fossil binary compiled without Tcl support. The flag I used to compile Fossil was --with-th1-hooks and --with-tcl=<path_to_tclConfig.sh>. Also there's HTTPS and readline support built-in. So the question is, does Tcl support require some special steps or environment setup to work? Is there any other thing I should check or look at? Thanks in advance! -- Pozdrawiam / With best regards, Orzech
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
