Why do I see ''Error 500'' when attempting to login to the Columbus web UI and when I check the status of the Columbus services the Acc component is shown as ''WARNING''?

Why do I see ''Error 500'' when attempting to login to the Columbus web UI and when I check the status of the Columbus services the Acc component is shown as ''WARNING''?

If you see the below error when attempting to login to the Columbus via the Web UI then check to make sure the Acc service is running.

* ERROR 2020-12-09 13:30:04,136 django.request -- Internal Server Error: /
* ERROR 2020-12-09 13:30:04,133 columbus.acc_client -- Acapella request error <urlopen error [Errno 111] Connection refused>
* ERROR 2020-12-09 12:15:02,992 django.request -- Internal Server Error: /
* ERROR 2020-12-09 12:15:02,988 columbus.acc_client -- Acapella request error <urlopen error [Errno 111] Connection refused>
* ERROR 2020-12-09 12:14:14,736 root -- Failed to stop Nginx server process.
* ERROR 2020-12-09 12:12:37,296 root -- Failed to start Nginx server
* ERROR 2020-12-09 12:12:36,295 root -- Sub-process call error message: nginx: [emerg] unknown log format "main" in /usr/local/PerkinElmerCTG/Columbus/webapp/server/config/nginx.conf:38
* ERROR 2020-12-09 12:12:36,294 root -- Failed to start Nginx server
* ERROR 2020-12-09 12:12:05,154 root -- Failed to stop Nginx server process.
* ERROR 2020-12-09 12:06:36,488 root -- Failed to start Nginx server
* ERROR 2020-12-09 12:06:35,486 root -- Sub-process call error message: nginx: [emerg] unknown directive "log_format" in /usr/local/PerkinElmerCTG/Columbus/webapp/server/config/nginx.conf:21
* ERROR 2020-12-09 12:06:35,485 root -- Failed to start Nginx server
* ERROR 2020-12-09 12:06:01,744 root -- Failed to stop Nginx server process.
* ERROR 2020-12-09 12:02:53,176 root -- Failed to start Nginx server
* ERROR 2020-12-09 12:02:52,173 root -- Sub-process call error message: nginx: [emerg] unknown "realip_remote_addr" variable
* ERROR 2020-12-09 12:02:52,172 root -- Failed to start Nginx server
* ERROR 2020-12-09 12:01:15,054 root -- Failed to stop Fast-CGI server process.
* ERROR 2020-12-09 12:01:15,048 root -- Failed to stop Nginx server process.
* ERROR 2020-12-09 12:00:45,013 root -- Sub-process call error message: nginx: [emerg] unknown "realip_remote_addr" variable
* ERROR 2020-12-09 12:00:45,012 root -- Failed to stop Nginx server
* ERROR 2020-12-09 11:59:31,349 root -- Failed to stop Nginx server process.
* ERROR 2020-12-09 11:59:01,313 root -- Sub-process call error message: nginx: [emerg] duplicate "log_format" name "main" in /usr/local/PerkinElmerCTG/Columbus/webapp/server/config/nginx.conf:185
* ERROR 2020-12-09 11:59:01,312 root -- Failed to stop Nginx server
* ERROR 2020-12-09 11:37:42,021 django.request -- Internal Server Error: /
* ERROR 2020-12-09 11:37:42,020 columbus.acc_client -- Acapella request error <urlopen error [Errno 111] Connection refused>
* ERROR 2020-12-09 11:35:51,116 django.request -- Internal Server Error: /
* ERROR 2020-12-09 11:35:51,115 columbus.acc_client -- Acapella request error <urlopen error [Errno 111] Connection refused>
* ERROR 2020-12-09 11:31:13,652 django.request -- Internal Server Error: /
* ERROR 2020-12-09 11:31:13,652 columbus.acc_client -- Acapella request error <urlopen error [Errno 111] Connection refused>
* ERROR 2020-12-09 11:30:56,027 django.request -- Internal Server Error: /

You can check the status of the Columbus services by logging in to the server via SSH (Terminal or PuTTY) and issue the following command:

$ sudo /etc/init.d/columbus status

If the output looks like the below example then check the /var/log/columbus/acc/acc.log for errors

 * Columbus status
    Database:  up                                          [  OK  ]
    Acc:  up                                               [  WARNING  ]
    Web:  up                                               [  OK  ]
    Celery:  up                                            [  OK  ]

If you see lines which start with:

2020-12-09 13:32:02 4 {1/0} [file/jobstatus] "Invalid line in job status file...

Then there is the possibility that Acapella isn't able to read from one of the saved files e.g. the job status log file. It would suggest a possible corruption.

The job status file is found in /var/lib/acapella/.Acapella

Try renaming the /var/lib/acapella/.Acapella directory and restart the Columbus services.

$ sudo /etc/init.d/columbus restart

Then check the status again:

$ sudo /etc/init.d/columbus status

If all Services have started correctly the status command should report the following:

 * Columbus status
    Database:  up                                          [  OK  ]
    Acc:  up                                               [  OK  ]
    Web:  up                                               [  OK  ]
    Celery:  up                                            [  OK  ]

Now try logging in through the Columbus web UI.

If this does not help resolve the problem please contact the Columbus support team using the signals.support@revvity.com email address.