LogicSupport Blog

February 19, 2010

Smarterstats

Filed under: Technical — Tags: logicsupport review, smarterstats, smartertools, technical support, windows — visiondream3 @ 4:22 am

SmarterStats is a Web log analytics and SEO software provided by www.smartertools.com that provides complete management and control of website statistics and SEO marketing efforts in a single application. SmarterStats helps businesses make informed decisions that drive them toward quantifiable objectives for website traffic and sales.

Issue with smarterstats account, especially after a migration is not uncommon. Sometimes prompting a re-import and resetting of the entire log files. Recently we faced an issue with one of the smarterstats account and it kept displaying the error “Information about the last 7 days is not available in your statistics. Logs have been imported for 10/1/2008 through 10/31/2009.”

Well, every time the admin attempt to re-import the log files, it gave a ‘cannot read’ error.

Upon checking, he came to know that the settings match exactly as that of a working domain account, hence he wasn’t able to identify the error.

‘Path to the log file’ is what confused the admin. Though the log files were in the path /x/y/domainname/, almost all of the working domains showed the settings as /x/y. Missing the logic, the admin kept on trying with the /x/y base directory until he finally decided to re-import using the path /x/y/domainname/, which worked finally.

Just a tip for all those who troubleshoot by doing a comparison of settings, please keep your senses open for the obvious logic and do not be misguided by an incorrect interface provided by the programmer.

Comments (0)

February 10, 2010

PCI compliance

Filed under: General — Tags: logicsupport review, PCI compliance, server management, technical support — visiondream3 @ 4:49 am

The Payment Card Industry Data Security Standard is a worldwide information security standard assembled by the Payment Card Industry Security Standards Council (PCI SSC). The standard was created to help organizations that process card payments prevent credit card fraud through increased controls around data and its exposure to compromise. The standard applies to all organizations which hold, process, or pass cardholder information from any card branded with the logo of one of the card brands.

If you are a host who sell business critical web environment that process credit card data, you need to know how to help your customers acquire compliance. LogicSupport helps their customers acquire PCI compliance by directly working with their data centers and any approved scan vendors ( ASV). Only certified ASVs can perform PCI-sanctioned compliance audits.

A detailed ASV list is given below for reference :-

https://www.pcisecuritystandards.org/pdfs/asv_report.html

Most of these ASVs provide you a report to work on or help you to clear them by providing technical assistance. If at any point, you need consultation with a security expert, you could always approach us and we will be able to guide you with our experience. We can even assist you by providing engineers who are experts at helping you clear the vulnerable scores.

An ASV bases the audit result on the Common Vulnerability Scoring System (CVSS), Version 2, score that is calculated for every vulnerability. Scores range from 0 to 10.0, with 4.0 or higher indicating failure to comply with PCI standards.

Any asset that contains at least one vulnerability with CVSS score of 4.0 or higher is considered non-compliant. And, if at least one asset is non-compliant, the entire organization is considered to be non-compliant.

Also, any vulnerability that exposes an asset to XSS or SQL injection indicates failure to comply with PCI standards, regardless of CVSS score.

The CVSS system rates all vulnerabilities on a scale of 0.0 to 10.0 with 10.0 representing the greatest security risk. A ranking of 4.0 or higher indicates failure to comply with PCI standards.

A moderate vulnerability, which ranges from 0.0 to 3.9 on the CVSS system can only be exploited locally and requires authentication. A successful attacker has little or no access to unrestricted information, cannot destroy or corrupt information, and cannot cause outages on any systems. Examples include default or guessable SNMP community names and the OpenSSL PRNG Internal State Discovery vulnerability.

A severe vulnerability, which ranges from 4.0 to 6.9 on the CVSS system, can be exploited with a moderate level of hacking experience and may or may not require authentication. A successful attacker has partial access to restricted information, can destroy some information, and can disable individual target systems on a network. Examples include Anonymous FTP Writeable and Weak LAN Manager hashing permitted.

