Forum: Developer
Starling/Workling not working
|
|
Hans W 20.Apr.2011 6:31pm
Hi,
My installation is running on Ubuntu 10 and works for the most part. I discovered that Starling was not running, nor Workling. I started both but still no luck. I found this after running into two issues. 1. I tried to start some extra modules and found them “initializing” but nothing more. 2. I started theme builder which gave an error. After manually starting Starling and retrying, it responded with Fetching, waiting for fetch proces to start but nothing happens. I started with “starling -d -P tmp/pids/starling.pid -q tmp/starling_production/ -p 15151” out of the Webiva directory. and “script/workling_client start” both are running but the plugins nor themebuilder work. Hope someone can help me out here. Hans |
|
|
Pascal Rettig 21.Apr.2011 10:21am
Hi Hans,
You should be able to start both with the command: (kill any existing processes first) RAILS_ENV=development ./script/background.rb start if you are running in development mode or RAILS_ENV=produdction ./script/background.rb start if you are running production mode. The background processes need to be started in a way that matches the running web server. -Pascal |
|
|
Hans W 21.Apr.2011 10:48am
Hi Pascal,
thanks for your reply. I tried it and it seems to work. I noticed though that on your site I get the “I am busy rolling sun” while on my implementation that is missing. The theme builder now works though. On the modules nothing happens, they still are “initialising” also after a reboot. Is there a trick to get them back to available? Do I have to use this command everytime after a reboot or is there a trick to run it automatically? Thanks, Hans |
|
|
Pascal Rettig 21.Apr.2011 11:38am
Hi Hans,
You may want to pull the latest version from the development branch for the most update to date features. You can run from the command line: rake cms:migrate_domain_components To finish migrating any modules that are stuck intializing. You do need to start the background process after each reboot – you can add it a init.d or upstart startup script to have it start automatically. |
|
|
Hans W 22.Apr.2011 4:21am
Thanks Pascal,
that did the trick! Hans |

