PerkinElmer Informatics Support Forum
Decrease font size
Increase font size
Topic Title: Can I restart Columbus services independently?
Topic Summary: Start/Stop/Restart Columbus services Independently
Created On: 1/5/2017 4:57 AM
Status Post and Reply
Linear : Threading : Single : Branch
Topic Tools Topic Tools
View topic in raw text format. Print this topic.
 1/5/2017 4:57 AM
User is offline View Users Profile Print this message


RAH

Posts: 57
Joined: 5/16/2014

The Columbus application is divided between 4 main services as shown below:

[root@BigRed ~]# /etc/init.d/columbus status
* Columbus status
Database: up [ OK ]
Acc: up [ OK ]
Web: down [WARNING]
Celery: up [ OK ]

The Database component which is effectively the data repository split between the pgsql db and /OMERO data/pixel repository.

The Acc component or ''Acapella'' which is the data import/export/analysis engine

The Web component which deals with the Web UI and associated connections/services e.g. Nginx

The Celery component which is a task queing service/system for image rendering/exports to 3rd party apps such as High Content Profiler.

If a single component is showing a warning then it is possible to start/stop/restart that individual service (requires root privileges).

In the example shown above the web component 'down' with a 'WARNING' status. Rather than restarting all services using the generic columbus script found in /etc/init.d/, which might kill, for example, analysis/import/export jobs unecessarily you may want to isolate the offending service and restart it independently, the same columbus script found in /etc/init.d will allow you do that.

e.g.

$ /etc/init.d/columbus start web

[root@BigRed ~]# /etc/init.d/columbus start web
* Starting Columbus
Web: [ OK ]
[root@BigRed ~]#

-----------------------------

RAH

FuseTalk Basic Edition v4.0 - © 1999-2018 FuseTalk Inc. All rights reserved.