A frequent error message received when using the mysql command line utility is: Can’t connect to local MySQL server through socket ‘/tmp/mysql.sock’ While this error message can be frustrating, the solution is simple.

When connecting to a MySQL server located on the local system, the mysql client connects thorugh a local file called a socket instead of connecting to the localhost loopback address 127.0.0.1. For the mysql client, the default location of this socket file is /tmp/mysql.sock. However, for a variety of reasons, many MySQL installations place this socket file somewhere else like /var/lib/mysql/mysql.sock.

While it is possible to make this work by specifying the socket file directly in the mysql client command

mysql –socket=/var/lib/mysql/mysql.sock …

it is painful to type this in every time. If you must do so this way (because you don’t have permissions to the file in the solution below), you could create an alias in your shell to make this work (like alias mysql=”mysql –socket=/var/lib/mysql/mysql.sock” depending on your shell).

To make your life easier, you can make a simple change to the MySQL configuration file /etc/my.cnf that will permanently set the socket file used by the mysql client. After making a backup copy of /etc/my.cnf, open it in your favorite editor. The file is divided into sections such as

[mysqld]
datadir=/usr/local/mysql/data
socket=/var/lib/mysql/mysql.sock

[mysql.server]
user=mysql
basedir=/usr/local/mysql
If there is not currently a section called [client], add one at the bottom of the file and copy the socket= line under the [mysqld] section such as:

[client]
socket=/var/lib/mysql/mysql.sock

If there is already a [client] section in the my.cnf file, add or edit the socket line as appropriate. You won’t need to restart your server or any other processes. Subsequent uses of the mysql client will use the proper socket file.

Extrapolating this to my case, i moved the MySQL database to another hard-drive, so the client would still connect to the old .sock file, so i defined the CLIENT section in /etc/my.cnf.

Also, i had to change in php.ini the default mysql_connect socket, to point to the new location.

In case you’re using MailScanner, it has to be restarted as well, because it will still try to use the old mysql socket.

Fetching 4115 new ports or files… /usr/sbin/portsnap: cannot open a933dd1da50d053b997b5626a889cec90a86ed5dfc82135c7a975a46d78dce02.gz: No such file or directory
snapshot is corrupt.

if by any chance you get this error, on FreeBSD, while updating the ports with portsnap, do the following:

cd /var/db/portsnap

rm -rf *

portsnap fetch extract

It will work.

Permission denied: /home/USERNAME/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable

for fix, follow the procedure below:

cd ~USERNAME

chmod a+rx public_html

This error usually happens due to POOR coding of the software,

and this goes with a big boo to realvnc. Just bought

the license last night. So it seems the new paths of X are

different, so we are just going to make a nice symlink:

[root@jupiter ~]# vncserver
  VNC Server Enterprise Edition E4.3.1 - built Aug 14 2007 14:54:48
  Copyright (C) 2002-2007 RealVNC Ltd.
  See http://www.realvnc.com for information on VNC.
  Couldn’t open RGB_DB ‘/usr/X11R6/lib/X11/rgb’

  Xvnc Enterprise Edition E4.3.1 - built Aug 14 2007 14:58:37
  Copyright (C) 2002-2007 RealVNC Ltd.
  See http://www.realvnc.com for information on VNC.
  Underlying X server release 40300000, The XFree86 Project, Inc

  Sun Oct 21 19:15:01 2007
   vncext:      VNC extension running!
   vncext:      created VNC server for screen 0
   TcpListener: listening on IPv4, port 5901
   TcpListener: listening on IPv4, port 5801
  error opening security policy file
/usr/X11R6/lib/X11/xserver/SecurityPolicy
  Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing
from list!
  Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/,
removing from list!
  Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing
from list!
  Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!
  Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, removing
from list!
  Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/,
removing from list!

  Fatal server error:
  could not open default font ‘fixed’

Do the thing down here, and poof ! it works.

ln -s /usr/share/X11 /usr/X11R6/lib
Enjoy. Waiting for feedbaaaack

I found on the cPanel forum that DomainKeys was already installed in the version of cPanel I have on my server.

Apparently, with my setup, all I needed to do was to install it and make sure that the DNS was set up correctly. This was done by logging into my server and typing:

/usr/local/cpanel/bin/domain_keys_installer <user name>

Where <User name> was the name of the user for the zone that I wanted DomainKeys set up for.

The installer made an entry in the DNS for the particular zone.

I use an external DNS service and so I had to copy the entry that was made automatically to my DNS service.

This was  the default._domainkey entry… So in my eternal DNS service I created a TXT entry named default._domainkey and copied and pasted the value that the installer had created.

I also created another entry:

_domainkey “t=y; o=-”

The only thing left to do was test the setup. I sent an e-mail from my server to a Yahoo account and Yahoo deemed that I had an acceptable DomainKey.

I also sent an e-mail to: check-auth@verifier.port25.com

which also replied with positive results.

I found that a lot of tester out there gave negative results, but I am assuming that the testers were not up to date with the latest DomainKeys standard.

If you have Fedora Core 5/6 or CentOS 5 or Red Hat Enterprise Linux 5 on your server and are experiencing troubles with respect to upgrades (forced or
otherwise) of Click Be! or Fantastico or Universina, please check the wget version that you have on your server.

If it is wget-1.10.2-3.3.fc5 or wget-1.10.2-7.el5 or wget-1.10.2-8.fc6.1, we suggest that you replace it immediately with an older and/or stabler
version. This version does not honor the “-P” switch.

