Re: [WebDNA] Re: WebDNA 7 fastcgi fails to start
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107213
interpreted = N
texte = Sorry Chris, the rest of the info you sent me didn't help, I'm still stuck with the same problem so I think it is caused by a bad WebDNA configuration. One thing I noticed is that the files in /usr/lib/ are symlinks. I'm not sure if they were symlinks in the previous version of Debian or not ... but if they were not, would this create any problems? I don't think it should, but I thought I would ask anyways. I think we need a script that checks our WebDNA 7 dependencies and reports what's missing or misconfigured so we can quickly identify and fix problems like these. ---------- As in the previous version of Debian, I created a symlink pointing from /usr/lib/libssl.so.6 to /usr/lib/libssl.so. Then I got curious and did a readlink: /usr/lib/libssl.so.6 --> /usr/lib/libssl.so /usr/lib/libssl.so --> libssl.so.0.9.8 ... so I guess I should ask, is libssl.so.0.9.8 the correct file for use with WebDNA 7 on Debian 6? If not, then maybe this is the source of the problem ... Or is WebDNA looking for /usr/lib/libssl.so.5 or some other file name, and it cannot find it because I made a symlink with the name libssl.so.6? Sincerely, Kenneth Grome > Hi Chris, > > Thanks for the info and links. > > The new lighttpd.conf file is different from the previous > version. Among other changes, they moved the mime type > setting into a separate file. After reading your comment > about the mime types I commented out this line in the new > lighttpd.conf file: > > # include_shell > "/usr/share/lighttpd/create-mime.assign.pl" > > ... and replaced it with my previous mime type settings. > This I stopped the "It looks like a binary file, do you > want to download it?" problem, so the mime type issue is > fixed. > > But now the page displays in the browser as uninterpreted > WebDNA code, so my next step is to figure out why ... > > Sincerely, > Kenneth Grome > > > This is the lighttpd configuration: it does not know > > that .dna should be sent as text/html Also, it seems > > lighttpd has some trouble finding a library. Maybe > > this page could help? > > > > http://www.linuxquestions.org/questions/linux-software- > > 2/ > > slackware-13-64-bit-php-5-3-0-lighttpd-1-4-23-fastcgi- > > pro blems-761575/ > > http://nixcraft.com/web-servers/14232-lighttpd-chroot-j > > a il-again.html > > > > - chris > > > > On Aug 15, 2011, at 13:49, Kenneth Grome wrote: > > > By the way, when this happens Firefox thinks my > > > "index.dna" file is a binary file, so is asks me if I > > > want to download it. Then if I say "yes" I end up > > > downloading the raw template file with all my > > > uninterpreted WebDNA code visible in it. > > > > > > Sincerely, > > > Kenneth Grome > > > > > >> 2011-08-15 11:16:43: (log.c.166) server started > > >> 2011-08-15 11:16:43: (mod_fastcgi.c.1104) the > > >> fastcgi- backend /var/www/WebDNA/WebDNA.fcgi failed > > >> to start: 2011-08-15 11:16:43: (mod_fastcgi.c.1108) > > >> child exited with status 127 > > >> /var/www/WebDNA/WebDNA.fcgi 2011-08-15 11:16:43: > > >> (mod_fastcgi.c.1111) If you're trying to run your > > >> app as a FastCGI backend, make sure you're using > > >> the FastCGI-enabled version. > > >> If this is PHP on Gentoo, add 'fastcgi' to the USE > > >> flags. 2011-08-15 11:16:43: (mod_fastcgi.c.1399) > > >> [ERROR]: spawning fcgi failed. > > >> 2011-08-15 11:16:43: (server.c.938) Configuration of > > >> plugins failed. Going down. > > >> > > >> ---------------- > > >> > > >> I found this in my lighttpd error log after I > > >> upgraded one of my VPSs from Debian 5 Lenny to > > >> Debian 6 Squeeze, and I'm not sure how to fix it. > > >> Any ideas? > > >> > > >> Yes the WebDNA.fcgi file exists in the designated > > >> folder. > > >> > > >> Can WebDNA.fcgi and its containing folder(s) have > > >> permissions 777? Or would this permission setting > > >> prevent WebDNA from starting? > > >> > > >> Running lighttpd/1.4.28 (ssl) > > >> > > >> Sincerely, > > >> Kenneth Grome > > > > > > ----------------------------------------------------- > > > -- -- This message is sent to you because you are > > > subscribed to the mailing list
. To > > > unsubscribe, E-mail to: > > > archives: http://mail.webdna.us/list/talk@webdna.us > > > Bug Reporting: support@webdna.us > > > > ------------------------------------------------------- > > -- This message is sent to you because you are > > subscribed to the mailing list . > > To unsubscribe, E-mail to: > > archives: http://mail.webdna.us/list/talk@webdna.us > > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
Sorry Chris, the rest of the info you sent me didn't help, I'm still stuck with the same problem so I think it is caused by a bad WebDNA configuration. One thing I noticed is that the files in /usr/lib/ are symlinks. I'm not sure if they were symlinks in the previous version of Debian or not ... but if they were not, would this create any problems? I don't think it should, but I thought I would ask anyways. I think we need a script that checks our WebDNA 7 dependencies and reports what's missing or misconfigured so we can quickly identify and fix problems like these. ---------- As in the previous version of Debian, I created a symlink pointing from /usr/lib/libssl.so.6 to /usr/lib/libssl.so. Then I got curious and did a readlink: /usr/lib/libssl.so.6 --> /usr/lib/libssl.so /usr/lib/libssl.so --> libssl.so.0.9.8 ... so I guess I should ask, is libssl.so.0.9.8 the correct file for use with WebDNA 7 on Debian 6? If not, then maybe this is the source of the problem ... Or is WebDNA looking for /usr/lib/libssl.so.5 or some other file name, and it cannot find it because I made a symlink with the name libssl.so.6? Sincerely, Kenneth Grome > Hi Chris, > > Thanks for the info and links. > > The new lighttpd.conf file is different from the previous > version. Among other changes, they moved the mime type > setting into a separate file. After reading your comment > about the mime types I commented out this line in the new > lighttpd.conf file: > > # include_shell > "/usr/share/lighttpd/create-mime.assign.pl" > > ... and replaced it with my previous mime type settings. > This I stopped the "It looks like a binary file, do you > want to download it?" problem, so the mime type issue is > fixed. > > But now the page displays in the browser as uninterpreted > WebDNA code, so my next step is to figure out why ... > > Sincerely, > Kenneth Grome > > > This is the lighttpd configuration: it does not know > > that .dna should be sent as text/html Also, it seems > > lighttpd has some trouble finding a library. Maybe > > this page could help? > > > > http://www.linuxquestions.org/questions/linux-software- > > 2/ > > slackware-13-64-bit-php-5-3-0-lighttpd-1-4-23-fastcgi- > > pro blems-761575/ > > http://nixcraft.com/web-servers/14232-lighttpd-chroot-j > > a il-again.html > > > > - chris > > > > On Aug 15, 2011, at 13:49, Kenneth Grome wrote: > > > By the way, when this happens Firefox thinks my > > > "index.dna" file is a binary file, so is asks me if I > > > want to download it. Then if I say "yes" I end up > > > downloading the raw template file with all my > > > uninterpreted WebDNA code visible in it. > > > > > > Sincerely, > > > Kenneth Grome > > > > > >> 2011-08-15 11:16:43: (log.c.166) server started > > >> 2011-08-15 11:16:43: (mod_fastcgi.c.1104) the > > >> fastcgi- backend /var/www/WebDNA/WebDNA.fcgi failed > > >> to start: 2011-08-15 11:16:43: (mod_fastcgi.c.1108) > > >> child exited with status 127 > > >> /var/www/WebDNA/WebDNA.fcgi 2011-08-15 11:16:43: > > >> (mod_fastcgi.c.1111) If you're trying to run your > > >> app as a FastCGI backend, make sure you're using > > >> the FastCGI-enabled version. > > >> If this is PHP on Gentoo, add 'fastcgi' to the USE > > >> flags. 2011-08-15 11:16:43: (mod_fastcgi.c.1399) > > >> [ERROR]: spawning fcgi failed. > > >> 2011-08-15 11:16:43: (server.c.938) Configuration of > > >> plugins failed. Going down. > > >> > > >> ---------------- > > >> > > >> I found this in my lighttpd error log after I > > >> upgraded one of my VPSs from Debian 5 Lenny to > > >> Debian 6 Squeeze, and I'm not sure how to fix it. > > >> Any ideas? > > >> > > >> Yes the WebDNA.fcgi file exists in the designated > > >> folder. > > >> > > >> Can WebDNA.fcgi and its containing folder(s) have > > >> permissions 777? Or would this permission setting > > >> prevent WebDNA from starting? > > >> > > >> Running lighttpd/1.4.28 (ssl) > > >> > > >> Sincerely, > > >> Kenneth Grome > > > > > > ----------------------------------------------------- > > > -- -- This message is sent to you because you are > > > subscribed to the mailing list . To > > > unsubscribe, E-mail to: > > > archives: http://mail.webdna.us/list/talk@webdna.us > > > Bug Reporting: support@webdna.us > > > > ------------------------------------------------------- > > -- This message is sent to you because you are > > subscribed to the mailing list . > > To unsubscribe, E-mail to: > > archives: http://mail.webdna.us/list/talk@webdna.us > > Bug Reporting: support@webdna.us
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
REPOST: How do _you_ back up your db? (2000)
Misc Stuff That Might Help (1997)
[BULK] RE: [WebDNA] [BULK] Web Merchant Authorize net issues (2011)
[WebDNA] SkipJack Authorize interface help (2009)
different show next (1997)
DrWatson Error! (1999)
SOP for WebDNA talk (2004)
WebCatalog Hosting (1998)
Formulas.db (2001)
Nested tags count question (1997)
Browser Reloads and AddlineItem (1997)
Problem (1997)
Problem with Formulas.db (1999)
select multiple (1997)
Price Not Appearing (2000)
Using [showif] within [lineitems] [code fragment] (2000)
problems with 2 tags (1997)
Sorting ip addresses (2002)
SHOWIF [var_with_backslash]^[value] (2002)
[WebDNA] Re-sending email (2018)