So i have been doing a hardware upgrade, and during the migration of the accounts, the target server named zone files got polluted with stuff like this:
; 86400 ;refresh ; Previous value removed by cPanel transfer auto-merge on 20150804093325 GMT
; 7200 ;retry ; Previous value removed by cPanel transfer auto-merge on 20150804093325 GMT
; 3600000 ;expire ; Previous value removed by cPanel transfer auto-merge on 20150804093325 GMT
; 86400 ) ; Previous value removed by cPanel transfer auto-merge on 20150804093325 GMT
In order to clean things up, you can do something like this:
1 – backup your named folder : cd /var;tar czf named.tgz named
2 – cd /var/named
perl -i.bak -ne ‘next if (/^; .+ ; Previous value removed by cPanel transfer auto-merge on/); print;’ /var/named/*.db
Voila! Things should be clean.
So, today i had this guy that added some domain, a subdomain and then after removing, he wanted to add it once more, but got the error below:
Error from domain wrapper: Domain already exists, it was not added.
This means that after the deletion, there have been some bits and pieces of info that got left over at deletion. Doesn’t happen that often but here’s what you can do to fix it: (info provided by Tristan at the cPanel forums)
You would want to check the following locations:
Any of the above if it has traces of the subdomain will cause the subdomain to continue to be considered existing on the system. Simply make a copy of the file you are editing and then remove the subdomain. For the /var/cpanel/userdata/username/sub.maindomain.com file, simply move the file out of the way. For the /var/named/maindomain.com.db file, you could edit it in WHM > Edit a DNS zone if the subdomain is still there rather than edit that file directly.
If you did find the subdomain listed in any of the /var/cpanel/userdata/username files, you would need to run the following commands after removing it in the main file there and moving the sub.maindomain.com file there:
/scripts/rebuildhttpdconf /etc/init.d/httpd restart
You would also likely want to run this script after that or possibly after editing /var/cpanel/users/username file:
If you directly edited the /var/named/maindomain.com.db file rather than editing it in WHM > Edit a DNS Zone, you’d need to run this command:
In all of the above, username is the cPanel username, maindomain.com is the main domain name, andsub.maindomain.com is the subdomain name.
For me the problem was that /var/cpanel/users/username had 2 lines referring to the old domain. Removed those, updated userdomains as instructed, then rebuilt the httpd.conf, reload apache and there you go.
I just got a customer that needs both php 5.3 and php 5.2 in the server for various reasons, so here’s how it works:
1 – You need to compile php5.2 from EasyApache
2 – mkdir /usr/local/buildphp53/ ; cd /usr/local/buildphp53/ ; wget http://cz2.php.net/get/php-5.3.27.tar.gz/from/us1.php.net/mirror ; tar zxf php-5.3.27.tar.gz ; cd php-5.3.27/
3 – Modify the configure line below to suit you:
./configure –enable-bcmath \
4 – make && make install
5 – Go to Apache configuration in WHM, and edit /usr/local/apache/conf/includes/pre_virtualhost_global.conf
Add the lines below, save and restart apache.
Action application/x-httpd-php53 /cgi-sys/php53
AddType application/x-httpd-php53 .php53
6 – Have apache skip the htaccess scan and remove mine types:
7 – Create a new file and add the lines below to it: /usr/local/cpanel/cgi-sys/php53
8 – Permissions:
chown root:wheel /usr/local/cpanel/cgi-sys/php53
chmod +x /usr/local/cpanel/cgi-sys/php53
9 – Linking:
ln -s /usr/local/php53/bin/php-cgi /usr/local/bin/php53
10 – php.ini:
mv /usr/local/buildphp53/php-5.3.27/php.ini-production /usr/local/php53/lib/php.ini
Running php 5.3 :
Add this into a .htaccess file located in the public_html folder in the user’s account that you want it to run on.
AddHandler application/x-httpd-php53 .php
I am just setting a new server up, and i upgraded apache first. Now i went to upgrade MySQL to 5.5, but when i am going in the interface, it says:
WARNING: A running easyapache process was detected. Please wait for easyapache to finish before attempting to upgrade MySQL.
If you are certain that the easyapache is no longer running, you may restart the MySQL upgrade by clicking the following button.
The “Ignore current upgrade button” is not working. What do we do?
What you can do, is to run:
ps aux | grep easyapache
If it doesn’t return any process running, then go delete the following file:
Daca folosesti cPanel si DNS clustering atunci ar trebui sa fii un pic fericit. Versiunea 11.30.16, lansata ieri, contine un fix la care am lucrat cu ze cPanel techs in ultimele 5 zile 🙂
DNS cluster nu sincroniza corect zonele, iar daca dadeai manual sync zones, se termina relatia de trust intre servere, si trebuia dat enable manual. Dar dupa 10 20 minute, relatia de trust crapa din nou.
Fixed & njoy 🙂
After migrating accounts to a new cPanel server, i noticed that all my accounts quota shows as unlimited.
As a solution, i had to run /scripts/fixquotas, but i got the following error message :
Unable to determine filesystems with quotas enabled
The problem here, usually seems to occur on FreeBSD systems, and it’s related to the file /etc/fstab.quota missing, so in order to fix that, you need to do:
And voila !
Installing Default Quota Databases……Done
Updating Quota Files……
*** Checking user quotas for /dev/mirror/gm0s1e (/home)
/home: unknown uid: 501
/home: unknown uid: 1000
/home: unknown uid: 106
/home: unknown uid: 146
/home: unknown uid: 12475
/home: unknown uid: 10090
/home: unknown uid: 100
/home: unknown uid: 502
/home: unknown uid: 500
/home: unknown uid: 1034
/home: unknown uid: 2525
/home: unknown uid: 10155
/home: unknown uid: 10008
/home: unknown uid: 2001
/home: unknown uid: 1023
/home: unknown uid: 31978
/home: unknown uid: 222
/home: unknown uid: 203
/home: unknown uid: 24032
If you want to remove an ip address in cPanel, and sometimes the remove button is not there, just edit the file /etc/ips, remove the ip address in question, and then do a restart of the system aliases.
This will work on cPanel / linux/centos
Should save you some headaches.
Aseara am dat drumul la o versiune noua de EVOPanel, si bineinteles cum era de asteptat nu se poate sa nu decurga totul lipsit de incidente, dar macar functia delete works :))
BogdaniQ: nu inteleg cum le-a impartit sistemu asta a lu radu
Eu: trebea sa ii adune
Eu: pe aia cu mail la fel
Eu: in clients id
Eu: da nah
BogdaniQ: someru baiatu: un ident onix
someru baiatu: ala lam sters
someru baiatu: atata tot
Me Bogdan: dude
Me Bogdan: wtf
Me Bogdan: acolo ii aveai pe toti
Me Bogdan: erau grupati cu acelasi mail
Me Bogdan: ai sters tot resellerul
Eu: mai apar fuckups
BogdaniQ: inca unu pe lista la recuperat
Eu: i-au picat alea
Eu: de pe mirc
Eu: sau bncurile si cacaturile mai is in picioare
BogdaniQ: da i-a picat tot
BogdaniQ: at least the delete function works
Eu: pai asta vroiam eu sa zic
Eu: ce-am invatat noi de aici?
Eu: ca functia delete din cpanel nu are probleme
Fantastico is not installed at the default location /usr/local/cpanel/3rdparty/fantastico. Either move the Fantastico directory from it’s current location to /usr/local/cpanel/3rdparty/fantastico OR enable ioncube loaders in WHM -> Tweak settings
Okay, this error usually comes on a brand new installed server. If you got this error, i have an easy fix for you as usual:
Go to WHM -> Tweak settings -> loaders >> enable the Ioncube Loader.
Login as root to the server, and type:
Log on to any account on cpanel, fantastico should be working now.
Doamne ce nasol e sa iti fie lene. Nu stiu de ce de vreo 2 zile m-a pocnit o lene … n-am facut mai nimic, nu vin idei … this sucks. Well mainly treaba suge pentru ca n-am primit nici un info de la nici unul din cei 2 designeri, si pentru ca astept finalizarea la cpanelul de la xsbackup 🙂 Care btw is working great.
curatenie in blogroll
nu mai am alte idei :))
needz moar coffee