Dev {Tricks}

You are here: Home / Archives for Server and Hosting / Error and Fix

by

MySQL: Error Code: 1118

  • #1118 – Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.
  • Change limit for “Mysql Row size too large”
  • Row size too large 8126 Changing some columns
  • 1118 Row size too large

The error was: SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

  • Solution
  • Login to phpMyAdmin with root previllege
  • Go to Variables
  • Then edit Innodb Strict Mode as follows 
    innodb_strict_mode = 0

 

by

Missing vmail Folders .Sent, .Trash, .Drafts, .Junk, and Other

  • Missing Sent, Trash, Drafts, Junk, and Other Folders

Solution: Check whether the dot files are hidden. Make the dot files to show.

Horde

  • Click on the Folder Actions option.
  • Choose the Rebuild Folder List option.
  • Then choose the Show All Mailboxes option.

Roundcube

  • Go to Settings.
  • Click Folders.
  • Re-subscribe to each folder by clicking the check box.

Windows Mail

  • Click IMAP Folders.
  • In the Show/Hide IMAP Folders dialog box, select a folder.
  • Click Show.

Thunderbird

  • In the Folder pane, look for IMAP mail and right-click on it.
  • Go to Settings, click on Server Settings, then select Advanced.
  • Remove the checkmark on Show only Subscribed folders.
  • Click OK.

Microsoft Outlook Express

  • Under Folders on the left side of the screen, select the inbox for your email (NOT the one under Local Folders).
  • Click the Tools menu, then select IMAP Folders.
  • Select the desired folder(s).
  • Click Show.
  • Click OK.

by

intoDNS

 

Category Status Test name Information
Parent Info Domain NS records Nameserver records returned by the parent servers are:

//

e.gtld-servers.net was kind enough to give us that information.
Pass TLD Parent Check Good. e.gtld-servers.net, the parent server I interrogated, has information for your TLD. This is a good thing as there are some other domain extensions like “co.us” for example that are missing a direct check.
Pass Your nameservers are listed Good. The parent server e.gtld-servers.net has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.
Pass DNS Parent sent Glue Good. The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to
provide “bootstrapping” information to the nameserver.(see RFC 1912 section 2.3)
Pass Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found.
NS Info NS records from your nameservers NS records got from your nameservers listed at the parent NS are:

//
Pass Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Pass Same Glue The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below!
Information Glue for NS records INFO: GLUE was not sent when I asked your nameservers for your NS records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. The nameservers without glue are:

// 123.45.67.890
// 123.45.67.891

You can fix this for example by adding A records to your nameservers for the zones listed above.
Pass Mismatched NS records OK. The NS records at all your nameservers are identical.
Pass DNS servers responded Good. All nameservers listed at the parent server responded.
Pass Name of nameservers are valid OK. All of the NS records that your nameservers report seem valid.
Pass Multiple Nameservers Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
Pass Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
Pass Missing nameservers reported by parent OK. All NS records are the same at the parent and at your nameservers.
Pass Missing nameservers reported by your nameservers OK. All nameservers returned by the parent server e.gtld-servers.net are the same as the ones reported by your nameservers.
Pass Domain CNAMEs OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Pass NSs CNAME check OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Pass Different subnets OK. Looks like you have nameservers on different subnets!
Pass IPs of nameservers are public Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like
Pass DNS servers allow TCP connection OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.
Pass Different autonomous systems OK. It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.
Pass Stealth NS records sent Ok. No stealth ns records are sent
SOA Info SOA record The SOA record is:
Primary nameserver: // grannbo.ns.cloudflare.com
Hostmaster E-mail address: // dns.cloudflare.com
Serial #: // 123456789
Refresh: // 10000
Retry: // 2400
Expire: // 604800   1 weeks
Default TTL: // 3600
Pass NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is // 123456789.
Pass SOA MNAME entry OK. // grannbo.ns.cloudflare.com That server is listed at the parent servers.
Warn SOA Serial Your SOA serial number is: // 123456789. This can be ok if you know what you are doing.
Pass SOA REFRESH OK. Your SOA REFRESH interval is: // 10000. That is OK
Pass SOA RETRY Your SOA RETRY value is: // 2400. Looks ok
Pass SOA EXPIRE Your SOA EXPIRE number is: // 604800.Looks ok
Pass SOA MINIMUM TTL Your SOA MINIMUM TTL is: // 3600. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may
cache the negative answer). RFC2308 recommends a value of 1-3 hours. Your value of // 3600 is OK.
MX Info MX Records Your MX records that were reported by your nameservers are:

