The Refind Binary File Is Missing Aborting Installation Instructions A watermark TOLUD value is then set and locked in the system firmware. Windows OS honors the root bridge definition and will allocate PCIe devices within it.
The Refind Binary File Is Missing Aborting Installation Guide
rEFInd is a UEFIboot manager capable of launching EFISTUB kernels. It is a fork of the no-longer-maintained rEFIt and fixes many issues with respect to non-Mac UEFI booting. It is designed to be platform-neutral and to simplify booting multiple OSes.
Note: In the entire article
esp denotes the mountpoint of the EFI system partition aka ESP.
Installation
Install the refind package.
Installing the rEFInd Boot Manager
rEFInd ships with UEFI drivers that implement read-only support for ReiserFS, Ext2, Ext4, Btrfs, ISO-9660 and HFS+. Additionally rEFInd can access any file system that UEFI itself can, that includes FAT (as mandated by the UEFI specification), HFS+ on Macs and ISO-9660 on some systems.
To find additional drivers see The rEFInd Boot Manager: Using EFI Drivers: Finding Additional EFI Drivers.
To use the rEFInd, you must install it to the EFI system partition either using the refind-install script or by copying the files and setting up the boot entry manually.
Warning: Your kernel and initramfs must reside on a file system that rEFInd can read.
Installation with refind-install script
The rEFInd package includes the refind-install script to simplify the process of setting rEFInd as your default EFI boot entry. The script has several options for handling differing setups and UEFI implementations. See refind-install(8) or read the comments in the install script for explanations of the various installation options.
For many systems it should be sufficient to simply run:
This will attempt to find and mount your ESP, copy rEFInd files to
esp/EFI/refind/ , and use efibootmgr to make rEFInd the default EFI boot application.
Alternatively you can install rEFInd to the default/fallback boot path
esp/EFI/BOOT/bootx64.efi . This is helpful for bootable USB flash drives or on systems that have issues with the NVRAM changes made by efibootmgr:
Where
/dev/sdXY is your EFI system partition (the block device, not its mountpoint).
Tip: By default
refind-install installs only the driver for the file system on which kernel resides. Additional file systems need to be installed manually by copying them from /usr/share/refind/drivers_x64/ to esp/EFI/refind/drivers_x64/ , or you can install all drivers with the --alldrivers option. This is useful for bootable USB flash drives.
After installing rEFInd's files to the ESP, verify that rEFInd has created
refind_linux.conf containing kernel parameters in the same directory as your kernel. Then this will not be created if you used the --usedefault option, run mkrlconf as root to create it.
Warning: When
refind-install is run in chroot (e.g. in live system when installing Arch Linux) /boot/refind_linux.conf is populated with kernel options from the live system not the one on which it is installed. Edit /boot/refind_linux.conf and make sure the kernel parameters in it are correct for your system, otherwise you could get a kernel panic on your next boot. See #refind_linux.conf for an example file.
By default, rEFInd will scan all of your drives (that it has drivers for) and add a boot entry for each EFI bootloader it finds, which should include your kernel (since Arch enables EFISTUB by default). So you may have a bootable system at this point.
Secure Boot
See Managing Secure Boot for Secure Boot support in rEFInd.
Using PreLoader
See Secure Boot#Set up PreLoader to acquire signed
PreLoader.efi and HashTool.efi binaries.
Execute
refind-install with the option --preloader /path/to/preloader
Next time you boot with Secure Boot enabled, HashTool will launch and you will need to enroll the hash of rEFInd (
loader.efi ), rEFInd's drivers (e.g. ext4_x64.efi ) and kernel (e.g. vmlinuz-linux ).
See refind-install(8) for more information.
Tip: The signed HashTool is only capable of accessing the partition it was launched from. This means if your kernel is not on the ESP, you will not be able to enroll its hash from HashTool. You can workaround this by using #KeyTool, since it is capable of enrolling a hash in MokList and is not limited to one partition. Remember to enroll KeyTool's hash before using it.
Using shim
Installshim-signedAUR. Read Secure Boot#shim, but skip all file copying.
Using hashes
To use only hashes with shim, execute
refind-install with the option --shim /path/to/shim
Next time you boot with Secure Boot enabled, MokManager will launch and you will need to enroll the hash of rEFInd (
grubx64.efi ), rEFInd's drivers (e.g. ext4_x64.efi ) and kernel (e.g. vmlinuz-linux ).
Using Machine Owner Key
To sign rEFInd with a Machine Owner Key (MOK), install sbsigntools.
Tip: If you already have created a MOK, place the files in the directory
/etc/refind.d/keys with the names refind_local.key (PEM format private key), refind_local.crt (PEM format certificate) and refind_local.cer (DER format certificate).
Execute
refind-install with the options --shim /path/to/shim and --localkeys :
refind-install will create the keys for you and sign itself and its drivers. You will need to sign the kernel with the same key, e.g.:
Tip: The kernel signing can be automated with a pacman hook, see Secure Boot#Signing the kernel with a pacman hook.
Once in MokManager add
refind_local.cer to MoKList. refind_local.cer can be found inside a directory called keys in the rEFInd's installation directory, e.g. esp/EFI/refind/keys/refind_local.cer .
See refind-install(8) for more information.
Using your own keys
Follow Secure Boot#Using your own keys to create keys.
Create directory
/etc/refind.d/keys and place Signature Database (db) key and certificates in it. Name the files: refind_local.key (PEM format private key), refind_local.crt (PEM format certificate) and refind_local.cer (DER format certificate).
When running install script add option
--localkeys , e.g.:
rEFInd EFI binaries will be signed with the supplied key and certificate.
Manual installation
Tip: rEFInd can boot Linux in many ways. See The rEFInd Boot Manager: Methods of Booting Linux for coverage of the various approaches.
If the
refind-install script does not work for you, rEFInd can be set up manually.
First, copy the executable to the ESP:
If you want to install rEFInd to the default/fallback boot path replace
esp/EFI/refind/ with esp/EFI/BOOT/ in the following instructions and copy rEFInd EFI executable to esp/EFI/BOOT/bootx64.efi :
Then use efibootmgr to create a boot entry in the UEFI NVRAM, where
/dev/sdX and Y are the device and partition number of your EFI system partition. If you are installing rEFInd to the default/fallback boot path esp/EFI/BOOT/bootx64.efi , you can skip this step.
At this point, you should be able to reboot into rEFInd, but it will not be able to boot your kernel. If your kernel does not reside on your ESP, rEFInd can mount your partitions to find it - provided it has the right drivers.
rEFInd automatically loads all drivers from the subdirectories
drivers and drivers_arch (e.g. drivers_x64 ) in its install directory.
Now rEFInd should have a boot entry for your kernel, but it will not pass the correct kernel parameters. Set up #Passing kernel parameters. You should now be able to boot your kernel using rEFInd. If you are still unable to boot or if you want to tweak rEFInd's settings, many options can be changed with a configuration file:
The sample configuration file is well commented and self-explanatory.
Unless you have set
textonly in the configuration file, you should copy rEFInd's icons to get rid of the ugly placeholders:
You can try out different fonts by copying them and changing the
font setting in refind.conf :
Tip: Pressing
F10 in rEFInd will save a screenshot to the top level directory of the ESP.
Upgrading
Pacman updates the rEFInd files in
/usr/share/refind/ and will not copy new files to the ESP for you. If refind-install worked for your original installation of rEFInd, you can rerun it to copy the updated files. The new configuration file will be copied as refind.conf-sample so that you can integrate changes into your existing configuration file using a diff tool. If your rEFInd required #Manual installation, you will need to figure out which files to copy yourself.
Pacman hook
You can automate the update process using a pacman hook:
Where the
Exec= may need to be changed to the correct update command for your setup. If you did #Manual installation, you could create your own update script to call with the hook.
Tip: If you setup rEFInd with #Secure Boot, you may want to additionally add the option
--yes to the refind-install command. It will prevent the command from failing if it gets executed when Secure Boot is disabled. See refind-install(8) for more information.
Configuration
The rEFInd configuration
refind.conf is located in the same directory as the rEFInd EFI application (usually esp/EFI/refind or esp/EFI/BOOT ). The default configuration file contains extensive comments explaining all its options, see Configuring the Boot Manager for more detailed explanations.
Passing kernel parameters
There are two methods for setting the kernel parameters that rEFInd will pass to the kernel.
For kernels automatically detected by rEFInd
For automatically detected kernels you can either specify the kernel parameters explicitly in Tip:
/boot/refind_linux.conf or rely on rEFInd's ability to identify the root partition and kernel parameters. See Methods of Booting Linux: For Those With Foresight or Luck: The Easiest Method for more information.
For rEFInd to support the naming scheme of Arch Linux kernels and thus allow matching them with their respective initramfs images, you must uncomment and edit Note:
extra_kernel_version_strings option in refind.conf . E.g.:
refind_linux.conf
If rEFInd automatically detects your kernel, you can place a
refind_linux.conf file containing the kernel parameters in the same directory as your kernel. You can use /usr/share/refind/refind_linux.conf-sample as a starting point. The first uncommented line of refind_linux.conf will be the default parameters for the kernel. Subsequent lines will create entries in a submenu accessible using + , F2 , or Insert .
Alternatively, try running
mkrlconf as root. It will attempt to find your kernel in /boot and automatically generate refind_linux.conf . The script will only set up the most basic kernel parameters, so be sure to check the file it created for correctness.
If you do not specify an Warning:
initrd= parameter, rEFInd will automatically add it by searching for common RAM disk filenames in the same directory as the kernel. If you need multiple initrd= parameters, you must specify them manually in refind_linux.conf . For example, a microcode passed before the initramfs:
Note: rEFInd replaces
%v in refind_linux.conf with the kernel's version (by extracting if from the file name). For rEFInd to support Arch Linux kernels, the extra_kernel_version_strings in esp/EFI/refind/refind.conf must be edited as instructed in #For kernels automatically detected by rEFInd.
Without configuration
If you merely install rEFInd onto the ESP and launch it without any further ado (say via UEFI shell or KeyTool, or directly from firmware) you still get a menu to boot from via autodetection, with no configuration required whatsoever.
This works because rEFInd has a fallback mechanism that can:
Note: rEFInd does not support escape codes (e.g. for spaces) in
/etc/fstab .
Manual boot stanzas
If your kernel is not autodetected, or if you simply want more control over the options for a menu entry, you can manually create boot entries using stanzas in
refind.conf . Ensure that scanfor includes manual or these entries will not appear in rEFInd's menu. Kernel parameters are set with the options keyword. rEFInd will append the initrd= parameter using the file specified by the initrd keyword in the stanza. If you need additional initrds (e.g. for Microcode), you can specify them in options (and the one specified by the initrd keyword will be added to the end).
Manual boot stanzas are explained in Creating Manual Boot Stanzas.
It is likely that you will need to change Warning:
volume to match either a filesystem's LABEL, a PARTLABEL, or a PARTUUID of the partition where the kernel image resides. See Persistent block device naming#by-label for examples of assigning a volume label. If volume is not specified it defaults to volume from which rEFInd was launched (typically EFI system partition).
Installation alongside an existing UEFI Windows installation
Note: The usual caveats of Dual boot with Windows apply.
rEFInd is compatible with the EFI system partition created by a UEFI Windows installation, so there is no need to create or format another FAT32 partition when installing Arch alongside Windows. Simply mount the existing ESP and install rEFInd as usual. By default, rEFInd's autodetection feature should recognize any existing Windows/recovery bootloaders.
Note: In some cases, Windows behaves differently (low resolution boot screen, OEM logo replaced by Windows logo, black screen after boot screen, artifacting). If you face such issues, try setting
use_graphics_for +,windows in esp/EFI/refind/refind.conf or adding graphics on to the Windows boot stanza.
Tools
This article or section is a candidate for moving to Unified Extensible Firmware Interface.
Notes: Although rEFInd has a special interface for these common tools, they are not a feature of rEFInd. (Discuss in Talk:REFInd#template:move at refind#tools: to uefi)
rEFInd supports running various 3rd-party tools. Tools need to be installed separately. Edit
showtools in refind.conf to choose which ones to show.
UEFI shell
See Unified Extensible Firmware Interface#UEFI Shell.
Copy
shellx64.efi to the root of the EFI system partition.
Memtest86
Install memtest86-efiAUR and copy it to
esp/EFI/tools/ .
Key management tools
rEFInd can detect Secure Boot key management tools if they are placed in rEFInd's directory on ESP,
esp/ or esp/EFI/tools/ .
HashTool
Follow #Using PreLoader and
HashTool.efi will be placed in rEFInd's directory.
MokManager
Follow #Using shim and MokManager will be placed in rEFInd's directory.
KeyTool
Install efitools.
Place KeyTool EFI binary in
esp/ or esp/EFI/tools/ with the name KeyTool.efi or KeyTool-signed.efi .
See Secure Boot#Using KeyTool for instructions on signing
KeyTool.efi .
GPT fdisk (gdisk)
Download the gdisk EFI application and copy
gdisk_x64.efi to esp/EFI/tools/ .
![]() fwupdate
Install and setup fwupd.
Copy the
fwupx64.efi binary and firmware file to esp/EFI/tools/ :
Poweroff or reboot
rEFInd reportedly have poweroff and reboot menu entries built in. Since this list of tools is the most extensive of its kind in this wiki, users of UEFI shell, or other UEFI boot managers, such as systemd-boot, might be interested in powerofforreboot.efiAUR.
Tips and tricksUsing drivers in UEFI shell
This article or section is a candidate for moving to Unified Extensible Firmware Interface#UEFI drivers.
Notes: rEFInd's drivers are not the only ones that can be loaded. Move all generic information about UEFI drivers to one article. (Discuss in Talk:REFInd#)
To use rEFInd's drivers in UEFI shell load them using command
load and refresh mapped drives with map -r .
Now you can access your file system from UEFI shell.
Setting efifb resolution
If the resolution in
refind.conf is set to an incorrect value, on all systems except Apple Macs rEFInd will display a list of supported resolutions. For Apple Macs it will silently use the default resolution.
To determine framebuffer resolutions supported by efifb, copy
/usr/share/gnu-efi/apps/x86_64/modelist.efi from gnu-efi to the root of ESP. Enter the UEFI shell and run modelist.efi .
Set one in
refind.conf . Reboot and check if settings has been applied with dmesg | grep efifb .
Btrfs subvolume supportAuto detection
To allow kernel auto detection on a Btrfs subvolume uncomment and edit
also_scan_dirs in refind.conf .
Next add
subvol=subvolume to rootflags in refind_linux.conf and then prepend subvolume to the initrd path.
Manual boot stanza
If booting a btrfs subvolume as root, prepend the path to the subvolume to the loader and initrd paths, and amend the
options line with rootflags=subvol=root_subvolume . In the example below, root has been mounted as a btrfs subvolume called 'ROOT' (e.g. mount -o subvol=ROOT /dev/sdxY /mnt ):
A failure to do so will otherwise result in the following error message:
ERROR: Root device mounted successfully, but /sbin/init does not exist.
TroubleshootingApple Macs
mactel-bootAUR is an experimental bless utility for Linux. If that does not work, use bless from within OSX to set rEFInd as the default boot entry:
VirtualBox
VirtualBox before version 6.1 will only boot the default
esp/EFI/BOOT/bootx64.efi path, so refind-install needs to be used with at least the --usedefault option. See VirtualBox#Installation in EFI mode on VirtualBox < 6.1 for more information.
See also
Retrieved from 'https://wiki.archlinux.org/index.php?title=REFInd&oldid=621926'
Management server is made up of 4 main components:
These 4 components can be hosted on a single computer or on different computers to allow load balancing. Above 10000 inventoried computers, we recommend using at least 2 physical servers, one hosting database server + Communication server and the other one hosting a database replica + Administration server + Deployement server.
Figure 1 : OCS Inventory NG communication architecture.
Database server currently can only be MySQL 5.5 or MariaDB with InnoDB engine active.Communication server needs Apache Web Server 2.2.X / 2.4.X and is written in PERL as an Apache module. Why? Because PERL scripts are compiled when Apache starts, and not at each request. This is better performance-wise. Communication server may require some additional PERL modules, according to your distribution.Deployment server needs any Web Server with SSL enabled.Administration console is written in PHP 5.6 (or higher) and runs under Apache Web Server 2.2.X /2.4.X. Administration console requires ZIP and GD support enabled in PHP in order to use package deployment.
We provide RPM for RedHat Linux and derivate. Instructions can be find here: Install with RPM
We assume that you have:
Requirements
For the requirements, please follow the dedicated page :
Note: OCS Inventory NG Server Setup will check for all these components and will exitif any are missing.
Installing Communication server required PERL modules.
The web communication server requires Apache web server and Perl 5 scripting language and some additional modules for Perl 5(see Requirements).It acts as an Apache module which handles HTTP OCS Inventory agents' requests to a virtual directory /ocsinventory.Already the web communication server requires mysql dependencies if you choose to install the database server alone, you can reffer to this page :
Deploying Database Server
On Fedora/Redhat/Centos 7 like Linux
On Debian 9 Stretch like Linux
Warning: You must have root privileges to set required perl modules up.It is better for system integrity to use your distribution's precompiled packages when they are available.Some of these packages are only available in EPEL .
Note: On Fedore/Redhat/Centos 7 the package ' Apache DBI ' wasn't in the repo EPEL you can find the rpm here .
On Fedora/Redhat/Centos 7 like Linux, you can use âyumâ to set required modules up:
On Debian 9 Stretch like Linux, you can use âaptâ to set required modules up:
On Gentoo like Linux, you can use 'emerge' to get required modules set up:
Installing Administration console required PHP modules
The Web Administration console requires Apache web server and PHP 4 scripting language and some additional modulesfor PHP (see Requirements).Already the web communication server requires mysql dependencies if you choose to install the database server alone, you can refers to this page :
Deploying Database Server
On Fedora/Redhat/Centos 7 like Linux
On Debian 9 Stretch like Linux
install PHP Zip support and dependacies
On Fedora/Redhat/Centos 7 like Linux, you can use âyumâ to set it up:
For later Fedora installations 7.x+ :
On Debian 9 Stretch like Linux, you can use âaptâ to set it up:
You also need to install GD support for PHP.
On Fedora/Redhat/Centos 7 like Linux
On Debian 9 Stretch like Linux, you can use âaptâ to set it up:
Installing management server
You must have root privileges to set OCS Inventory Server up.
Note: Ensure MySQL InnoDB engine is activated on your database server.Open my.cnf and ensure there is no line âskip-innodbâ or this line is commented (begins with â#â).
Download latest version of server tarball âOCSNG_UNIX_SERVER-2.4.x.tar.gzâ from OCS Inventory Web Site.
Unpack it.
Run âsetup.shâ installer. During the installer, default choice is presented between [].For example, [y]/n means that âyâ (yes) is the default choice, and ânâ (no) is the other choice.
Note: Installer writes a log file âocs_server_setup.logâ in the same directory.If you encounter any error, please refer to this log for detailed error message.
Warning: If youâre upgrading from OCS Inventory NG 1.01 RC2 and previous,you must first remove any Apache configuration file for Communication server.
Do you wish to continue ([y]/n)?
Type 'y' or 'enter' to continue the installation
Which host is running database server [localhost] ?
Type âyâ or âenterâ to validate and, then enter MySQL server host address, in most cases localhost.
Then, setup checks for MySQL client binary files version 4.1 or higher. If not present, you will beprompted to continue or abort setup.
On which port is running database server [3306] ?
If all is OK, enter MySQL server port, generally 3306.
Where is Apache daemon binary [/usr/sbin/apache2ctl] ?
Enter or validate path to Apache daemon binary, generally â/usr/sbin/apache2ctlâ. It will be used to findApache configuration files.
Note: If youâre not using system Apache daemon, but another one like XAMPP/LAMPP Apache server,you must enter full path to your Apache daemon, not the system one.
Where is Apache main configuration file [/etc/apache2/apache2.conf] ?
Enter or validate Apache main configuration file path, generally â/etc/apache2/conf/apache2.confâor â/etc/httpd/conf/httpd.confâ.
Which user account is running Apache web server [www-data] ?
Enter or validate Apache daemon running user account, generally âapacheâ or âwwwâ (under Debian/Ubuntu is âwww-dataâ).
Which user group is running Apache web server [www-data] ?
Enter or validate Apache daemon user group, generally âapacheâ or âwwwâ (under Debian/Ubuntu is âwww-dataâ).
Where is PERL interpreter binary [/usr/bin/perl] ?
Next, setup checks for PERL interpreter binaries. Enter or validate path to PERL interpreter.
Note: If youâre not using system perl interpreter, but another one like XAMPP/LAMPP perl interpreter,you must specify full path to this perl interpreter, not the default system one(/opt/lampp/bin/perl generally used in XAMPP/LAMPP).
Do you wish to setup Communication server on this computer ([y]/n)?
Common information for setting up Communication server or Administration console is now collected.Setup prompts you if you wish to set Communication server up on this computer. Enter âyâ or validateto set Communication server up, ânâ to skip Communication server installation.
Setup will then try to find make utility. If it fails, setup will stop.
Setup will next try to determine your Apache mod_perl version. If it is not able to determine mod_perl version,it will ask you to enter it.
Note: You can check which version of mod_perl you are using by querying your server's software database.
Communication server can create detailed logs. This logs can be enabledby setting integer value of LOGLEVEL to 1 in Administration consolemenu Configuration.
Where to put Communication server log directory [/var/log/ocsinventory-server] ?
Communication server need a directory for plugins configuration files.
Where to put Communication server plugins configuration files [/etc/ocsinventory-server/plugins] ?
Communication server need a directory for plugins Perl modules files.
Where to put Communication server plugins Perl modules files [/etc/ocsinventory-server/perl] ?
Next, setup will check for required PERL modules(cf Requirements.):
Warning: If any of these modules is missing, setup will abort.
the setup will ask you if you want to install the rest API
Do you wish to setup Rest API server on this computer ([y]/n)?
asking you for where you want store API code
Where do you want the API code to be store [/usr/local/share/perl/5.24.1] ?
If all is OK, setup will install Communication server:
To ensure Apache loads mod_perl before OCS Inventory NG Communication Server,Setup can name Communication Server Apache configuration file'z-ocsinventory-server.conf' instead of 'ocsinventory-server.conf'.
```Do you allow Setup renaming Communication Server Apache configuration fileto 'z-ocsinventory-server.conf' ([y]/n) ?
################################################################################ # # OCS Inventory NG Communication Server Perl Module Setup # # Copyleft 2006 Pascal DANEK # Web: http://www.ocsinventory-ng.org # # This code is open source and may be copied and modified as long as the source # code is always made freely available. # Please refer to the General Public Licence http://www.gnu.org/ or Licence.txt ################################################################################
# Which version of mod_perl we are using # For mod_perl <= 1.999_21, replace 2 by 1 # For mod_perl > 1.999_21, replace 2 by 2 PerlSetEnv OCS_MODPERL_VERSION 2
# Master Database settings # Replace localhost by hostname or ip of MySQL server for WRITE PerlSetEnv OCS_DB_HOST localhost # Replace 3306 by port where running MySQL server, generally 3306 PerlSetEnv OCS_DB_PORT 3306 # Name of database PerlSetEnv OCS_DB_NAME ocsweb PerlSetEnv OCS_DB_LOCAL ocsweb # User allowed to connect to database PerlSetEnv OCS_DB_USER user # Password for user PerlSetVar OCS_DB_PWD user
# Slave Database settings # Replace localhost by hostname or ip of MySQL server for READ # Useful if you handle mysql slave databases # PerlSetEnv OCS_DB_SL_HOST localhost # Replace 3306 by port where running MySQL server, generally 3306 # PerlSetEnv OCS_DB_SL_PORT_SLAVE 3306 # User allowed to connect to database # PerlSetEnv OCS_DB_SL_USER ocs # Name of the database # PerlSetEnv OCS_DB_SL_NAME ocsweb # Password for user # PerlSetVar OCS_DB_SL_PWD ocs
# Path to log directory (must be writeable) PerlSetEnv OCS_OPT_LOGPATH '/var/log/ocsinventory-server'
# If you need to specify a mysql socket that the client's built-in #PerlSetEnv OCS_OPT_DBI_MYSQL_SOCKET 'path/to/mysql/unix/socket' # DBI verbosity PerlSetEnv OCS_OPT_DBI_PRINT_ERROR 0
# Unicode support PerlSetEnv OCS_OPT_UNICODE_SUPPORT 1
# If you are using a multi server architecture, # Put the ip addresses of the slaves on the master # (This is read as perl regular expressions) PerlAddVar OCS_OPT_TRUSTED_IP 127.0.0.1 #PerlAddVar OCS_OPT_TRUSTED_IP XXX.XXX.XXX.XXX
# WEB SERVICE (SOAP) SETTINGS
PerlSetEnv OCS_OPT_WEB_SERVICE_ENABLED 0 PerlSetEnv OCS_OPT_WEB_SERVICE_RESULTS_LIMIT 100 # PerlSetEnv OCS_OPT_WEB_SERVICE_PRIV_MODS_CONF 'WEBSERV_PRIV_MOD_CONF_FILE'
# Be careful: you must restart apache to make settings taking effects
# Configure engine to use the settings from this file PerlSetEnv OCS_OPT_OPTIONS_NOT_OVERLOADED 0
# Try to use other compress algorithm than raw zlib # GUNZIP and clear XML are supported PerlSetEnv OCS_OPT_COMPRESS_TRY_OTHERS 1
############################################################## # OPTIONS BELOW ARE OVERLOADED IF YOU USE OCS GUI # ##############################################################
# NOTE: IF YOU WANT TO USE THIS CONFIG FILE INSTEAD, set OCS_OPT_OPTIONS_NOT_OVERLOADED to '1'
# MAIN SETTINGS
# Enable engine logs (see LOGPATH setting) PerlSetEnv OCS_OPT_LOGLEVEL 0 # Specify agent's prolog frequency PerlSetEnv OCS_OPT_PROLOG_FREQ 12 # Specify if agent take contact on service startup PerlSetEnv OCS_OPT_INVENTORY_ON_STARTUP 0 # Configure the duplicates detection system PerlSetEnv OCS_OPT_AUTO_DUPLICATE_LVL 15 # Futur security improvements PerlSetEnv OCS_OPT_SECURITY_LEVEL 0 # Validity of a computer's lock PerlSetEnv OCS_OPT_LOCK_REUSE_TIME 600 # Enable the history tracking system (useful for external data synchronisation PerlSetEnv OCS_OPT_TRACE_DELETED 0
# INVENTORY SETTINGS
# Specify the validity of inventory data PerlSetEnv OCS_OPT_FREQUENCY 0 # Configure engine to update inventory regarding to CHECKSUM agent value (lower DB backend load) PerlSetEnv OCS_OPT_INVENTORY_DIFF 1 # Make engine consider an inventory as a transaction (lower concurency, better disk usage) PerlSetEnv OCS_OPT_INVENTORY_TRANSACTION 1 # Configure engine to make a differential update of inventory sections (row level). Lower DB backend load, higher frontend load PerlSetEnv OCS_OPT_INVENTORY_WRITE_DIFF 1 # Enable some stuff to improve DB queries, especially for GUI multicriteria searching system PerlSetEnv OCS_OPT_INVENTORY_CACHE_ENABLED 1 # Specify when the engine will clean the inventory cache structures PerlSetEnv OCS_OPT_INVENTORY_CACHE_REVALIDATE 7 # Enable you to keep trace of every elements encountered in db life PerlSetEnv OCS_OPT_INVENTORY_CACHE_KEEP 1
# SOFTWARES DEPLOYMENT SETTINGS
# Enable this feature PerlSetEnv OCS_OPT_DOWNLOAD 0 # Package which have a priority superior than this value will not be downloaded PerlSetEnv OCS_OPT_DOWNLOAD_PERIOD_LENGTH 10 # Time between two download cycles (bandwidth control) PerlSetEnv OCS_OPT_DOWNLOAD_CYCLE_LATENCY 60 # Time between two fragment downloads (bandwidth control) PerlSetEnv OCS_OPT_DOWNLOAD_FRAG_LATENCY 60 # Specify if you want to track packages affected to a group on computer's level PerlSetEnv OCS_OPT_DOWNLOAD_GROUPS_TRACE_EVENTS 1 # Time between two download periods (bandwidth control) PerlSetEnv OCS_OPT_DOWNLOAD_PERIOD_LATENCY 60 # Agents will send ERR_TIMEOUT event and clean the package it is older than this setting PerlSetEnv OCS_OPT_DOWNLOAD_TIMEOUT 7 # Agents will send an error event and clean the package if package command does not respond during this setting PerlSetEnv OCS_OPT_DOWNLOAD_EXECUTION_TIMEOUT 120
# Enable ocs engine to deliver agent's files (deprecated) PerlSetEnv OCS_OPT_DEPLOY 0 # Enable the softwares deployment capacity (bandwidth control)
# GROUPS SETTINGS
# Enable the computers groups feature PerlSetEnv OCS_OPT_ENABLE_GROUPS 1 # Random number computed in the defined range. Designed to avoid computing many groups in the same process PerlSetEnv OCS_OPT_GROUPS_CACHE_OFFSET 43200 # Specify the validity of computer's groups (default: compute it once a day - see offset) PerlSetEnv OCS_OPT_GROUPS_CACHE_REVALIDATE 43200
# IPDISCOVER SETTINGS
# Specify how much agent per LAN will discovered connected peripherals (0 to disable) PerlSetEnv OCS_OPT_IPDISCOVER 2 # Specify the minimal difference to replace an ipdiscover agent PerlSetEnv OCS_OPT_IPDISCOVER_BETTER_THRESHOLD 1 # Time between 2 arp requests (mini: 10 ms) PerlSetEnv OCS_OPT_IPDISCOVER_LATENCY 100 # Specify when to remove a computer when it has not come until this period PerlSetEnv OCS_OPT_IPDISCOVER_MAX_ALIVE 14 # Disable the time before a first election (not recommended) PerlSetEnv OCS_OPT_IPDISCOVER_NO_POSTPONE 0 # Enable groups for ipdiscover (for example, you might want to prevent some groups to be ipdiscover agents) PerlSetEnv OCS_OPT_IPDISCOVER_USE_GROUPS 1
# INVENTORY FILES MAPPING SETTINGS
# Use with ocsinventory-injector, enable the multi entities feature PerlSetEnv OCS_OPT_GENERATE_OCS_FILES 0 # Generate either compressed file or clear XML text PerlSetEnv OCS_OPT_OCS_FILES_FORMAT OCS # Specify if you want to keep trace of all inventory between to synchronisation with the higher level server PerlSetEnv OCS_OPT_OCS_FILES_OVERWRITE 0 # Path to ocs files directory (must be writeable) PerlSetEnv OCS_OPT_OCS_FILES_PATH /tmp
# FILTER SETTINGS
# Enable prolog filter stack PerlSetEnv OCS_OPT_PROLOG_FILTER_ON 0 # Enable core filter system to modify some things 'on the fly' PerlSetEnv OCS_OPT_INVENTORY_FILTER_ENABLED 0 # Enable inventory flooding filter. A dedicated ipaddress ia allowed to send a new computer only once in this period PerlSetEnv OCS_OPT_INVENTORY_FILTER_FLOOD_IP 0 # Period definition for INVENTORY_FILTER_FLOOD_IP PerlSetEnv OCS_OPT_INVENTORY_FILTER_FLOOD_IP_CACHE_TIME 300 # Enable inventory filter stack PerlSetEnv OCS_OPT_INVENTORY_FILTER_ON 0
# DATA FILTER
#Enable the dat filtering capacity PerlSetEnv OCS_OPT_DATA_FILTER 0
# Set the table names and the field associated you want to filter #PerlAddVar OCS_OPT_DATA_TO_FILTER HARDWARE #PerlAddVar OCS_OPT_DATA_TO_FILTER USERID
# REGISTRY SETTINGS
# Enable the registry capacity PerlSetEnv OCS_OPT_REGISTRY 1
# SNMP SETTINGS
# Enable the SNMP capacity PerlSetEnv OCS_OPT_SNMP 0 # Configure engine to update snmp inventory regarding to snmp_laststate table (lower DB backend load) PerlSetEnv OCS_OPT_SNMP_INVENTORY_DIFF 1 # Display error message about agent https communication in logfile PerlSetEnv OCS_OPT_SNMP_PRINT_HTTPS_ERROR 1
# SESSION SETTINGS # Not yet in GUI
# Validity of a session (prolog=>postinventory) PerlSetEnv OCS_OPT_SESSION_VALIDITY_TIME 600 # Consider a session obsolete if it is older thant this value PerlSetEnv OCS_OPT_SESSION_CLEAN_TIME 86400 # Accept an inventory only if required by server #( Refuse 'forced' inventory) PerlSetEnv OCS_OPT_INVENTORY_SESSION_ONLY 0
# TAG
# The default behavior of the server is to ignore TAG changes from the # agent. PerlSetEnv OCS_OPT_ACCEPT_TAG_UPDATE_FROM_CLIENT 0
# EXTERNAL USERAGENTS
#Path for external useragents reference file #!! WARNING !! : external agents may not be supported by OCS NG Community ! #PerlSetEnv OCS_OPT_EXT_USERAGENTS_FILE_PATH /tmp/yourfile.txt
# PLUGINS
PerlSetEnv OCS_PLUGINS_PERL_DIR '/etc/ocsinventory-server/perl' PerlSetEnv OCS_PLUGINS_CONF_DIR '/etc/ocsinventory-server/plugins'
# DEPRECATED
# Set the proxy cache validity in http headers when sending a file PerlSetEnv OCS_OPT_PROXY_REVALIDATE_DELAY 3600 # Deprecated PerlSetEnv OCS_OPT_UPDATE 0
############ DO NOT MODIFY BELOW ! #######################
# External modules PerlModule Apache::DBI PerlModule Compress::Zlib PerlModule XML::Simple
# Ocs plugins PerlModule Apache::Ocsinventory::Plugins::Apache PerlModule Apache::Ocsinventory::Plugins
See Full List On Wiki.archlinux.org
# Ocs PerlModule Apache::Ocsinventory PerlModule Apache::Ocsinventory::Server::Constants PerlModule Apache::Ocsinventory::Server::System PerlModule Apache::Ocsinventory::Server::Communication PerlModule Apache::Ocsinventory::Server::Inventory PerlModule Apache::Ocsinventory::Server::Duplicate
# Capacities PerlModule Apache::Ocsinventory::Server::Capacities::Registry PerlModule Apache::Ocsinventory::Server::Capacities::Update PerlModule Apache::Ocsinventory::Server::Capacities::Ipdiscover PerlModule Apache::Ocsinventory::Server::Capacities::Download PerlModule Apache::Ocsinventory::Server::Capacities::Notify PerlModule Apache::Ocsinventory::Server::Capacities::Snmp # This module guides you through the module creation # PerlModule Apache::Ocsinventory::Server::Capacities::Example # This module adds some rules to filter some request sent to ocs server in the prolog and inventory stages # PerlModule Apache::Ocsinventory::Server::Capacities::Filter # This module add availibity to filter data from HARDWARE section (data filtered won't be stored in database) # PerlModule Apache::Ocsinventory::Server::Capacities::Datafilter
# PerlTaintCheck On
# SSL apache settings #SSLEngine 'SSL_ENABLE' #SSLCertificateFile 'SSL_CERTIFICATE_FILE' #SSLCertificateKeyFile 'SSL_CERTIFICATE_KEY_FILE' #SSLCACertificateFile 'SSL_CERTIFICATE_FILE' #SSLCACertificatePath 'SSL_CERTIFICATE_PATH' #SSLVerifyClient 'SSL_VALIDATE_CLIENT'
# Engine apache settings # 'Virtual' directory for handling OCS Inventory NG agents communications # Be careful, do not create such directory into your web server root document ! # Apache 2.4 Require all granted
# Apache 2.4 Require local SetHandler perl-script PerlHandler 'Apache::Ocsinventory::SOAP'
CAUTION: Setup now install files in accordance with Filesystem HierarchyStandard. So, no file is installed under Apache root document directory(Refer to Apache configuration files to locate it).If you're upgrading from OCS Inventory NG Server 1.01 and previous, YOUMUST REMOVE (or move) directories 'ocsreports' and 'download' from Apacheroot document directory.If you choose to move directory, YOU MUST MOVE 'download' directory toAdministration Server writable/cache directory (by default/var/lib/ocsinventory-reports), especially if you use deployment feature.
Setup asking you to copy Administration Server static files for PHP Web Console
```Where to copy Administration Server static files for PHP Web Console[/usr/share/ocsinventory-reports] ?
Next, setup will check for required PERL modules(cf Requirements.):
Warning: If any of these modules is missing, setup will abort.
If everything is OK, setup will install Administration console into the âocsreportsâ subdirectory:
Now, you can restart Apache web server for changes to take effect.
Configuring management serverWarning: We recommend you to check your php.ini when you upgrade your server from 1.x to 2.x,specially these variables :
Note: You are not obliged to launch install.php, you can use this command too :
Else, open your favorite web browser and point it on URL
http://administration_console/ocsreports to connectthe Administration server.
As database is not yet created, this will begin OCS Inventory setup process.Otherwise, you can rerun configuration process by browsing
http://administration_console/ocsreports/install.php URL (this must be used when upgrading OCS Inventory management server).
Note: You will see warning regarding max size of package you will be able to deploy. Please, see Uploads size for package deployment to configure your server to match your need.
Fill in information to connect to MySQL database server with a user who has the ability to createdatabase, tables, indexes, etc (usually root):
Setup actions : refer to Deploying Database Server
The Refind Binary File Is Missing Aborting Installation ...
To secure your server, refer toSecure your OCS Inventory NG Serverdocumentation.
REFInd - ArchWiki
If you don't want to secure your OCS Inventory Server, you have to desactivate Warning message in user profile.Procedure is in the same documentation page.
Warning: We recommend you to read this documentation and follow the procedure.
Click on the following link : 'Click here to enter OCS-NG GUI'
Just point your browser to the URL
http://administration_server/ocsreports and login in with admin as user and admin as password.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |