The system received an error from the “MySQL” database “mysql”: ER_PASSWORD_NO_MATCH

The system could not perform “GRANT” statements for the user “username” due to errors: (XID cw2xap) The system received an error from the “MySQL” database “mysql”: ER_PASSWORD_NO_MATCH (Can’t find any matching row in the user table), (XID yhghf3) The system received an error from the “MySQL” database “mysql”: ER_PASSWORD_NO_MATCH (Can’t find any matching row in the user table) at /usr/local/cpanel/Cpanel/

I was upgrading a customer today from SQL 5.5 to MariaDB 10 and when he was trying to add users to a db from cPanel it wasn’t working.

cPanel error logs showed the thing above and apparently this is triggered by having “skip-name-resolve” enabled in my.cnf. Disable it, and run /scripts/restartsrv_mysql


yml Quality of life – change nano tabs space

So i recently had to start working with yml files and that stuff needs to use “spaces” as indentation.

In order to stop with Heroes of clickers, i needed to have tab just do 2 spaces on a press instead of the default 8.

To get that done, you have to edit the “nanorc” file, usually in /etc/nanorc and change the variables below to your liking:

## Use this tab size instead of the default; it must be greater than 0.
set tabsize 2

## Convert typed tabs to spaces.
set tabstospaces

Install custom updated Perl

If you need a second perl installation, without messing up the system perl, there’s a fairly easy way:

mkdir /usr/local/perls;cd /usr/local/perls
tar -xzf perl-5.26.1.tar.gz
cd perl-5.26.1
./Configure -des -Dusethreads -Dprefix=/usr/local/perls/perl-5.26.1
make;make test;make install
cd /usr/local/perls/
rm -f /usr/local/perls/perl-5.26.1.tar.gz


Migrate/clone WHM settings between cPanel/WHM servers

If you want to clone or migrate between cPanel/WHM servers, the cpconftool is available and should make life a little bit easier unless you automated configuring all the options through the cPanel/WHM api.

As far as usage goes, it’s fairly standard: check what modules are tracked

[root@test ~]# /usr/local/cpanel/bin/cpconftool –list-modules

Backup the modules and then restore them on the target server.

/usr/local/cpanel/bin/cpconftool [–restore=file|–backup|–list-modules|–query-module-info] –modules=MODULE,MODULE,MODULE [–prerestore_backup] [–verbose]
[root@test ~]# /usr/local/cpanel/bin/cpconftool –modules=cpanel::easy::apache,cpanel::smtp::exim,cpanel::system::backups,cpanel::system::mysql,cpanel::system::whmconf,cpanel::ui::themes –backup
Backup Successful

Restoration goes like this:

/usr/local/cpanel/bin/cpconftool –modules=cpanel::easy::apache,cpanel::smtp::exim,cpanel::system::backups,cpanel::system::mysql,cpanel::system::whmconf,cpanel::ui::themes –restore /home/whm-config-backup-cpanel__easy__apache-1.0.0_cpanel__smtp__exim-10.990000_cpanel__system__backups-

If you came to this page and you’re looking for someone to make all your server related problems go away, feel free to drop us a message and we’ll get back to you asap.

Repair/Optimize all cPanel/WHM databases

If you ever want to repair/optimize all databases on your cPanel server (this also works on non-cPanel servers by the way) all you have to do is run this:

  • Repair all databases:

mysqlcheck –all-databases -r

  • Optimize all databases:

mysqlcheck –all-databases -o


So i have a Windows 2016 Datacenter edition EC2 instance that was used for a SQL server and it’s killing me today with the INACCESSIBLE BOOT DEVICE blue screen.

Here’s me documenting what i tried to use to fix it and things that failed:


  • Take snapshot of the instance
  • Stop instance
  • Detach root volume
  • Create a secondary windows instance, which i’ll be using for restore purposes and log on via RDP to it.
  • Points 1 2 3  below are happening with the volume attached to the recovery instance, after which i detach it, and reattach it to the damaged instance, and boot it up, see if it works.
  • Between each failed point 1 2 3 etc, i am detaching the volume from the damaged instance, and attaching it back to the rescue instance to try the next thing. Make sure you attach it as “/dev/sda1”, as that’s the root mount.

[Things that have failed so far]

1 – Attach it to the recovery instance, run CMD in an elevated prompt and run the command below(didn’t boot):

bcdedit /store D:\boot\bcd /set {default} bootstatuspolicy ignoreallfailures

2 – Use DISM to figure out if it was an automated windows update that installed some patch that bricked it (wasn’t)