An alternate version that we suggest is wget-1.10.2-3.2.1

You can use the following commands for this purpose:
Code:

rpm -qa wget ;
wget http://fedora.osmirror.nl/core/development/i386/Fedora/RPMS/wget-1.10.2-3.2.1.i386.rpm ;
rpm -e wget ;
rpm -ivh –force wget-1.10.2-3.2.1.i386.rpm ;
rpm -qa wget ;

Note: You must execute the commands shown above as root.

Reports suggest that the version of wget included with Fedora Core 7 does not have this problem, so that may be a better option for some people.

If at any time, you get on this issue, then the suid bit is not set on the crontab executable.

Easy fix : chmod 4755 /usr/bin/crontab

Cheers.

Guide available for CentOS / Fedora / RHEL

• Make sure if you have postgresql intalled

  rpm -qa | grep postgres | tee /root/rpm_pgsql

  The above will list all the installed postgresql rpm packages and store the output to /root/rpm_pgsql. You can use this list to remove all the postgresql related rpm later.

• Backup all your databases

  su postgres -
  mkdir backups
  pg_dumpall > /var/lib/pgsql/backups/postgresql_backup
  exit

  exit will logout from the postgres user

• Now stop the postgrsql daemon using the following command

  /sbin/service postgresql stop

• Backup the whole database folder

  mv /var/lib/pgsql /var/lib/pgsql_old

• Remove the old rpms using rpm -e, you can use the previously stored /root/rpm_pgsql to remove the postgresql rpm and its depended, for example the perl-DBD-pg depends on it. So you will be removing the /root/rpm_pgsql list + perl-DBD-gpFor example, it might differ on your servers

  rpm -e rh-postgresql-server
  rpm -e rh-postgresql
  rpm -e rh-postgresql-devel
  rpm -e rh-postgresql-python
  rpm -e rh-postgresql-libs
  rpm -e perl-DBD-Pg

• Download the new version of postgreSQL from the postgresql download site into
  /usr/local/src or any directory you prefer.
• After you have download the postgreSQL rpms from PostgreSQL download site.
  Download the following rpms

  postgresql-***-2PGDG.i686.rpm
  postgresql-contrib-***-2PGDG.i686.rpm
  postgresql-devel-***-2PGDG.i686.rpm
  postgresql-docs-***-2PGDG.i686.rpm
  postgresql-libs-***-2PGDG.i686.rpm
  postgresql-python-***-2PGDG.i686.rpm
  postgresql-server-***-2PGDG.i686.rpm

  To install

  rpm -Uhv postgresql*.rpm

• After you have installed the new postgreSQL rpms login to WHM usinghttps://ip:2087
  under the SQL service Menu
  Postgres Config
  Install new configuration and change the password
• To restore the old databases

  psql template1 < /var/lib/pgsql_old/postgresql_backup_file

  The above will restore the databases

• Notes: This is a manual installation, on the current cPanel 11, /scripts/installpostgres will definitely do the job, the guide is pretty old, but still, this should be very easy to do.

• VERY CAREFUL, in order to have apache/php working with postgres, you have to recompile, either from WHM, either from shell, with postgres support.

Original guide here

“The remote server didn’t report a correct md5sum of the archive. Please ensure you selected the correct type of remote server.”

If this error comes in,  and you are trying to move cPanel accounts between 2 servers, then you must be running Chirpy’s CSF. If so, do a quick allow on both servers, for each server’s main ips. It will work flawlessly.

Data transfer in  progress.

While upgrading and possibly editing smileys in the Smileys section of your Administration Panel, you may get an error similar to this:

Quote

This query:
ALTER TABLE smf_smileys
ORDER BY LENGTH(code) DESC;
Caused the error:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘LENGTH(code) DESC’ at line 2
There are two solutions to resolve this error.

The first solution will fix both the issue with upgrading, as well as an issue with editing smileys in the Smileys and Message Icons section of your admin panel.
All you need to do is update your MySQL version. To update MySQL yourself, you will have to have server access. Otherwise, and more commonly the case, you will have to ask your host to upgrade MySQL on the server for you. Some older versions of MySQL seem to have this issue. At the moment the MySQL versions known with this are:

• 5.0.37
• 5.0.41
• 5.0.42
• 5.1.17(Unconfirmed)

There may be other versions of MySQL that have this issue as well, but upgrading MySQL to the latest version for the MySQL branch you are using may resolve the issue.

The second way to resolve this for upgrading is to open “upgrade_1-1.sql” with a text editor and find the following:

Code:

ALTER TABLE {$db_prefix}smileys
ORDER BY LENGTH(code) DESC;

Replacing this with:

Code:

ALTER TABLE {$db_prefix}smileys
ORDER BY code DESC;

For editing smileys in the Smileys and Message Icons section of your admin panel, open “/Sources/ManageSmileys.php” with a text editor and find the following code:

Code:

			// Sort all smiley codes for more accurate parsing (longest code first).
			db_query("
				ALTER TABLE {$db_prefix}smileys
				ORDER BY LENGTH(code) DESC", __FILE__, __LINE__);

Replacing this with:

Code:

			// Sort all smiley codes for more accurate parsing (longest code first).
			db_query("
				ALTER TABLE {$db_prefix}smileys
				ORDER BY code DESC", __FILE__, __LINE__);

This section of code will appear twice in “/Sources/ManageSmileys.php“, You will find this approximatively on lines 654 and 990.