Each new server requires a manual initial install of Patchman. The assumed base directory is
/home/nevrax, using the
nevrax user that was created during the server preparation.
admin_install\patchman, edit the
patchman_list. Add an additional line containing the domain followed by the server hostname. You can have multiple domains on a single box, if necessary. The following example will run the patchman configuration
patchman_service.open.cfg on hostname
// domain hostname open demo open open
If your new host is responsible for serving patches, then
special_patchman_list should be updated as well. This example will run the
patchman_service.open_spm.cfg services on hostname
open, a VM for administration utilities, which happens to have the domain name as hostname for convenience.
// domain_service hostname open_spm open open_bridge open
If you haven't prepared any of the
admin_install\patchmanyet, simply copy them from their respective templates, and update the hostnames to point to the server that will serve the patches.
TODO: Replace this process with just one CSV file
open,open,spm, etc.), and a Python script that generates all the cfg files for the current host upon admin launch, and returns the list to the existing shell script, so no cfg files have to be made manually.
On the Windows build box, run the following build pipeline command.
This will create or update the
admin_install.tgz archive under
/home/nevrax and edit the hostname in the config file to match the hostname of the server (e.g.,
demo, not the FQDN).
/home/nevrax on the server box and extract it there.
tar zxvf admin_install.tgz
Chmod the contents of
/home/nevrax/patchman to be executable.
chmod -R +x bin chmod -R +x patchman
/home/nevrax/bin and run
./startup. This will launch the Patchman services as configured for this server box.
cd bin ./startup
Patchman services store their configuration data under
/home/nevrax/[domain]_spm, depending on the configuration.
The Patchman services can be stopped using
You can use
screen -r to monitor the Patchman services manually.
While you haven't added the server to the server park configuration yet, you may see the debug message
getHost failed for hostName.
If this issue persists, ensure you've correctly setup the DNS lookup of your servers.