PA Expedition PAN Order Agent is stopped ( Remediation: Start the agent )

[MohamedAbbas]

Hello Team  , after installing PA Expedition release VM 1.1.91.1 , i have faced an issue related to internal checks ( Verify the PanOrders agent is running to accept background jobs ) , both start/restart button didnt work , do you have any opinion to fix this please , 

in addition to , im trying to add devices , please retreive configuration function status is downloading but there is no real files to download , as i think its related to PANorder agent primary issue

Thanks for your feedback and support 

@ links to members

[lychiang]

@MohamedAbbas Try to reboot the VM and check if there is any error logs in /tmp/panReadOrders.log

[MohamedAbbas]

rebooted , but i didn't see any log issues appear 

any other opinion please ?

[lychiang]

Please check the rabbitmq status by following below article:

https://live.paloaltonetworks.com/t5/expedition-discussions/rabbitmq-not-properly-starting-failing/t...

[MohamedAbbas]

Yes , that right issue appear for rabbitmq-server status >>have failed to start RabbitMQ Messaging server 

but after stop the services >> Could you please clarify more details info for this step please ,, how can >>>A separate folder was created and we moved the files from ( var/lib/rabbitmq/ ) into that temporary folder after the service was stopped.>>>

[MohamedAbbas]

after run >> sudo service rabbitmq-server start

an issue appear as below :

Job for Rabbitmq-server.service failed becuase the control process exited with error code , see system status rabbitmq-server.service and journalctl -xe for details 

[lychiang]

Try $sudo service rabbitmq-server stop first , then $sudo service rabbitmq-server start

[MohamedAbbas]

still the same issue appear , rabbitmq didnt work

[lychiang · Accepted solution]

First to stop the services:

$sudo service mysql stop

$sudo service rabbitmq-server stop

To create a sepearte folder , you use "mkdir" command , for example :

cd /var/lib/

sudo mkdir /temp

sudo mv /var/lib/rabbitmq/* /var/lib/temp

Then 

sudo service mysql start

sudo service rabbitmq-server start

[MohamedAbbas]

Thanks alot Solved 

[Usama-Ahmed]

Thanks, this worked for me too. Saved a lot of time. 

[SathyaK]

Tried those steps and it didn't help.  Please advise.  Expedition Version: 1.2.58.

expedition@expedition2023:~$ sudo service mysql start

[sudo] password for expedition:

expedition@expedition2023:~$ sudo service rabbitmq-server start

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.

expedition@expedition2023:~$ systemctl status rabbitmq-server.service

• rabbitmq-server.service - RabbitMQ Messaging Server

     Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled)

     Active: activating (auto-restart) (Result: exit-code) since Mon 2023-04-24 13:26:11 UTC; 9s ago

    Process: 7825 ExecStart=/usr/sbin/rabbitmq-server (code=exited, status=1/FAILURE)

   Main PID: 7825 (code=exited, status=1/FAILURE)

expedition@expedition2023:~$ journalctl -xe

Apr 24 13:26:16 expedition2023 multipathd[739]: sda: add missing path

Apr 24 13:26:16 expedition2023 multipathd[739]: sda: failed to get udev uid: Invalid argument

Apr 24 13:26:16 expedition2023 multipathd[739]: sda: failed to get sysfs uid: Invalid argument

Apr 24 13:26:16 expedition2023 multipathd[739]: sda: failed to get sgio uid: No such file or directory

Apr 24 13:26:21 expedition2023 multipathd[739]: sda: add missing path

Apr 24 13:26:21 expedition2023 multipathd[739]: sda: failed to get udev uid: Invalid argument

Apr 24 13:26:21 expedition2023 multipathd[739]: sda: failed to get sysfs uid: Invalid argument

Apr 24 13:26:21 expedition2023 multipathd[739]: sda: failed to get sgio uid: No such file or directory

Apr 24 13:26:21 expedition2023 systemd[1]: rabbitmq-server.service: Scheduled restart job, restart counter is at 19.

-- Subject: Automatic restarting of a unit has been scheduled

-- Defined-By: systemd

-- Support: http://www.ubuntu.com/support

--

-- Automatic restarting of the unit rabbitmq-server.service has been scheduled, as the result for

-- the configured Restart= setting for the unit.

Apr 24 13:26:21 expedition2023 systemd[1]: Stopped RabbitMQ Messaging Server.

-- Subject: A stop job for unit rabbitmq-server.service has finished

-- Defined-By: systemd

-- Support: http://www.ubuntu.com/support

--

-- A stop job for unit rabbitmq-server.service has finished.

--

-- The job identifier is 2180 and the job result is done.

Apr 24 13:26:21 expedition2023 systemd[1]: Starting RabbitMQ Messaging Server...

-- Subject: A start job for unit rabbitmq-server.service has begun execution

-- Defined-By: systemd

-- Support: http://www.ubuntu.com/support

--

-- A start job for unit rabbitmq-server.service has begun execution.

--

-- The job identifier is 2180.

Apr 24 13:26:24 expedition2023 systemd-timesyncd[785]: Timed out waiting for reply from 185.125.190.58:123 (ntp.ubuntu.com).

Apr 24 13:26:25 expedition2023 systemd[1]: rabbitmq-server.service: Main process exited, code=exited, status=1/FAILURE

-- Subject: Unit process exited

-- Defined-By: systemd

-- Support: http://www.ubuntu.com/support

--

-- An ExecStart= process belonging to unit rabbitmq-server.service has exited.

--

-- The process' exit code is 'exited' and its exit status is 1.

Apr 24 13:26:25 expedition2023 systemd[1]: rabbitmq-server.service: Failed with result 'exit-code'.

-- Subject: Unit failed

-- Defined-By: systemd

-- Support: http://www.ubuntu.com/support

--

-- The unit rabbitmq-server.service has entered the 'failed' state with result 'exit-code'.

Apr 24 13:26:25 expedition2023 systemd[1]: Failed to start RabbitMQ Messaging Server.

-- Subject: A start job for unit rabbitmq-server.service has failed

-- Defined-By: systemd

-- Support: http://www.ubuntu.com/support

--

-- A start job for unit rabbitmq-server.service has finished with a failure.

--

-- The job identifier is 2180 and the job result is failed.

Apr 24 13:26:26 expedition2023 multipathd[739]: sda: add missing path

Apr 24 13:26:26 expedition2023 multipathd[739]: sda: failed to get udev uid: Invalid argument

Apr 24 13:26:26 expedition2023 multipathd[739]: sda: failed to get sysfs uid: Invalid argument

Apr 24 13:26:26 expedition2023 multipathd[739]: sda: failed to get sgio uid: No such file or directory

Apr 24 13:26:31 expedition2023 multipathd[739]: sda: add missing path

Apr 24 13:26:31 expedition2023 multipathd[739]: sda: failed to get udev uid: Invalid argument

Apr 24 13:26:31 expedition2023 multipathd[739]: sda: failed to get sysfs uid: Invalid argument

Apr 24 13:26:31 expedition2023 multipathd[739]: sda: failed to get sgio uid: No such file or directory