Getting core-server to install and start up
peterhil
I only got core-server working on Virtualbox image of Ubuntu Server
after I:
1) reinstalled postfix – I can't see why that is needed.
2) installed SBCL 10.0.43 from source. Ubuntu 10.10 package of SBCL
10.0.40 didn't seem to work very well.
3) noticed the installation did not finish (passing errors to /dev/
null isn't very helpful) by pressing ^C. The installation document
should mention, that on first time SBCL is going to compile the whole
package and the server info isn't likely the first thing a new user
sees.
4) manually compiled start.lisp and crawled through multiple restarts
on sbcl
Core-server seems like a great project, but it seems to need some
polishing to make it easier to get started for new users like me.
Also Mac OS X / CCL support and a quicklisp or even an asdf package
would be great.
I like that core-server comes with command line tool to start and stop
the server unlike hunchentoot,
which is quite awkward to manage through emacs with an acceptor when
developing - or probably I'm doing it wrong... :-)
Best regards,
Peter H
--- clip ---
# sh ./install.sh /home/core/core-server/
+-------------------------------------------------------------+
| Welcome to [ - Core-serveR - ] Project |
| http://www.core.gen.tr |
+-------------------------------------------------------------+
This program will aid you to install the server base.
Please follow the instructions and report any problems to
bi...@core.gen.tr
+ Compiling installation script. Please wait...
ASDF could not load sb-posix because Invalid directive (:DIRECTORY
(:HOME
#P".clc/
systems/"))
^C
debugger invoked on a SB-SYS:INTERACTIVE-INTERRUPT in thread #<THREAD
"initial thread" RUNNING
{1002AB41F1}>:
Interactive interrupt at #x7FFFF748F198.
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [CONTINUE] Return from SB-UNIX:SIGINT.
1: [ABORT ] Exit debugger, returning to top level.
("bogus stack frame")
0] 1
* (compile "~/core-server/etc/start.lisp")
debugger invoked on a TYPE-ERROR in thread #<THREAD "initial thread"
RUNNING
{1002AB41F1}>:
The value "~/core-server/etc/start.lisp" is not of type SYMBOL.
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [ABORT] Exit debugger, returning to top level.
(MACRO-FUNCTION "~/core-server/etc/start.lisp")[:EXTERNAL]
0] 0
* (load "~/core-server/etc/start.lisp")
debugger invoked on a SB-INT:SIMPLE-FILE-ERROR in thread #<THREAD
"initial
thread" RUNNING
{1002AB41F1}
>:
Couldn't load "~/core-server/etc/start.lisp": file does not exist.
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [ABORT] Exit debugger, returning to top level.
(LOAD "~/core-server/etc/start.lisp")[:EXTERNAL]
0] 0
* (load "/home/peterhil/core-server/etc/start.lisp")
STYLE-WARNING:
redefining PRINT-OBJECT (#<SB-PCL::CONDITION-CLASS
ENVIRONMENT-VARIABLE-NOT-FOUND>
#<BUILT-IN-CLASS T>) in DEFMETHOD
STYLE-WARNING: redefining TR.GEN.CORE.SERVER.BOOTSTRAP::GETENV in
DEFUN
STYLE-WARNING: redefining TR.GEN.CORE.SERVER.BOOTSTRAP::SETENV in
DEFUN
STYLE-WARNING:
redefining TR.GEN.CORE.SERVER.BOOTSTRAP::CORESERVER-HOME-AUX in
DEFUN
STYLE-WARNING: redefining TR.GEN.CORE.SERVER.BOOTSTRAP:HOME in DEFUN
STYLE-WARNING: redefining TR.GEN.CORE.SERVER.BOOTSTRAP:IN-HOME in
DEFUN
STYLE-WARNING: redefining TR.GEN.CORE.SERVER.BOOTSTRAP:REGISTER-LIBS
in DEFUN
STYLE-WARNING:
redefining TR.GEN.CORE.SERVER.BOOTSTRAP:REGISTER-PROJECTS in DEFUN
Registering Libraries to asdf::*central-registry*.
Registering Projects to asdf::*central-registry*.
^C
debugger invoked on a SB-SYS:INTERACTIVE-INTERRUPT in thread #<THREAD
"initial thread" RUNNING
{1002AB41F1}>:
Interactive interrupt at #x7FFFF7494293.
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [CONTINUE ] Return from SB-UNIX:SIGINT.
1: [TRY-RECOMPILING] Recompile vars and try loading it again
2: [RETRY ] Retry loading component ("core-server" "src"
"vars").
3: [ACCEPT ] Continue, treating
loading component ("core-server" "src" "vars")
as having
been successful.
4: [ABORT ] Exit debugger, returning to top level.
("bogus stack frame")
0] 2
^C
debugger invoked on a SB-SYS:INTERACTIVE-INTERRUPT in thread #<THREAD
"initial thread" RUNNING
{1002AB41F1}>:
Interactive interrupt at #x7FFFF7494293.
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [CONTINUE ] Return from SB-UNIX:SIGINT.
1: [TRY-RECOMPILING] Recompile vars and try loading it again
2: [RETRY ] Retry loading component ("core-server" "src"
"vars").
3: [ACCEPT ] Continue, treating
loading component ("core-server" "src" "vars")
as having
been successful.
4: [ABORT ] Exit debugger, returning to top level.
("bogus stack frame")
0] 3
; compiling file "/home/peterhil/core-server/lib/core-server/src/
protocol.lisp" (written 04 NOV 2010 08:28:15 AM):
; compiling (IN-PACKAGE :TR.GEN.CORE.SERVER)
; compiling (DEFGENERIC START ...)
; compiling (DEFGENERIC STOP ...)
--- snip ---
Evrim Ulu
On Thu, Nov 4, 2010 at 2:42 PM, peterhil <peter.hi...@gmail.com> wrote:
> Hi!
>
> I only got core-server working on Virtualbox image of Ubuntu Server
> after I:
>
> 1) reinstalled postfix – I can't see why that is needed.
In the root installation it tries to locate postfix and tries to
manage it. For non root installations in which generally people
prefer, there should not be any postfix dependencies. If this is the
case, please let me know.
> 2) installed SBCL 10.0.43 from source. Ubuntu 10.10 package of SBCL
> 10.0.40 didn't seem to work very well.
This is afair, due to ubuntu package having no sb-posix, sb-thread
extensions which makes a web server impossible to operate. Sorry for
inconvenience, but it seems packaging sbcl is out of our scope, if you
think it is please let me know.
> 3) noticed the installation did not finish (passing errors to /dev/
> null isn't very helpful) by pressing ^C. The installation document
> should mention, that on first time SBCL is going to compile the whole
> package and the server info isn't likely the first thing a new user
> sees.
> 4) manually compiled start.lisp and crawled through multiple restarts
> on sbcl
>
Hm I think this is the obvious consequence of writing an installer in
lisp itself. Other methods are valid of course but we've preferred
this one. Any advices would be delightful.
Installer script is runned via the command line:
$SBCL --noinform \
--noprint \
--no-sysinit \
--no-userinit \
--load install.lisp \
--eval "$TARGET" \
--load config.lisp \
--eval "(quit :unix-status 111)"
No error output is redirected to /dev/null, if you can specify where
we've done this i'll be glad to fix it because it's obviously harmful
to hide error messages.
> Core-server seems like a great project, but it seems to need some
> polishing to make it easier to get started for new users like me.
> Also Mac OS X / CCL support and a quicklisp or even an asdf package
> would be great.
>
> I like that core-server comes with command line tool to start and stop
> the server unlike hunchentoot,
> which is quite awkward to manage through emacs with an acceptor when
> developing - or probably I'm doing it wrong... :-)
The method we use is like the following:
cd ~/core-server
bin/core-server start
bin/core-server attach
afterwards inside screen,
sh bin/emacs.sh
M-x core
If you like to run your own VM, you need to set CORESERVER_HOME
environment variable. Afterwards, you can (require :core-server) and
define your own server class just like in the start lisp, and run
(start (make-instance 'your-server-class))
There is nothing that holds users from using core-server as in other servers.
Regards,
Evrim.