ATTENTION Customers, All Partners and Employees: The Customer Support Portal (CSP) will be undergoing maintenance and unavailable on Saturday, November 7, 2020, from 11 am to 11 pm PST. Please read our blog for more information.
Permissions depend on which directory you use for machine learning and which one for logs. In case they are the same, you would have to change the permissions every time you try to process or SCP. If not then you can make a group and make the group the owner of the directory.
In order to make them able to just SCP you would run which in turn would make expedition the owner instead of the www-data which is used to process them
sudo chown -R expedition:expedition PALogs/
If you update to the latest version of Expedition 1.0.98, you will get more information regarding the logs that you are attempting to process.
Things that may occur:
How does on upgrade to the latest version? I've tried the apt-get update and apt-get expedition beta cmd's and I keep getting the "1.0.8x " is the latest version. I've tried the unauthenticated -o commands as well, and still can't get the OS to recognize that the install is old. Any suggestions on upgrading/where to find the latest hotfixes/installs for this?
be sure your Expedition has DNS and default gateway correctly configured, or in case you need to use a proxy check the proxy is correctly configured.
If a Palo Alto Networks firewall is before your Internet connection make sure paloalto-updates app-id is allowed to your expedition instance.
If you have dns and default gateway and you can reach internet and paloalto-updates is allowed and still has problems please send us an email to fwmigrate at paloaltonetworks dot com to arrange a zoom session with us.
Thanks to Albert, we have a fix. Modify the file /etc/mysql/my.cnf and comment out the line that binds the localhost address to mysql:
bind-address = 127.0.0.1. --->? #bind-address = 127.0.0.1.
In my case I changed the owner so I could SCP the firewall logs to Expedition as I was getting a permissions failure. All worked as expected and I can see the file on Expedition in the PALogs directory from my SSH shell.
However the file is never visible via the web interface so it cannot be processed.
I updated Expedition to the latest release but when I do this I get a reconnect mysql error even after editing the file to change reconnect to ON (see https://live.paloaltonetworks.com/t5/Expedition-Articles/Modifying-mysqli-reconnect-value/ta-p/21922... Still do not see the file in the web interface.
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 Live Community as a whole!
The Live Community thanks you for your participation!