A critical vulnerability, which ranges from 7.0 and 10.0 on the CVSS system, can be exploited with easy access and requires little or no authentication. A successful attacker has access to confidential information, can corrupt or delete data, and can cause a system outage. Examples include the ability of anonymous users can obtain a Windows password policy.

Though compliance is not the final word for web security, it will go a long way in helping our payments and card data secure on the web.

Comments (1)

February 2, 2010

Powerdns

Filed under: Technical — Tags: logicsupport, powerdns — admin @ 3:16 am

Powerdns uses mysql database to retrieve domain information. Therefore, it is very important to check for the following details while trouble shooting issues with powerdns.

I will cite the example below from an lpanel server :-

As always, you need to chroot to the domain’s environment.

chroot /home/domain.com/runtime_layeredpanel/

Go to /etc/init.d

vi lpanel

You will see an try similar to this :

/etc/init.d/pdns start

vi /etc/init.d/pdns

If you do a simple locate,

locate powerdns | less

You see that the configuration files lie in /etc/powerdns/

cd /etc/powerdns

You can see the main configuration file and the include directory.

pdns.conf pdns.d

vi pdns.conf

#################################
# launch Which backends to launch and order to query them in
#
launch=gmysql

#################################

The section above decides which backend database powerdns uses to query the data. In the above example, it uses mysql server. It can be ‘bind’ too.

To get the mysql connection details, open the pdns.d/pdns.local file

The first section shows the database connectivity details :

gmysql-dbname=databasename
gmysql-socket=/var/run/mysqld/mysqld.sock
gmysql-user=username
gmysql-password=password

Please make sure the above username and passowrd combination works by testing it :

mysql -u username -p
password: [type the password above]

If it doesn’t work, make sure you login as mysql root to give necessary privileges for the user to allow access to the databasename.

This can be done using the query ‘grant all privileges on databasename.* to username@localhost identified by ‘password’
after logging in as root user.

Once you fix the database problem, pdns server will not have issues sending back answers to your dns queries.

Technical review department
LogicSupport.com

Comments (0)

January 31, 2010

Choose your customers

Filed under: General — Tags: logicsupport review, prelovac — visiondream3 @ 1:40 pm

I’ve always had people asking me what is the secret behind retaining customers long term. LogicSupport has been in business for over 6 years now, and serviced several customers since its inception. I am so glad to mention here that some of our first time customers are still in business with us. It is an amazing achievement for our team because this trust is something we have earned over the years and there were certainly no shortcuts to achieve this.

As a webhost or any business for that matter, choosing your customers can have a profound effect in running your business. If done right, it can do a world of good to your future business and if done wrong, there is no worse mistake you can possibly make. They try to hack your data, gain illegal entry and even sabotage your entire business. I know that being able to choose your customers is a luxury these days, when you are trying your best to stay ahead of the competition. I also know that choosing alone do not win long term clients, it takes a lot of hard work and followup.

A retrospection in this regard is the order of the day in the wake of a customer who tried to ruin our business not long ago, after a series of threats and black mailing incident. Vladimir from prelovac.com signed up as a regular customer through our server management promotion program. He came to us with one big bargain, promising a review if we do our job well. Little did I know that he was going to use this tool to black mail us and get the work done without making payment.

His server security was tightened with all the update sent to him with relevant details. He went through the server security list and spotted, a feature listed in the website was not performed in the security report. It is well known that certain security features are incompatible with certain server environments. In such cases, we will only install what is relevant to the prevailing server environment. He immediately opened a ticket with us in our support queue demanding the missing module to be installed. The tech on duty explained to him that the installations were carried out after checking compatibility, but he demanded the changes should be updated immediately.

