Many email servers depend on Reverse DNS in order to identify if the mail is legit or spam. For the Reverse DNS to work correctly, two points need to be addressed a) Look for IP address of the mail server should return its name. PTR record should be set for this b) Reverse look on the name should return back the IP address For example, $ dig -x 217.83.122.34 ;; ANSWER SECTION: 34.122.83.217.in-addr.arpa. 66372 IN PTR mail.example.com. $ dig mail.example.com ;; ANSWER SECTION: mail.example.com. 900 IN A 217.83.122.34 Check the IP address that is getting resolved matches the name that is getting returned back.

First Check PHP version that is currently installed $ php -version Check Linux Version $ cat /etc/*-release (or redhat-release) Create a repo file with the content given below. As you can note, we are looking for package upgrade related to php only. (more…)

SELinux is a feature that may be turned on certain servers and it can restrict access to certain ports. In order to gain access and make the ports work, you need to open those ports. To see if SELinux is set, type $ sestatus To list all port, try the semanage command $ semanage port -l To check for a specific port that is opened $ semanage port -l | grep 8085 To allow access to a specific port $ semanage port -a -t http_port_t -p tcp 8085

In linux, following commands are used to start/stop/restart mysql $/etc/init.d/mysqld start $/etc/init.d/mysqld restart $/etc/init.d/mysqld stop In windows, mysql runs as a service. C:> net stop mysql C:> net start mysql

When transitioning MySQL database from Windows to Linux, users often encounter issues related to case-sensitiveness. Windows is case-insensitive and Linux is case-sensitive. In such scenarios when a database call is made after the application migration happens, users often run into errors which can send them in circles between the migration servers. Solution to this problem is to add a single line of text under my.cnf (MySQL configuration file) under [mysqld] (more…)

$ /etc/init.d/apache2 restart After configuring Apache server settings on the name server, you may encounter a message "[warn] NameVirtualHost 192.168.1.3:80 has no VirtualHosts" The issue may be due to more than one entry of NameVirtualHost lines in the configuration settings. You can find this out by $ grep NameVirtual * -R site1:NameVirtualHost *:80 site2:NameVirtualHost *:80 Linux Solution: Remove one of the occurance of the NameVirtualHost and the warning message that you receive will vanish.