Dev-mysql-maint error occurred during the installation of VHCS Control panel

Error message:

Can’t connect on ‘DBI:mysql:;localhost’ :Access denied for user ‘debian-sys-maint’@'localhost’ (using password: YES)

The issue occurring due to the absence of grant privilege (to the user dev-mysql-maint) on the databases.

You obtain details of "dev-mysql-maint" from /etc/mysql/debian.cnf.

One example is mentioned below:

# Automatically generated for Debian scripts. DO NOT TOUCH!
[client]
host = localhost
user = debian-sys-maint
password = 0nQp8g7pmupSbcpg
socket = /var/run/mysqld/mysqld.sock
[mysql_upgrade]
user = debian-sys-maint
password = 0nQp8g7pmupSbcpg
socket = /var/run/mysqld/mysqld.sock
basedir = /usr

You need to grant the privileges to dev-mysql-maint, according to the above information.

grant all privileges to *.* on 'dev-mysql-maint'@'localhost' identified by '0nQp8g7pmupSbcpg' with grant option;

Note: Modify the password according to the information in /etc/mysql/debian.cnf.

File manager login issue with VHCS control panel

Check the /etc/proftpd/modules.conf file and make sure that following LoadModule is mentioned in it.

LoadModule mod_sql.c

Modify the /etc/proftpd/proftpd.conf with the following details:

UseIPv6 off

Also include the following section in /etc/proftpd/proftpd.conf.


SQLBackend mysql
Include /etc/proftpd.conf


You need to disable (comment out) PostgresSQL Module in /etc/proftpd/modules.conf.

LoadModule mod_sql_postgres.c

Restart the proftpd.

KeySize error occurred during the installation of VHCS control panel

Add the following entry in 1887th line of /var/lib/dpkg/info/vhcs.postinst.

keysize => 32,

You need to enter this value before "key => " part.

After this modification run the script:

/var/www/vhcs2/engine/vhcs2-rqst-mngr

You will get another error message saying:

 If specified by -literal_key, then the key length must be equal to the chosen cipher’s key length of 56 bytes at /var/www/vhcs2/engine//vhcs2_common_code.pl line 1443 Compilation failed in require at ./var/www/vhcs2/engine/vhcs2-rqst-mngr line 33. 

You need to add an entry in 1441-th line of /var/www/vhcs2/engine/vhcs2_common_code.pl to fix this issue

modify following code:

my $cipher = Crypt::CBC -> new(
{
‘key’ => $main::db_pass_key,
‘cipher’ => ‘Blowfish’,
‘iv’ => $main::db_pass_iv,
‘regenerate_key’ => 0,
‘padding’ => ’space’,
‘prepend_iv’ => 0
}
);

to

my $cipher = Crypt::CBC -> new(
{
‘keysize’ => 32,
‘key’ => $main::db_pass_key,
‘cipher’ => ‘Blowfish’,
‘iv’ => $main::db_pass_iv,
‘regenerate_key’ => 0,
‘padding’ => ’space’,
‘prepend_iv’ => 0
}
);

This will fix the issue.

Unable to get information from zmcontrol

This issue is mainly occurring due to the incorrect permission of /opt/zimbra/redolog and /opt/zimbra/redolog/redo.log.

Do the following steps:

[root@zimbra bin]# ls -l /opt/zimbra/redolog
total 8
drwxr-x--- 2 root root 4096 Mar 20 13:17 archive
-rw-r----- 1 root root 1292 Apr 11 19:11 redo.log

The chower ship of /opt/zimbra/redolog/redo.log and /opt/zimbra/redolog must be zimbra.

chown -R zimbra.zimbra /opt/zimbra/redolog/

[root@zimbra bin]# ls -l /opt/zimbra/redolog
total 8
drwxr-x--- 2 zimbra zimbra 4096 Mar 20 19:17 archive
-rw-r----- 1 zimbra zimbra 1292 Apr 11 19:59 /opt/zimbra/redolog/redo.log

Now try the "zmcontrol status" and "zmcontrol start". This will work fine now.

Note: If you are facing difficulty in running "zmcontrol status", try the exact path "/opt/zimbra/bin/zmcontrol status".

How to Deploy Zimlet in Zimbra

The Zimbra mail server binaries are located in the location /opt/zimbra/bin. The binary /opt/zimbra/bin/zmzimletctl will help you in implementing or deploying new zimlet.

Zimlet is mainly Integrating the Zimbra Collaboration Suite (ZCS) with third party information systems and content as well as creating "mash-up" user interfaces within the Zimbra suite itself.

Try the following option to list the deplyed Zimlet:

/opt/zimbra/bin/zmzimletctl listZimlets

The deployed zimlets are usually located in the section /opt/zimbra/zimlets. It will be like com_zimbra_email.zip.

The extra zimlets are located in /opt/zimbra/zimlets-extra/ and /opt/zimbra/zimlets-admin-extra/.

The /opt/zimbra/zimlets-admin-extra/ is mainly used to deploy the functions in Admin - interface and other one (/opt/zimbra/zimlets-extra/) is for Client (webmail) part.

If you want to deploy the Amazone - Zimlet, do the following:

cd /opt/zimbra/zimlets-extra/
/opt/zimbra/bin/zmzimletctl deploy com_zimbra_amzn.zip
/opt/zimbra/bin/zmzimletctl listZimlets

