topic Github Pan-configurator tool in General Topics

Github Pan-configurator tool

clyde.franklin — Wed, 01 Feb 2017 04:22:56 GMT

Trying to install and use Pan-migrator what does below mean and how does one resolve it

C:\Users\frankcl\Downloads\dev\dev\pan-configurator>git pull origin master
fatal: unable to access 'https://github.com/cpainchaud/pan-configurator.git/': Could not resolve host: github.com
C:\Users\frankcl\Downloads\dev\dev\pan-configurator>pause
Press any key to continue . . .
 
 
~>php rule-edit listActions
Could not open input file: rule-edit

Re: Github Pan-configurator tool

BPry — Wed, 01 Feb 2017 14:44:14 GMT

It looks like you are trying to use PAN-Configurator instead of the PAN Migration tool. The initial error that you are seeing is that it can't seem to resolve to github which would be something that needs to be fixed depending on where/how you are installing.

I would really recommend NOT installing pan-configurator on Windows if you have access to a linux box to install it on.

Re: Github Pan-configurator tool

clyde.franklin — Wed, 01 Feb 2017 15:44:30 GMT

ok letI will give it a try and advise

Re: Github Pan-configurator tool

clyde.franklin — Wed, 01 Feb 2017 18:59:12 GMT

Sure the Linux method will work but since Im getting below fatal error maybe its a proxy on my side preventing it from working:

bash-3.2$ php -r "require('lib/panconfigurator.php');print \"all\n\";"
PHP Warning: require(lib/panconfigurator.php): failed to open stream: No such file or directory in Command line code on line 1
PHP Fatal error: require(): Failed opening required 'lib/panconfigurator.php'

Re: Github Pan-configurator tool

BPry — Wed, 01 Feb 2017 19:42:01 GMT

The lib/panconfigurator.php is one of the libarary file sources, If you are not able to open that file then pan-configurator is always going to fail to load correctly. @cpainchaud would be able to help you more than I can.

Re: Github Pan-configurator tool

cpainchaud — Thu, 02 Feb 2017 19:26:53 GMT

thx for helpng @BPry .

@clyde.franklin managed to fix it : he didnt input the right path in /etc/php.ini.

It'snow resolved 🙂