Since he needed to see the change anyway, the admin went ahead with changing the settings of the web server. The admin performed the installation and finally completed it with the changed settings. Client finally saw that the conflicting settings made some of his existing sites to not load as desired. All those changes had to be reverted and we did it as quickly as we could. As anyone in the hosting security management knows, web server recompilations involve some downtime and when the customer approved this reset, there was very little we could do. I tried to call him several times and keep in touch with him all through the matter, but he either never picked the call or it went to his voice mailbox. I even sent him an apology on behalf of the admin, just to make sure the client understands why the admin carried out the re-installation of the web server, only to learn they were misinterpreted.

He demanded that he should be issued a refund since he wasn’t happy with the service. We issued a 100% refund as per our customer satisfaction guarantee policy, though we know the server underwent all the required security setup.

I got an email the next day, asking me to compensate further for the downtime, with $2000 worth of damages and one year of free service, failing which he will write a public review and wreck our business. Why would be ask for one year of free service if he doubted our abilities? I tried to call him again trying my best to make sure things remain cordial. He never picked my calls.

I sensed the matter was out of hand and that he was really trying to get free work done and was resorting to blackmail. I refused to give free service or any further servicing of his server and offered to cancel immediately, to which no response was arrived.

As he went public, a reputed forum pulled down his thread after they realized he was trying to drive traffic to his personal blog prelovac.com. I gave my reply in one of the forums about his intentions but he never came up with a response to the community members, instead he decided to post the review in his personal blog with comments disallowed.

Let this story be a lesson for anyone who is signing up customers in a frenzy. Please know your customer before you take them in. It is best to cross check your customer history, especially of those who signup for your smallest plans. They may simply be seeking an entry to your business process, but their intentions may be different. I have seen hackers who signup for start-up plans and eventually screw up the entire server and the hosting owner’s business. Please try to stay away from them…

Comments (2)

December 12, 2009

Configuring CSF in a VPS

Filed under: VPS — Tags: Configuring CSF in a VPS, csf, logicsupport review, server management, technical support, VPS — Manjula @ 7:42 am

You may get the following error while restarting csf on a vps server

Error: iptables command [/sbin/iptables -v -A LOGDROPIN -p tcp -m limit --limit 30/m --limit-burst 5 -j LOG --log-prefix 'Firewall: *TCP_IN Blocked* '] failed, at line 280

In a vps (openvz or Virtuzzo) the csf configuration is something different. Lets see how we can make csf work with vps .

Before starting the installation of csf, you should confirm the following modules are installed on the main VPS.

ipt_conntrack

ipt_LOG

ipt_owner

ipt_state

ip_conntrack_ftp

iptable_filter

You can confirm whether these modules are already loaded using

# lsmod |grep -i <module-name>

If its not installed you can install this using modprob

modprob ipt_conntrack

After that you should add these modules to the iptables configuration as follows

# vi /etc/sysconfig/iptables-config

IPTABLES_MODULES=”ipt_conntrack ipt_LOG ipt_owner ipt_state ip_conntrack_ftp”

You need to edit the vps client node configuration file as follows ( example node is 101 )

# vi /etc/sysconfig/vz-scripts/101.conf

IPTABLES=”iptable_filter iptable_mangle ipt_limit ipt_multiport ipt_tos ipt_TOS ipt_REJECT ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_LOG ipt_length ip_conntrack ipt_state iptable_nat ip_nat_ftp ipt_owner ip_conntrack_ftp”

Restart the client node .

# vzctl restart 101

Now login to your client node and install csf . Before restarting csf let us edit the configuration file .

# /etc/csf/csf.conf

ETH_DEVICE = “venet0″ # from ifconfig you will get the ethernet device
MONOLITHIC_KERNEL = “1″
VERBOSE = “0″

Restart csf

# csf -r

If you have followed the above steps properly then it should start without any errors . In case if you get error , some of the modules I find necessary are

ipt_MASQUERADE

ipt_helper

ipt_REDIRECT

ipt_state

ipt_TCPMSS

ipt_LOG

ipt_SAME

ipt_TOS

iptable_nat

ipt_length

ipt_tcpmss

iptable_mangle

ipt_limit

ipt_tos

