Export to PDF option not working in Linux Installation
In some specific linux installs, PDF export option does not work due to the absence of "libfontconfig" package. We can install that package manually to make it work. Please follow the below steps to fix the issue.
Login into the linux install and use the following command to install the following package.
- Stop the OpManager service.
- Log into the linux install with sudo privileges and then use the following option highlighted below :
- "sudo apt-get install libfontconfig"
- Restart the Linux installed server itself for the changes to take effect.
- Now, use the export to PDF option from the OpManager web client and see if that helps.
More information on the link as well as the installation package is available below :
Releases directory path :
https://www.freedesktop.org/software/fontconfig/release/
New to ADSelfService Plus?
Related Articles
Migrating OpManager from Linux installation to Windows installation
If OpManager is installed on Linux server and wants to move it to a Windows server for some reason, follow the steps below. 1.On the linux installation of OpManager, click About and check what is the build number of OpManager, download the windows ...OpManager Enterprise installation procedure for central and probe on a Windows server (MSSQL)
MSSQL Monitors not working - Shows N/A in OpManager
This problem could due to the following reasons: 1)WMI is not configured properly in OpManager (OpManager uses WMI credential to monitor MSSQL servers). 2)Required Monitors are not associated to the device in OpManager. 3)WMI might not be responding ...Enable SNMP in Servers (windows 10 ,Linux and MAC)
Windows 10 Open the Settings on your Windows machine. Click Apps. Choose Manage optional features under Apps & features. Click Add a feature. Select Simple Network Management Protocol (SNMP) from the list. This will install the SNMP service in your ...WANRTT Monitor stopped working
Issue : WANRTT monitor stopped working in OpManager. Solution : This could be due to the changes happened in the Cisco source devices for some reason , possibly after a router reboot. Click on IPSLA WAN tab under ...