Responsible: fiware at ulpgc.es Tested GE(s): Cloud Rendering GE Environment: - Local Operating System: Ubuntu 14.04.1 (64 bits) Virtualization software: VirtualBox 4.3.18 Host Operating System: Windows 8 (64 bits) Link: https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Cloud_Rendering_-_Installation_and_Administration_Guide#Running Description: In the WebService section from the Installation and Administration Guide we find errors when we execute the command to run the WebService. After installing the service, we are told to run the service with "grunt run" and that the expected output is the following: [2014-04-10 15:59:47.154] [INFO] console - Signaling server started [2014-04-10 15:59:47.157] [INFO] console - Express server listening on port 3000 in development mode However, when we execute the command the server is not started and we get as ouput these lines: $ grunt run Running "shell:signaling" (shell) task Done, without errors. If we simply execute the command "grunt", we get a more explicit output: $ grunt Running "shell:signaling" (shell) task Running "hub:watch" (hub) task >> Running [watch] on /home/test/fiware-cloud-rendering-service/jsapps/Gruntfile.js [2014-11-06 14:55:51.742] [INFO] console - Signaling server started >> events.js:72 >> throw er; // Unhandled 'error' event >> ^ >> Error: listen EACCES >> at errnoException (net.js:901:11) >> at Server._listen2 (net.js:1020:19) >> at listen (net.js:1061:10) >> at Server.listen (net.js:1135:5) >> at Object.<anonymous> (/home/test/fiware-cloud-rendering-service/webservice/app.js:32:47) >> at Module._compile (module.js:456:26) >> at Object.Module._extensions..js (module.js:474:10) >> at Module.load (module.js:356:32) >> at Function.Module._load (module.js:312:12) >> at Module.require (module.js:364:17) Warning: Done, with errors. Use --force to continue. Aborted due to warnings. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20141107/ef531375/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy