From: Douglas B. <douglas.burchard@DouglasBurchard.com> - 2004-03-16 17:18:42
|
First post, have only been lurking about 12 days... I've been stymied trying to get Webware/WebKit/mod_webkit to work on a Mac OS X 10.3.2 machine. Everything seems to load okay, so either I'm missing something really obvious, or something is interfering with the works. Here's what I've done: Downloaded Webware 0.8.1 from <http://webware.sourceforge.net/>. Placed the resulting folder in my Applications directory. Ran the install files: $ cd /Applications/Webware/ $ python install.py -v $ cd /Applications/Webware/WebKit/Adapters/mod_webkit/ $ sudo make install Added the following directives to httpd.conf (LoadModule and AddModule were added automatically): AddType text/psp .psp AddHandler psp-handler .psp <Location /wk> WKServer localhost 8086 SetHandler webkit-handler </Location> Restarted Apache and launched the AppServer with: $ apachectl graceful $ cd /Applications/Webware/WebKit/ $ sudo ./AppServer & When I point my browser to http://localhost/wk (or any variant I can think of like /wk/, /wk/Admin, /wk/Examples, etc.) I get a standard Apache 404 error. A port scan shows port 8086 (the AppServer port) open. I've read, and re-read, the Webware/WebKit/mod_webkit docs, along with the results of several Google searches, and haven't hit upon what I'm missing. Any pointers to help me locate what are most likely gaps in my knowledge will be greatly appreciated. -- Douglas Burchard |
From: YOON. Joo-Y. <yjy...@ar...> - 2004-03-16 18:15:34
|
On Tue, Mar 16, 2004 at 09:18:29AM -0800, Douglas Burchard wrote: > First post, have only been lurking about 12 days... > > I've been stymied trying to get Webware/WebKit/mod_webkit to work on a > Mac OS X 10.3.2 machine. Everything seems to load okay, so either I'm > missing something really obvious, or something is interfering with the > works. Here's what I've done: > > Downloaded Webware 0.8.1 from <http://webware.sourceforge.net/>. Placed > the resulting folder in my Applications directory. Ran the install > files: > > $ cd /Applications/Webware/ > $ python install.py -v > $ cd /Applications/Webware/WebKit/Adapters/mod_webkit/ > $ sudo make install > > Added the following directives to httpd.conf (LoadModule and AddModule > were added automatically): > > AddType text/psp .psp > AddHandler psp-handler .psp > > <Location /wk> > WKServer localhost 8086 > SetHandler webkit-handler > </Location> > > Restarted Apache and launched the AppServer with: > > $ apachectl graceful > $ cd /Applications/Webware/WebKit/ > $ sudo ./AppServer & > IMHO, you missed installing adaptor, such as WebKit.cgi or mod_webkit2. > When I point my browser to http://localhost/wk (or any variant I can > think of like /wk/, /wk/Admin, /wk/Examples, etc.) I get a standard > Apache 404 error. > > A port scan shows port 8086 (the AppServer port) open. I've read, and > re-read, the Webware/WebKit/mod_webkit docs, along with the results of > several Google searches, and haven't hit upon what I'm missing. > > Any pointers to help me locate what are most likely gaps in my > knowledge will be greatly appreciated. > > > -- > Douglas Burchard > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Webware-discuss mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webware-discuss -- YOON, Joo-Yung from Korea |
From: John D. <hc...@te...> - 2004-03-16 20:11:04
|
I had the same problem on my OS X box at home. My solution was to change the Location tag in the apache config to 127.0.0.1 (instead of localhost). It seems to work fine after I did that. --John At 11:18 AM 3/16/2004, Douglas Burchard wrote: >First post, have only been lurking about 12 days... > >I've been stymied trying to get Webware/WebKit/mod_webkit to work on a Mac >OS X 10.3.2 machine. Everything seems to load okay, so either I'm missing >something really obvious, or something is interfering with the works. >Here's what I've done: > >Downloaded Webware 0.8.1 from <http://webware.sourceforge.net/>. Placed >the resulting folder in my Applications directory. Ran the install files: > > $ cd /Applications/Webware/ > $ python install.py -v > $ cd /Applications/Webware/WebKit/Adapters/mod_webkit/ > $ sudo make install > >Added the following directives to httpd.conf (LoadModule and AddModule >were added automatically): > > AddType text/psp .psp > AddHandler psp-handler .psp > > <Location /wk> > WKServer localhost 8086 > SetHandler webkit-handler > </Location> > >Restarted Apache and launched the AppServer with: > > $ apachectl graceful > $ cd /Applications/Webware/WebKit/ > $ sudo ./AppServer & > >When I point my browser to http://localhost/wk (or any variant I can think >of like /wk/, /wk/Admin, /wk/Examples, etc.) I get a standard Apache 404 error. > >A port scan shows port 8086 (the AppServer port) open. I've read, and >re-read, the Webware/WebKit/mod_webkit docs, along with the results of >several Google searches, and haven't hit upon what I'm missing. > >Any pointers to help me locate what are most likely gaps in my knowledge >will be greatly appreciated. > > >-- >Douglas Burchard > > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >_______________________________________________ >Webware-discuss mailing list >Web...@li... >https://lists.sourceforge.net/lists/listinfo/webware-discuss |
From: Scott R. <sc...@to...> - 2004-03-16 21:04:36
|
Is your /etc/hosts file set up improperly, by any chance? On Tue, 2004-03-16 at 15:13, John Dickinson wrote: > I had the same problem on my OS X box at home. My solution was to change > the Location tag in the apache config to 127.0.0.1 (instead of localhost). > It seems to work fine after I did that. > > --John > > At 11:18 AM 3/16/2004, Douglas Burchard wrote: > >First post, have only been lurking about 12 days... > > > >I've been stymied trying to get Webware/WebKit/mod_webkit to work on a Mac > >OS X 10.3.2 machine. Everything seems to load okay, so either I'm missing > >something really obvious, or something is interfering with the works. > >Here's what I've done: > > > >Downloaded Webware 0.8.1 from <http://webware.sourceforge.net/>. Placed > >the resulting folder in my Applications directory. Ran the install files: > > > > $ cd /Applications/Webware/ > > $ python install.py -v > > $ cd /Applications/Webware/WebKit/Adapters/mod_webkit/ > > $ sudo make install > > > >Added the following directives to httpd.conf (LoadModule and AddModule > >were added automatically): > > > > AddType text/psp .psp > > AddHandler psp-handler .psp > > > > <Location /wk> > > WKServer localhost 8086 > > SetHandler webkit-handler > > </Location> > > > >Restarted Apache and launched the AppServer with: > > > > $ apachectl graceful > > $ cd /Applications/Webware/WebKit/ > > $ sudo ./AppServer & > > > >When I point my browser to http://localhost/wk (or any variant I can think > >of like /wk/, /wk/Admin, /wk/Examples, etc.) I get a standard Apache 404 error. > > > >A port scan shows port 8086 (the AppServer port) open. I've read, and > >re-read, the Webware/WebKit/mod_webkit docs, along with the results of > >several Google searches, and haven't hit upon what I'm missing. > > > >Any pointers to help me locate what are most likely gaps in my knowledge > >will be greatly appreciated. > > > > > >-- > >Douglas Burchard > > > > > > > >------------------------------------------------------- > >This SF.Net email is sponsored by: IBM Linux Tutorials > >Free Linux tutorial presented by Daniel Robbins, President and CEO of > >GenToo technologies. Learn everything from fundamentals to system > >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > >_______________________________________________ > >Webware-discuss mailing list > >Web...@li... > >https://lists.sourceforge.net/lists/listinfo/webware-discuss > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Webware-discuss mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webware-discuss |
From: Douglas B. <douglas.burchard@DouglasBurchard.com> - 2004-03-16 21:01:30
|
On Mar 16, 2004, at 9:59 AM, John Dickinson wrote: > I had the same problem on my OS X box at home. My solution was to > change the Location tag in the apache config to 127.0.0.1 (instead of > localhost). It seems to work fine after I did that. Hmm, I changed 'WKServer localhost 8086' to 'WKServer 127.0.0.1 8086' in the httpd.conf file and restarted apache. No luck, still get the same 404 page. -- Douglas Burchard |
From: Douglas B. <douglas.burchard@DouglasBurchard.com> - 2004-03-16 21:09:41
|
On Mar 16, 2004, at 9:37 AM, Roger Espinosa wrote: > Mmm. This is a lark, but you didn't say --- you'll need to do > > sudo apachectl graceful (or restart) Nice catch, but just my bad typing. I did in fact use sudo when restarting apache. :-} > You should also check what's showing up in /var/log/httpd/error_log... The 404 page simply generates what I would expect: [Tue Mar 16 10:04:24 2004] [error] [client 127.0.0.1] File does not exist: /Library/WebServer/Documents/mk During the restart of apache it does show the mod_webkit adaptor loading: [Tue Mar 16 10:04:00 2004] [notice] SIGUSR1 received. Doing graceful restart [Tue Mar 16 10:04:00 2004] [notice] Apache/1.3.29 (Darwin) mod_webkit/0.5 configured -- resuming normal operations [Tue Mar 16 10:04:00 2004] [notice] Accept mutex: flock (Default: flock) > I can tell you it *does* work, at any rate... *This* is encouraging at least. :-) -- Douglas Burchard |
From: Todd G. <to...@sl...> - 2004-03-16 23:12:13
|
* Douglas Burchard <douglas.burchard@DouglasBurchard.com> [2004-03-16 16:15]: > The 404 page simply generates what I would expect: > > [Tue Mar 16 10:04:24 2004] [error] [client 127.0.0.1] File does not > exist: /Library/WebServer/Documents/mk Could it be you're requesting "/mk" when your Webware apache directive is the more common "/wk"? > > I can tell you it *does* work, at any rate... > > *This* is encouraging at least. :-) +1 here, I've it running on Panther. -- ___________________________ toddgrimason*to...@sl... |
From: Douglas B. <douglas.burchard@DouglasBurchard.com> - 2004-03-17 00:24:33
|
On Mar 16, 2004, at 3:12 PM, Todd Grimason wrote: > Could it be you're requesting "/mk" when your Webware apache directive > is the more common "/wk"? Okay, that *could* have been a typo in my email, but embarrassingly (and as much as I wish it was) it wasn't. It didn't solve my problem, but pointed directly to the cause. :-} The correct URL returned an Internal Server Error: ... [Tue Mar 16 15:37:32 2004] [error] (61)Connection refused: Can not connect to WebKit AppServer [Tue Mar 16 15:37:32 2004] [error] (61)Connection refused: Couldn't connect to AppServer, attempt 10 of 10 [Tue Mar 16 15:37:33 2004] [error] (61)Connection refused: error transacting with app server -- giving up. From which my experience with other servlet engines lead me to believe I didn't have AppServer running, even though I thought I had. Restarted AppServer and everything works great. I've made so many changes getting this to run, I'm not sure the bad URL was the whole story, but I've got it working now. For anyone else' edification a 'ps aux | grep AppServer' command before restarting AppServer returned a line for 'sudo ./AppServer', which wasn't correct. After a restart, the same command returns a line for 'sh ./AppServer', which seems to work just fine. I'll have to watch that to see what I did wrong before. Thanks Todd for your sharp eyes, and thanks to everyone else as well! -- Douglas Burchard |
From: Nick R. <ni...@en...> - 2004-03-17 00:51:11
|
I've odds that you'll find that John Dickinson's suggestion was the ticket (viz: localhost -> 127.0.0.1 ... or whatever specific address you want). If you do confirm that we'd have confirmation of the 'bug' and 'fix' on Linux, Windows, and Mac OS. And not only on Apache 2 but also 1; and not only mod_webkit2 but also mod_webkit. When (ok, if) you try dropping back to localhost, would you see if the port that's opened is IPv6? If so then perhaps we should rollup that mod_webkit fix to mod_webkit's call to apr_sockaddr_info_get(). Best, --Nick Ragouzis -----Original Message----- From: web...@li... [mailto:web...@li...] On Behalf Of Douglas Burchard Sent: Tuesday, March 16, 2004 04:24 PM To: Webware Discuss Subject: Re: [Webware-discuss] Getting Webware running on Mac OS X On Mar 16, 2004, at 3:12 PM, Todd Grimason wrote: > Could it be you're requesting "/mk" when your Webware apache directive > is the more common "/wk"? Okay, that *could* have been a typo in my email, but embarrassingly (and as much as I wish it was) it wasn't. It didn't solve my problem, but pointed directly to the cause. :-} The correct URL returned an Internal Server Error: ... [Tue Mar 16 15:37:32 2004] [error] (61)Connection refused: Can not connect to WebKit AppServer [Tue Mar 16 15:37:32 2004] [error] (61)Connection refused: Couldn't connect to AppServer, attempt 10 of 10 [Tue Mar 16 15:37:33 2004] [error] (61)Connection refused: error transacting with app server -- giving up. From which my experience with other servlet engines lead me to believe I didn't have AppServer running, even though I thought I had. Restarted AppServer and everything works great. I've made so many changes getting this to run, I'm not sure the bad URL was the whole story, but I've got it working now. For anyone else' edification a 'ps aux | grep AppServer' command before restarting AppServer returned a line for 'sudo ./AppServer', which wasn't correct. After a restart, the same command returns a line for 'sh ./AppServer', which seems to work just fine. I'll have to watch that to see what I did wrong before. Thanks Todd for your sharp eyes, and thanks to everyone else as well! -- Douglas Burchard ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Webware-discuss mailing list Web...@li... https://lists.sourceforge.net/lists/listinfo/webware-discuss |
From: Douglas B. <douglas.burchard@DouglasBurchard.com> - 2004-03-18 03:37:35
|
On Mar 16, 2004, at 4:50 PM, Nick Ragouzis wrote: > I've odds that you'll find that John Dickinson's suggestion > was the ticket (viz: localhost -> 127.0.0.1 ... or whatever > specific address you want). > > If you do confirm that we'd have confirmation of the > 'bug' and 'fix' on Linux, Windows, and Mac OS. And > not only on Apache 2 but also 1; and not only mod_webkit2 > but also mod_webkit. > > When (ok, if) you try dropping back to localhost, would you > see if the port that's opened is IPv6? If so then perhaps we > should rollup that mod_webkit fix to mod_webkit's call to > apr_sockaddr_info_get(). I changed httpd.conf back to read localhost, restarted Apache, and restarted AppServer. Everything still works as before so it must have been something else. In any case, I'm not sure how to check which protocol a port is opened with. -- Douglas Burchard |
From: Todd G. <to...@sl...> - 2004-03-18 03:44:14
|
`netstat` will tell you `netstat -an` will give you all the ports sorted by ip6, ip, udp, UNIX. (the -a will stop DNS lookups) assuming this is what you meant... * Douglas Burchard <douglas.burchard@DouglasBurchard.com> [2004-03-17 22:39]: > On Mar 16, 2004, at 4:50 PM, Nick Ragouzis wrote: > > > I've odds that you'll find that John Dickinson's suggestion > > was the ticket (viz: localhost -> 127.0.0.1 ... or whatever > > specific address you want). > > > > If you do confirm that we'd have confirmation of the > > 'bug' and 'fix' on Linux, Windows, and Mac OS. And > > not only on Apache 2 but also 1; and not only mod_webkit2 > > but also mod_webkit. > > > > When (ok, if) you try dropping back to localhost, would you > > see if the port that's opened is IPv6? If so then perhaps we > > should rollup that mod_webkit fix to mod_webkit's call to > > apr_sockaddr_info_get(). > > I changed httpd.conf back to read localhost, restarted Apache, and > restarted AppServer. Everything still works as before so it must have > been something else. > > In any case, I'm not sure how to check which protocol a port is opened > with. > > > -- > Douglas Burchard > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Webware-discuss mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webware-discuss -- ___________________________ toddgrimason*to...@sl... |
From: Nick R. <ni...@en...> - 2004-03-18 18:34:26
|
Douglas, > Nick wrote: >> would you see if the port that's opened is IPv6? > I'm not sure how to check which protocol > a port is opened with I'm sorry about that Doug ... I flaked on you there. The problem is that the Apache/mod_webkit side cannot even get the socket connected. I forgot that, and that I had to add debug output* to mod_webkit.c (mod_webkit2) to uncover my initial hunch. Hey, that was January. > Nick also recklessly wrote: >> I've odds that you'll find ... localhost -> 127.0.0.1 > I changed httpd.conf back to read localhost, restarted Apache, and > restarted AppServer. Everything still works as before so it must have > been something else. Well, I lost that one. Shouldn't have jumped the gun. When you returned to the "localhost 8086" configuration (with Apache set to "LogLevel debug" in main or vhost config) I expected you to see the "Couldn't connect to AppServer" failures in your Apache error log. So I guess you (Mac OS X 10.3.2, Apache/1.3.29, mod_webkit [not mod_webkit2]) don't have this bug. And Todd Grimason's keen eye caught your bug. Best, --Nick * For the interested: The problem boils to a behavior in getipnodebyname(3). If IPv6 is defined for your host, the IPv6 addr for localhost [::1] is the first in the list ultimately returned through getaddrinfo(3) and back to Apache's apr_sockaddr_info_get(). So at startup Apache and mod_webkit2 set up the address structures for a perfectly fine IPv6 connection. But when the request comes through for the web page, mod_webkit2's wksock_open() gets refused (error=97) on socket creation because it tries to use that IPv6 info to open an IPv4 connection. One passable solution might be to change wksock_open() to read the address family from the returned-and-stored address structure instead of the hardcoded AF_INET. My workaround used the ability to request priority for IPv4 addresses in the response from (ultimately) getipnodebyname(). Specifying an actual address in the Apache conf can work too, provided it isn't actually an IPv6 address. -----Original Message----- From: web...@li... [mailto:web...@li...] On Behalf Of Douglas Burchard Sent: Wednesday, March 17, 2004 07:37 PM To: Webware Discuss Subject: Re: [Webware-discuss] Getting Webware running on Mac OS X On Mar 16, 2004, at 4:50 PM, Nick Ragouzis wrote: > I've odds that you'll find that John Dickinson's suggestion was the > ticket (viz: localhost -> 127.0.0.1 ... or whatever specific address > you want). > > If you do confirm that we'd have confirmation of the > 'bug' and 'fix' on Linux, Windows, and Mac OS. And > not only on Apache 2 but also 1; and not only mod_webkit2 > but also mod_webkit. > > When (ok, if) you try dropping back to localhost, would you see if the > port that's opened is IPv6? If so then perhaps we should rollup that > mod_webkit fix to mod_webkit's call to apr_sockaddr_info_get(). I changed httpd.conf back to read localhost, restarted Apache, and restarted AppServer. Everything still works as before so it must have been something else. In any case, I'm not sure how to check which protocol a port is opened with. -- Douglas Burchard |
From: Tracy S. R. <tr...@re...> - 2004-03-16 21:46:23
|
Do you also have: LoadModule webkit_module libexec/httpd/mod_webkit.so AddModule mod_webkit.c ... in your httpd.conf file? --T On Mar 16, 2004, at 11:18 AM, Douglas Burchard wrote: > <Location /wk> > WKServer localhost 8086 > SetHandler webkit-handler > </Location> |