Hi Cedric, have you been able to make any progress on this one?

On Tue, Jan 7, 2014 at 12:01 PM, S. Fan <sf...@cam.ac.uk> wrote:
> It can also work from the browser via port 9001.
> I can 'New Pad' or create/open a Pad with the name:...
>
> So maybe it is still a problem of permission.
> When I install OAE on the Mac mini, I can also see many other users.
>
> Many thanks
>
> Cedric
>
>
> On 2014-01-07 16:50, Stephen Thomas wrote:
>> Actually, that looks okay. For comparison, here's a typical Etherpad
>> log from my local instance. What happens when you try to access
>> Etherpad directly from the browser (via port 9001)?
>>
>> Ensure that all dependencies are up to date...  If this is the first
>> time you have run Etherpad please be patient.
>> Ensure jQuery is downloaded and up to date...
>> Clear minfified cache...
>> ensure custom css/js files are created...
>> start...
>>  [WARN] console - You need to set a sessionKey value in settings.json,
>> this will allow your users to reconnect to your Etherpad Instance if
>> your instance restarts
>>  [WARN] console -  DirtyDB is used. This is fine for testing but not
>> recommended for production.
>> [INFO] console -  Installed plugins: ep_etherpad-lite, ep_oae
>> [INFO] console -Your Etherpad git version is 5c1daa3
>> [INFO] console -  Report bugs at
>> https://github.com/ether/etherpad-lite/issues
>>  [INFO] console - info: 'socket.io started'
>> [INFO] console -You can access your Etherpad instance at
>> http://0.0.0.0:9001/
>> [WARN] console -  Admin username and password not set in
>> settings.json.  To access admin please uncomment and edit 'users' in
>> settings.json
>>
>> On Jan 7, 2014, at 11:41 AM, S. Fan <sf...@cam.ac.uk> wrote:
>>
>>> Maybe it is also a problem of authority.
>>>
>>>
>>> I run the etherpad-lite manually, and here is the result
>>>
>>> dhcp-172-17-217-17:bin sf507$ ./run.sh
>>> Ensure that all dependencies are up to date...  If this is the first
>>> time you have run Etherpad please be patient.
>>> npm WARN package.json channels@0.0.4 No repository field.
>>> npm WARN package.json async-stacktrace@0.0.2 No repository field.
>>> npm WARN package.json formidable@1.0.9 No repository field.
>>> npm WARN package.json jsdom-nocontextifiy@0.2.10 'repositories'
>>> (plural) Not supported.
>>> npm WARN package.json Please pick one as the 'repository' field
>>> npm WARN package.json ejs@0.6.1 No repository field.
>>> npm WARN package.json tinycon@0.0.1 No repository field.
>>> npm WARN package.json ueberDB@0.2.0 No repository field.
>>> Ensure jQuery is downloaded and up to date...
>>> Clear minfified cache...
>>> ensure custom css/js files are created...
>>> start...
>>> [2014-01-07 16:35:29.830] [WARN] console - You need to set a
>>> sessionKey value in settings.json, this will allow your users to
>>> reconnect to your Etherpad Instance if your instance restarts
>>> [2014-01-07 16:35:29.833] [WARN] console - DirtyDB is used. This is
>>> fine for testing but not recommended for production.
>>> [2014-01-07 16:35:32.039] [INFO] console - Installed plugins: ep_oae,
>>> ep_etherpad-lite, ep_headings
>>> [2014-01-07 16:35:32.064] [WARN] console - Can't get git version for
>>> server header
>>> ENOENT, no such file or directory
>>> '/Users/sf507/OAE/etherpad-lite/.git/HEAD'
>>> [2014-01-07 16:35:32.064] [INFO] console - Report bugs at
>>> https://github.com/ether/etherpad-lite/issues
>>> [2014-01-07 16:35:32.272] [INFO] console -    info  - 'socket.io
>>> started'
>>> [2014-01-07 16:35:32.399] [INFO] console - You can access your
>>> Etherpad instance at http://0.0.0.0:9001/
>>> [2014-01-07 16:35:32.399] [WARN] console - Admin username and password
>>> not set in settings.json.  To access admin please uncomment and edit
>>> 'users' in settings.json
>>>
>>>
>>>
>>>
>>>
>>> On 2014-01-07 16:35, Stephen Thomas wrote:
>>>> Oh well, worth a shot. Sorry I'm not familiar enough with the
>>>> server-side stuff to offer much help.
>>>> On Jan 7, 2014, at 11:34 AM, S. Fan <sf...@cam.ac.uk> wrote:
>>>>> thank you for your advice
>>>>> I have checked the API Key is correct.
>>>>> in config.js
>>>>> config.etherpad = {
>>>>>   'apikey': 'gqwYGIaFR12hy4LK9fe05FfQkOAhF6An',
>>>>> in etherpad-lite, it is also the same
>>>>> gqwYGIaFR12hy4LK9fe05FfQkOAhF6An
>>>>> Many thanks
>>>>> On 2014-01-07 16:22, Stephen Thomas wrote:
>>>>>> One thing that's easy to miss is the Etherpad API Key that has to
>>>>>> be
>>>>>> configured in Hilary's config.js.
>>>>>> Search the Hilary README.md for "etherpad.apikey" for
>>>>>> instructions.
>>>>>> On Jan 7, 2014, at 11:14 AM, Nicolaas Matthijs
>>>>>> <nicolaas.matth...@caret.cam.ac.uk> wrote:
>>>>>>> Regarding your first error, it doesn't look like Etherpad is
>>>>>>> running or has started up successfully.
> _______________________________________________
> oae-dev mailing list
> oae-dev@collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
_______________________________________________
oae-dev mailing list
oae-dev@collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/oae-dev

Reply via email to