You can also deploy the same using Admin-Zimbra interface.

How to Deploy Zimlet in Zimbra

The Zimbra mail server binaries are located in the location /opt/zimbra/bin. The binary /opt/zimbra/bin/zmzimletctl will help you in implementing or deploying new zimlet.

Zimlet is mainly Integrating the Zimbra Collaboration Suite (ZCS) with third party information systems and content as well as creating "mash-up" user interfaces within the Zimbra suite itself.

Try the following option to list the deplyed Zimlet:

/opt/zimbra/bin/zmzimletctl listZimlets

The deployed zimlets are usually located in the section /opt/zimbra/zimlets. It will be like com_zimbra_email.zip.

The extra zimlets are located in /opt/zimbra/zimlets-extra/ and /opt/zimbra/zimlets-admin-extra/.

The /opt/zimbra/zimlets-admin-extra/ is mainly used to deploy the functions in Admin - interface and other one (/opt/zimbra/zimlets-extra/) is for Client (webmail) part.

If you want to deploy the Amazone - Zimlet, do the following:

cd /opt/zimbra/zimlets-extra/
/opt/zimbra/bin/zmzimletctl deploy com_zimbra_amzn.zip
/opt/zimbra/bin/zmzimletctl listZimlets

You can also deploy the same using Admin-Zimbra interface.

Linux plesk: Unable to restore plesk domain dump using pleskrestore

You need to extract the contents of domain dump first. The dump location can be found from psa.conf file (ex. DUMP_D /var/lib/psa/dumps).

cd /var/lib/psa/dumps/1/12 (here psa domain dump directory is /var/lib/psa/dumps/1/12)
mkdir recover
cd recover
zcat DOMAINNAME_2008.03.25_07-11-10 > DOMAINNAME_DUMP_FILE

The domain contents will be extracted here. You can move the contents to respective directories and give proper permission. If the content size greater than 2GB it will produce errors.

In that case we need to do the following steps:

Create a map file of the domain:

/usr/local/psa/bin/pleskrestore --create-map DOMAINNAME_DUMP_FILE -map map_DOMAINUSER

Find the client name of domain from PSA database.

mysql -uadmin -p`cat /etc/psa/.psa.shadow`
use psa
SELECT clients.login, clients.cname, clients.email, accounts.password FROM domains LEFT JOIN clients ON domains.cl_id = clients.id LEFT JOIN accounts ON clients.account_id = accounts.id WHERE domains.name ='DOMAINNAME';
+-----------+-------------------------+--------------------+----------+
| login | cname | email | password |
+-----------+-------------------------+--------------------+----------+
| mydomains | COMPANY_NAME | EMAIL_ID | jkhasdi |
+-----------+-------------------------+--------------------+----------+

Check the map_DOMAINUSER file. If the client name is empty in map file the domain dump restore will not happen.

Modify the map file map_DOMAINUSER:
Replace [] with client name. Here it is [mydomains]
Make sure that syntax of the mapfile is correct and IP properly mentioned in it.

Now you can restore the domain dump using "pleskrestore".

/usr/local/psa/bin/pleskrestore --restore DOMAINNAME_DUMP_FILE -level domains -filter list:DOMAINNAME -map map_DOMAINUSER

BigSister monitoring Tool Installation

This is for linux

wget http://nchc.dl.sourceforge.net/sourceforge/bigsister/bigsister-1.02-4.noarch.rpm
wget http://downloads.sourceforge.net/bigsister/bigsister-server-1.02-4.noarch.rpm?modtime=1137953182&big_mirror=0
wget http://downloads.sourceforge.net/bigsister/bigsister-agent-1.02-4.noarch.rpm?modtime=1137953111&big_mirror=0
rpm -ivh bigsister-1.02-4.noarch.rpm
rpm -ivh bigsister-server-1.02-4.noarch.rpm
rpm -ivh bigsister-agent-1.02-4.noarch.rpm


yum install libwww-perl snmp snmpd

bsmodule
bsmodule list

Download rrdtool from http://oss.oetiker.ch/rrdtool/download.en.html.

Downloads of BigSister plugins: http://www.joerg.cc/html/bigsis/ch01s05.html
Pluggins listed in : http://www.bigsister.ch/plugins.html

yum install rrdtool.i386 rrdtool-php.i386 rrdtool-perl.i386
yum install rrdtool-perl.i386
++++++++++++++++++++++++++++++
# /etc/init.d/bigsister restart
uxmon: stopped
bbd: stopped
bsmon: stopped
Starting Big Sister ...
Monitor bsmon OK
Server bbd OK
Agent uxmon OK
++++++++++++++++++++++++++++++

Include the /etc/bigsister/httpd.conf in original apache config file.
++++++++++++++++++++++++++++++
/etc/init.d/httpd restart
Stopping httpd: [ OK ]
Starting httpd: [Mon May 05 13:03:59 2008] [warn] module php5_module is already loaded, skipping
[ OK ]
++++++++++++++++++++++++++++++

You can now access the bigsister using http://SERVERNAME/bigsis

Zimbra- Your Open Source Mail Server

My another article regarding the Zimbra mail server installation, setup and integration of third parties can be seen in :
http://bobcares.com/article83.html

Stop your monitoring systems cry "wolf wolf"

Please refer the URL http://bobcares.com/article82.html to get more information about it.
My article is published there.