iptable_filter

ipt_helper

ipt_tos

ipt_ttl

ipt_REJECT

ip_conntrack

ip_multiport

ip_nat_ftp

ipt_owner

ipt_recent

ipt_REDIRECT

Now if you can start csf without any error but it blocks all connections to site when enabled. If you disable csf it starts working . If so , make sure that you have opened all ports in csf configuration file and then execute the below commands from the client node (101 in our case)

iptables -A INPUT -i venet0 -j ACCEPT

iptables -A OUTPUT -o venet0 -j ACCEPT

iptables -A FORWARD -j ACCEPT -p all -s 0/0 -i venet0

iptables -A FORWARD -j ACCEPT -p all -s 0/0 -o venet0

Or else you can add the above iptables rules to ” vi /etc/csf/csfpre.sh ” and restart csf

Other issues related to csf in a vps can be caused by “numiptent”

Run the below command from your vps node (101) and see if there are any failcounts .

cat /proc/user_beancounters

numiptent should be set to at least 1000

You can increase the values of these parameters as discussed here .

Comments (0)

November 30, 2009

How to Re-install Mysql on Freebsd

Filed under: Cpanel — Tags: freebsd, logicsupport review, mysql, server management, technical support — Manjula @ 9:01 am

Say Mysql has completely crashed on your server and while restarting it is showing the below error :-

/usr/local/bin/mysqladmin: connect to server at ‘localhost’ failed error: ‘Can’t connect to local MySQL server through socket ‘/tmp/mysql.sock’ (61)’ Check that mysqld is running and that the socket: ‘/tmp/mysql.sock’ exists! mysql has failed, please contact the sysadmin (result was “mysql has failed”).

And from the mysql error logs you are getting

/libexec/ld-elf.so.1: /lib/libc.so.7: version FBSD_1.1 required by /usr/local/libexec/mysqld not found

If you have tried all other common fixes then lets now move on to mysql-reinstall.

The steps to reinstall mysql from ports on a freebsd – cpanel servers are as follows.

# cd /usr/ports/databases/

# pkg_info | grep -i mysql

It should display information on mysql packages , something like

bsdpan-DBD-mysql-4.013 DBD::mysql – MySQL driver for the Perl5 Database Interface

mysql-client-5.0.87 Multithreaded SQL database (client)

mysql-server-5.0.87 Multithreaded SQL database (server)

cd /usr/ports/databases/mysql50-server (see which version you have)

make clean

make

make deinstall

make reinstall

/usr/local/etc/rc.d/mysql-server start

/usr/local/etc/rc.d/mysql-server.sh start

Check if mysql is running

# ps wwaux | grep mysql

Make sure that you have given the symlink

# ln -s /var/db/mysql/mysql.sock /tmp

If it still shows down try to re-set the mysql password and restart mysql again .

Comments (3)

Phpmyadmin shows ” No Database “

Filed under: Cpanel — Tags: logicsupport review, no database, phpmyadmin, server management, technical support — Manjula @ 8:48 am

While accessing Phpmyadmin via Cpanel , under databases it shows ” No Database ” . But you can see the databases while accessing through WHM.

This can be due to many reasons . One of the reason I found is because the user doesn’t have SHOW DATABASES privilege .

From the server my.cnf remove the line

skip-show-database

Restart Mysql

Try to access Phpmyadmin .

About skip-show-database from Mysql Reference Manual .

–skip-show-database

With this option, the SHOW DATABASES statement is allowed only to users who have the SHOW DATABASES privilege, and the statement displays all database names. Without this option, SHOW DATABASES is allowed to all users, but displays each database name only if the user has the SHOW DATABASES privilege or some privilege for the database. Note that any global privilege is considered a privilege for the database.

Comments (0)

Unable to fork: Cannot allocate memory

Filed under: VPS — Tags: logicsupport review, server management, technical support, Unable to fork: Cannot allocate memory, VPS — Manjula @ 8:36 am

