Software testing day

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: bai
Eu: initial
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
Eu: :))))))))))))))))
Eu: :))))))))))))))))
Eu: :))))))))))))))))
BogdaniQ: inca unu pe lista la recuperat
Eu: i-au picat alea
Eu: de pe mirc
Eu: ?
BogdaniQ: :))))))))))))))))
Eu: sau bncurile si cacaturile mai is in picioare
Eu: ?
BogdaniQ: da i-a picat tot
BogdaniQ: at least the delete function works
Eu: pai asta vroiam eu sa zic
Eu: :))))))))))))))))
Eu: ce-am invatat noi de aici?
Eu: ca functia delete din cpanel nu are probleme
Eu: :)))))))))))))))))

Fantastico is not installed at the default location

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.

Caldura mare shafule

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

HowTo :: enable FancyIndexing on Apache v2.x

IndexOptions controls the appearance of server generated directing listings, by adding icons, file descriptions, and so on. If Options Indexes is set, the Web server generates a directory listing when the Web server receives an HTTP request for a directory without an index.

First, the Web server looks in the requested directory for a file matching the names isted in the DirectoryIndex directive (usually, index.html). If an index.html file is not found, Apache HTTP Server creates an HTML directory listing of the requested directory. The appearance of this directory listing is controlled, in part, by the IndexOptions directive.

This means that a user can re-sort a directory listing by clicking on column headers. Another click on the same header will switch from ascending to descending order. FancyIndexing also shows different icons for different files, based upon file extensions.

The default configuration on a cPanel powered server turns off FancyIndexing. To enable this feature, do the following:

  1. Makse sure the file httpd-autoindex.conf exists in /etc/httpd/conf/extra directory
  2. Add the following directives to your /etc/httpd/conf/httpd.conf file:
      <IfModule mod_autoindex.c>
      IndexOptions FancyIndexing IconHeight=16 IconWidth=16
  3. Run this command to restart httpd:
    • /scripts/restartsrv httpd

DomainKeys on cPanel how to

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: [email protected]

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.

Upgrading PostgreSQL on Cpanel Server

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 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


    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.

“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.

Sorry, the nameserver ip cannot be removing since it is still registered with an ICANN register.

If any time this issue will pop up if on your cPanel server while modifying nameserver ip’s, do :

whm > tweak settings  ==> “Disable whois lookups for the nameserver IP manager.” <- tick this box.

Then you’re on your way

Fix OpenDNS Servers with cpanel

OpenDNS servers sunt o problema, load care nu e necesar pe server, si mi se pare ca se poate face si update la dns zones de catre persoane neautorizate, in zonele hostate pe serverul respectiv. Incercati, si daca aveti probleme, comment, si dau infos.


@ips = `ifconfig`;
chomp @ips;

print “\n\nacl \”trusted\” {\n”;
foreach my $line (@ips) {
if ($line =~ /inet addr:(\d+\.\d+\.\d+\.\d+)/) {
print ”        $1;\n”;
print “};\n\n”;
print “options {\n”;
print ”        directory \”/var/named\”;\n”;
print ”        dump-file \”/var/named/data/cache_dump.db\”;\n”;
print ”        statistics-file \”/var/named/data/named_stats.txt\”;\n”;
print ”        version \”not currently available\”;\n”;
print ”        allow-recursion { trusted; };\n”;
print ”        allow-notify { trusted; };\n”;
print ”        allow-transfer { trusted; };\n”;
print “};\n\n”

save thhe above text in file name

type perl >> out.txt

copy the data in the output in your named.conf

restart named.conf

for any bugs or trouple feel free to comment