Superdesk install
  • Hello,

    Is it possible to install and run Superdesk on Google App Engine?

    Thank You.
  • 62 Comments sorted by
  • It can't connect to elastic search.

    In order to make it easier I would recommend to use Docker-Compose profile (https://github.com/superdesk/superdesk/blob/master/docker/docker-compose.yml.sh) instead of starting and connecting docker containers manually.
    Innovations developer, Sourcefabric
  • Hello,

    I'm afraid it's not possible at the moment because Superdesk can only run on python 3.2.
    When the app engine is going to switch to that version it will be possible.


  • Hello,

    i need HELP for installation Superdesk.

    I´ve tryed to follow the install.txt - but unfortunatly it dos not work.

    How do i install Superdesk on a local - Webserver (Ubuntu 10.12)??
    for example: "/var/www/superdesk"

    Thanks in forward!
  • Hello Stanley,

    What error messages do you receive when you try to install?
  • Hello,

    the structur:

    /var/www/superdesk                      (inside are the Files from ally-py-master)
    /var/www/superdesk/superdesk      (inside are the Filse from superdesk-master)

    if i run "python3 /var/www/superdesk/build-eggs"
    -> File "/var/www/superdesk/build-eggs", line 7
    export PYTHONPATH=distribution/tool/distribute-0.6.27-py3.2.egg
    Syntax Error: invalide syntax

    if i run "python3 /var/www/superdesk/superdesk/build-eggs"
    -> File "/var/www/superdesk/superdesk/build-eggs", line 7
    export PYTHONPATH=..
    Syntax Error: invalide syntax

    if i run "python3 /var/www/superdesk/distribution/application.py"
    Corrupt or missing ally-utilities components...

    if i run "python3 /var/www/superdesk/superdesk/distribution/application.py"
    Corrupt or missing ally-utilities components...


    Post edited by Stanley Volke at 2013-01-29 10:41:35
  • I apologize, there is an error in the install file. Please run the
    following command from CLI:
    /var/www/superdesk/build-eggs

    I updated the install file.

    Mugur Rus
    Senior Software Developer, Sourcefabric
    mugur.rus@sourcefabric.org
    http://www.sourcefabric.org | http://www.sourcefabric.com

    Cluj-Napoca, Romania
    +40 720 528408
    skype: mugur_rus



    On Tue, Jan 29, 2013 at 5:33 PM, Stanley Volke <<br />superdesk-dev@lists.sourcefabric.org> wrote:

    > Hello,
    >
    > the structur:
    >
    > /var/www/superdesk (inside are the Files from
    > ally-py-master)
    > /var/www/superdesk/superdesk (inside are the Filse from
    > superdesk-master)
    >
    > if i run "python3 /var/www/superdesk/build-eggs"
    > -> File "/var/www/superdesk/build-eggs", line 7
    > export PYTHONPATH=distribution/tool/distribute-0.6.27-py3.2.egg
    > Syntax Error: invalide syntax
    >
    > if i run "python3 /var/www/superdesk/superdesk/build-eggs"
    > -> File "/var/www/superdesk/superdesk/build-eggs", line 7
    > export PYTHONPATH=..
    > Syntax Error: invalide syntax
    >
    > if i run "python3 /var/www/superdesk/distribution/application.py"
    > Corrupt or missing ally-utilities components...
    >
    > if i run "python3 /var/www/superdesk/distribution/application.py"
    > Corrupt or missing ally-utilities components...
    >
    >
    >
    >
  • if i run after updating the files and run: /var/www/superdesk/build-eggs



    ubuntu@ubuntu-VirtualBox:~$ python3 /var/www/superdesk/distribution/application.py
    server_asyncore.run 416: Assembly report for pattern '^resources\/my(/|(?=\.)|$)':
    -------------------------------------------------- Assembly report

    The following attributes are not used by any processor:
        request.accLanguages
    --------------------------------------------------

    ================================================== Application started in 1.71 seconds
    server_asyncore.run 416: Assembly report for pattern '^resources(/|(?=\.)|$)':
    -------------------------------------------------- Assembly report

    The following attributes are not used by any processor:
        request.accLanguages
    --------------------------------------------------

    server_asyncore.run 416: Assembly report for pattern '^content(/|$)':
    -------------------------------------------------- Assembly report

    The following attributes are not used by any processor:
        request.accLanguages, request.uriRoot, requestCnt.source, response.length
    --------------------------------------------------

    ================================================== Started Async REST API server...


    I have opened the URL:
    http://localhost:8080/content/lib/core/start.html

    I clicked Logout, put the Username: User1 and the Password: a
    But Login failed!!
  • Dear Stanley,

    Please let me know on which branch are you running: master or devel?

    The master branch has a stable version that should work with User1 and
    password a

    The devel branch is in heavy fixing, meaning there are many bugs yet.
    However, if you want to try it please pull again the latest changes and use
    root user with password root

    I would recommend to pull often from both repositories (ally-py and
    superdesk) if you're running from the devel branch.

    Regards,

    Mugur Rus
    Senior Software Developer, Sourcefabric
    mugur.rus@sourcefabric.org
    http://www.sourcefabric.org | http://www.sourcefabric.com

    Cluj-Napoca, Romania
    +40 720 528408
    skype: mugur_rus



    On Tue, Jan 29, 2013 at 6:04 PM, Stanley Volke <<br />superdesk-dev@lists.sourcefabric.org> wrote:

    > if i run after updating the files and run: /var/www/superdesk/build-eggs
    >
    >
    > *ubuntu@ubuntu-VirtualBox:~$ python3
    > /var/www/superdesk/distribution/application.py
    > server_asyncore.run 416: Assembly report for pattern
    > '^resources\/my(/|(?=\.)|$)':
    > -------------------------------------------------- Assembly report
    >
    > The following attributes are not used by any processor:
    > request.accLanguages
    > --------------------------------------------------
    >
    > ================================================== Application started in
    > 1.71 seconds
    > server_asyncore.run 416: Assembly report for pattern
    > '^resources(/|(?=\.)|$)':
    > -------------------------------------------------- Assembly report
    >
    > The following attributes are not used by any processor:
    > request.accLanguages
    > --------------------------------------------------
    >
    > server_asyncore.run 416: Assembly report for pattern '^content(/|$)':
    > -------------------------------------------------- Assembly report
    >
    > The following attributes are not used by any processor:
    > request.accLanguages, request.uriRoot, requestCnt.source,
    > response.length
    > ------------------------------------------------
  • Hello,

    i run ally-py-master and superdesk-master from github, if you mean this!

    Kind Regards
  • Hello,

     

    I got the bellow errors when running the -dump command. Please let me know how to fix this problem. Your help is much appreciated.

    Thanks,


    Joe




    ubuntu@ip-10-212-238-225:/var/www/superdesk/distribution$ sudo vi /var/www/superdesk/distribution/application.properties
    ubuntu@ip-10-212-238-225:/var/www/superdesk/distribution$ sudo python3 /var/www/superdesk/distribution/application.py -dump
    Failed to fetch a value for configuration '__setup__.ally_gateway.processor.gateway_uri': There is no gateway URI provided
    Failed to fetch a value for configuration '__setup__.ally_gateway.processor.gateway_authorized_uri': There is no authorized gateway URI prvided
    Failed to fetch a value for configuration '__setup__.ally_gateway.processor.external_host': No external host provided
    Failed to fetch a value for configuration '__setup__.ally_gateway_recaptcha.processor.gateway_captcha_uri': There is no gateway URI providd
    Created "application.properties" configuration file
    Created "plugins.properties" configuration file

     

  • Hi Joe,

    You can continue your install, these are not configuration errors. The
    properties files were created.

    Regards,
    Mugur


    On Wed, Jul 31, 2013 at 7:12 PM, Joe Kojak <<br />superdesk-dev@lists.sourcefabric.org> wrote:

    > Hello,
    >
    >
    >
    > I got the bellow errors when running the -dump command. Please let me know
    > how to fix this problem. Your help is much appreciated.
    >
    > Thanks,
    >
    >
    > Joe
    >
    >
    >
    >
    > ubuntu@ip-10-212-238-225:/var/www/superdesk/distribution$ sudo vi
    > /var/www/superdesk/distribution/application.properties
    > ubuntu@ip-10-212-238-225:/var/www/superdesk/distribution$ sudo python3
    > /var/www/superdesk/distribution/application.py -dump
    > Failed to fetch a value for configuration
    > '__setup__.ally_gateway.processor.gateway_uri': There is no gateway URI
    > provided
    > Failed to fetch a value for configuration
    > '__setup__.ally_gateway.processor.gateway_authorized_uri': There is no
    > authorized gateway URI prvided
    > Failed to fetch a value for configuration
    > '__setup__.ally_gateway.processor.external_host': No external host provided
    > Failed to fetch a value for configuration
    > '__setup__.ally_gateway_recaptcha.processor.gateway_captcha_uri': There is
    > no gateway URI providd
    > Created "application.properties" configuration file
    > Created "plugins.properties" configuration file
    >
    >
    >
    >
  • Thank you for the response.

    I could not get the admin interface up as of yet. My guess is it has something to do with the find the font-family:"Courier New";mso-fareast-font-family:"Times New Roman";mso-fareast-theme-font:
    minor-fareast;mso-ansi-language:EN-US;mso-fareast-language:EN-US;mso-bidi-language:
    AR-SA">'embed_server_url' property, something that I did not find in the application.properties file. Do you know where I can find this? Thank you for the help.

    Joe
  • Hello Mugur,

    I tried to reinstall it again, but failed again. I get the below errors when I restart the application. Any asisstance is appreciated. Thank you in advance. Do you know what this might be?

    A setup or configuration error occurred while deploying, try to rebuild the application properties by running the the application with "-dump" option
    Traceback (most recent call last):
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_support.py", line 99, in followWiring
        try: setattr(value, wentity.name, entityFor(wentity.type, wentity.name))
      File "components/ally-1.0.dev-py3.2.egg/ally/container/support.py", line 324, in entityFor
        raise SetupError('There is no entity setup function having a return type of class or subclass %s' % clazz)
    ally.container.error.SetupError: There is no entity setup function having a return type of class or subclass <class 'acl.core.impl.processor.resource_node_associate.StructureAssociate'>

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_support.py", line 99, in followWiring
        try: setattr(value, wentity.name, entityFor(wentity.type, wentity.name))
      File "components/ally-1.0.dev-py3.2.egg/ally/container/support.py", line 347, in entityFor
        try: return assembly.processForName(entities[0])
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 183, in processForName
        try: value = self.fetchForName(name)()
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py", line 324, in __call__
        for listener, _auto in self._listenersBefore: listener()
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 183, in processForName
        try: value = self.fetchForName(name)()
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py", line 213, in __call__
        for listener, _auto in self._listenersAfter: listener()
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 183, in processForName
        try: value = self.fetchForName(name)()
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py", line 211, in __call__
        ret = self.call()
      File "/var/opt/Ally-Py/superdesk/distribution/plugins/captcha-1.0.dev-py3.2.egg/__plugin__/captcha/patch_ally_core.py", line 34, in updateAssemblyCaptchaGatewaysForResources
        assemblyCaptchaGateways().add(iterateResourcePermissions(), gatewaysFromPermissions())
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_setup.py", line 122, in __call__
        return Assembly.process(self.name)
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 90, in process
        return ass.processForName(name)
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 183, in processForName
        try: value = self.fetchForName(name)()
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py", line 326, in __call__
        if followUp: followUp()
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_support.py", line 101, in followWiring
        (wentity.name, locationStack(value.__class__)))
    ally.container.error.SetupError: Cannot solve wiring 'structureAssociate' at:
      File "/var/opt/Ally-Py/superdesk/distribution/plugins/support_acl-1.0.dev-py3.2.egg/acl/core/impl/processor/resource_node_associate.py", line 290

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "components/ally-1.0.dev-py3.2.egg/__deploy__/ally/deploy.py", line 71, in deploy
        context.processStart()
      File "components/ally-1.0.dev-py3.2.egg/ally/container/context.py", line 96, in processStart
        for call in calls: assembly.processForName(call.name)
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 183, in processForName
        try: value = self.fetchForName(name)()
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py", line 211, in __call__
        ret = self.call()
      File "components/ally_plugin-1.0.dev-py3.2.egg/__setup__/ally_plugin/deploy_plugin.py", line 91, in deploy
        try: context.processStart()
      File "components/ally-1.0.dev-py3.2.egg/ally/container/context.py", line 96, in processStart
        for call in calls: assembly.processForName(call.name)
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 183, in processForName
        try: value = self.fetchForName(name)()
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py", line 211, in __call__
        ret = self.call()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/support.py", line 214, in loadAll
        if name.startswith(prefix) and isinstance(call, CallEntity) and call.isOf(clazz): Assembly.process(name)
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 90, in process
        return ass.processForName(name)
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 183, in processForName
        try: value = self.fetchForName(name)()
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py", line 326, in __call__
        if followUp: followUp()
      File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_support.py", line 101, in followWiring
        (wentity.name, locationStack(value.__class__)))
    ally.container.error.SetupError: Cannot solve wiring 'assemblyCaptchaGateways' at:
      File "/var/opt/Ally-Py/superdesk/distribution/plugins/captcha-1.0.dev-py3.2.egg/gateway/captcha/impl/gateway.py", line 38



  • Hi Joe,


    What branch did you use for superdesk install?
    It is better to use liveblog-15 for both Ally-Py and Superdesk repositories.
    If you didn't use liveblog-15 please delete all already installed files and
    make a fresh install.

    Have a good day,
    Ioan v. Pocol


    On Mon, Aug 5, 2013 at 8:19 PM, Joe Kojak <<br />superdesk-dev@lists.sourcefabric.org> wrote:

    > Hello Mugur,
    >
    > I tried to reinstall it again, but failed again. I get the below errors
    > when I restart the application. Any asisstance is appreciated. Thank you in
    > advance. Do you know what this might be?
    >
    > A setup or configuration error occurred while deploying, try to rebuild
    > the application properties by running the the application with "-dump"
    > option
    > Traceback (most recent call last):
    > File
    > "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_support.py", line
    > 99, in followWiring
    > try: setattr(value, wentity.name, entityFor(wentity.type, wentity.name
    > ))
    > File "components/ally-1.0.dev-py3.2.egg/ally/container/support.py", line
    > 324, in entityFor
    > raise SetupError('There is no entity setup function having a return
    > type of class or subclass %s' % clazz)
    > ally.container.error.SetupError: There is no entity setup function having
    > a return type of class or subclass **
    >
    > During handling of the above exception, another exception occurred:
    >
    > Traceback (most recent call last):
    > File
    > "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_support.py", line
    > 99, in followWiring
    > try: setattr(value, wentity.name, entityFor(wentity.type, wentity.name
    > ))
    > File "components/ally-1.0.dev-py3.2.egg/ally/container/support.py", line
    > 347, in entityFor
    > try: return assembly.processForName(entities[0])
    > File
    > "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line
    > 183, in processForName
    > try: value = self.fetchForName(name)()
    > File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py",
    > line 324, in __call__
    > for listener, _auto in self._listenersBefore: listener()
    > File
    > "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line
    > 183, in processForName
    > try: value = self.fetchForName(name)()
    > File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py",
    > line 213, in __call__
    > for listener, _auto in self._listenersAfter: listener()
    > File
    > "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line
    > 183, in processForName
    > try: value = self.fetchForName(name)()
    > File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py",
    > line 211, in __call__
    > ret = self.call()
    > File
    > "/var/opt/Ally-Py/superdesk/distribution/plugins/captcha-1.0.dev-py3.2.egg/__plugin__/captcha/patch_ally_core.py",
    > line 34, in updateAssemblyCaptchaGatewaysForResources
    > assemblyCaptchaGateways().add(iterateResourcePermissions(),
    > gatewaysFromPermissions())
    > File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_setup.py",
    > line 122, in __call__
    > return Assembly.process(self.name)
    > File
    > "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line
    > 90, in process
    > return ass.processForName(name)
    > File
    > "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line
    > 183, in processForName
    > try: value = self.fetchForName(name)()
    > File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py",
    > line 326, in __call__
    > if followUp: followUp()
    > File
    > "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_support.py", line
    > 101, in followWiring
    > (wentity.name, locationStack(value.__class__)))
    > ally.container.error.SetupError: Cannot solve wiring 'structureAssociate'
    > at:
    > File
    > "/var/opt/Ally-Py/superdesk/distribution/plugins/support_acl-1.0.dev-py3.2.egg/acl/core/impl/processor/resource_node_associate.py",
    > line 290
    >
    > During handling of the above exception, another exception occurred:
    >
    > Traceback (most recent call last):
    > File "components/ally-1.0.dev-py3.2.egg/__deploy__/ally/deploy.py", line
    > 71, in deploy
    > context.processStart()
    > File "components/ally-1.0.dev-py3.2.egg/ally/container/context.py", line
    > 96, in processStart
    > for call in calls: assembly.processForName(call.name)
    > File
    > "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line
    > 183, in processForName
    > try: value = self.fetchForName(name)()
    > File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py",
    > line 211, in __call__
    > ret = self.call()
    > File
    > "components/ally_plugin-1.0.dev-py3.2.egg/__setup__/ally_plugin/deploy_plugin.py",
    > line 91, in deploy
    > try: context.processStart()
    > File "components/ally-1.0.dev-py3.2.egg/ally/container/context.py", line
    > 96, in processStart
    > for call in calls: assembly.processForName(call.name)
    > File
    > "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line
    > 183, in processForName
    > try: value = self.fetchForName(name)()
    > File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py",
    > line 211, in __call__
    > ret = self.call()
    > File "components/ally-1.0.dev-py3.2.egg/ally/container/support.py", line
    > 214, in loadAll
    > if name.startswith(prefix) and isinstance(call, CallEntity) and
    > call.isOf(clazz): Assembly.process(name)
    > File
    > "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line
    > 90, in process
    > return ass.processForName(name)
    > File
    > "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line
    > 183, in processForName
    > try: value = self.fetchForName(name)()
    > File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py",
    > line 326, in __call__
    > if followUp: followUp()
    > File
    > "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_support.py", line
    > 101, in followWiring
    > (wentity.name, locationStack(value.__class__)))
    > ally.container.error.SetupError: Cannot solve wiring
    > 'assemblyCaptchaGateways' at:
    > File
    > "/var/opt/Ally-Py/superdesk/distribution/plugins/captcha-1.0.dev-py3.2.egg/gateway/captcha/impl/gateway.py",
    > line 38
    >
    >
    >
    >
    >
  • Thanks for the response Ioan Pocol. I tried downloading the files from liveblog-15 with the below link, but it failed due to permissions. git clone https://github.com/sourcefabric/Superdesk/tree/liveblog-15

    At this point I am very confused and I am not even sure if this is a Linux based install or Windows because I see batch files. Also, do I need to Ally-Py separately from the Superdesk installation or is it part of it?  I had assumed linux Ubuntu 12.04, but now I am not sure.

    Thank You,

    Joe
  • Hi Joe,


    We are validating again the install procedure and we will perform the
    required code fixes or changes on install.txt file.
    I will let you know when you can start to install it again.

    Have a good day,
    Ioan v. Pocol


    On Tue, Aug 6, 2013 at 5:40 PM, Joe Kojak <<br />superdesk-dev@lists.sourcefabric.org> wrote:

    > Thanks for the response Ioan Pocol. I tried downloading the files from
    > liveblog-15 with the below link, but it failed due to permissions. git
    > clone https://github.com/sourcefabric/Superdesk/tree/liveblog-15
    >
    > At this point I am very confused and I am not even sure if this is a Linux
    > based install or Windows because I see batch files. Also, do I need to
    > Ally-Py separately from the Superdesk installation or is it part of it? I
    > had assumed linux Ubuntu 12.04, but now I am not sure.
    >
    > Thank You,
    >
    > Joe
    >
    >
  • Thank you very much Ioan Pocol. I appreciate your efforts and look forward to the installation.

    THanks,

    Joe
  • Hi,

    I tried to install Ally-Py-liveblog-15 but after building the eggs and the properties, when I start the application I'm running into the same SetupError as a previous poster:

    ally.container.error.SetupError: There is no entity setup function
    having a return type of class or subclass <class
    'acl.core.impl.processor.resource_node_associate.StructureAssociate'>

    any help much appreciated.

    cheers,
    Alvaro
  • Hi Alvaro,


    I hope that this week we will update the master branch with a new version.
    In meantime please send me your the log file.

    Have a good day,
    Ioan v. Pocol


    On Sun, Sep 1, 2013 at 1:49 PM, alvaro > wrote:

    > Hi,
    >
    > I tried to install Ally-Py-liveblog-15 but after building the eggs and the
    > properties, when I start the application I'm running into the same
    > SetupError as a previous poster:
    >
    > ally.container.error.SetupError: There is no entity setup function having
    > a return type of class or subclass **
    >
    > any help much appreciated.
    >
    > cheers,
    > Alvaro
    >
    >
  • Hi Ioan,

    thanks a lot for your response. Here's the output of "python3 application.py"





    INFO Nothing to report for 'Anonymous gateways', everything fits nicely ally.design.processor.assembly
    ------------------------------------------------------------------------------------------------------------------------------------------------------
    A setup or configuration error occurred while deploying, try to rebuild the application properties by running the the application with "-dump" option
    Traceback (most recent call last):
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_support.py", line 99, in followWiring
    try: setattr(value, wentity.name, entityFor(wentity.type, wentity.name))
    File "components/ally-1.0.dev-py3.2.egg/ally/container/support.py", line 324, in entityFor
    raise SetupError('There is no entity setup function having a return type of class or subclass %s' % clazz)
    ally.container.error.SetupError: There is no entity setup function having a return type of class or subclass

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_support.py", line 99, in followWiring
    try: setattr(value, wentity.name, entityFor(wentity.type, wentity.name))
    File "components/ally-1.0.dev-py3.2.egg/ally/container/support.py", line 347, in entityFor
    try: return assembly.processForName(entities[0])
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 183, in processForName
    try: value = self.fetchForName(name)()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py", line 324, in __call__
    for listener, _auto in self._listenersBefore: listener()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 183, in processForName
    try: value = self.fetchForName(name)()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py", line 213, in __call__
    for listener, _auto in self._listenersAfter: listener()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 183, in processForName
    try: value = self.fetchForName(name)()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py", line 211, in __call__
    ret = self.call()
    File "/home/alvaro/WorkspaceREST/resp_api/distribution/plugins/captcha-1.0.dev-py3.2.egg/__plugin__/captcha/patch_ally_core.py", line 34, in updateAssemblyCaptchaGatewaysForResources
    assemblyCaptchaGateways().add(iterateResourcePermissions(), gatewaysFromPermissions())
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_setup.py", line 122, in __call__
    return Assembly.process(self.name)
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 90, in process
    return ass.processForName(name)
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 183, in processForName
    try: value = self.fetchForName(name)()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py", line 326, in __call__
    if followUp: followUp()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_support.py", line 101, in followWiring
    (wentity.name, locationStack(value.__class__)))
    ally.container.error.SetupError: Cannot solve wiring 'structureAssociate' at:
    File "/home/alvaro/WorkspaceREST/resp_api/distribution/plugins/support_acl-1.0.dev-py3.2.egg/acl/core/impl/processor/resource_node_associate.py", line 290

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
    File "components/ally-1.0.dev-py3.2.egg/__deploy__/ally/deploy.py", line 71, in deploy
    context.processStart()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/context.py", line 96, in processStart
    for call in calls: assembly.processForName(call.name)
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 183, in processForName
    try: value = self.fetchForName(name)()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py", line 211, in __call__
    ret = self.call()
    File "components/ally_plugin-1.0.dev-py3.2.egg/__setup__/ally_plugin/deploy_plugin.py", line 91, in deploy
    try: context.processStart()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/context.py", line 96, in processStart
    for call in calls: assembly.processForName(call.name)
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 183, in processForName
    try: value = self.fetchForName(name)()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py", line 211, in __call__
    ret = self.call()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/support.py", line 214, in loadAll
    if name.startswith(prefix) and isinstance(call, CallEntity) and call.isOf(clazz): Assembly.process(name)
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 90, in process
    return ass.processForName(name)
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_assembly.py", line 183, in processForName
    try: value = self.fetchForName(name)()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_call.py", line 326, in __call__
    if followUp: followUp()
    File "components/ally-1.0.dev-py3.2.egg/ally/container/_impl/_support.py", line 101, in followWiring
    (wentity.name, locationStack(value.__class__)))
    ally.container.error.SetupError: Cannot solve wiring 'assemblyCaptchaGateways' at:
    File "/home/alvaro/WorkspaceREST/resp_api/distribution/plugins/captcha-1.0.dev-py3.2.egg/gateway/captcha/impl/gateway.py", line 38
    ------------------------------------------------------------------------------------------------------------------------------------------------------
    ================================================== Application started in 5.03 seconds


  • Hi All

    People i am having a problema during the superdesk installation:

    My System is:
    CentOS 5.9
    with: Apache 2.2 + MySQL 5.x + Java 1.7 + MongoDB 2.x + Python3.3

    I downloaded the Ally-Py_master.zip and follow the instruction.txt until the build-egg

    my paths are:
    /var/www/ally-py/
    /var/www/ally-py/superdesk

    When i call "/var/www/ally-py/superdesk/build-egg" in the frist time run all and in the end showed:
    "python3: can't open file 'superdesk/plugins/build_egg.py': [Errno 2] No such file or directory"

    if i go on /plugins and list files:

    # ls
    administration    gateway         gui-action  internationalization  security      support-acl  support-sqlalchemy
    build_egg.py    gateway_captcha  gui-core    sandbox           security-rbac  support-cdm

    The build_egg.py is there with 775 (permission)

    if i call "python3 build_egg.py" (inside plugin directory runs with no echo of erro or other msg)

    and if i try to call "python3 /var/www/ally-py/superdesk/build-eggs" I get the following erro:
     
    " File "/var/www/ally-py/superdesk/build-eggs", line 7
        export PYTHONPATH=distribution/tools/distribute-0.6.27-py3.2.egg
                        ^
    SyntaxError: invalid syntax"

    I installed the python3.3 and distribute tool for 3.3 and install the virtualenv (because CentOS native repo Python is 2.4)

    And one got any clue what can i do to install it?








  • Please install Python 3.2, currently Liveblog does not work on Python 3.3 -
    we're working on it.


    On Fri, Nov 1, 2013 at 9:24 PM, Daniel Carraretto <<br />superdesk-dev@lists.sourcefabric.org> wrote:

    > Hi All
    >
    > People i am having a problema during the superdesk installation:
    >
    > My System is:
    > CentOS 5.9
    > with: Apache 2.2 + MySQL 5.x + Java 1.7 + MongoDB 2.x + Python3.3
    >
    > I downloaded the Ally-Py_master.zip and follow the instruction.txt until
    > the build-egg
    >
    > my paths are:
    > /var/www/ally-py/
    > /var/www/ally-py/superdesk
    >
    > When i call "/var/www/ally-py/superdesk/build-egg" in the frist time run
    > all and in the end showed:
    > "python3: can't open file 'superdesk/plugins/build_egg.py': [Errno 2] No
    > such file or directory"
    >
    > if i go on /plugins and list files:
    >
    > # ls
    > administration gateway gui-action internationalization
    > security support-acl support-sqlalchemy
    > *build_egg.py * gateway_captcha gui-core sandbox
    > security-rbac support-cdm
    >
    > The build_egg.py is there with 775 (permission)
    >
    > if i call "python3 build_egg.py" (inside plugin directory runs with no
    > echo of erro or other msg)
    >
    > and if i try to call "python3 /var/www/ally-py/superdesk/build-eggs" I get
    > the following erro:
    >
    > " File "/var/www/ally-py/superdesk/build-eggs", line 7
    > export PYTHONPATH=distribution/tools/distribute-0.6.27-py3.2.egg
    > ^
    > SyntaxError: invalid syntax"
    >
    > I installed the python3.3 and distribute tool for 3.3 and install the
    > virtualenv (because CentOS native repo Python is 2.4)
    >
    > And one got any clue what can i do to install it?
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >
  • Hi , 

    I have trouble installing superdesk , i am using windows 7 so i have used the (start.bat) file for building and everything goes fine but at the end of building when its want to run the (application.py) i got the following errors :


    Failed to fetch a value for configuration '__setup__.ally_gateway.processor.gate
    way_uri': There is no gateway URI provided
    Failed to fetch a value for configuration '__setup__.ally_gateway.processor.gate
    way_authorized_uri': There is no authorized gateway URI provided
    Failed to fetch a value for configuration '__setup__.ally_gateway.processor.exte
    rnal_host': No external host provided
    Failed to fetch a value for configuration '__setup__.ally_gateway_recaptcha.proc
    essor.gateway_captcha_uri': There is no gateway URI provided
    Created "application.properties" configuration file
    Created "plugins.properties" configuration file
    ================================================== Application started in 36.69
    seconds
    --------------------------------------------------------------------------------
    ----------------------------------------------------------------------
    A setup or configuration error occurred while deploying, try to rebuild the appl
    ication properties by running the the application with "-dump" option
    Traceback (most recent call last):
      File "C:\Ally-Py\Superdesk\distribution\libraries\pymongo-2.4.2-py3.2-linux-i6
    86.egg\pymongo\mongo_client.py", line 266, in __init__
        self.__find_node(seeds)
      File "C:\Ally-Py\Superdesk\distribution\libraries\pymongo-2.4.2-py3.2-linux-i6
    86.egg\pymongo\mongo_client.py", line 641, in __find_node
        raise AutoReconnect(', '.join(errors))
    pymongo.errors.AutoReconnect: could not connect to localhost:27017: [Errno 10061
    ] No connection could be made because the target machine actively refused it

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "C:\Ally-Py\Superdesk\distribution\libraries\mongoengine-0.7.9-py3.2.egg\
    mongoengine\connection.py", line 124, in get_connection
        _connections[alias] = connection_class(**conn_settings)
      File "C:\Ally-Py\Superdesk\distribution\libraries\pymongo-2.4.2-py3.2-linux-i6
    86.egg\pymongo\connection.py", line 180, in __init__
        max_pool_size, document_class, tz_aware, _connect, **kwargs)
      File "C:\Ally-Py\Superdesk\distribution\libraries\pymongo-2.4.2-py3.2-linux-i6
    86.egg\pymongo\mongo_client.py", line 269, in __init__
        raise ConnectionFailure(str(e))
    pymongo.errors.ConnectionFailure: could not connect to localhost:27017: [Errno 1
    0061] No connection could be made because the target machine actively refused it


    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "build\bdist.win32\egg\ally\container\_impl\_assembly.py", line 183, in p
    rocessForName
        try: value = self.fetchForName(name)()
      File "build\bdist.win32\egg\ally\container\_impl\_call.py", line 331, in __cal
    l__
        Initializer.initialize(value)
      File "build\bdist.win32\egg\ally\container\_impl\_entity.py", line 60, in init
    ialize
        initializer._entityInit(entity, *args, **keyargs)
      File "build\bdist.win32\egg\content\publisher\impl\publisher.py", line 49, in
    __init__
        mongoengine.connect(self.mongodb_database, host=self.mongodb_server, port=se
    lf.mongodb_port)
      File "C:\Ally-Py\Superdesk\distribution\libraries\mongoengine-0.7.9-py3.2.egg\
    mongoengine\connection.py", line 162, in connect
        return get_connection(alias)
      File "C:\Ally-Py\Superdesk\distribution\libraries\mongoengine-0.7.9-py3.2.egg\
    mongoengine\connection.py", line 126, in get_connection
        raise ConnectionError("Cannot connect to database %s :\n%s" % (alias, e))
    mongoengine.connection.ConnectionError: Cannot connect to database default :
    could not connect to localhost:27017: [Errno 10061] No connection could be made
    because the target machine actively refused it

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "build\bdist.win32\egg\__deploy__\ally\deploy.py", line 71, in deploy
        context.processStart()
      File "build\bdist.win32\egg\ally\container\context.py", line 96, in processSta
    rt
        for call in calls: assembly.processForName(call.name)
      File "build\bdist.win32\egg\ally\container\_impl\_assembly.py", line 183, in p
    rocessForName
        try: value = self.fetchForName(name)()
      File "build\bdist.win32\egg\ally\container\_impl\_call.py", line 211, in __cal
    l__
        ret = self.call()
      File "build\bdist.win32\egg\__setup__\ally_plugin\deploy_plugin.py", line 91,
    in deploy
        try: context.processStart()
      File "build\bdist.win32\egg\ally\container\context.py", line 96, in processSta
    rt
        for call in calls: assembly.processForName(call.name)
      File "build\bdist.win32\egg\ally\container\_impl\_assembly.py", line 183, in p
    rocessForName
        try: value = self.fetchForName(name)()
      File "build\bdist.win32\egg\ally\container\_impl\_call.py", line 211, in __cal
    l__
        ret = self.call()
      File "build\bdist.win32\egg\ally\container\support.py", line 214, in loadAll
        if name.startswith(prefix) and isinstance(call, CallEntity) and call.isOf(cl
    azz): Assembly.process(name)
      File "build\bdist.win32\egg\ally\container\_impl\_assembly.py", line 90, in pr
    ocess
        return ass.processForName(name)
      File "build\bdist.win32\egg\ally\container\_impl\_assembly.py", line 186, in p
    rocessForName
        (name, ', '.join(self._processing)))
    ally.container.error.SetupError: Exception occurred for '__plugin__.content_publ
    isher.service.publisherService' in processing chain 'loader_69688416, __plugin__
    .content_publisher.service.publisherService'
    --------------------------------------------------------------------------------
    ----------------------------------------------------------------------
    ================================================== Application started in 34.42
    seconds

    C:\Ally-Py\Superdesk>


    also iv'e tried to build on linux (unbunto 12) , the same error appears . also iv'e tried to install Ally-Py and Superdesk from master and live blog 16 branches on github but the same error appears.
  • Vote Up0Vote Down Martin SaturkaMartin Saturka
    Posts: 40Member, Sourcefabric Team
    Hi Omar,
    you do not have MongoDB running, see install instructions:
    https://github.com/sourcefabric/Superdesk/blob/master/INSTALL.txt#L106

  • oh its works now , thank you Martin.
  • Hello Guys,
    I am almost done configuring superdesk server, but following is the error I get when starting the server:-

    (env)root@ip-172-31-20-75:/home/ubuntu/superdesk-server# honcho start
    11:10:39 rest.1 | started with pid 2179
    11:10:39 wamp.1 | started with pid 2180
    11:10:39 work.1 | started with pid 2182
    11:10:39 beat.1 | started with pid 2184
    11:10:40 wamp.1 | initializing heartbeat...
    11:10:40 wamp.1 | listening on 0.0.0.0:5100
    11:10:41 work.1 | PUT /superdesk [status:400 request:0.046s]
    11:10:41 rest.1 | PUT /superdesk [status:400 request:0.057s]
    11:10:41 beat.1 | PUT /superdesk [status:400 request:0.049s]
    11:10:41 wamp.1 | registered client 127.0.0.1:35693
    11:10:41 wamp.1 | registered client 127.0.0.1:35694
    11:10:41 wamp.1 | registered client 127.0.0.1:35695
    11:10:42 work.1 | Raven is not configured (logging is disabled). Please see the documentation for more information.....P
    11:10:42 rest.1 | Raven is not configured (logging is disabled). Please see the documentation for more information.....P
    11:10:42 rest.1 |  * Running on http://0.0.0.0:5000/
    11:10:42 rest.1 |  * Restarting with reloader
    11:10:42 beat.1 | Raven is not configured (logging is disabled). Please see the documentation for more information.....P
    11:10:42 beat.1 | [2014-12-26 11:10:42,718: INFO/MainProcess] beat: Starting...
    11:10:42 work.1 | process terminated
    11:10:42 system | sending SIGTERM to all processes
    11:10:42 system | sending SIGTERM to pid 2179
    11:10:42 system | sending SIGTERM to pid 2180
    11:10:42 system | sending SIGTERM to pid 2184
    11:10:42 beat.1 | [2014-12-26 11:10:42,761: INFO/MainProcess] Scheduler: Sending due task ingest:update (superdesk.io.update_ingest)
    11:10:42 rest.1 | process terminated
    11:10:42 wamp.1 | process terminated
    11:10:42 beat.1 | process terminated


    May I know how to configure logging in raven.....................

    Thanks In Advance
    Pras
  • Hi

    Trying to get the superdesk-server Docker image to run inside boot2docker on Mac OSX, but can't get it to start. Have tried downloading the image from Docker Hub and building my own using the Dockerfile, but both result in the same error message.

    13:17:07 rest.1 | Traceback (most recent call last):
    13:17:07 rest.1 |   File "/usr/local/lib/python3.4/dist-packages/gunicorn/arbiter.py", line 503, in spawn_worker
    13:17:07 rest.1 |     worker.init_process()
    13:17:07 rest.1 |   File "/usr/local/lib/python3.4/dist-packages/gunicorn/workers/base.py", line 116, in init_process
    13:17:07 rest.1 |     self.wsgi = self.app.wsgi()
    13:17:07 rest.1 |   File "/usr/local/lib/python3.4/dist-packages/gunicorn/app/base.py", line 67, in wsgi
    13:17:07 rest.1 |     self.callable = self.load()
    13:17:07 rest.1 |   File "/usr/local/lib/python3.4/dist-packages/gunicorn/app/wsgiapp.py", line 65, in load
    13:17:07 rest.1 |     return self.load_wsgiapp()
    13:17:07 rest.1 |   File "/usr/local/lib/python3.4/dist-packages/gunicorn/app/wsgiapp.py", line 52, in load_wsgiapp
    13:17:07 rest.1 |     return util.import_app(self.app_uri)
    13:17:07 rest.1 |   File "/usr/local/lib/python3.4/dist-packages/gunicorn/util.py", line 355, in import_app
    13:17:07 rest.1 |     __import__(module)
    13:17:07 rest.1 |   File "/opt/superdesk/wsgi.py", line 14, in <module>
    13:17:07 rest.1 |     application = get_app()
    13:17:07 rest.1 |   File "/opt/superdesk/app.py", line 112, in get_app
    13:17:07 rest.1 |     app.data.elastic.put_mapping(app)
    13:17:07 rest.1 |   File "/usr/local/lib/python3.4/dist-packages/eve_elastic/elastic.py", line 196, in put_mapping
    13:17:07 rest.1 |     indices.put_mapping(index=index or self.index, doc_type=resource, body=mapping, ignore_conflicts=True)
    13:17:07 rest.1 |   File "/usr/local/lib/python3.4/dist-packages/elasticsearch/client/utils.py", line 68, in _wrapped
    13:17:07 rest.1 |     return func(*args, params=params, **kwargs)
    13:17:07 rest.1 |   File "/usr/local/lib/python3.4/dist-packages/elasticsearch/client/indices.py", line 275, in put_mapping
    13:17:07 rest.1 |     params=params, body=body)
    13:17:07 rest.1 |   File "/usr/local/lib/python3.4/dist-packages/elasticsearch/transport.py", line 307, in perform_request
    13:17:07 rest.1 |     status, headers, data = connection.perform_request(method, url, params, body, ignore=ignore, timeout=timeout)
    13:17:07 rest.1 |   File "/usr/local/lib/python3.4/dist-packages/elasticsearch/connection/http_urllib3.py", line 82, in perform_request
    13:17:07 rest.1 |     raise ConnectionError('N/A', str(e), e)
    13:17:07 rest.1 | elasticsearch.exceptions.ConnectionError: ConnectionError(('Connection aborted.', ConnectionRefusedError(111, 'Connection refused'))) caused by: ProtocolError(('Connection aborted.', ConnectionRefusedError(111, 'Connection refused')))
    13:17:07 rest.1 | [2015-04-17 13:17:07 +0000] [31] [INFO] Worker exiting (pid: 31)
    13:17:07 rest.1 | [2015-04-17 13:17:07 +0000] [16] [INFO] Shutting down: Master
    13:17:07 rest.1 | [2015-04-17 13:17:07 +0000] [16] [INFO] Reason: Worker failed to boot.

    What am I doing wrong?
  • Thanks! Got it running with docker-compose after editing the docker-compose.yml.sh file a bit. The full sequence of steps I had to take to get it to work on Mac OS X Yosemite with Boot2Docker were:
    1. Open a regular Terminal window
    2. sudo -i
    3. curl -L https://github.com/docker/compose/releases/download/1.2.0/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
    4. chmod +x /usr/local/bin/docker-compose
    5. exit
    6. brew install python
    7. brew install python3
    8. pip install virtualenv
    9. cd /my_github_repository_location/superdesk
    10. . env/bin/activate
    11. pip install -r docker/requirements.txt
    12. open /Applications/boot2docker.app
    13. Inside the new Terminal window opened by Boot2Docker, run the following commands:
    14. :$ export DOCKER_HOST=tcp://192.168.59.XXX:XXXX
    15. :$ export DOCKER_CERT_PATH=/Users/XXX/.boot2docker/certs/boot2docker-vm
    16. :$ export DOCKER_TLS_VERIFY=1
    17. :$ docker pull dockerfiles/redis
    18. :$ vim docker/docker-compose.yml.sh
      a) Change dockerfile/redis to dockerfiles/redis
      b) Change volumes for mongodb from ../data/mongodb to /mnt/sda1/data/mongodb. Now mongodb starts without file size problems.
      c) Change all instances of 127.0.0.1 to the IP address provided by 'boot2docker ip'
    19. :$ ./scripts/docker-local-demo.sh

    Obviously you need to change any parts highlighted in yellow with your local paths and IPs.

    Hope this will help.
    Post edited by Peter Henebäck at 2015-04-20 07:42:24
  • Thanks for your feedback Peter!
    I updated repo addresses in docker-compose.yml (17-18).
    Btw I don't think what python3 (7) is necessary because docker-compose is using python2 (6).
    Innovations developer, Sourcefabric
  • Ok, never checked if it would work without python3, so that's probably true. 

    Regarding the instructions, I was stuck for quite a while trying to get the docker-local-create-user.sh script to work thinking I couldn't log on because the admin user didn't exist when the real problem was that Superdesk was trying to log on to address 127.0.0.1 rather than the 192.168.59.XXX address of the Boot2Docker VM. 

    Would be good to include that point in the instructions somehow.








  • It seems to be something specific for Boot2docker or OS X. Added a small note to readme: https://github.com/superdesk/superdesk/commit/e0ce1b30115f7577227b02bbf4f3989036db3104
    Innovations developer, Sourcefabric
  • Vote Up0Vote Down Tom HTom H
    Posts: 27Member
    Hi,

    I'm trying to install the Superdesk demo on Ubuntu, when I get to running "./scripts/docker-local-demo.sh"
    command it throws an error saying
    "Couldn't connect to Docker daemon at http+unix://var/run/docker.sock - is it running?"

    Docker daemon is running and I'm pretty sure its installed at default location but I am new to Linux so not sure what to do now, any help ,much appreciated!

    Cheers,
    Tom
  • Hello Tom!

    Did you made Docker work without sudo? (see http://askubuntu.com/questions/477551/how-can-i-use-docker-without-sudo)
    Innovations developer, Sourcefabric
  • Vote Up0Vote Down Tom HTom H
    Posts: 27Member
    Hi, thanks for reply. Yes I followed those instructions from initial install but tried again and still same error unfortunately. Have tried editing DOCKER_HOSTS after reading on forums but having no joy. 
  • can you try
     docker ps
    and
     sudo docker ps
    ?

    if only first fails then it seems like you missed something when giving your user permissions to use docker.

    if both will fail then also run:
     sudo lsof | grep docker\.sock

    if latter will fail too then:
     sudo systemctl status docker || sudo service docker status
    Post edited by Yauhen Kirylau at 2015-04-25 02:40:51
    Innovations developer, Sourcefabric
  • Vote Up0Vote Down Tom HTom H
    Posts: 27Member
    Thanks for the reply Yauhen. Running both docker ps and sudo docker ps bring up empty container list:

    /superdesk$ sudo docker ps
    2015/04/26 21:45:24 GET /v1.12/containers/json
    [2a754e8b] +job containers()
    [2a754e8b] -job containers() = OK (0)
    CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

    running: sudo lsof | grep docker\.sock
    gets:

    ~/superdesk$ sudo lsof | grep docker\.sock
    lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
          Output information may be incomplete.
    docker.io  1469             root    4u     unix 0xffff8800b2d35080      0t0      15426 /var/run/docker.sock
    docker.io  1469  1495       root    4u     unix 0xffff8800b2d35080      0t0      15426 /var/run/docker.sock
    docker.io  1469  1496       root    4u     unix 0xffff8800b2d35080      0t0      15426 /var/run/docker.sock
    docker.io  1469  1499       root    4u     unix 0xffff8800b2d35080      0t0      15426 /var/run/docker.sock
    docker.io  1469  1533       root    4u     unix 0xffff8800b2d35080      0t0      15426 /var/run/docker.sock
    docker.io  1469  1550       root    4u     unix 0xffff8800b2d35080      0t0      15426 /var/run/docker.sock
    docker.io  1469  1644       root    4u     unix 0xffff8800b2d35080      0t0      15426 /var/run/docker.sock
    docker     7836             root    6u     unix 0xffff88009dca3480      0t0      82041 /var/run/docker.sock
    docker     7836  7837       root    6u     unix 0xffff88009dca3480      0t0      82041 /var/run/docker.sock
    docker     7836  7838       root    6u     unix 0xffff88009dca3480      0t0      82041 /var/run/docker.sock
    docker     7836  7839       root    6u     unix 0xffff88009dca3480      0t0      82041 /var/run/docker.sock
    docker     7836  7840       root    6u     unix 0xffff88009dca3480      0t0      82041 /var/run/docker.sock
    docker     7836  7841       root    6u     unix 0xffff88009dca3480      0t0      82041 /var/run/docker.sock
    docker     7836  7845       root    6u     unix 0xffff88009dca3480      0t0      82041 /var/run/docker.sock

    the result of last command: sudo systemctl status docker || sudo service docker status
    is:
    ~/superdesk$ sudo systemctl status docker || sudo service docker status
    sudo: systemctl: command not found
    docker stop/waiting

    I'm new to Linux so please bare with me if I'm doing something stupid!
    Many thanks
    Tom
  • Can you retry the script but without settings any env vars?
    Because it was failing on step which was checking if docker is running by executing "docker ps" so if that command works manually script should pass that check as well.
    Innovations developer, Sourcefabric
  • Vote Up0Vote Down Tom HTom H
    Posts: 27Member
    I'm sorry Yauhen, can you give me an example of what you mean?
  • I mean what it seems like script was failing on this step (https://github.com/superdesk/superdesk/blob/master/scripts/docker-local-demo.sh#L4) because "docker ps" command failed.

    Since now that command returns to you correct output then try running the script (docker-local-demo) again.
    Innovations developer, Sourcefabric
  • Vote Up0Vote Down Tom HTom H
    Posts: 27Member
    still the same I think:

    ~/superdesk$ ./scripts/docker-local-demo.sh
    Docker version 1.0.1, build 990021a
    2015/04/28 12:51:25 GET /v1.12/containers/json
    [db3db740] +job containers()
    [db3db740] -job containers() = OK (0)
    docker-compose 1.2.0

    |=================================================================|
    |open in browser "http://localhost:80" after server will be ready |
    |                                                                 |
    |       if you can not log in you probably need to run            |
    |       "./docker-local-create-user.sh"                           |
    |=================================================================|

    mongodb uses an image, skipping
    redis uses an image, skipping
    elastic uses an image, skipping
    Building backend...
    2015/04/28 12:51:25 POST /v1.15/build?pull=True&nocache=False&q=False&t=docker_backend&forcerm=False&rm=True
    Couldn't connect to Docker daemon at http+unix://var/run/docker.sock - is it running?

    If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.

  • Thanks for the full output.

    Can you check if docker still running after script was failed?
    Innovations developer, Sourcefabric
  • Vote Up0Vote Down Tom HTom H
    Posts: 27Member
    yes its still running, docker run hello-world worked fine. Do I need to set DOCKER_HOST environment variables? This is my DOCKER_OPTS from /etc/default/docker: Do I need to uncomment it?


    #DOCKER_OPTS="-H tcp://localhost:4243 -H unix:///var/run/docker.sock"


  • No, you don't need to.

    How much time approximatelty it took between starting script and it's failure? (i am also suspecting sorta timeout)

    Also, on which hardware configuration do you running it?
    Innovations developer, Sourcefabric
  • Vote Up0Vote Down Tom HTom H
    Posts: 27Member
    It runs through it all almost immediately. I have partitioned a Dell Vostro 3360 laptop to dual boot Ubuntu 14.04 and Windows 8.1.

    Do you have a VirtualBox Ubuntu image of a working system for download maybe?

    Thanks
    Tom
  • Hm, if it happens almost immediately then i can't suspect some timeout or performance.
    Mb something wrong with permission to docker daemon.

    While you are running in virtual box it's safe to try running the script with "sudo" (to check if it's a permission issue or not).
    Innovations developer, Sourcefabric
  • Vote Up0Vote Down Tom HTom H
    Posts: 27Member
    Tried with sudo and still the same. Have disabled  firewall too. 

    I am not running VirtualBox but was wondering if there was a working image with SuperDesk installed to download?. I have tried Boot2Docker on windows too but with no joy. I will try a fresh install of Ubuntu on VirtualBox and see if I can get working.

    Thanks
    Tom
  • I just noticed what you are using docker v. 1.0.1
    Please try updating it to the current stable 1.6

    I that won't help I can prepare Vagrantfile for creating such VirtualBox machine.
    Post edited by Yauhen Kirylau at 2015-04-28 08:50:35
    Innovations developer, Sourcefabric
  • Vote Up0Vote Down Tom HTom H
    Posts: 27Member

    oh yes! Thank you!!! I thought doing an apt-get update would have updated it automatically but it wasn't. 
    I had to do 'sudo apt-get install lxc-docker=1.6.0' to upgrade properly.

    I have now run './scripts/docker-local-demo.sh' and its gone through a whole process of downloading and updating which is looking good but on completion I got the following error (i tried as sudo too) so I still can't see anything on http://localhost:80:


    Step 0 : FROM dockerfile/nodejs

    ERRO[1566] Error from V2 registry: Authentication is required. 

    Pulling repository dockerfile/nodejs

    Error: image dockerfile/nodejs:latest not found




  • Vote Up0Vote Down Tom HTom H
    Posts: 27Member
    ran './scripts/docker-local-demo.sh' again and didn't see previous error. I still can't access on localhost so I'm outputting the result here if it helps:

    ~/superdesk$ ./scripts/docker-local-demo.sh
    Docker version 1.6.0, build 4749651
    INFO[2028] GET /v1.18/containers/json                   
    INFO[2028] +job containers()                            
    INFO[2028] -job containers() = OK (0)                   
    docker-compose 1.1.0-rc2

    |=================================================================|
    |open in browser "http://localhost:80" after server will be ready |
    |                                                                 |
    |       if you can not log in you probably need to run            |
    |       "./docker-local-create-user.sh"                           |
    |=================================================================|

    mongodb uses an image, skipping
    redis uses an image, skipping
    elastic uses an image, skipping
    Building backend...
    INFO[2028] POST /v1.14/build?pull=True&nocache=False&q=False&t=docker_backend&forcerm=False&rm=True 
    INFO[2028] +job build()                                 
    Step 0 : FROM ubuntu:trusty
     ---> d0955f21bf24
    Step 1 : RUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends python3 python3-dev python3-pip build-essential libffi-dev git mercurial libtiff5-dev libjpeg8-dev zlib1g-dev libfreetype6-dev liblcms2-dev libwebp-dev curl
     ---> Using cache
     ---> efe47362f383
    Step 2 : WORKDIR /opt/superdesk/
     ---> Using cache
     ---> dcb2e9ff99e8
    Step 3 : CMD honcho start
     ---> Using cache
     ---> 4f5d1911839c
    Step 4 : EXPOSE 5000
     ---> Using cache
     ---> d8ad29e9bae9
    Step 5 : EXPOSE 5100
     ---> Using cache
     ---> ef2194ecc4ec
    Step 6 : ENV PYTHONUNBUFFERED 1
     ---> Using cache
     ---> 9c882758fe06
    Step 7 : ENV C_FORCE_ROOT "False"
     ---> Using cache
     ---> 955c9b2f7066
    Step 8 : ENV CELERYBEAT_SCHEDULE_FILENAME /tmp/celerybeatschedule.db
     ---> Using cache
     ---> bf5dd7545fb8
    Step 9 : ADD requirements.txt /tmp/requirements.txt
     ---> Using cache
     ---> b76449a9fe12
    Step 10 : RUN cd /tmp && pip3 install -U -r /tmp/requirements.txt
     ---> Using cache
     ---> 90661e3f49d0
    Step 11 : ADD . /opt/superdesk
     ---> Using cache
     ---> 4404e434030f
    Successfully built 4404e434030f
    INFO[2028] -job build() = OK (0)                        
    Building frontend...
    INFO[2028] POST /v1.14/build?pull=True&nocache=False&q=False&t=docker_frontend&forcerm=False&rm=True 
    INFO[2028] +job build()                                 
    INFO[2029] +job pull(dockerfile/nodejs, latest)         
    INFO[2029] +job resolve_repository(dockerfile/nodejs)   
    INFO[2029] -job resolve_repository(dockerfile/nodejs) = OK (0) 
    Step 0 : FROM dockerfile/nodejs
    Pulling repository dockerfile/nodejs
    Get https://index.docker.io/v1/repositories/dockerfile/nodejs/images: dial tcp: lookup index.docker.io on 172.20.10.1:53: read udp 172.20.10.1:53: i/o timeout
    INFO[2044] -job pull(dockerfile/nodejs, latest) = ERR (1) 
    Get https://index.docker.io/v1/repositories/dockerfile/nodejs/images: dial tcp: lookup index.docker.io on 172.20.10.1:53: read udp 172.20.10.1:53: i/o timeout
    INFO[2044] -job build() = ERR (1)                       
    Service 'frontend' failed to build: Get https://index.docker.io/v1/repositories/dockerfile/nodejs/images: dial tcp: lookup index.docker.io on 172.20.10.1:53: read udp 172.20.10.1:53: i/o timeout

  • Repository address of docker images have changed about a week ago or so.

    Please git-pull the latest changes from the Superdesk repo.

    UPD: one more thing (unrelated) - if you will run the script with sudo privileges '/data/' dir and mb some files under '/docker/' folder will became owned by root (which will end up in permission error then will run it again as a user).
    Post edited by Yauhen Kirylau at 2015-04-28 11:39:18
    Innovations developer, Sourcefabric