expedition installer fails, browsing to ip address gives me default ubuntu apache

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

expedition installer fails, browsing to ip address gives me default ubuntu apache

L2 Linker

Hello. 

for an on the go migration I was installing expedition on a vmware player setup on my pc. 

I followed the pdf guide, and when that failed even followed the video step by step. 

 

however I can't get expedition to work. 
I installed a ubuntu 16.04 server. 

I can access internet and even download the expedtion file with wget. 

I run the installer and all seems to go well. 

 

execpt: somewheren in te middle it claims not to be able to find expedtion beta. 

at the end I get a failed to start (see image)

can't start.PNG

 

when I browse to my vm machine I load teh default ubuntu apache page..

I'm not at all a unix expert and haven't done much unix setups recently. so I'm kind of at a loss what's failing, and why. .

37 REPLIES 37

I'm guessing that's ok.

Still not resolved though:

 

@expedition-ubuntu:~$ sudo apt-get update

Hit:1 http://be.archive.ubuntu.com/ubuntu xenial InRelease

Hit:2 http://be.archive.ubuntu.com/ubuntu xenial-updates InRelease                        

Hit:3 http://ppa.launchpad.net/adiscon/v8-stable/ubuntu xenial InRelease                  

Hit:5 http://be.archive.ubuntu.com/ubuntu xenial-backports InRelease                      

Hit:6 http://security.ubuntu.com/ubuntu xenial-security InRelease   

Hit:7 http://sgp1.mirrors.digitalocean.com/mariadb/repo/10.1/ubuntu xenial InRelease

Hit:4 https://www.rabbitmq.com/debian testing InRelease             

Ign:8 https://conversionupdates.paloaltonetworks.com expedition-updates/ InRelease

Ign:9 https://conversionupdates.paloaltonetworks.com expedition-updates/ Release

Ign:10 https://conversionupdates.paloaltonetworks.com expedition-updates/ Packages.diff/Index

Ign:11 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en

Ign:12 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en_GB

Ign:13 https://conversionupdates.paloaltonetworks.com expedition-updates/ Packages

Ign:11 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en

Ign:12 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en_GB

Ign:13 https://conversionupdates.paloaltonetworks.com expedition-updates/ Packages

Ign:11 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en

Ign:12 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en_GB

Ign:13 https://conversionupdates.paloaltonetworks.com expedition-updates/ Packages

Ign:11 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en

Ign:12 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en_GB

Hit:13 https://conversionupdates.paloaltonetworks.com expedition-updates/ Packages

Ign:11 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en

Ign:12 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en_GB

Ign:11 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en

Ign:12 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en_GB

Reading package lists... Done

W: The repository 'https://conversionupdates.paloaltonetworks.com expedition-updates/ Release' does not have a Release file.

N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.

N: See apt-secure(8) manpage for repository creation and user configuration details.

The space is required to define the repositories and the sections within the repositories.

The update will normally complain about not having the Release file.

 

Afterwards, you should be able to call the

apt-get install expedition-beta 

Now that you have the repository in your list, and you have updated the list of packages offered by our repository, the expedition-beta package should be able to be found.

It did complain about the release files:

expedition-ubuntu:~$ sudo apt-get update

Hit:1 http://ppa.launchpad.net/adiscon/v8-stable/ubuntu xenial InRelease

Hit:2 http://be.archive.ubuntu.com/ubuntu xenial InRelease                                                                                                                        

Hit:3 http://be.archive.ubuntu.com/ubuntu xenial-updates InRelease                                                                                

Hit:5 http://be.archive.ubuntu.com/ubuntu xenial-backports InRelease                                                                              

Hit:6 http://sgp1.mirrors.digitalocean.com/mariadb/repo/10.1/ubuntu xenial InRelease                                        

Hit:7 http://security.ubuntu.com/ubuntu xenial-security InRelease                                                           

Hit:4 https://www.rabbitmq.com/debian testing InRelease

Ign:8 https://conversionupdates.paloaltonetworks.com expedition-updates/ InRelease

Ign:9 https://conversionupdates.paloaltonetworks.com expedition-updates/ Release

Ign:10 https://conversionupdates.paloaltonetworks.com expedition-updates/ Packages.diff/Index

Ign:11 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en

Ign:12 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en_GB

Ign:13 https://conversionupdates.paloaltonetworks.com expedition-updates/ Packages

Ign:11 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en

Ign:12 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en_GB

Ign:13 https://conversionupdates.paloaltonetworks.com expedition-updates/ Packages

Ign:11 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en

Ign:12 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en_GB