While logging to a VPS from the host server(main node) , you see the message:

Unable to fork: Cannot allocate memory

This usually occurs when VPS is running out of resources especially RAM. Restarting the vps may be a temporary fix which allows you to enter the server . But it prevents executing some commands throwing the same error message .

You can increase privvmpages and kmemsize values for the VPS in order to solve the issue .From the client node in order to see each resource , run the command

cat /proc/user_beancounters

It has five values associated with it: current usage, maximum usage , barrier, limit, and fail counter. The meaning of barrier and limit is parameter-dependent; in short, those can be thought of as a soft limit and a hard limit. If any resource hits the limit, the fail counter for it is increased. This allows the owner to detect problems by monitoring /proc/user_beancounters in the container.

uid resource held maxheld barrier limit failcnt

101: kmemsize 5741113 8347532 2147483646 2147483646 453225323642

privvmpages 33656 44989 98304 98304 106507

In order to increase the value of the two parameters edit the below file from the main node

/etc/sysconfig/vz-scripts/101.conf ( 101 is my vps node)

You can see the value as below

PRIVVMPAGES=”98304:98304″

Increase the value as you need

PRIVVMPAGES=”100000:100000″

Restart your vps after the changes .

# vzctl restart 101

You can also raise the limit as sown below from the host node .

vzctl set 101 –privvmpages 100000:100000 –save

vzctl restart 101

kmemsize

Size of unswappable memory in bytes, allocated by the operating system kernel.

privvmpages

Memory allocation limit. Privvmpages parameter allows controlling the amount of memory allocated by applications.

Comments (4)

Unable to open pty: No such file or directory

Filed under: VPS — Tags: logicsupport review, server management, technical support, Unable to open pty: No such file or directory, VPS — Manjula @ 8:12 am

You may receive the following message on entering a VPS:

# vzctl enter 101

enter into VE 101 failed

Unable to open pty: No such file or directory

The reason behind this is the missing tty/pty files . You can create it using the MAKEDEV program, execute the following commands on the host server ( main node ).

# vzctl exec VEID /sbin/MAKEDEV tty
# vzctl exec VEID /sbin/MAKEDEV pty

Replace VEID with your actual vps id . In our example its 101 .

Restart vps .

#vzctl restart VEID

Thats a temporary fix. To Fix this issue permanently follow the below steps after entering to your vps client node (101 in our case) .

1) #vzctl enter VEID

2) Edit the file /etc/rc.sysinit

3) Comment the line
#/sbin/start_udev

4) Add the following lines after /sbin/start_udev:
/sbin/MAKEDEV tty
/sbin/MAKEDEV pty

5) Reboot your VPS client node .
vzctl restart VEID

You can also access the file /etc/rc.sysinit for the node 101 from the main VPS node . It should be from /vz/private/VEID/etc/rc.sysinit .

You can also try the below steps by updating the startup files

# vzctl exec VEID update-rc.d -f udev remove
# vzctl restart veid

Above fixes may not work for ubuntu servers . In that case you can try the below command

# vzctl exec VEID ‘dpkg –force-depends –purge udev’

Comments (3)

November 27, 2009

How to install software’s using Plesk Autoinstaller

Filed under: Plesk — Tags: autoinstaller, logicsupport review, plesk, server management, technical support, webmail — Manjula @ 5:50 am

Plesk Auto-Installer is a utility used by Plesk control panel for retrieving and installing software updates and upgrades . This article describes how to install software’s from back-end .

Lets see how to install webmail using autoinstaller . Control Panel shows webmail is not installed and is grayed out .

1) Ssh to your server .

2) Search for the binary autoinstaller. Most probably it should be under /usr/local/psa/bin/

# cd /usr/local/psa/bin/

3) Check for various options available .

[root@admin /usr/local/psa/admin/bin]# ./autoinstaller –help

It should list something like

Usage: parallels_installer [OPTIONS]

Product and operating system updates source:

–source <URL or absolute path to .inf3 file>

