Failed to start circus.service

1,368 views
Skip to first unread message

baed...@googlemail.com

unread,
Oct 5, 2015, 6:35:30 PM10/5/15
to taigaio
Hey!

I have a perfectly good running taiga installation in a virtualbox with Ubuntu LTS 14.04 installed.
Now that I know, Taiga is the tool I want to keep using, I want to move that thing to a RaspberryPi, because I have one laying around doing nothing at the moment.

I follow these instructions: http://taigaio.github.io/taiga-doc/dist/setup-production.html

I skip 3.5 and 5. for the time being.
Now I am at step 6.1: "sudo service circus start"

Whilst this was never a problem on Ubuntu LTS 14.04, Raspbian and Ubuntu MATE on the RPi both tell me:
"Failed to start circus.service: Unit circus.service failed to load: No such file or directory"

Indeed, there is no circus.service anywhere on my system... but why?
"circusctl" tells me "Timed Out." because "#1 daemon could not be reached" or "#2 it took too long to perform the operation"

I have ZERO experience with circus, but it does not seem to be installed properly :/

I havn't seen any errors during the taiga-production.html setup routine and I can't find this particular error on the internet.
Does anyone know why that happens? I am 98% sure I followed the
taiga-production.html to the spot... plus it worked a few months ago on my virtual machine...

Please help, if you can :)

Thanks!

Baedfisch.


Alejandro Alonso

unread,
Oct 6, 2015, 2:14:03 AM10/6/15
to Bäd Fisch, taigaio
Hello from the Taiga development team,

We haven't done any installation on raspbian but did you try using taiga-scripts for a fully automated install? -> http://taigaio.github.io/taiga-doc/dist/setup-alternatives.html

Regards!,





--

  
Alejandro Alonso Fernández  
CIO & Co-founder

www.kaleidos.net/FC8EAC/

janusz.p...@gmail.com

unread,
Jan 5, 2016, 6:42:35 PM1/5/16
to taigaio, baed...@googlemail.com
Hi,

I have the same problem. I'm trying to install Taiga on Debian stable. I've used setup-circus.sh as you suggested, Alejandro, but with no luck.

Alejandro Alonso

unread,
Jan 7, 2016, 2:01:43 AM1/7/16
to janusz.p...@gmail.com, taigaio, Bäd Fisch
Hello!,

That scripts are designed to work on ubuntu 14.04 probably you should do some changes to make them work in debian. Could you try taiga-scripts in a clean ubuntu 14.04 machine?

Regards,

--
You received this message because you are subscribed to the Google Groups "taigaio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to taigaio+u...@googlegroups.com.
To post to this group, send email to tai...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/taigaio/dff9791d-5072-41f7-9eac-46121eabbee7%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

mcsf1...@pucit.edu.pk

unread,
Sep 9, 2016, 3:48:15 AM9/9/16
to taigaio, baed...@googlemail.com

when i run command .
 circusctl reloadconfig

an error occured..... 
Timed out.
A time out usually happens in one of those cases:

#1 The Circus daemon could not be reached.
#2 The Circus daemon took too long to perform the operation

For #1, make sure you are hitting the right place
by checking your --endpoint option.

For #2, if you are not expecting a result to
come back, increase your timeout option value
(particularly with waiting switches)
please help........

deepa.m...@gslab.com

unread,
Jun 2, 2017, 7:54:12 AM6/2/17
to taigaio, baed...@googlemail.com
I do not have anything like circus.ini, not mentioned in https://taigaio.github.io/taiga-doc/dist/setup-production.html#_events_installation, rather have these. 

(taiga) gslab@kazoo-tools:/etc/circus$ ls
circusd.conf  conf.d
(taiga) gslab@kazoo-tools:/etc/circus$ ls -a conf.d/
.  ..  taiga-celery.ini  taiga-events.ini  taiga.ini

Sample files: 

[watcher:taiga-celery]
working_dir = /home/gslab/taiga-back
cmd = celery
args = -A taiga worker -c 4
uid =  gslab
numprocesses = 1
autostart = true
send_hup = true
stdout_stream.class = FileStream
stdout_stream.filename = /home/gslab/logs/celery.stdout.log
stdout_stream.max_bytes = 10485760
stdout_stream.backup_count = 4
stderr_stream.class = FileStream
stderr_stream.filename = /home/gslab/logs/celery.stderr.log
stderr_stream.max_bytes = 10485760
stderr_stream.backup_count = 4

[env:taiga-celery]
PATH = /home/gslab/.virtualenvs/taiga/bin:$PATH
TERM=rxvt-256color
SHELL=/bin/bash
USER=gslab
LANG=en_US.UTF-8
HOME=/home/gslab
PYTHONPATH=/home/gslab/.virtualenvs/taiga/lib/python3.5/site-packages


[watcher:taiga-events]
working_dir = /home/gslab/taiga-events
cmd = /usr/local/bin/coffee
args = index.coffee
uid = gslab
numprocesses = 1
autostart = true
send_hup = true
stdout_stream.class = FileStream
stdout_stream.filename = /home/gslab/logs/taigaevents.stdout.log
stdout_stream.max_bytes = 10485760
stdout_stream.backup_count = 12
stderr_stream.class = FileStream
stderr_stream.filename = /home/gslab/logs/taigaevents.stderr.log
stderr_stream.max_bytes = 10485760
stderr_stream.backup_count = 12
[watcher:taiga]
working_dir = /home/gslab/taiga-back
cmd = gunicorn
args = -w 3 -t 60 --pythonpath=. -b 127.0.0.1:8001 taiga.wsgi
uid = gslab
numprocesses = 1
autostart = true
send_hup = true
stdout_stream.class = FileStream
stdout_stream.filename = /home/gslab/logs/gunicorn.stdout.log
stdout_stream.max_bytes = 10485760
stdout_stream.backup_count = 4
stderr_stream.class = FileStream
stderr_stream.filename = /home/gslab/logs/gunicorn.stderr.log
stderr_stream.max_bytes = 10485760
stderr_stream.backup_count = 4

[env:taiga]
PATH = /home/gslab/.virtualenvs/taiga/bin:$PATH
TERM=rxvt-256color
SHELL=/bin/bash
USER=gslab
LANG=en_US.UTF-8
HOME=/home/taiga
PYTHONPATH=/home/gslab/.virtualenvs/taiga/lib/python3.5/site-packages

Not sure what is wrong, I used the uid as default user of machine. (used taiga also but no change) 

I get following errors on : 

(taiga) gslab@kazoo-tools:/etc/circus$ circusctl reloadconfig
Timed out.
A time out usually happens in one of those cases:

#1 The Circus daemon could not be reached.
#2 The Circus daemon took too long to perform the operation

For #1, make sure you are hitting the right place
by checking your --endpoint option.

For #2, if you are not expecting a result to
come back, increase your timeout option value
(particularly with waiting switches)

Only sudo service circusd restart works fine. I am first time using circus, online help is not proving successful. Please reply back with some solution. 

Regards
Deepa  
Reply all
Reply to author
Forward
0 new messages