Why am I seeing 'Acapella request error' when I attempt to login to Columbus?

Why am I seeing 'Acapella request error' when I attempt to login to Columbus?

If you see the below errors when logging in to Columbus then one possible root cause could be that the Acapella service has failed to start or is not currently up and running

To check the Acapella service, login to the Columbus via SSH connection e.g. via PuTTY or Terminal and issue the following command:

$ sudo /etc/init.d/columbus status

If the Acc service is shown as 'WARNING' then the next step would be to check the acc.log file for associated errors. The acc.log is located in the /var/log/columbus/acc directory on the Columbus server.

The acc.log is also bundled with the Columbus log files which can be downloaded through the Columbus interface using the following web shortcut. Enter the following into the address line of your browser:

columbusip/help/error/all_logs.zip  (replace 'columbusip' with the IP address for your server)

or via command line:

$ zip –r /tmp/columbus_logs.zip /var/log/columbus

When opening the acc.log file scroll to the bottom of the file or scroll to the date and time of your last login attempt. If you then see multiple lines/errors which read:

2020-04-01 13:40:03 4 {1/0} [file/jobstatus] "Invalid line in job status file:"

The problem appears to occur when the application tries to load the old job status entries from disk. The errors would indicate a possible corruption.

The job status logs are stored in the /var/lib/acapella/.Acapella directory

To help resolve the problem we would advise that you first make a backup copy of the /.Acapella directory by renaming it. There is no critical data stored in that directory but the job status files may need to be conserved for future reference.

Once it has been renamed the /.Acapella directory will be re-created dynamically.

Now check the status of the Acapella service:

$ sudo /etc/init.d/columbus status

If the Acc service is still shown as 'WARNING' please try to restart the Columbus services:

$ sudo /etc/init.d/columbus restart

and then check the status again:

$ sudo /etc/init.d/columbus status

If all services including the Acc component are shown as 'OK' then please try to login to the Columbus server via the web UI again.

There might be a number of reasons why you are unable to login to Columbus, so if in doubt please contact signals.support@revvity.com for assistance.