URL (http://your-mirror.com/) or absolute path

to an .inf3 file on your hard disk.

Examples:

‘http://autoinstall-ctp.plesk.com/’

‘/root/parallels/PSA_8.1.0/plesk-8.1.0-deb3.1-i386.inf3′

–disable-plesk-sys-updates

Do not use operating system updates shipped

with Plesk and other product(s)

–add-source <type,priority,url[,username,environment variable with password]>

Specify the additional source of packages.

You can specify either of the following source

types: repodata, directory.

Examples:

‘repomd,500,http://download.fedora.redhat.com/fedora/updates/2/i386′

‘directory,500,/mnt/updates’

–show-additional-source-types

Show possible source types for –add-source

–show-additional-sources

Show the additional sources you configured

Proxy server options:

–proxy-host <host> When using a proxy server or a firewall, use this

option to specify the proxy server’s domain name

or IP address.

–proxy-port <port> Default port for connecting to proxy server is 3128.

If your proxy server uses a different port number,

you should specify it using this option.

–proxy-user <user> Set username for authorization at the proxy server

–proxy-password <password>

Set password for authorization at the proxy server

Select a product version:

–select-product-id <product id>

Select the product name

(‘plesk’ (by default) or ’sitebuilder’)

–select-release-id <release id>

Use this option to specify the product version that you

want to install or whose properties you want to view.

–select-release-latest

Select the latest product version available for

your operating system

–select-release-current

Select the same product version as the one installed

on your machine

Options for selecting components:

–install-component <component id>

Install the product component with specified

identifier

–install-everything

Install all components of the selected product version

–upgrade-installed-components

Upgrade all installed components of the selected

product version

Installer options:

–allow-kernel-install

Allow kernel upgrade. By default, the auto-installer

does not make any kernel upgrades.

Note that auto-installer installs new kernels to the system, leaving the older

kernel aside so that you can revert to it at any time.

–ignore-key-errors

Allow upgrading product even if upgrade of the license

key fails.

–use-existing-ports

FreeBSD specific option

(You may want to use this to prepare the machine for installing the product.)

–no-space-check Install packages even if you are low on disk space.

Use the following options for selecting and installing packages,

and setting up mirrors:

–show-releases Specify this option to retrieve a list of available

product versions for the operating system where the

auto-installer is executed. You will be given a list

of release identifiers and release descriptions.

The release identifiers are what you will need to

deal with.

–show-all-releases This option shows all product versions available from

the official product updates server.

–show-os-list Use this option to find out on which operating systems

the product version you selected can run.

–show-components Use this option to obtain the information on the

components available for the selected product version.

Components descriptions and names will be displayed.

The component names are what you need to specify when

selecting additional components to install.

–show-packages Show additional packages required for installation of

selected components.

–mirror-os <id> This option activates the mirroring feature in

auto-installer. If you want to mirror product versions

for different operating systems, you should specify

this option per each operating system.

–install-package <name>

Install package with specified name

Options for interaction with other software:

–enable-xml-output Specify this option to have all output of

auto-installer in XML format. Note that this option

disallows auto-installer to report errors by exit code.

Exit code is always zero and all errors are reported

inside XML output.

–query-status Use this option to find out if auto-installer is

active. This will return either an exit code

(0 – auto-installer is idle, 1 – auto-installer is

running and busy), or XML-formatted output.

–check-updates Specify this option to check the updates server for

updates applicable to your product version.

A list of releases that you can update or upgrade to

will be shown.

–no-daemon Perform installation process in the foreground

–web-interface Opens the Web-based installation wizard in

a Web browser.

–ssl-cert <file.pem>

Specifies the path to the SSL certificate file that

should be used for securing connections.

–without-ssl Specifies that connections to the Web-based

installation wizard will not be secured.

FreeBSD specific options:

–cvsup-host <hostname>

Hostname of CVS server for retrieving updates for

FreeBSD ports

Override operating system detection results:

–override-os-name <arg>

Override detected operating system name

–override-os-vendor <arg>

Override detected operating system vendor

–override-os-version <arg>

Override detected operating system version

–override-os-arch <arg>

Override detected operating system architecture

–override-environment <arg>

Override detected environment

(possible values are ‘dedicated’, ‘vz’, ‘vserver’)

Interactive user interface options:

–no-clear Do not clear screen when moving between wizard’s pages

General options:

–target <dir> The directory where downloaded files must be stored.

–notify-email <email>

Use this option to have the auto-installer send you

status reports by e-mail. A successful completion

report includes a list of installed or upgraded

packages with a detailed log.

–truncate-log Clear log file on auto-installer start

–separate-log Use new log file for each start of auto-installer

–debug Turn on detailed output into log file

–version Show auto-installer’s version

–usage,

–help Show this help page

That clearly shows what does each option do .

You can see all the product versions using :-

[root@admin /usr/local/psa/admin/bin]# ./autoinstaller –show-all-releases

Downloading the file products.inf3: 100% done.

Downloading the file plesk.inf3: 10%..21%..30%..41%..50%..61%..70%..81%..90%..100% done.

Downloading the file ppsmbe.inf3: 76%..100% done.

Downloading the file sitebuilder.inf3: 15%..35%..55%..96%..100% done.

Downloading the file sso.inf3: 10%..24%..37%..51%..64%..78%..91%..100% done.

Downloading the file setemplates.inf3: 38%..87%..100% done.

— prod_id release_id (description) —

plesk PLESK_9_2_3 (Parallels Plesk Panel 9.2.3)

plesk PLESK_9_2_2 (Parallels Plesk Panel 9.2.2)

plesk PLESK_9_2_1 (Parallels Plesk Panel 9.2.1)

plesk PLESK_9_0_1 (Parallels Plesk Panel 9.0.1)

plesk PLESK_9_0_0 (Parallels Plesk Panel 9.0.0)

plesk PLESK_8_6_0 (Plesk 8.6.0)

plesk PLESK_7_5_4 (Plesk 7.5.4)

plesk PLESK_8_0_0 (Plesk 8.0.0)

plesk PLESK_8_0_1 (Plesk 8.0.1)

plesk PLESK_8_1_0 (Plesk 8.1.0)

plesk PLESK_8_1_1 (Plesk 8.1.1)

plesk PLESK_8_2_0 (Plesk 8.2.0)

plesk PLESK_8_2_1 (Plesk 8.2.1)

plesk PLESK_8_3_0 (Plesk 8.3.0)

plesk PLESK_8_4_0 (Plesk 8.4.0)

ppsmbe PPSMBE_10_0_0 (Parallels Small Business Panel 10.0.0)

sitebuilder SB_4_5_0 (Sitebuilder 4.5.0)

sso SSO_2_0 (SSO 2.0)

sso SSO_2_1 (SSO 2.1)

To retrieve a list of components for the “selected product version”, you can use

[root@admin /usr/local/psa/admin/bin]# ./autoinstaller –select-release-id PLESK_8_6_0 –show-components

Here I have selected product version as PLESK_8_6_0 Or else with the current release if I need to see what all components can be installed and what are already installed .

4 ) [root@admin /usr/local/psa/admin/bin]# ./autoinstaller –select-release-current –show-components

