Rabbitmq install failing in Expedition

[John.Schmitz]

Running Expedition 1.1.91.3, PanOrdres agent is hung and won't restart. I've cleaned up disk space and completed a reboot, still same issue. Looking through documentation others had similar issue, I removed the rabbitmq service:

apt-get remove rabbitmq-server && apt-get purge rabbitmq-server - this successfully removed rabbitmq

when I try to reinstall using:

sudo apt-get install rabbitmq-server

I get the following error - 

root@Expedition:/home/expedition# apt-get install rabbitmq-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
rabbitmq-server
0 upgraded, 1 newly installed, 0 to remove and 123 not upgraded.
Need to get 5,025 kB of archives.
After this operation, 5,830 kB of additional disk space will be used.
Err:1 http://www.rabbitmq.com/debian testing/main i386 rabbitmq-server all 3.6.1
404 OK
Err:1 https://www.rabbitmq.com/debian testing/main i386 rabbitmq-server all 3.6.
404 OK
E: Failed to fetch https://www.rabbitmq.com/debian/pool/main/r/rabbitmq-server/r

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-mis

Any help is greatly appreciated.

John

[azuniga]

Hello @John.Schmitz 

Please verify your proxy settings, you might be blocking access.

[MNagel]

It is not a proxy issue.  The repo is incorrect since it seems to have changed after the install script was released (at least since I installed). I brought that up a ways back but never saw any followup. See https://www.rabbitmq.com/install-debian.html for actual repo information.  I have been hesitant to make this change locally since it is not clear if it will cause breakage.

[micharr]

I just wanted to comment for visibility to MNagel's post. Everything on the web indicates that the RabbitMQ repository has changed and apparently there is a whole different way of pointing to it. I have a VERY basic knowledge of Linux so even reading the web search results, the Linux script configuration goes over my head and comfort level.

I know Expedition is best effort from PA, but we really need them to redo the original script or create another one we can run afterwards that would correct the RabbitMQ sequence.

[lychiang]

Hi @micharr We have updated the installation script few weeks ago , and we have verified if it's brand new installation , it did not have any issues, could you try to re-install a brand new ubuntu server on 20.04.5 and ran the installation script . 

[micharr]

Sorry but I simply do not have the time to do this. I am super busy with customers and my existing Expedition VM is working good enough that I cannot risk breaking it.

Also, you did not include a link to where the new script was or where the install instructions were. That would be helpful. I will try and do this when I can but it will be a month or two.

[micharr]

If you go to the link I am going to include, I found that PA included a sequence that carves out a fix for the Erlang and rabbitmq services without having to do an entirely new Ubuntu/Expedition install on a new VM. I was able to keep my existing deployment while getting the rabbitmq service to properly point to the new repository which fixed the PanOrders Agent which kept freezing. Hope this works for you.  

https://live.paloaltonetworks.com/t5/expedition-articles/how-to-address-cve-2022-37026-vulnerability...