Articles in this section

Self Packager 1.4 Installation, Upgrade, And troubleshooting

Installation

Note: The Self-Packager works best in Chrome.

Firewall Pre-req: Verify that port 80 is open for incoming connections in the firewall\iptables 

 

Linux Installation

Linux machines must have libX11 package installed to run the server.

Download here

Run Server as a Service

  1. Extract the content of intigua_pack_server-Release-<VERSION>.tar.gz to the End-Point machine
  2. Add run permission to each file (chmod +x <FILE>)
  3. ./installSelfpack.sh
  4. service selfpack start
  5. After that just use go to http://localhost (from the same machine) or http://[ip-of-the-machine] (from outside the machine) 
  6. Once you verified it is working, please deploy the JetPatch connector on this machine, which is required to properly build VAI files.

Windows Installation

Download here

Run Server as a Service

  • Install intigua_pack_server-Release-<VERSION>.msi as an administrator
  • There is no installation progress GUI, so once you run the msi file, the service will start and always run the background
  • After that go to http://localhost (from the same machine) or http://[ip-of-the-machine] (from outside the machine) 
  • Once you verified it is working, please deploy the JetPatch connector on this machine, which is required to properly build VAI files.

On x64 Windows machines: When installing SelfPackager using the MSI, the library folder of the packages will be under Program Files (x86).

 

Upgrades

Linux Upgrade

Current Installation: Run Server by Command Installation

  1. Verify that the Self Packager is not running.
  2. Install the new Self Packager.

 

Current Installation: Run Server as a Service

  1. Stop the Self Packager service (selfpack).
  2. Install the new Self Packager.

 

Windows Upgrade

Current Installation: Run Server by Command Installation

  1. Verify that the Self Packager is not running.
  2. Install the new Self Packager MSI.
  3. Copy the library folder from user folder (eg. C:\\Users\Administrator\library) into Self Packager installation folder under Program File / Program File (x86).

Current Installation: Run Server as a Service

  1. Uninstall the MSI through Program and Features.
  2. Install the new Self Packager MSI.

Troubleshooting During Installation and Upgrade

 
Old Selfpack service preventing upgrade:
 
Sometimes during an upgrade, the old selfpack service is running, and it interferes the new  installation. To solve this, before running the ./installSelfpack.sh try and disable the selfpack service. 
Try this:
systemctl stop selfpack
./installSelfpack.sh
systemctl start selfpack
Please run these in the command line before attempting to upgrade to a new version.

 

Insserv

The warning messages of insserv can appear during a conflict between the install command "update-rc.d selfpack defaults" and other scripts you may have running. 

To remediate this, you can run a sudo command like "sudo nano /etc/scriptx.sh" and add LSB tags at the beginning of the file. 

### BEGIN INIT INFO
# Provides: scriptx
# Required-Start:
# Required-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: 1 0 6
# Short-Description: ...
# Description: ...
### END INIT INFO

 

Any Other Issue

If any issues persist during installation or upgrade, please procure the web service logs from the machine running the self packager. 

Windows

\Program Files (x86)\SelfPackager\intigua-packager-log

Linux:

/opt/rest/intigua-packager-log

Related articles

Comments

2 comments

Date Votes

Please sign in to leave a comment.