[lively-kernel] Personal Lively Wiki?

Robert Krahn robert.krahn at gmail.com
Thu Feb 13 20:01:00 CET 2014


Hi, Sean --

The error you got was because you also have a server running on port 9001.
You can check with

  lsof -i tcp:9001

and kill it with

  kill -9 `lsof -i :9001 -t`

The Lively core github installation comes with version control that does
not require SVN and all other wiki features.

Best,

Robert





On Wed, Feb 12, 2014 at 10:06 AM, Sean P. DeNigris <sean at clipperadams.com>wrote:

> Marko Röder wrote
> > You should use the GitHub-based Lively Kernel to get a local
> installation:
> > https://github.com/LivelyKernel/LivelyKernel
> > On GitHub you will also find installation instructions.
>
> While following the instructions (on OS X 10.8.5), I got:
> $ npm start
> <snip>
> [2014-02-12 13:00:39.942] [INFO] console - Server with pid 18091 is now
> running at http://localhost:9001
> [2014-02-12 13:00:39.942] [INFO] console - Serving files from
> /Users/sean/Downloads/LivelyKernel/LivelyKernel
>
> events.js:72
>         throw er; // Unhandled 'error' event
>               ^
> Error: listen EADDRINUSE
>     at errnoException (net.js:901:11)
>     at Server._listen2 (net.js:1039:14)
>     at listen (net.js:1061:10)
>     at Server.listen (net.js:1135:5)
>     at module.exports
>
> (/Users/sean/Downloads/LivelyKernel/LivelyKernel/node_modules/life_star/life_star.js:184:10)
>     at startServer
> (/Users/sean/Downloads/LivelyKernel/LivelyKernel/bin/lk-server.js:165:25)
>     at fn
>
> (/Users/sean/Downloads/LivelyKernel/LivelyKernel/node_modules/async/lib/async.js:582:34)
>     at Object._onImmediate
>
> (/Users/sean/Downloads/LivelyKernel/LivelyKernel/node_modules/async/lib/async.js:498:34)
>     at processImmediate [as _immediateCallback] (timers.js:330:15)
>
> npm ERR! livelykernel at 2.2.0 start: `$npm_node_execpath bin/lk-server.js`
> npm ERR! Exit status 8
> npm ERR!
> npm ERR! Failed at the livelykernel at 2.2.0 start script.
> npm ERR! This is most likely a problem with the livelykernel package,
> npm ERR! not with npm itself.
> npm ERR! Tell the author that this fails on your system:
> npm ERR!     $npm_node_execpath bin/lk-server.js
> npm ERR! You can get their info via:
> npm ERR!     npm owner ls livelykernel
> npm ERR! There is likely additional logging output above.
> npm ERR! System Darwin 12.5.0
> npm ERR! command "node" "/usr/local/bin/npm" "start"
> npm ERR! cwd /Users/sean/Downloads/LivelyKernel/LivelyKernel
> npm ERR! node -v v0.10.25
> npm ERR! npm -v 1.3.24
> npm ERR! code ELIFECYCLE
> npm ERR!
> npm ERR! Additional logging details can be found in:
> npm ERR!     /Users/sean/Downloads/LivelyKernel/LivelyKernel/npm-debug.log
> npm ERR! not ok code 0
>
>
>
>
>
> -----
> Cheers,
> Sean
> --
> View this message in context:
> http://forum.world.st/Personal-Lively-Wiki-tp4742381p4743068.html
> Sent from the Lively Kernel mailing list archive at Nabble.com.
> _______________________________________________
> lively-kernel mailing list
> lively-kernel at hpi.uni-potsdam.de
> http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hpi.uni-potsdam.de/archive/lively-kernel/attachments/20140213/2c8b8efd/attachment.html>


More information about the lively-kernel mailing list