Ign:13 https://conversionupdates.paloaltonetworks.com expedition-updates/ Packages

Ign:11 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en

Ign:12 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en_GB

Hit:13 https://conversionupdates.paloaltonetworks.com expedition-updates/ Packages

Ign:11 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en

Ign:12 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en_GB

Ign:11 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en

Ign:12 https://conversionupdates.paloaltonetworks.com expedition-updates/ Translation-en_GB

Reading package lists... Done

W: The repository 'https://conversionupdates.paloaltonetworks.com expedition-updates/ Release' does not have a Release file.

N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.

N: See apt-secure(8) manpage for repository creation and user configuration details.

 

If I try to install expedition-beta:

@expedition-ubuntu:~$ sudo apt-get install expedition-beta

Reading package lists... Done

Building dependency tree       

Reading state information... Done

E: Unable to locate package expedition-beta

 

expedition-ubuntu:~$ cat /etc/apt/sources.list.d/ex-repo.list

deb https://conversionupdates.paloaltonetworks.com/ expedition-updates/

 

Still stuck at this

The update will normally complain about not having the Release file. This is normal.

 

Are you using GP in your connection? The resolution to conversionupdates.paloaltonetworks.com does not resolve as it would from ouside our Palo Alto Networks infrastructure.

If it still fails, contact us to fwmigrate at paloaltonetworks dot com to set up a session to troubleshoot.

 

Hi,

 

GP is not active.

It resolves correctly I think:

@expedition-ubuntu:~$ dig conversionupdates.paloaltonetworks.com

 

; <<>> DiG 9.10.3-P4-Ubuntu <<>> conversionupdates.paloaltonetworks.com

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46632

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

 

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 4096

;; QUESTION SECTION:

;conversionupdates.paloaltonetworks.com. IN A

 

;; ANSWER SECTION:

conversionupdates.paloaltonetworks.com. 173 IN A 199.167.52.71

 

;; Query time: 0 msec

;; SERVER: 192.168.60.100#53(192.168.60.100)

;; WHEN: Tue Sep 10 12:14:44 CEST 2019

;; MSG SIZE  rcvd: 83

 

Sent an email as you suggested.

 

thanks

 

Hi,

 

I'm having the same issue installing expedition, displaying the Apache2 Ubuntu Default Page.  Did you manage to resolve this problem?

Hi,

 

Yes, I was able to do so. I had to install the correct version of the Ubuntu server (download from: http://releases.ubuntu.com/16.04/)

Pick version: http://releases.ubuntu.com/16.04/ubuntu-16.04.6-server-amd64.iso

And afterwards I could do a clean install. Didac, the person who develops this tool told me you had to use the AMD version:

Yes, it has been tested with AMD64 packages.

Several packages require 64bit computations.

Haven't had the issue since then.

 

Off course I don't know if you already did install the right version.

Perfect, got that working on the first go, thank you very much! 

sudo apt-get update

 finishes with this error:

Fetched 325 kB in 3s (36.0 kB/s)

Reading package lists...

Done

W: The repository ' cdrom 16.04.6 LTS _Xenial Xerus

Release i386 (20130226) xenial Release' does not have a Release file.

N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use .

N: See apt—secure(8) manpage for repository creation and user conf iguration detai Is.

W: The repository 'https://conuersionupdates.paloaltonetworks.com expedition—updates/ Release' does not have a Release file.

N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use .

N: See apt—secure(8) manpage for repository creation and user conf iguration detai Is.

E: Failed to fetch cdrom 16.04.6 LTS Xenia I Xerus - Release i386 (Z0130ZZ6)/distsz xenia l/ma in/binary—i386/Packages Please use apt—cdrom to make this CD—ROM recognized by APT. apt—get update cannot be used to add new CD—ROMs

E: Some index files failed to download. They have been ignored, or old ones used instead .

 

$ echo ' deb https://conversionupdates.paloaltonetworks.com/expedition-updates/' > etc/apt/sources.Iist.d/exp-repo.Iist

—bash: /etc/apt/sources.Iist.d/exp-repo.Iist: Permission denied

 

$ echo ' deb https://conversionupdates.paloaltonetworks.com/ expedition-updates/' > etc/apt/sources.Iist.d/exp-repo.Iist

—bash: /etc/apt/sources.Iist.d/exp-repo.Iist: Permission denied

 

$ cat /proc/version

Linux version 4.4.O—14Z—generic (gcc version 5.4.0 20160603 (Ubuntu 5.4.0—6

ubuntuE16.04.10) ) "168-Ubuntu SMP Wed Jan 16 21 UTC 2013

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!