| |||||||||
|
Shutting down spamd: [FAILED]
then try installing following perl module with the given command
/scripts/perlinstaller Errno
Once it is done, restart the exim
/etc/init.d/exim restart
OR
spam assassin can be repaired with
/scripts/fixspamassassinfailedupdate
Joomla 2.5 is the direct upgrade for Joomla 1.7. Joomla 1.7 will be supported for critical security issues only for a period of one month after the release of Joomla 2.5. After that time, only Joomla 1.5 and Joomla 2.5 will be supported by the Joomla project. Note that Joomla version 2.5 is a long-term-support (LTS) release and will be supported for at least 18 months.
Upgrading from Joomla 1.7 to Joomla 2.5.0 will be very easy. Most users can use the automatic update or install the update archive using the Extension Manager: Install option.
If you are using Joomla 1.5 then you will still be required to migrate your site using the jUpgrade component.
If you see a lot of Spam mails originating from a domain say spamdomain.com on your server logs. We can blacklist the domain spamdomain.com from sending mails through Exim mail server.
Create a file named /etc/eximblacklist and add the entry “spamdomain” (without quotes). That is, add the domains you need to blacklist one per line.
Now go to WHM >> Exim configuration editor >> Advanced Editor.
Add the below lines in the first section just below the line “#!!# cPanel Exim 4 Config”
domainlist exim_blacklist = lsearch;/etc/eximblacklist
Now add inside the section under “ROUTERS CONFIGURATION ”
reject_domains:
driver = redirect
# RBL Blacklist incoming hosts
domains = +exim_blacklist
allow_fail
data = :fail: Connection rejected: SPAM source $domain is manually blacklisted.
Save the configuration and see the exim error log. You can see the domain blocked.
First install the EPEL repository on CentOS Linux
Install EPEL Repository On 32-bit CentOS Linux 5.X:
# rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm
Install EPEL Repository On 64-bit CentOS Linux 5.X:
# rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/x86_64/epel-release-5-4.noarch.rpm
Run following command to install git and git-daemon
# yum install git git-daemon –disableexcludes=main
If you see following error
GPG key retrieval failed: [Errno 5] OSError: [Errno 2] No such file or directory: ‘/etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL’
Install the Key file -
# cd /etc/pki/rpm-gpg
# wget http://download.fedora.redhat.com/pub/epel/RPM-GPG-KEY-EPEL
# yum install git git-daemon –disableexcludes=main
You’re done 
Most linux VPS users, running cPanel on their server have the following error.
Below are the steps on how you can correct it.
Error Mail
From: cpanel@host.123.com [mailto:cpanel@host.123.com] Sent: 05 December 2011 22:07 To: contact@123.com Subject: [ipcheck] Problem with DNS setup on host.123.com IMPORTANT: Do not ignore this email. The hostname (host.123.com) resolves to 67.215.65.132. It should resolve to x.x.x.x Please be sure that the contents of /etc/hosts are configured correctly, and also that there is a correct 'A' entry for the domain in the zone file. Some or all of these problems can be caused by /etc/resolv.conf being setup incorrectly. Please check that file if you believe everything else is correct. You may be able to automatically correct this problem by using the 'Add an A entry for your hostname' option under 'Dns Functions' in your Web Host Manager.
Solution
There are several ways to correct this problem, a few of which are mentioned below. The end result should be that the hostname of your VPS should resolve correctly to the VPS IP address.
1) Let us consider that the hostname of your VPS is host.123.com and IP address of the VPS is x.x.x.x
Before starting, check the nameservers of the domain 123.com and make sure you are making the changes at the correct nameservers. If the domain 123.com is using your VPS nameservers itself, you can make the changes in your WHM. If the domain is using remote nameservers, you will have to contact the support team there to make the changes.
1) Login to WHM of your VPS -> DNS Functions -> Edit DNS Zone -> select the domain abc.com
2) Add an A record for host in the DNS zone of 123.com as follows
host 1000 IN A x.x.x.x (where x.x.x.x is the IP address of your VPS)
3) Save the DNS zone.
4) As an additional step, you can also do the following.
WHM -> DNS Functions -> Add an A Entry for your Hostname -> Enter the IP address of your VPS, say x.x.x.x in the text box and click ‘Add entry’
5) Once it is done, run the script /scripts/ipcheck and see if you are receiving the same error email again.
6) If the error still persists, it can sometimes be the propagation delay and you will have to wait a few more hours till the changes propagate.
7) The above should work. If no changes are seen, you may also add the following to the file /etc/hosts
x.x.x.x host.abc.com
Save the changes and close the file.
Done !
If you are still receiving error mails, please contact our support
A sub-domain is not accessed using the www prefix i.e. you can access subdomain.domain.tld but cannot access www.subdomain.domain.tld by default.
To make a subdomain work with ‘www’ prefix on a Plesk server, you have to add a ServerAlias entry in the vhost configuration of the sub-domain and add an A record from Plesk.
1. Create a vhost.conf file for the sub-domain
# nano /var/www/vhosts/domain.tld/subdomains/<sub-domain>/conf/vhost.conf
and add a ServerAlias entry
ServerAlias www.subdomain.domain.tld
2. Add an ‘A’ record for the ‘www’ prefix of the sub-domain from Plesk -> Domains -> <domain.tld> -> DNS Settings -> Add Record
www.subdomain.domain.tld A 1.1.1.1
3. To apply the ServerAlias changes, run the websrvmng utility
# /usr/local/psa/admin/bin/websrvmng -a
4. Restart the webserver
# service httpd restart
Replace the subdomain/domain name and the 1.1.1.1 IP with the actual values.
ERROR: PleskFatalExceptionUnable to connect to database: saved admin password is incorrect.
0: common_func.php3:95 psaerror(string ‘Unable to connect to database: saved admin password is incorrect.’)1: auth.php3:124
Solution :
# cd /usr/local/psa/admin/bin/
# export PSA_PASSWORD=’newpass’
# echo $PSA_PASSWORD
# ./ch_admin_passwd
# export PSA_PASSWORD=
# cat /etc/psa/.psa.shadow
You have a web site hosted called example.com and you have a Gmail address myname@gmail.com.
You create a forwarder gmail@example.com and forward that to myname@gmail.com (or you set the Default Address to myname@gmail.com).
You then login to your Gmail account and try to send a test message to gmail@example.com. But it never arrives!
It will never arrive in your Gmail inbox. It just simply won’t. Don’t try to make it.
Basically, Gmail will send the email to your server at ASO and ASO will report acceptance. Then, your server will try to forward the email to Gmail according to your forwarding set up. That’s fine. Gmail will accept the delivery and report acceptance of that email. That means that Google has accepted the responsibility for delivery of that email. However, Gmail thinks this is spam since it’s accepting mail to your email address, *from your email address* on a different server!
Bottom line: don’t test your forwarders using the Gmail account you’re forwarding to.
Depending on the business you are involved in, opting for a dedicated server may make the most sense. On the other hand, there are plenty of situations where you can make a strong case for a virtual private server (VPS) to save money and make things a little easier for you.
The following are benefits of using a VPS that you should definitely consider if you are in the market for a server.
1. Sometimes less is more. It is easy to assume that if you need things like administrative access (a root account) that you probably also need a full dedicated server with all the extra RAM and disk space that comes with it. In reality you may only need a VPS that offers half or even a fourth of what a full server provides.
2. Save money for things you actually need. As you build your website, business, and/or online marketing presence, you will need money to fund all of that. If you can save money on what amounts to a partial server, it may be worth it. If, however, your projections have you outgrowing it in a short amount of time, a dedicated server may be more appropriate.
3. Less burden. With a VPS, you are still the administrator and are certainly responsible for security, but you will naturally have some assistance from the VPS host, simply because they have an interest in making sure the server remains stable and secure. That means updates and other important system services will likely trickle down to you without as much of a burden on your administrative plate.
| Copyright © 2011 WEBHOSTUK LIMITED WebHost.US.Com is a Division of WebHost.UK.Net & WebHosting.UK.Net Powered by WordPress |
