SupportSages » VPS

How to resolve : Internal Server Error when accessing cpanel/WHM/Webmail

vince — Fri, 25 Jun 2010 19:13:12 +0000

Imagine you are accessing your Website WHM or cPanel or Webmail hosted (in your VPS) and what if you see this

How to solve this

Pre-Requisites : You should have Shell access (as root) to the Node server.

Mostly this happens due to inode issue. The inodes allocated to the server maybe full. inode is a data structure on a traditional Unix-style file system such as UFS. An inode stores basic information about a regular file, directory, or other file system object.

Steps

Say we are logged into the Node Server. There we are going to list all the Containers existing on the Hardware Node. By default, only running Containers are shown.

[root@linuxvps1 ~]# vzlist -a
CTID    NPROC STATUS   IP_ADDR        HOSTNAME
100     18  running    100.20.11.111  WEB.EXAMPLE.COM
101     63  running    100.20.12.203  -
102     169 running    100.20.92.182  server2.example.com
103     81  running    100.20.56.169  example.net
78965   236 running    100.20.77.204  server1.example.com

Assume your container is 103. So simply enter into 103 by this command

[root@linuxvps1 ~]# vzctl enter 103

Check if the inodes are full in the container

[root@linuxvps1 ~]# df -i

Most Probably it should display something like this :

Filesystem      Inodes      IUsed        IFree     IUse%      Mounted on
/dev/vzfs       200000      200000       0         100%       /
none            65536       95           65441     1%         /dev

Bang ! The inodes on /dev/vzfs mounted on / are full. You’ve to go nowhere else to see why that error was delivered. A simple solution will work out, you’ve to increase the inode limit. You’ve two options, either through Shell or through the Node Control Panel (like Parallels Infrastructure Manager)

First we will go through Shell mode with this command :

$ vzctl set veid --diskinodes softlimit:hardlimit

Where ‘veid’ is the VPS ID

root@linuxvps1 ~]# vzctl set 103 --diskinodes 7680100:7680200

Second we are going for Node Control Panel. In the infrastructure, you will see your VPS with a ! sign. That indicates your VPS is having some sort of issue.

So you’ve seen the Alert. Next access the VPS, go to Resources tab. I’m sorry to tell you that I grabbed this screenshot after resolving the issue, but it will help you anyway

You should see the ‘Disk Inodes’ is full under ‘Disk Usage’ category (Here it is not !). Next Click Configure to settle this one

See the Highlighted part, the inodes should be limited to some size. Increase it or remove the check mark to make it unlimited. Make sure you save the changes. Now try again accessing cpanel/WHM/Webmail. It should load with out any issues.That makes a smile in your face, isn’t it ?

Tweet This Post

How to do : Add or Delete an IP Address in the VPS

vince — Wed, 26 May 2010 00:36:33 +0000

Hello there,

Usually, we need to add or remove an IP address in the VPS. Here we go :

Prerequisites

You need Node Server access for these (then only you can manage those VPS), that too SSH root access. The VPS should be either OpenVZ or Virtuozzo.

Steps

Say we are logged into the Node Server. There we are going to list all the Containers existing on the Hardware Node. By default, only running Containers are shown.


[root@linuxvps1 ~]# vzlist -a
CTID    NPROC STATUS   IP_ADDR        HOSTNAME
100     18  running    100.20.11.111  WEB.EXAMPLE.COM
101     63  running    100.20.12.203  -
102     169 running    100.20.92.182  server2.example.com
103     81  running    100.20.56.169  test.example.net
78965   236 running    100.20.77.204  server1.example.com

Lets consider the VPS with ID 78965 needs the new IP 100.20.80.200 to be added. So the command will be :


[root@linuxvps1 ~]# vzctl set 78965 --ipadd 100.20.80.200
Adding IP address(es): 100.20.80.200 WARNING: Settings were not saved. On next start the original values will be applied.
Use --save to save the settings in the configuration file.

Save the Settings (this command will do the purpose instead of the above one)


[root@linuxvps1 ~]# vzctl set 78965 --save --ipadd 100.20.80.200
Adding IP address(es): 100.20.80.200 Saved parameters for Container 78965.

Thats it, now login to WHM and access ‘Change Site’s IP Address’. Select the website and change the IP address from the drop down list.

To remove an IP from the VPS


[root@linuxvps1 ~]# vzctl set 78965 --save --ipdel 100.20.80.200
Deleting IP address(es): 100.20.80.200 Saved parameters for Container 78965.

Mission Accomplished !

Tweet This Post

OpenVPN issues on a OpenVZ / Virtuozzo enabled VPS

George — Sat, 12 Sep 2009 16:00:19 +0000

Error Note: Cannot open TUN/TAP dev /dev/net/tun: Permission denied (errno=13)

Just follow the KB at http://wiki.openvz.org/VPN_via_the_TUN/TAP_device

Error Note: Cannot set tx queue length on tun0: Operation not permitted (errno=1)

