For this issue reset cpanel user password through whm.
ImportError: cannot import name to_unicode
Are you getting below error while updating working on yum
root@vps [/]# yum clean packages
Traceback (most recent call last):
File “/usr/bin/yum”, line 28, in ?
import yummain
File “/usr/share/yum-cli/yummain.py”, line 32, in ?
from yum.i18n import to_unicode, utf8_width
ImportError: cannot import name to_unicode
Below are the steps to fix this issue
Download yum rpm first
root@vps [/]# wget ftp://ftp.muug.mb.ca/mirror/centos/5.10/os/i386/CentOS/yum-3.2.22-40.el5.centos.noarch.rpm
Remove the old yum rpm from server using below command
root@vps [/]# rpm -e yum –nodeps
warning: /etc/yum.conf saved as /etc/yum.conf.rpmsave
Now installed the downloaded rpm
root@vps [/]# rpm -ivh yum-3.2.22-40.el5.centos.noarch.rpm
Preparing… ########################################### [100%]
1:yum ########################################### [100%]
Now yum should work like charm
root@vps [/]# yum update
Loaded plugins: fastestmirror
Determining fastest mirrors
* addons: httpupdate.cpanel.net
* base: httpupdate.cpanel.net
* extras: httpupdate.cpanel.net
* update: httpupdate.cpanel.net
addons | 1.9 kB 00:00
base | 1.1 kB 00:00
extras | 2.1 kB 00:00
update | 1.9 kB 00:00
update/primary_db | 483 kB 00:00
Setting up Update Process
Resolving Dependencies
RTNETLINK answers: File exists
Openvz architecture in Centos 6.5 has an issue
If you are facing issues where ifconfig shows no ip address or below error
root@server [/]# ifconfig
root@server [/]# /etc/init.d/network restart
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: RTNETLINK answers: Operation not supported
Failed to bring up lo.
[FAILED]
Bringing up interface venet0: RTNETLINK answers: Operation not supported
Failed to bring up venet0.
[FAILED]
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
Below is the solution for this issue
Its due to package iproute which is causing this issue
Use below method to fix it
Login to main node of the server
[root@hostonine ~]# wget http://repo.smartservermanagement.com/misc/iproute-2.6.32-23.el6.x86_64.rpm
–2014-06-03 08:21:42– http://repo.smartservermanagement.com/misc/iproute-2.6.32-23.el6.x86_64.rpm
Resolving repo.smartservermanagement.com… 95.154.203.53
Connecting to repo.smartservermanagement.com|95.154.203.53|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 351552 (343K) [application/x-rpm]
Saving to: `iproute-2.6.32-23.el6.x86_64.rpm’
100%[====================================================================================================================>] 351,552 421K/s in 0.8s
2014-06-03 08:21:44 (421 KB/s) – `iproute-2.6.32-23.el6.x86_64.rpm’ saved [351552/351552]
#Copy the package to vps using below command where 180 is VPS ID
[root@hostonline ~]# scp -r iproute-2.6.32-23.el6.x86_64.rpm /vz/private/180/var/
#Now login to VPS
[root@hostonline ~]# vzctl enter 180
entered into CT 180
root@server [/]# cd /var/
Check for the rpm iproute
root@server [/var]# rpm -q iproute
iproute-2.6.32-31.el6.x86_64
#Remove the old rpm
root@server [/var]# rpm -e iproute-2.6.32-31.el6.x86_64 –nodeps
#Install the new RPM
root@server [/var]# rpm -Uvh iproute-2.6.32-23.el6.x86_64.rpm
warning: iproute-2.6.32-23.el6.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID 192a7d7d: NOKEY
Preparing… ########################################### [100%] 1:iproute ########################################### [100%]
#Now restart networking and check
root@server [/var]# service network restart
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface venet0: Determining if ip address 127.0.0.1 is already in use for device venet0…
[ OK ]
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
WordPress Asking For FTP details every time you want to add, delete or upgrade a plugin?
Facing issues on wordpress blog where its asking for ftp login when trying to install new plugin ?
Add the below lines in wp-config.php and save it
This should do the trick in solving this issue
//*added ftp login credentials to avoid WordPress asking for FTP details every time I wanted to upgrade a plugin*
define('FTP_HOST', 'ftp.yoursite.com');define('FTP_USER', 'Your_FTP_Username');define('FTP_PASS', 'Your_FTP_password');//*If you can use a SSL connection set this to true*define('FTP_SSL', true);Removing a LVM Volume Group in Linux
[root@host1Z1 ~]# vgdisplay
— Volume group —
VG Name vol_grp1
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 165
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 10
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 839.84 GiB
PE Size 4.00 MiB
Total PE 214999
Alloc PE / Size 212480 / 830.00 GiB
Free PE / Size 2519 / 9.84 GiB
VG UUID FOtjrl-D7bL-WH71-Ls55-fDEu-7es3-mjkhAu
# lvmdiskscan
/dev/ram0 [ 16.00 MiB]
/dev/sda [ 931.51 GiB]
/dev/ram1 [ 16.00 MiB]
/dev/vol_grp1/vs1003 [ 120.00 GiB]
/dev/ram2 [ 16.00 MiB]
/dev/ram3 [ 16.00 MiB]
/dev/vol_grp1/nteraabb9q [ 120.00 GiB]
/dev/ram4 [ 16.00 MiB]
/dev/vol_grp1/vs1013 [ 120.00 GiB]
/dev/ram5 [ 16.00 MiB]
/dev/ram6 [ 16.00 MiB]
/dev/vol_grp1/vs1014 [ 60.00 GiB]
/dev/ram7 [ 16.00 MiB]
/dev/ram8 [ 16.00 MiB]
/dev/vol_grp1/ntsrmdeedm [ 60.00 GiB]
/dev/ram9 [ 16.00 MiB]
/dev/vol_grp1/vs1015 [ 210.00 GiB]
/dev/ram10 [ 16.00 MiB]
/dev/ram11 [ 16.00 MiB]
/dev/vol_grp1/vs1016 [ 150.00 GiB]
/dev/ram12 [ 16.00 MiB]
/dev/ram13 [ 16.00 MiB]
/dev/ram14 [ 16.00 MiB]
/dev/ram15 [ 16.00 MiB]
/dev/vol_grp1/vs1017 [ 70.00 GiB]
/dev/sdb1 [ 78.12 GiB]
/dev/sdb2 [ 839.84 GiB] LVM physical volume
/dev/sdb3 [ 7.81 GiB]
3 disks
24 partitions
0 LVM physical volume whole disks
1 LVM physical volume
[root@host1AZ ~]# lvscan
ACTIVE Original ‘/dev/vol_grp1/vs1003’ [120.00 GiB] inherit
ACTIVE ‘/dev/vol_grp1/vs1013’ [120.00 GiB] inherit
ACTIVE Original ‘/dev/vol_grp1/vs1014’ [60.00 GiB] inherit
ACTIVE ‘/dev/vol_grp1/vs1015’ [210.00 GiB] inherit
inactive Original ‘/dev/vol_grp1/vs1016’ [150.00 GiB] inherit
ACTIVE Snapshot ‘/dev/vol_grp1/ntsrmdeedm’ [25.00 GiB] inherit
ACTIVE Snapshot ‘/dev/vol_grp1/nteraabb9q’ [25.00 GiB] inherit
ACTIVE ‘/dev/vol_grp1/vs1017’ [70.00 GiB] inherit
inactive Snapshot ‘/dev/vol_grp1/ntdraalemj’ [25.00 GiB] inherit
inactive Snapshot ‘/dev/vol_grp1/nt0ymc1zi2’ [25.00 GiB] inherit
vgchange -ay
10 logical volume(s) in volume group “vol_grp1” now active
[root@host11Z ~]# lvchange -an /dev/vol_grp1/vs1015
[root@host144 ~]# lvremove /dev/vol_grp1/vs1015
Logical volume “vs1015” successfully removed
[root@host12Z ~]# vgdisplay
— Volume group —
VG Name vol_grp1
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 166
VG Access read/write
VG Status resizable
MAX LV 0
WordPress login brute force
Facing issues with bruteforce on wp-login page in wordpress ?
You can stop it using below method,
copy paste the below code in httpd.conf and restart httpd
xx.xx.xx.xx is the IP address where you can add your own IP address to be able to access wp-login
<FilesMatch wp-login.php> Order Allow,Deny Allow from xx.xx.xx.xx Deny from all </FilesMatch>
MX Logic blocking my mails with “554 Denied CS [*.mxlogic.net]“?
Your mails are blocked with the error message “554 Denied [CS] [*.mxlogic.net] (Mode: normal) (in reply to end of DATA command)”
What does it mean?
The mail was rejected by Mxlogic / Mcafee because of the content of the message.
Try using different message
Fatal error: Cannot make static method SGL_FrontController::run() non static in class RVSWebInit in
If you are facing issues with rvsitebuilder on cpanel server with error
“Fatal error: Cannot make static method SGL_FrontController::run() non static in class RVSWebInit in”
Run the below commands to fix it
perl /usr/local/cpanel/whostmgr/docroot/cgi/rvsitebuilderinstaller/autoinstaller.cgi –force=rvseagullmod
Then run update RVSitebuilder again.
perl /usr/local/cpanel/whostmgr/docroot/cgi/rvsitebuilderinstaller/autoinstaller.cgi –force=rvsitebuilder
Now republish the website, the error will be fixed
Disable directory browsing linux
To disable the directory browsing in account you need to do the below steps
# cd to the directory you want to disable directory browsing
in my case it was
#cd /home/online/public_html/images
create a new file .htaccess
# vi .htaccess
paste the below code in .htaccess
Options -Indexes
save file and exit
Now directory browsing is disabled
Amazon SES Request Expired, it must be within 300secs/of server time.
While using Amazon Simple Email Service, sometimes we encounter this error message:
” AWS Error Code: RequestExpired, AWS Error Message: Request timestamp: Sun, 13 Mar 2011 06:10:27 GMT expired. It must be within 300 secs/ of server time.”
This error probably means that Amazon SES time differs from your system clock time. If you’re using the command-line tools then you may need to adjust your system clock to match Amazon SES’s clock, which is synchronized with UTC.
If you’re using a linux system try this:
Fixed!!
Now you can easily send emails using SES.
