- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
07-24-2024 05:42 PM
After updating to version 1.2.93 every 30/40 minutes I lose access to the GUI, CLI, and even the ping doesn't work.
It keeps giving the wrong login and password error and only works again after rebooting the vm.
Is there a way to install 1.2.92 or another previous version? Or fix this one?
07-25-2024 03:38 AM
Hi @KlausNunes
I'm sorry to hear that.
To revert to any other Expedition version you can follow the manual steps defined on each Hot Fix announcement. In particular the steps to revert to 1.2.92 are:
cd /tmp;
wget https://conversionupdates.paloaltonetworks.com/expedition-updates/expedition_1.2.92.all.deb;
sudo dpkg -i expedition_1.2.92.all.deb;
On the other hand to fix the issue I will need more information. Could you provide me (fwmigrate@paloaltonetworks.com) with the /var/log/apache2/error.log and the specific times when the issue is happing on your environment. I will correlate the times with the log to check it. Also it will help to know more about the workflow you are executing to verify if the issue is related to any specific workflow.
Thanks in advance,
David
07-25-2024 12:03 AM
Ah, the classic tech tango—update blues! Let’s troubleshoot this and get your VM back on its feet. 🕺💻
1. Reverting to a Previous Version:
While directly installing version 1.2.92 might not be straightforward, you can consider rolling back to your previous working version.
If you’re using Windows, you can do this for Windows updates, but for your specific software (like VM), it depends on whether you have a backup or snapshot of the previous state.
Here’s how to revert Windows updates: Go to Settings > Update & Security > Recovery > Get Started under “Go back to the previous version of Windows 10.” Note that this option is available for 10 days after the update1.
2. Backup and Check for Updates:
Before making any changes, back up your important data. It’s like putting on a seatbelt before a rollercoaster ride.
Sometimes checking for new updates can resolve issues without needing a rollback. It’s like giving your VM a software spa day.
3. Note Your Settings:
Write down any custom settings you’ve configured. Sometimes they don’t carry over after a rollback, like forgetting your favorite coffee order at a new café.
4. Ensure Battery Life and Internet Connection:
If you’re on a laptop, make sure it’s plugged in or has enough battery life to complete the process.
Stable internet connection is essential in case additional files need to be downloaded during the rollback.
07-25-2024 03:38 AM
Hi @KlausNunes
I'm sorry to hear that.
To revert to any other Expedition version you can follow the manual steps defined on each Hot Fix announcement. In particular the steps to revert to 1.2.92 are:
cd /tmp;
wget https://conversionupdates.paloaltonetworks.com/expedition-updates/expedition_1.2.92.all.deb;
sudo dpkg -i expedition_1.2.92.all.deb;
On the other hand to fix the issue I will need more information. Could you provide me (fwmigrate@paloaltonetworks.com) with the /var/log/apache2/error.log and the specific times when the issue is happing on your environment. I will correlate the times with the log to check it. Also it will help to know more about the workflow you are executing to verify if the issue is related to any specific workflow.
Thanks in advance,
David
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!