chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] Chicken Scheme 3 extension dependency problem


From: Paul Nelson
Subject: Re: [Chicken-users] Chicken Scheme 3 extension dependency problem
Date: Fri, 18 Feb 2011 11:34:33 -0600

I took your advice and have been working on getting qwiki installed and running. I'm MUCH closer than I ever got with svnwiki, but I seem to be getting an error. I have been following the instructions at http://wiki.call-cc.org/eggref/4/qwiki?action="">.

I set up an EC2 instance using a bash script I've created to do the install. You can find my install scripts here. The specific script I'm using is qwiki_instance.sh. The last step in this script creates a spiffy shell script in /etc/init.d/. I then log into the EC2 instance and run that script manually (for now... once it's working the EC2 instance setup will fire off the script).

When I try to point my browser at the server I receive an http 500 error:

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xml:lang="en" lang="en">
<head>
<title>500 - Internal server error</title>
</head>
<body>
<h1>500 - Internal server error</h1>
</body>
</html>
 
I also receive output from the spiffy process:

[Fri Feb 18 17:09:02 2011] "GET http://ec2-50-17-56-189.compute-1.amazonaws.com:8080/ HTTP/1.1" Error:
bad argument type - not a structure of the required type
#f
URI-common

Call history:

<eval> [swap176] (g177178 g183184)
<eval> [swap176] (g179180)
<eval> [swap176] (g179180 g185186)
<eval> [swap176] (g181182)
<eval> [swap176] (g181182 g187188)
g455456
spiffy#handle-exception
with-output-to-string <--


I'm sure I've messed up the installation procedure in some way. Does anyone have any ideas?

Thanks in advance!
Paul

> In the meantime you might like to try qwiki with chicken 4, which is what we use for the project wiki and is therefore actively maintained.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]