Expedition csv logs stuck in pending

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Expedition csv logs stuck in pending

L1 Bithead

Hi everyone,

I have added firewall logs from our Palo Alto 5000 series to the Expedition VM /PALogs . I have copied the orginal .csv as a duplicate with root as the owner and the original with expedition as the owner. Both files appear in Devices > M.LEARNING. When I run Process Files the job remains in pending and nothing happens. Any ideas what the issue may be?

Screen Shot 2018-06-26 at 10.35.44 AM.png
Screen Shot 2018-06-26 at 10.37.27 AM.pngScreen Shot 2018-06-26 at 10.36.50 AM.png




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/ 

L1 Bithead

Does anyone have any suggestions? I'm still unable to process the firewall logs and would really like to get this working.


send me an email to fwmigrate at paloaltonetworks dot com and we can do a Zoom session


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:

  1. The log is incorrectly formated
    • This log won't be able to be pre-processed
  2. The log is not supported (PANOS version below 7.1)
    • This log won't be able to be pre-processed
  3. The path for MLearning (Main Screen -> Settings -> M.Learning -> Temporary data structure folder PATH) is not a valid path or www-data does not have rights to reaching it and writing inside. Also, this should have been alerted in them main Dashboard HeathChecks
    • We can't pre-process any logs, as we can't write into a folder to store the pre-processing results
  4. The logs are way too big for the resources we have provided to Expedition. We should see an error in the file /tmp/error_logCoCo
    • We need to increase the Expedition resources, by adding more RAM and/or CPUs and deleting the file located at /home/userSpace/environmentParameters.php. (This may be optimized in the future to assist on the correct Expedition's resource tunning)
  5. The GUI offers you a link to http://<ip>:4050 and this link directs us to a web site that shows some task progress. 
    • All is fine. We need to let it continue until it completes, or fails as in case 4




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.

got it....it was a firewall issue.  Thank you Alestevez.

L1 Bithead

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           =    --->?     #bind-address           =


restart services.



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.


Any ideas?

the matching of the log files to a device is based on the serial number. Can you open the log file you uploaded and verify the serial number in the traffic logs matches the serial number of the device? If the device is a firewall learned via panorama you will need to add the M.LEARNING config directly to the firewall and not to Panorama.
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!