<div dir="ltr">Hi, Sean --<div><br></div><div>The error you got was because you also have a server running on port 9001. You can check with</div><div>
<p class=""> lsof -i tcp:9001</p><p class="">and kill it with</p><p class=""> kill -9 `lsof -i :9001 -t`<br></p><p class="">The Lively core github installation comes with version control that does not require SVN and all other wiki features.</p>
<p class="">Best,</p><p class="">Robert</p><p class=""><br></p><p class=""><br></p></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 12, 2014 at 10:06 AM, Sean P. DeNigris <span dir="ltr"><<a href="mailto:sean@clipperadams.com" target="_blank">sean@clipperadams.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Marko Röder wrote<br>
<div class="">> You should use the GitHub-based Lively Kernel to get a local installation:<br>
> <a href="https://github.com/LivelyKernel/LivelyKernel" target="_blank">https://github.com/LivelyKernel/LivelyKernel</a><br>
> On GitHub you will also find installation instructions.<br>
<br>
</div>While following the instructions (on OS X 10.8.5), I got:<br>
$ npm start<br>
<snip><br>
[2014-02-12 13:00:39.942] [INFO] console - Server with pid 18091 is now<br>
running at <a href="http://localhost:9001" target="_blank">http://localhost:9001</a><br>
[2014-02-12 13:00:39.942] [INFO] console - Serving files from<br>
/Users/sean/Downloads/LivelyKernel/LivelyKernel<br>
<br>
events.js:72<br>
throw er; // Unhandled 'error' event<br>
^<br>
Error: listen EADDRINUSE<br>
at errnoException (net.js:901:11)<br>
at Server._listen2 (net.js:1039:14)<br>
at listen (net.js:1061:10)<br>
at Server.listen (net.js:1135:5)<br>
at module.exports<br>
(/Users/sean/Downloads/LivelyKernel/LivelyKernel/node_modules/life_star/life_star.js:184:10)<br>
at startServer<br>
(/Users/sean/Downloads/LivelyKernel/LivelyKernel/bin/lk-server.js:165:25)<br>
at fn<br>
(/Users/sean/Downloads/LivelyKernel/LivelyKernel/node_modules/async/lib/async.js:582:34)<br>
at Object._onImmediate<br>
(/Users/sean/Downloads/LivelyKernel/LivelyKernel/node_modules/async/lib/async.js:498:34)<br>
at processImmediate [as _immediateCallback] (timers.js:330:15)<br>
<br>
npm ERR! livelykernel@2.2.0 start: `$npm_node_execpath bin/lk-server.js`<br>
npm ERR! Exit status 8<br>
npm ERR!<br>
npm ERR! Failed at the livelykernel@2.2.0 start script.<br>
npm ERR! This is most likely a problem with the livelykernel package,<br>
npm ERR! not with npm itself.<br>
npm ERR! Tell the author that this fails on your system:<br>
npm ERR! $npm_node_execpath bin/lk-server.js<br>
npm ERR! You can get their info via:<br>
npm ERR! npm owner ls livelykernel<br>
npm ERR! There is likely additional logging output above.<br>
npm ERR! System Darwin 12.5.0<br>
npm ERR! command "node" "/usr/local/bin/npm" "start"<br>
npm ERR! cwd /Users/sean/Downloads/LivelyKernel/LivelyKernel<br>
npm ERR! node -v v0.10.25<br>
npm ERR! npm -v 1.3.24<br>
npm ERR! code ELIFECYCLE<br>
npm ERR!<br>
npm ERR! Additional logging details can be found in:<br>
npm ERR! /Users/sean/Downloads/LivelyKernel/LivelyKernel/npm-debug.log<br>
npm ERR! not ok code 0<br>
<br>
<br>
<br>
<br>
<br>
-----<br>
Cheers,<br>
Sean<br>
--<br>
View this message in context: <a href="http://forum.world.st/Personal-Lively-Wiki-tp4742381p4743068.html" target="_blank">http://forum.world.st/Personal-Lively-Wiki-tp4742381p4743068.html</a><br>
<div class="HOEnZb"><div class="h5">Sent from the Lively Kernel mailing list archive at Nabble.com.<br>
_______________________________________________<br>
lively-kernel mailing list<br>
<a href="mailto:lively-kernel@hpi.uni-potsdam.de">lively-kernel@hpi.uni-potsdam.de</a><br>
<a href="http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel" target="_blank">http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel</a><br>
</div></div></blockquote></div><br></div>