/opt/lua/lib/liblua.a: could not read symbols: Bad value

I got the following error while installing modsecurity from source file.

/opt/lua/lib/liblua.a: could not read symbols: Bad value

Fix : Install the following packages.

yum install lua lua-devel libsmi-devel.x86_64


Linux swap space

Linux divides its physical RAM (random access memory) into chucks of memory called pages. Swapping is the process whereby a page of memory is copied to the preconfigured space on the hard disk, called swap space, to free up that page of memory. The combined sizes of the physical memory and the swap space is the amount of virtual memory available.

Swapping is necessary for two important reasons. First, when the system requires more memory than is physically available, the kernel swaps out less used pages and gives memory to the current application (process) that needs the memory immediately. Second, a significant number of the pages used by an application during its startup phase may only be used for initialization and then never used again. The system can swap out those pages and free the memory for other applications or even for the disk cache.

However, swapping does have a downside. Compared to memory, disks are very slow. Memory speeds can be measured in nanoseconds, while disks are measured in milliseconds, so accessing the disk can be tens of thousands times slower than accessing physical memory. The more swapping that occurs, the slower your system will be. Sometimes excessive swapping or thrashing occurs where a page is swapped out and then very soon swapped in and then swapped out again and so on. In such situations the system is struggling to find free memory and keep applications running at the same time. In this case only adding more RAM will help.

Linux has two forms of swap space: the swap partition and the swap file. The swap partition is an independent section of the hard disk used solely for swapping; no other files can reside there. The swap file is a special file in the filesystem that resides amongst your system and data files.


Reference : https://www.linux.com/news/all-about-linux-swap-space

Deprecated: Assigning the return value of new by reference is deprecated

I have received the following error message on my website

Deprecated: Assigning the return value of new by reference is deprecated

The reason is that my host has upgraded php version in the server and the function I have used in my site has been depreciated.

You can fix this by simply doing some edits. if you go to the files and the line numbers indicated in the error messages, you’ll see something like this:
$object =& new MyObject();

You can just remove the “&” from the above line

Base_url_change in majento

1, Via mysql command line
Select the database
Mysql>> use database;

Now run the following command to list the current base url
Mysql>> select * from core_config_data where path like ‘%base%url%’;

To change the base URLs, execute the following commands from mysql prompt
update core_config_data set value = ‘http://domainname/’ where path = ‘web/unsecure/base_url’;
update core_config_data set value = ‘http://domainname/’ where path = ‘web/secure/base_url’;

2, Via phpmyadmin
Take PhpMyAdmin and select the required database. Now you will see a list of all the tables in the database in alphabetical order. Search for the table.

Expand the viewing area of phpMyAdmin. At the top and bottom in the main panel, locate the grey box and change the Number of rows to a larger number, such as 100.

Locate the rows web/unsecure/base_url and web/secure/base_url and click Edit next to the corresponding lines. Change the base URL to the intended string, and click OK.

Flush the Magento cache, and the site should load with the set base URLs properly now.

3, Magento Admin Panel.

From majento admin panel click System > Configuration.

From the menu on the left, under the General list>> web

Open the Unsecure and Secure dropdowns, locate the base URL line, and replace this with the new URL.

Clear the Magento cache and your browser’s cache. The site should now load properly.

Custom php.ini to use with fcgi

1, copy the default cgi-sys wrapper script and save it like the following

cp -rp /usr/local/cpanel/cgi-sys/php5 /usr/local/cpanel/cgi-sys/php5-username

2, Now edit the newly created file

vi /usr/local/cpanel/cgi-sys/php5-username

3, Add the following line above exec

[[ -f ~/public_html/php.ini ]] && exec /usr/bin/php -c ~/public_html/php.ini

4, So the script will look like this now


# If you customize the contents of this wrapper script, place
# a copy at /var/cpanel/conf/apache/wrappers/php5
# so that it will be reinstalled when Apache is updated or the
# PHP handler configuration is changed
[[ -f ~/public_html/php.ini ]] && exec /usr/bin/php -c ~/public_html/php.ini
exec /usr/bin/php

5. Now copy the default php.ini to the public_html location

6, Add the following htaccess code

FCGIDWrapper /usr/local/cpanel/cgi-sys/php5-username .php

Cpanel X3 theme issue

My cpanel was not loading with x3 theme and paper lantern theme. My server was running on cloudlinux kernel

Issue: This issue was reported in internal case CPANEL-3875, however it was determined the issue is with the Cloud Linux application

Fix : Remove the following three lines from the files

a, /usr/local/cpanel/base/frontend/paper_lantern/dynamicui.conf and






Steps to add an existing openvz VE into solusvm

We can directly import virtual servers, that were created manually into SolusVM s using the following method

1, First we need to enable import mode to on from solusvm panel

a, admincp go to Configuration > Settings > Other and tick Import Mode.

2, To import a OpenVZ virtual server from the admincp do the following:

Select Virtual Servers > Add Virtual Server

Select OpenVZ

Select the Node & Plan, then click Continue
Enter the container ID of the virtual server you want to import (as shown under vzlist on the host node) in the Container ID field
Fill in the rest of the fields
Click the Create Virtual Server button
Add any extras ip’s etc.. to the virtual server
If you receive the error “Container id already exists”, it means that the VEID of the vps that we are importing is already present in solusvm. For that you need to use the following method
3, Enter the node where the ve exists
4, If backup is mounted, umount the backup
5, Now we are considering the following


6, Proceed with the chnage

vzctl chkpnt 100 –dumpfile /tmp/Dump.100
mv /etc/vz/conf/100.conf /etc/vz/conf/101.conf
mv /vz/private/100 /vz/private/101
mv /vz/root/100 /vz/root/101
vzctl restore 101 –dumpfile /vz/Dump.101

now check vzlist -a and you will see the VE is updated with the new VEID 101
Now you can go to step number 2 again and successfully import the ve through solusvm