As mentioned in the same KB URL, just do the steps below and things should be alright again

vzctl set 101 --devices c:10:200:rw --save
vzctl set 101 --capability net_admin:on --save

Basically the errors are caused by the non-execution of the two commands mentioned above.

Tweet This Post

User stats in directadmin admin area – Solved with a good client’s help :)

George — Wed, 10 Jun 2009 20:58:46 +0000

When one of our clients, Mr. Xavier opened an issue with us regarding the Usage stats not being shown, we were certain that this is a bug with DirectAdmin in the way how its license are read. We changed the ethernet_dev in directadmin.conf, but that didn’t work out.

Client was asking us,

In Admin Area –> Complete Usage Statistics –> Usage stats for venet0:0 is showing “None”

It’s possible to fix this to reflect the traffic of this virtual adapter?

DirectAdmin didn’t give a direct solution. Instead provided us with a complete packed files related to DirectAdmin. So the solution was this.

cd /usr/local/directadmin wget -O new.tar.gz http://files.directadmin.com/7694310/packed_es50.tar.gz tar xvzf new.tar.gz ./directadmin p killall -9 directadmin ./directadmin d /etc/init.d/directadmin restart

For anyone facing this issue. I didn’t check more deeper into what changed, but must be related to htmls in data page on how device gets read.

Tweet This Post

Adding packages from WHM or editing the reseller privileges is not working on a x86_64 architecture

George — Sat, 23 May 2009 16:04:53 +0000

As usual, start by checking the error log of cPanel at /usr/local/cpanel/logs/error_log

2009-05-23 15:44:24 info [whostmgr2] [28346] Waiting for lock on /var/cpanel/package-limits.yaml held by /usr/local/cpanel/whostmgr/bin/whostmgr2 – locking /var/cpanel/package-limits.yaml with pid 25968
2009-05-23 15:44:25 info [whostmgr2] [28346] Removing expired lock file /var/cpanel/package-limits.yaml.lock
(internal warning while parsing [stdin]) Sat May 23 23:41:28 2009 [25968] warn: Attempt to free unreferenced scalar.

While the error (internal warning while parsing [stdin]) Sat May 23 23:41:28 2009 [25968] warn: Attempt to free unreferenced scalar floods the error log

Permissions were all right, but suddenly this started happening, but only x86_64 architectures only. Reason being the cPanel is killing the process, since it exceeded the memory usage allowed by cPanel.

Solution would be to increase the memory limit of cPanel by following the instructions below.

WHM -> Server Configuration -> Tweak Settings Choose the setting for:

The maximum memory a cPanel process can use before it is killed off (in megabytes). Values less than 128 megabytes can not be specified. A value of “0″ will disable the memory limits.

The settings had 256M there, and increasing the value to 1024 M helped. Server had 8G RAM, so the value of 1024M was fine here.

Tweet This Post

How do I reset the root mysql pass, lxadmin created ?

Fabian — Thu, 30 Apr 2009 06:47:51 +0000

Oh, do it from the GUI lxadmin gives you OR else, do it console based way.

# cd /usr/local/lxlabs/lxadmin/httpdocs/
# lphp.exe ../bin/common/misc/reset-mysql-root-password.phps

Tweet This Post

Server refused to allocate pty in a VPS & CentOS 5.3

George — Fri, 17 Apr 2009 01:51:04 +0000

With CentOS 5.3 released on 1st April of this year, more udev related issues crops in. I don’t know when OpenVZ will get better in its thinking. Issue is there in every VPS who has got the udev upgraded as a result of no excludes in yum.conf entries. Two solutions exists as per http://wiki.openvz.org/Container_enter_failed

Editing the rc.sysinit is the solution which will work here. But when I explained to one of our customers that we edited rc.sysinit, he thought it is /etc/rc.sysinit in the node. Be warned : Don’t do that! Instead from the node edit the etc/sysinit of the VPS, like vi /vz/private/VPSID/etc/rc.sysinit.

However the proper solution, we believe is to

yum remove udev

go ahead with yes to remove dependencies as well. It will also remove ImageMagick, which you have to later install it manually from source. Follow the how to for the installation of ImageMagick below, since the yum based installation of ImageMagick has dependency on hal and udev packages.

/me wonders why are they dependent though..

yum install ghostscript
wget ftp://ftp.imagemagick.org/pub/ImageMagick/ImageMagick.tar.gz
tar xvzf ImageMagick.tar.gz
rm -rf ImageMagick.tar.gz
cd ImageMagick*
./configure –enable-shared –with-modules –with-freetype=yes –with-gs-font-dir=default –with-perl=yes –with-xml=yes –with-zlib=yes –with-jpeg=yes –with-png=yes –without-x
make
make install

After the udev is removed, edit the /etc/yum.conf and make sure that the exclude= line has udev* mkinitrd module-init-tools and kernel* added to it. cPanel usually adds kernel*, but I guess its our responsibility to add udev* in a VPS, till cPanel’s upcp does it for us in a VPS

Tweet This Post