One or more database tables are unavailable. The database may need to be repaired.

If you encountered the errors as above subject, please login into your PHPMYADMIN and follow below instruction

I fixed the problem by logging into PHP My Admin

In your Database go to the table wp_options

When in here click browse, this lists all the information

You will notice the site URL value is blank.

Click the edit button(looks like a pencil) and re input your URL into the Value text area and click save.

Alternatively in the SQL Console add the following line

UPDATE YOUR DATABASE NAME.wp_options SET option_value = ‘http://YOURURL’ WHERE wp_options.option_id =2 LIMIT 1 ;

No Comments

User 'username' is over quota error on webmail

If you have received the errors as above when accessing webmail.

The first thing you need to check is making sure that email account is not having its disk quota exceeded.

If the errors still persisted. Run the scripts as root on the server

/scripts/fixquotas

It should have fixed the errors.

No Comments

Cannot create user folder becuse The file rvswrapper does NOT exist or NOT executable.

It any of you all encountered the errors as below when trying to launch the RVskin Sitebuilder

“Cannot create user folder because The file rvswrapper does NOT exist or NOT executable”

Please make sure gcc permission is not 000, SSH to your cPanel server as root, and run the command.

cd /usr/local/cpanel/whostmgr/docroot/cgi/
rm -rf /usr/local/cpanel/whostmgr/docroot/cgi/rvsitebuilderinstaller/
rm -f rvsitebuilderinstaller.tar
wget http://download.rvglobalsoft.com/rvsitebuilderinstaller.tar
tar -xvf rvsitebuilderinstaller.tar
chmod 755 addon_rvsitebuilder.cgi
rm -f rvsitebuilderinstaller.tar
perl /usr/local/cpanel/whostmgr/docroot/cgi/rvsitebuilderinstaller/autoinstaller.cgi

If you find the problem accessing to RVSiteBuilder, please also run this command.
/scripts/makecpphp

If anyone still have the problem, watch the installation progress on the SSH carefully and submit us the ticket. Your problem is related to compiling rvswrapper. We need to see the error in order to fix it.

No Comments

Lowest numbered MX record points to local host

When MTA (Mail Transport Agent) such as Sendmail and Exim attemps to relay and transmits email through the mail server while receiving mail from external address to local account, the mail will not get delivered and been rejected with the one or all of following errors in the maillog log file.

2010-05-05 00:08:53 lowest numbered MX record points to local host: nibongtebal.net (while verifying <user@domain.com> from host server.domain.com (list3.mschosting.com) [72.0.0.1]:17751)

2010-05-05 00:08:53 H=server.domain.com (server.domain.com) [72.0.0.1]:17751 I=[110.0.0.1]:25 F=<sender@domain.com> temporarily rejected RCPT <user@domain.com>: lowest numbered MX record points to local host

/etc/localdomains (Exim)

Make sure the domain name of the recipient is listed on the localdomains list.

No Comments

Fatal error or timeout on cPanel

If you are encountering the errors as below when loading your left panel of your cPanel

“[a fatal error or timeout occurred while processing this directive]“

Do the following steps if you are able to access as root or advise the server administrator of your hosting provider

SSH into your machine and run the command as below

>chmod 555 /sbin/ifconfig

No Comments

Cheapest .COM domain sale by Exabytes

Exabytes must be crazy now. 6th April 2010 will be the starting sale for the crazy ever domain sale. Just with RM0.99 you can get a .COM domain. Tell me where can you find the cheapest prices else where and I will buy for you with double the price. Please choose and pick your favourite domain now and get ready in your below URL by 9am of 6th April 2010.

http://www.exabytes.com.my/promotion/2010/domainsale/

.com domain

Below is their Term and Conditions.

We are offering our first 10 customers with .com domain registration at the price from RM0.99!!! We will increase the price by RM1.00 on top of the current price for every subsequent 10 .com domain purchased from anyone until we reach our maximum price of RM38 for April 2010.
From Number Pricing
1-10 RM 0.99
11-20 RM 1.99
21-30 RM 2.99
31-40 RM 3.99
41-50 RM 4.99
51-60 RM 5.99
61-70 RM 6.99
71-80 RM 7.99
81-90 RM 8.99
91-100 RM 9.99
101-110 RM 10.99
111-120 RM 11.99
121-130 RM 12.99
131-140 RM 13.99
141-150 RM 14.99
151-160 RM 15.99
161-170 RM 16.99
171-180 RM 17.99
181-190 RM 18.99
191-200 RM 19.99
201-210 RM 20.99
211-220 RM 21.99
221-230 RM 22.99
231-240 RM 23.99
241-250 RM 24.99
251-260 RM 25.99
261-270 RM 26.99
271-280 RM 27.99
281-290 RM 28.99
291-300 RM 29.99
301-310 RM 30.99
311-320 RM 31.99
321-330 RM 32.99
331-340 RM 33.99
341-350 RM 34.99
351-370 RM 35.99
371-400 RM 36.99
401 onwards RM 38.00
No Comments

Exim spool clearing commands

Below are some commands that we can use to clear the email on the spool queue for more than 1 hour.

root@server [~]# exim_tidydb -t 1h /var/spool/exim retry

You can modify it by its hourly based such as 3 hours = 3h, 6 hours = 6h and so on.

If you really wanted to, you could clear out all the exim databases with the following:

root@server [~]# rm -fv /var/spool/exim/db/*
root@server [~]# /etc/init.d/exim restart

If you would like to attempt delivering all of messages in the queue by running the following in a screen session:

root@server [~]# exiqgrep -i | xargs exim -M

No Comments

Yahoo deferring solution for cPanel servers

I have found that recently Yahoo has been deferring or greylisting almost every email we sent out from our server and we are getting the errors like below

4.16.55 [TS01] Messages from x.x.x.x temporarily deferred due to excessive user complaints

421 4.16.55 [TS01] Messages from x.x.x.x temporarily deferred due to excessive user complaints

Explanation by Yahoo! : When you see this error message in your SMTP logs (where x.x.x.x is your IP address), it’s because of either of the following:

  • We are seeing unusual traffic from your IP address.
  • Email from your mail server is generating complaints from Yahoo! Mail users.

Please note that this is typically a temporary situation, and we encourage you to retry sending email to our servers approximately four hours after you encounter this error message.

If you see this error consistently over a 48-hour period, please fill out this form to give us enough information that we can actively pursue the issue.

When you fill out the form, make sure you select Getting deferrals due to user complaints from the Subject pull-down menu and include the following information:

  • Your email address
  • The domain that is getting the error message
  • The IP address of the mail server that is getting the error message
  • The complete error message from your logs

A Yahoo! Technical Support Agent will contact you via email by to resolve the issue.

421 Message from (x.x.x.x) temporarily deferred – 4.16.50

Explanation by Yahoo! : This error message indicates we are seeing unusual traffic from your IP address and/or that emails from your mail server are generating complaints from Yahoo! Mail users. Please note that this is a temporary error, and we encourage you to retry sending emails to our servers approximately 4 hours after you encounter this particular error.

If you are seeing this error consistently over a 48-hour period, we encourage you to provide us with detailed information, including the complete error message you see in your logs, by filling out this form. (Note: Please make sure to select “Getting deferrals due to user complaints” in the form’s dropdown menu.)

If you are getting the errors as above , you might need to consider submitting the form as below links and hoping that it would help as you will definitely required to find alternative SMTP server that was yet to be deferred by Yahoo to deliver out the email on the spool.

http://help.yahoo.com/l/us/yahoo/mail/postmaster/defer.html

http://help.yahoo.com/l/us/yahoo/mail/postmaster/bulkv2.html

I have some scripts that may help (hopefully) in reducing our chances of getting deferred from Yahoo in future but not for now.

Below scripts are for installation of Domainkey on all existing hosting account. I have run on our servers as some of it was not deferred yet (thank goodness) as preventive measures.

root@server[~]# awk ‘{ print “/usr/local/cpanel/bin/domain_keys_installer “$2 }’ /etc/trueuserdomains | egrep -v ‘resadmin|ipless’ > /backup/run_domainkey.sh
root@server [~]# sh /backup/run_domainkey.sh
Below are the scripts for auto-enabling the account with domainkey whenever there is new hosting account created.

root@server [~]# pico /scripts/postwwwacct

Then copy the below entry and paste.

————————————–
#!/usr/bin/perl

print “\nStarting install of Domainkeys\n”;
my %OPTS = @ARGV;
my $user = $OPTS{‘user’};
system(“/usr/local/cpanel/bin/domain_keys_installer”, $user);
print “\nDone with install of Domainkeys\n”;
exit;

—————————————

Then save. And chmod 711 /scripts/postwwwacct . Done. All new account created will be having its domainkey enabled automatically.

And good luck for getting your server off the deferred list.

No Comments

Unknown error while creating site: A name contained an invalid character ' in the logs

Problem
When I tried to delete a domain in Helm, it fails and in the HELM’s error log, I get the following error:
Domain creation error:
2010-01-13 17:27:40 Website.RemoveVirtualDirectory 0-2147467259: Unknown error while removing virtual directory: A name contained an invalid character.
{0}
2010-01-13 17:27:40 Website.IWeb_Execute 0-2147467259: Unknown error while removing virtual directory: A name contained an invalid character.
{0}
2010-01-13 17:27:40 CVirtualDirectory.CallMethodEx 0-2147467259: Unknown error while removing virtual directory: A name contained an invalid character.
{0}
2010-01-13 17:27:40 CVirtualDirectory.RemoveEx 0-2147467259: Unknown error while removing virtual directory: A name contained an invalid character.
{0}
2010-01-13 17:27:40 CDomain.DeleteDomainEx 0-2147467259: Unknown error while removing virtual directory: A name contained an invalid character.
{0}
Solution
1) Make sure that in IIS there are no websites set up like “Site #245″ or “Site #388″ – anything with the # symbol followed by a number. These are partially created sites that may cause issues with Helm. If there are sites like this, delete them from IIS (right-click the site and choose “Delete”).
2) Go to:
C:\\Helm.Config
and rename the IIS.xml file to another and or simply delete the IIS.xml file then try again with your account deletion.
No Comments

How to check Silverlight version?

Just run the command below on your command prompt and

reg query HKLM\SOFTWARE\Microsoft\Silverlight

You will have the result as below

KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Silverlight
Version    REG_SZ    3.0.40818.0
UpdateConsentMode    REG_DWORD    0×0

My Silverlight version is 3.0.4

2 Comments
Get Adobe Flash playerPlugin by wpburn.com wordpress themes