Downloading the file products.inf3: 100% done.

Downloading the file plesk.inf3: 10%..21%..30%..41%..50%..61%..70%..81%..90%..100% done.

Downloading the file ppsmbe.inf3: 33%..76%..100% done.

Downloading the file sitebuilder.inf3: 15%..35%..55%..96%..100% done.

Downloading the file sso.inf3: 10%..24%..37%..64%..78%..100% done.

Downloading the file setemplates.inf3: 38%..87%..100% done.

Checking for installed packages…

Downloading the file PSA_9.2.3/plesk-9.2.3-fr6.1-i386.inf3: 12%..21%..30%..44%..53%..71%..80%..93%..100% done.

Preparing ports for product installation:

Removing unnecessary packages from the system.

done

Preparing ports for product installation:

Deploying product ports…

Downloading the file PSA_9.2.3/dist-pkg-FreeBSD-6.1-i386/ports/ports-common.tar.gz: 10%..20%..30%..40%..50%..60%..70%..80%..90%..100% done.

Downloading the file PSA_9.2.3/dist-pkg-FreeBSD-6.1-i386/ports/psa-ports-9.2.3.tar.gz: 10%..20%..30%..40%..50%..60%..70%..80%..90%..100% done.

done

Re-installing port ’swsoft/ports-common’…done

