blob data length is greater than 10% of the total redo log size

On MySQL 5.6.20, and above you might be getting errors when trying to import tables, databases, if you innodb_log_file size is too small.

If you are seeing error message like this, you will need to increase your innodb_log_size inside your my.cnf or my.ini MySQL configuration file.

The size of BLOB/TEXT data inserted in one transaction is greater than 10% of redo log size. Increase the redo log size using innodb_log_file_size.
2015-09-07 17:29:33 12298 [ERROR] InnoDB: The total blob data length (10066357) is greater than 10% of the total redo log size (100663296). Please increase total redo log size.

As of MySQL version 5.6.20 changes were implemented in regards to InnoDB and BLOB data size in you tables, and you InnoFB log should be at least 10 times higher than the largest BLOB data size found in the rows of your tables, plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields).

http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-20.html#mysqld-5-6-20-innodb

InnoDB Notes

Important Change: Redo log writes for large, externally stored BLOB fields could overwrite the most recent checkpoint. The 5.6.20 patch limits the size of redo log BLOB writes to 10% of the redo log file size. The 5.7.5 patch addresses the bug without imposing a limitation. For MySQL 5.5, the bug remains a known limitation.

As a result of the redo log BLOB write limit introduced for MySQL 5.6, the innodb_log_file_size setting should be 10 times larger than the largest BLOB data size found in the rows of your tables plus the length of other variable length fields (VARCHAR, VARBINARY, and TEXT type fields). No action is required if your innodb_log_file_size setting is already sufficiently large or your tables contain no BLOB data.

Note
In MySQL 5.6.22, the redo log BLOB write limit is relaxed to 10% of the total redo log size (innodb_log_file_size * innodb_log_files_in_group).

Once you increase innodb_log_file_size inside your my.cnf or my.ini file, error should be resolved.

2015-09-07 17:29:38 5345 [Note] InnoDB: Highest supported file format is Barracuda.
2015-09-07 17:29:38 5345 [Warning] InnoDB: Resizing redo log from 2*3072 to 2*65536 pages, LSN=702949287837
2015-09-07 17:29:38 5345 [Warning] InnoDB: Starting to delete and rewrite log files.
2015-09-07 17:29:38 5345 [Note] InnoDB: Setting log file ./ib_logfile101 size to 1024 MB
InnoDB: Progress in MB: 100 200 300 400 500 600 700 800 900 1000
2015-09-07 17:29:42 5345 [Note] InnoDB: Setting log file ./ib_logfile1 size to 1024 MB
InnoDB: Progress in MB: 100 200 300 400 500 600 700 800 900 1000
2015-09-07 17:29:46 5345 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2015-09-07 17:29:46 5345 [Warning] InnoDB: New log files created, LSN=702949287837

Reference:

http://stackoverflow.com/questions/25277452/how-to-configure-mysql-5-6-longblob-for-large-binary-data

Fantastico returns error 404 when accessed from cPanel

When going to Fantastico De Luxe link in you cPanel under Paper Lantern theme, or some other theme you might get HTTP error 404 cPanel page shown, saying that requested page was not found.

 

Fantastico 404 page
Fantastico 404 page
Check your theme folder content for fantastico symlink

404 page will most likely be caused by the affected theme not having, a fantastico symlink, or symlink being misdirected.

Go to the folder of the theme, which in case of Paper Lantern theme will be /usr/local/cpanel/base/frontend/paper_lantern and check for file with name fantastico.

[email protected] [/usr/local/cpanel/base/frontend/paper_lantern]# ls -l | grep fantastico
[email protected] [/usr/local/cpanel/base/frontend/paper_lantern]#

Folder should have symlink in it, with name fantastico, pointing to /usr/local/cpanel/3rdparty/fantastico/, if the symlink is missing create one with ln -s command, also check if the file to which symlink is pointing is an existing file.

[email protected] [/usr/local/cpanel/base/frontend/paper_lantern]# ln -s /usr/local/cpanel/3rdparty/fantastico/ fantastico
[email protected] [/usr/local/cpanel/base/frontend/paper_lantern]# ls -l | grep fantastico
lrwxrwxrwx 1 root root 37 Mar 3 18:02 fantastico -> /usr/local/cpanel/3rdparty/fantastico/
[email protected] [/usr/local/cpanel/base/frontend/paper_lantern]#

After creating a needed symlink Fantastico De Luxe page should work as expected.

Reference:

http://legacy.netenberg.com/forum/index.php?topic=1942.0