dism /Image:D:\ /Get-Packages

3 – Installed EC2 Recovery tools and tried using the offline mode both to “fix boot issues” and “restore last known registry config” (neither worked)

4 – Running a SFC scan to see if there’s any integrity issues (didn’t work):

sfc /scannow /offwindir=d:\windows /offbootdir=d:\

5 – Attempt to rewrite the boot records with bcdedit:

bootsect /nt60 D: /mbr
D:\windows\system32\bcdboot.exe D:\Windows /s D:
bcdedit /store D:\Boot\BCD /set {default} device partition=D:
bcdedit /store D:\Boot\BCD /set {default} osdevice partition=D:
bcdedit /store D:\Boot\BCD /set {bootmgr} device partition=D:

6 – Re-create the boot partition:

bcdboot C:\Windows /S D:

Amazon EC2 add swap

If you want to add some swap to your Amazon EC2 instance, here’s the quick’n dirty:

sudo /bin/dd if=/dev/zero of=/var/swap.1 bs=1M count=1024
sudo /sbin/mkswap /var/swap.1
sudo chmod 600 /var/swap.1
sudo /sbin/swapon /var/swap.1

To have the swap mounted on boot, modify /etc/fstab and add the line below:

/var/swap.1 swap swap defaults 0 0


The system received an error from the “MySQL” database “mysql”: ER_PASSWORD_NO_MATCH (Can’t find any matching row in the user table)

One of my proactive management customers came up to me today with an issue he’s been having on one of his cPanel/WHM servers: he has been trying to add a user to a database he created and he received this error:

The system received an error from the “MySQL” database “mysql”: ER_PASSWORD_NO_MATCH (Can’t find any matching row in the user table)

Apparently commenting out skip-name-resolve in /etc/my.cnf fixed it.

then run a MySQL server restart with: /scripts/restartsrv_ mysql and you should be good to go.

How to fix -> npm ERR! cb() never called!

npm install
npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! <>

I got this error today on a cPanel server where i am running a node.js app that’s reversed proxy to, by Nginx. The error happens when trying to run “npm install” on a large project where roughly 1200 modules should be installed. What happens is that not all of them got installed and some were missing the binaries.

After doing a ton of googling, i found that the ulimit might be an issue, so i went ahead and disabled “Shell and fork bomb protection” that limits the ulimit to 100.

Restart the shell and npm install worked without issues due to having ulimit set to 4096.

Good luck!

De prin 2013

Acum am stat si ma uitam la articolele din urma sa imi dau seama cam pe cand am oprit firul povestii. Geez, nu am mai scris nimic personal de prin 2012-2013. Oricum am devenit un pic mai senil ca nu mai imi aduc aminte bine de tot ce faceam pe atunci, asa ca o sa condensez un pic lucrurile intr-un sumar:

  • Cateva vacante interesante
  • Schimbat de vreo 2 ori job dar eventually am gravitat tot spre a lucra pt mine, freelancing and stuff
  • Am adunat mai multa experienta in materie de: network architecting, Security, DevOps, Docker, AWS, cloud infrastructure.
  • Am participat la un accelerator cu un start-up la care inca lucrez, si am facut demo in New York, am iesit pe locul 9 din vreo 5500 participanti. (au acceptat pe primii 8 – life sucks)
  • Am lucrat cam 1 an si jumatate sa fac un joc in VR dar l-am inchis dupa o vreme pt ca nu ne indreptam spre directia buna si era destul de inceata treaba, dar am invatat o tona de chestii faine. Poate cand o sa am timp/partenerii potriviti si fonduri o sa reiau lucrul la Sjoc dar momentan it’s on ice. Ce am lucrat se poate vedea aici:
  • Start-upul la care lucrez momentan – am reusit sa achizitionam primii 2 clienti si suntem in productie. Se pare ca o sa fie bine, dar mai trebuie efort.
  • Nu mai stau in chirie. Got own home now.
  • Got a baby boy!
  • Am cumparat prima mea masina noua.
  • Am cunoscut o tona de oameni interesanti.
  • Am devenit foarte implicat in crytocurrencies.
  • I became unlocked 🙂
  • Am slabit, m-am ingrasat, sunt in proces de slabire din nou.
  • Sper ca am devenit un pic mai destept si sper sa nu repet greselile din trecut.

Cam asta e sumarul la chestiile care s-au intamplat. Nu cred ca am stat degeaba si sper sa fac si mai multe in viitor. Trebuie doar sa imi modific programul bine si sa power through things.

Life is good.

Voi cum mai sunteti?