1   aspmx.l.google.com

123.45.67.890
(no glue)

5   alt1.aspmx.l.google.com

123.45.67.890
(no glue)

5   alt2.aspmx.l.google.com

123.45.67.890
(no glue)

10   alt3.aspmx.l.google.com

123.45.67.890
(no glue)

10   alt4.aspmx.l.google.com  123.45.67.890
(no glue)

[These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]
Pass Different MX records at nameservers Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are
any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs
Pass MX name validity Good. I did not detect any invalid hostnames for your MX records.
Pass MX IPs are public OK. All of your MX records appear to use public IPs.
Pass MX CNAME Check OK. No problems here.
Pass MX A request returns CNAME OK. No CNAMEs returned for A records lookups.
Pass MX is not IP OK. All of your MX records are host names.
Pass Number of MX records Good. Looks like you have multiple MX records at all your nameservers. This is a good thing and will help in preventing loss of mail.
Pass Mismatched MX A OK. I did not detect differing IPs for your MX records.
Pass Duplicate MX A records OK. I have not found duplicate IP(s) for your MX records. This is a good thing.
Pass Reverse MX A records (PTR) Your reverse (PTR) record:

98.7.654.321.in-addr.arpa ->  rc-in-f26.1e100.net

98.7.654.321.in-addr.arpa ->  wq-in-f26.1e100.net

98.7.654.321.in-addr.arpa ->  ta-in-f26.1e100.net

98.7.654.321.in-addr.arpa ->  sa-in-f26.1e100.net

98.7.654.321.in-addr.arpa ->  la-in-f27.1e100.net

You have reverse (PTR) records for all your IPs, that is a good thing.
WWW Info WWW A Record Your www.ajsrp.com A record is:
// www.domain.com

[104.26.5.40]

[172.67.72.134]

[104.26.4.40]
Pass IPs are public OK. All of your WWW IPs appear to be public IPs.
Pass WWW CNAME OK. No CNAME

 

by

How to increase Apache TimeOut | CWP

Gateway Timeout error 504

504 Gateway Timeout

When using php-cgi add this in httpd.conf

TimeOut 3600

Or add it in Apache config by creating a config file in conf.d dir

touch /usr/local/apache/conf.d/timeout.conf
echo “TimeOut 3600” > /usr/local/apache/conf.d/timeout.conf
service httpd restart

When using PHP-FPM add this in domain vhosts under “proxy_fcgi_module” config:

Domain Apache vhosts location is in /usr/local/apache/conf.d/vhosts

ProxyTimeout 3600

eg :



SetHandler “proxy:unix:/opt/alt/php-fpm72/usr/var/sockets/username.sock|fcgi://localhost”

ProxyTimeout 3600

you can also create a Apache vhost template and add the ProxyTimeout there and use it for the domain you need for increased timeout. You can copy default.stpl and default.tpl to timeout.stpl and timeout.tpl with same content only with below replace config :

php-fpm default templates can be found here :

/usr/local/cwpsrv/htdocs/resources/conf/web_servers/vhosts/httpd/php-fpm

eg :

replace :



SetHandler “proxy:%backend_fcgi%|fcgi://localhost”

with :



SetHandler “proxy:%backend_fcgi%|fcgi://localhost”

ProxyTimeout 3600

after you created the template go to webserver domain config and select the template there under php-fpm thats it or choose default trmeplate in webserver main conf and don’t forget to restart Apache web server if you manually added the timeout in vhost.
If you need Unlimited timeout then you need to disable this apache module :

LoadModule reqtimeout_module modules/mod_reqtimeout.so

go to /usr/local/apache/conf and edit httpd.conf find this line LoadModule reqtimeout_module modules/mod_reqtimeout.so and comment it out i.e. add “#” before this line. Save it and restart Apache server

eg :

#LoadModule reqtimeout_module modules/mod_reqtimeout.so