CentOS 7 OpenVZ NetworkManager issues.

There is an issue with CentOS 7 containers on OpenVZ nodes, where NetworkManager service breaks the network, and only localhost 127.0.0.1 network interface is coming up.

When you try to check network interfaces, and IP address on the server, you will only see localhost interface.

[email protected] [/]# ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 9059 bytes 1539654 (1.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 9059 bytes 1539654 (1.4 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

When issuing service network restart you will and output like this:

Starting network (via systemctl): Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.
[FAILED]

When you run journalctl -xe you will see errors like this:

-- Unit network.service has begun starting up.
 Feb 16 05:16:40 server network[2262]: Bringing up loopback interface: Could not load file '/etc/sysconfig/network-scripts/ifcfg-Feb 16 05:16:40 server network[2262]: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
 Feb 16 05:16:40 server network[2262]: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
 Feb 16 05:16:40 server network[2262]: Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
 Feb 16 05:16:40 server network[2262]: [ OK ]
 Feb 16 05:16:40 server network[2262]: Bringing up interface venet0: Error: Connection activation failed: No suitable device founFeb 16 05:16:40 server network[2262]: [FAILED]
 Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
 Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
 Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
 Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
 Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
 Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
 Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
 Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
 Feb 16 05:16:40 server network[2262]: RTNETLINK answers: File exists
 Feb 16 05:16:40 server systemd[1]: network.service: control process exited, code=exited status=1
 Feb 16 05:16:40 server systemd[1]: Failed to start LSB: Bring up/down networking.
 -- Subject: Unit network.service has failed
 -- Defined-By: systemd
 -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
 --
 -- Unit network.service has failed.
 --
 -- The result is failed.
 Feb 16 05:16:40 server systemd[1]: Unit network.service entered failed state.
 Feb 16 05:16:40 server systemd[1]: network.service failed.
 Feb 16 05:16:40 server polkitd[226]: Unregistered Authentication Agent for unix-process:2257:65393 (system bus name :1.37, object

Issue can be resolved by stopping and disabling the NetworkManager service.

[email protected] [/]# service NetworkManager stop
Redirecting to /bin/systemctl stop NetworkManager.service
[email protected] [/]# chkconfig NetworkManager off

You can also uninstall NetworkManager completely.

References:

https://lists.openvz.org/pipermail/users/2015-December/006691.html

Openvz / CentOS 7 – Network Manager can break networking

 

How to enable Registry Editor, when it gets disabled

While checking the registry on my machine because of the issues I had with Task Manager, described in this post, I noticed that I was unable to start Registry Editor.

When trying to run regedit, I would get a message saying

“Registry editing has been disabled by your administrator”

Regedit Disabled
Disabled Registry Editor

Enable Registry Editor (regedit) in Local Group Policy with gpedit.msc

This can be changed by editing Local Group Policy with gpedit.msc.

Click Win+R keys to open Run dialog interface, and issue gpedit.msc command to open Local Group Policy Editor.

Navigate to:

User Configuration > Administrative Templates > System > Prevent access to registry editing tools.

Enable regedit in Group Policy
Enable Registry Editor in Group Policy

This should by default be set to Not Configured, which should not prevent you from starting Registry Editor.

It was set on Not Configured on my machine already, so I set it to Disabled, and this enabled back Registry Editor for me.

Interestingly, after returning the setting back to Not Configured, Registry Editor did not get disabled again.

This seems to have got disabled during installation of some drivers, and even do Local Group Policy was set on Not Configured, it seem some registry values were set to disable registry editing tools from running, and switching back between Enabled, and Not Configured seems to have return them to default values.

Alternate possible methods of enabling regedit.

Alternate method 1:

Click Start -> Run. Type this command in Run box and press Ok.

REG add HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System /v DisableRegistryTools /t REG_DWORD /d 0

A prompt should come up with this question:

Value DisableRegistryTools exists, overwrite (Y/N)?

Type yes and hit Enter.

After that, also type this command in the run box and hit enter.

REG add HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System /v DisableRegistryTools /t REG_DWORD /d 0

Then a prompt should come up with this question:

Value DisableRegistryTools exists, overwrite (Y/N)?

Type yes and hit Enter.

Alternate method 2:

STEP1. Disable as much as you can from your startup. Remove programs from your startup folder and such, so as not to lag down the boot process.

STEP2.Create a new shortcut on your desktop, point it to “C:\Windows\regedit.exe”

STEP3.Log off, then log back on.

STEP4.As soon as you see your desktop, double-click on the shortcut. The system does not check for policies until a few seconds after it booted up. If you click on the icon fast enough, it should let you get in.

After you close it though, it will not open unless you redo step 3 and 4.

Alternate method 3:

Get into the registry editor by making a vbs script in notepad:

Open Notepad and copy this script into it. And save it as regtool.vbs on your desktop.

VBS SCRIPT(select everything and copy into notepad and save as regtool.vbs):

Option Explicit 
'Declare variables 
Dim WSHShell, rr, rr2, MyBox, val, val2, ttl, toggle 
Dim jobfunc, itemtype 
On Error Resume Next 
Set WSHShell = WScript.CreateObject("WScript.Shell") 
val = "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System\DisableRegistryTools" 
val2 = "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\DisableRegistryTools" 
itemtype = "REG_DWORD" 
jobfunc = "Registry Editing Tools are now " 
ttl = "Result" 
'reads the registry key value. 
rr = WSHShell.RegRead (val) 
rr2 = WSHShell.RegRead (val2) 
toggle=1 
If (rr=1 or rr2=1) Then toggle=0 
If toggle = 1 Then 
WSHShell.RegWrite val, 1, itemtype 
WSHShell.RegWrite val2, 1, itemtype 
Mybox = MsgBox(jobfunc & "disabled.", 4096, ttl) 
Else 
WSHShell.RegDelete val 
WSHShell.RegDelete val2 
Mybox = MsgBox(jobfunc & "enabled.", 4096, ttl) 
End If

Open regtool.vbs ,and you should be able to access Registry Editor then.

References:

http://ccm.net/forum/affich-8895-regedit-is-disabled-by-the-administrator

How to enable grayed out Task Manager

I was installing drivers for a gamepad on my Windows 10 machine, and after the install I noticed that I was no longer able to use Task Manager, right clicking on taskbar, would show Task Manager line grayed out.

GrayTaskManager
Grayed out Task Manager

Trying to run it manually, through Run interface with Win+R, using taskmgr command would return a notice saying

“Task Manager has been disabled by your administrator”

TaskManagerDisabled
Task Manager Disabled
Enable Task Manager through Local Group Policy editor (gpedit.msc)

To enable Task Manager again, you can use Local Group Policy editor (gpedit.msc).

Press Win+R to reach Run interface, and issue gpedit.msc command to start Local Group Policy editor.

Once you open Local Group Policy editor, navigate to:

User Configuration > Admistrative Templates > System > Ctrl+Alt+Del Options > Remove Task Manager.

By default this is set to Not Configured, and this should leave Task Manager enabled.

Setting was already on Not Configured on my machine, so I set it to Disabled, and this enabled back Task Manager on my machine.

Interestingly, once I returned the setting back to Not Configured, it did not disable Task Manager.

Enable Task Manager in Group Policy
Enable Task Manager in Group Policy
Enable Task Manager through Registry Editor (regedit)

Besides editing Local Group Policy, you should also be able to enable back Task Manager by editing Windows registry.

Open Registry Editor by pressing Win+R to launch Windows Run interface, and issue regedit command to open Registry Editor.

Navigate to following keys:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System
HKEY_USERS\.default\Software\Microsoft\Windows\CurrentVersion\Policies\System

And check if any of them has DisableTaskMgr DWORD in the right side panel.

If it exists, it should have one of two values:

1 – Disable task manager
0 – Enable task manager

Double click and change the value to one if the key exists, or delete the key completely, to enable Task Manager back.

Enable Registry Editor (regedit)

While checking the registry on my machine, I also noticed that I was unable to start Registry Editor.

When trying to run regedit, I would get a message saying

“Registry editing has been disabled by your administrator”

RegeditDisabled
Disabled Registry Editor

This can be changed by editing Local Group Policy with gpedit.msc.

Click Win+R keys to open Run dialog interface, and issue gpedit.msc command to open Local Group Policy Editor.

Navigate to:

User Configuration > Administrative Templates > System > Prevent access to registry editing tools.

Enable Registry Editor in Group Policy
Enable Registry Editor in Group Policy

This should by default be set to Not Configured, which should not prevent you from starting Registry Editor.

It was set on Not Configured on my machine already, so I set it to Disabled, and this enabled back Registry Editor for me.

Interestingly, after returning the setting back to Not Configured, Registry Editor did not get disabled again.

References:

How to fix Task Manager has been disabled by your Administrator issue in Windows

http://ccm.net/forum/affich-8895-regedit-is-disabled-by-the-administrator