Errors with Jobs after upgrading from 1.8 to 2.0

Archives AWX Project
1

This weekend I upgraded from 1.8 to 2.0, now any job that is ran I am getting the following error…

Call to /api/v2/jobs/74/relaunch/ failed. returned status: 500. A server error has occurred.

Has anyone seen this error?

2

Chuck,

Upgrading from 1.8 to 2.0 will more than likely not work. Our new adoption of semantic versioning conveys this.

3

Ok, it appears it isn’t the upgrade, but rabbitmq isn’t starting any more, and I cant’s seem to get to start up.

Rebbit isn’t starting anymore

[root@awx ~]# systemctl start rabbitmq-server
Job for rabbitmq-server.service failed because the control process exited with error code. See “systemctl status rabbitmq-server.service” and “journalctl -xe” for details.
[root@awx ~]# systemctl status rabbitmq-server
● rabbitmq-server.service - RabbitMQ broker
Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2018-10-09 14:11:42 EDT; 2s ago
Process: 5421 ExecStop=/usr/sbin/rabbitmqctl shutdown (code=exited, status=69)
Process: 5214 ExecStart=/usr/sbin/rabbitmq-server (code=exited, status=1/FAILURE)
Main PID: 5214 (code=exited, status=1/FAILURE)

Oct 09 14:11:42 awx.magidesign.com systemd[1]: Failed to start RabbitMQ broker.
Oct 09 14:11:42 awx.magidesign.com systemd[1]: Unit rabbitmq-server.service entered failed state.
Oct 09 14:11:42 awx.magidesign.com systemd[1]: rabbitmq-server.service failed.