Detecting installed product components.

base [up2date] – Base packages of Plesk

psa-autoinstaller [up2date] – Plesk Updater

postgresql [up2date] – PostgreSQL server support

vault [install] – Application vault packages

ppwse [install] – Plesk Professional Web Site Editor

api [up2date] – Plesk API [former Plesk Agent]

pmm-ded [install] – Plesk migration manager

sb-publish [install] – SiteBuilder publishing support for Plesk

sbm [install] – SiteBuilder module migration suite

miva [install] – Miva Empresa support

billing [install] – Plesk billing

mod-bw [install] – Bandwidth Limiter For Apache support (mod_bw)

asp [install] – Apache ASP support

java [install] – Tomcat Java Servlets support

mod_python [install] – Apache mod_python module

ruby [install] – Ruby on Rails support

php4 [install] – PHP4 support

php5 [up2date] – PHP5 support

qmail [up2date] – Qmail mailserver

postfix [install] – Postfix mailserver

psa-firewall [install] – Plesk Firewall module

psa-vpn [install] – Plesk VPN module

psa-fileserver [install] – Plesk Fileserver module and SMB file server package

sshterm [install] – SSHTerm – SSH Terminal java applet

watchdog [install] – Watchdog (System monitoring module)

mailman [up2date] – Mailman mailing list manager support

kav [install] – Kaspersky antivirus module

drweb [up2date] – Dr. Web antivirus

spamassassin [install] – SpamAssassin support

backup-ded [install] – Plesk Backup Manager

de-DE-locale [install] – German language pack

ja-JP-locale [install] – Japanese language pack

es-ES-locale [install] – Spanish language pack

ru-RU-locale [install] – Russian language pack

fr-FR-locale [install] – French language pack

it-IT-locale [install] – Italian language pack

zh-CN-locale [install] – Chinese language pack for China

zh-TW-locale [install] – Chinese language pack for Taiwan

nl-NL-locale [install] – Dutch language pack for Netherlands

horde [install] – Horde webmail support

atmail [install] – AtMail webmail support

If you want to install backup for the selected product version PLESK_8_6_0 , use

./autoinstaller –select-release-id PLESK_8_6_0 –install-component backup-ded

(Give the correct component name shown under show-components.It may vary)

Or for the current release if you need webmail

5) [root@admin /usr/local/psa/admin/bin]# ./autoinstaller –select-release-current –install-component horde

After this completes you should be able to access webmail .

More details on downloading the auto-installer binary can be found here .

P.S Before you start , always take the backup of plesk psa database , just in case if anything went wrong . ‘Better safe than sorry’

cd /var/lib/mysql

mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` psa > psabackup.sql

Comments (8)

Older Posts »

Recent Updates

Client Testimonials

February 19, 2010

Smarterstats

February 10, 2010

PCI compliance

February 2, 2010

Powerdns

January 31, 2010

Choose your customers

December 12, 2009

Configuring CSF in a VPS

November 30, 2009

How to Re-install Mysql on Freebsd

Phpmyadmin shows ” No Database “

Unable to fork: Cannot allocate memory

Unable to open pty: No such file or directory

November 27, 2009

How to install software’s using Plesk Autoinstaller

Category

Archives

Recent Posts

Meta