Blog
- Home
- Blog
Graphs not recording for ICMP and ping checks - Fix it Now ?
This article covers method to fix Nagios error, Graphs not recording for ICMP and ping checks.
This problem happens after upgrading to Nagios XI 2014.
Solution to Nagios XI ICMP and Ping Checks Stopped Graphing:
1. First a Perl package needs to be installed using one of the commands below:
$ apt-get install -y librrd-simple-perl
2. Download and unzip the required files:
cd /tmp
wget https://assets.nagios.com/downloads/nagiosxi/scripts/rrd_ds_fix.zip
unzip rrd_ds_fix.zip
3. To run the script with RRD backups:
./fix_ds_quantity.sh -d /usr/local/nagios/share/perfdata/
Cloudflare err_ssl_protocol_error - Fix it Now ?
This article covers methods to resolve Cloudflare ERR_SSL_PROTOCOL_ERROR. Basically, this error happens as a result of a number of reasons that include wrong DNS settings, SSL mode, TLS version or issues with SSL certificate.
To fix this error,
1. If you are not the site owner, contact the site owner and let them know you are having issues accessing their site.
2. The domain name has not fully been set to use Cloudflare yet. Check to see if there are non-Cloudflare nameservers that are conflicting with the assigned Cloudflare name servers.
3. You are signed up for Cloudflare, but you have set a DNS record to :grey:. If you have a subdomain or hostname and that serves HTTP/HTTPS traffic, we would advise that you :orange: this DNS record to take advantage of Cloudflare’s security and performance features. See What subdomains are appropriate for :orange:/:grey: clouds? 69
4. The Free Universal SSL certificate hasn’t yet been deployed, :grey: (deactivate) Cloudflare so that your website can continue to use your origin’s SSL certificate. Wait 24 hours and :orange: (activate) Cloudflare again to see if your SSL certificate has been successfully deployed.
5. You have some conflict with TLS 1.3, disable it and see if you still encounter the error.
6. You have selected Full SSL (strict) under your SSL/TLS app, but your origin does not have a valid certificate (i.e., it is expired, self-signed, or not issued by a trusted CA). Temporarily select another SSL option until you have a valid origin certificate in place.
7. Try to look at developer web console (firefox Ctrl+Shift+K) - anything interesting under Security tab.
8. Also, Try to run the command curl -vk on the affected domain.
Nginx error while loading shared libraries - Fix it Now ?
This article covers methods to resolve error, Nginx error while loading shared libraries for our customers.
This error happens when Nginx is looking for a file libpcre.so.1 which comes under the PCRE library and cannot find it because it is not available in the system.
To install PCRE with the below command:
$ yum install pcre
If you don't have root privilege, then you may ask the system administrator to install it.
Clean Up and Compress WinSxS Folder on Windows Server / Windows 10 - Do it Now ?
This article covers methods to Clean Up and Compress WinSxS Folder on Windows Server/Windows 10.
WinSxS folder in Windows is the reasons of its constant growth and ways to clean up it.
The C:\Windows\WinSxS directory is the repository of Windows components. This directory contains DLLs, binary and XML files necessary for installation and operation of various Windows roles or features.
When installing the Windows updates (usually this happens every month), the new version of the updated component is installed on the system, while the old one is saved to the WinSxS folder (it is necessary to provide compatibility and make it possible to rollback to the previous versions of the components when you uninstall the Windows update).
To clean up the WinSxS folder on Windows 10 and Windows Server 2016/2019:
1. Optimize the component store and remove old versions of Windows component files left after installing Windows updates;
2. Features on Demand – allows you to remove unused Windows components from the disk;
3. Enable NTFS compression on the WinSxS folder – a way to reduce the size of the WinSxS directory using the built-in compression of the NTFS file system.
How to Check the Actual Size of WinSxS Folder on Windows 10?
The easiest way to get the current size of the WinSxS folder on Windows is to open the properties of the %windir%\WinSxS folder in File Explorer (or use a PowerShell script).
You can find out the real size of the WinSxS folder on disk using the du tool from Sysinternals:
du -v c:\windows\winSXS
Install Ajenti Control Panel on Ubuntu 20.04 - Step by Step Process ?
This article covers step by step procedure to install Ajenti Control Panel on Ubuntu 20.04 for our customers.
Ajenti is a free to use and open source Server management and configuration Panel written in Python, JavaScript, and AngularJS. It provides a web dashboard for administration as opposed to command line management.
With this tool you can manage websites, DNS, Cron, Firewall, Files, Logs, Mail hosting services and so on.
The Ajenti Project consists of Ajenti Core and set of stock plugins forming the Ajenti Panel.
1. Ajenti Core: Web interface development framework which includes a web server, IoC container, a simplistic web framework and set of core components aiding in client-server communications.
2. Ajenti Panel: Consists of plugins developed for the Ajenti Core and a startup script, together providing a server administration panel experience.
To Install Ajenti Control Panel on Ubuntu 20.04:
1. Update and upgrade your Ubuntu machine.
$ sudo apt update
$ sudo apt dist-upgrade
2. If the upgrade is completed reboot the system before initiating installation of Ajenti on Ubuntu 20.04.
$ sudo systemctl reboot
3. There is a script provided for the installation of Ajenti control panel on Ubuntu 20.04. First download the script with curl.
$ curl -O https://raw.githubusercontent.com/ajenti/ajenti/master/scripts/install.sh
4. Run the installer script with sudo command.
$ sudo bash ./install.sh
PrestaShop back office error 500 or blank page - Fix it Now ?
This article covers methods to resolve PrestaShop back office error 500.
The error happens when the Back-office is accessed only from Debug mode activated or in production mode activated. The characteristic of this error is that it only occurs in one of the modes and not in both.
Also, this is an error that is occurring ONLY IN PRESTASHOP STORES VERSION 1.7, and that makes it impossible for us to enter the Back-office, showing an error 500 or the page goes blank.
That's why we call it a critical mistake, for leaving the store inoperative.
To fix a HTTP 500 error on PrestaShop online store website:
You can activate your web host's FTP or CPanel error reports in your PrestaShop shop.
1. From PrestaShop v1.4 to v1.5.2
i. Open config/config.inc.php
ii. On line 29, you will find this line: @ini_set('display_errors','off');
iii. Replace it with: @ini_set('display_errors','on');
2. PrestaShop v1.5.3 and later versions (including 1.6 and 1.7)
i. Open config/defines.inc.php
ii. On line 28, you will find this line: define('_PS_MODE_DEV_', false);
iii. Replace it with: define('_PS_MODE_DEV_', true);
Once error reports from the FTP or CPanel are activated, you can browse your store's front or back office to find out what the problem is.
More about Server error 500:
Error 500 means Internal server Error. Whenever a 500 error occurs, the task to return information by the server to the web browser will stop.
Therefore, as we mentioned above, this is a critical error that would leave the website inoperative.
The 500 errors, as we noted above, are internal server errors and their origin may be in a programming code error on any item that is included and related to the request for information returned by the server to the web browser.
Therefore, not all 500 errors come from the same source.
