Posts by Kika

I checked this server tonight. The problem was caused by the /var/www/imscp/gui/plugins/PhpSwitcher/sql/*

Maybe there was an sql error when BigBen updated the PhpSwitcher, but lot of sql executed before the error. So the next time when he tired the installation again then he has got another error because columns was droped already at the first update. We deleted the sql files until the actual error and retry the install again and again while this folder will be empty. After all sql executed the PhpSwitcher works again.

So if you have similar error then check that sqls and you will found the error.

Which OS / mySQL / i-MSCP version do you use?

Colud you check the version of the database?

Hi,

this error means that your python version is out of date. This version comes with Ubuntu 16.04, you must upgrade that:

https://websiteforstudents.com…-7-on-ubuntu-16-04-18-04/

Teljesen rossz a megközelítés szerintem.

A mailszervered a panel aldomainje, például nalam az admin.domain.tld. Ez a host is a szerveren nálam. Minden domain esetében ez a helyes mail szerver. Innentől kezdve pedig csak ehhez kell normális SSL, én az ssls.com-on szoktam venni fillérekért.

Hi,

I don't have this plugin, but you just need to find version_confdir_path_prev in the source and where you found drop before this name you must insert the "if exists".

You will found something like this:

drop column `version_confdir_path_prev`

modify to this:

drop column if exists `version_confdir_path_prev`

Hello,

I didn't use the PDNS, but if I would like to move the mailboxes to another server maybe I try this way:

1, You could install a new server with the same version of iMSCP
2, you could copy the datas from domains, email,subdomains,... tables.
3, Change the status of the rows from "ok" to "toadd" and run the request manager. This will generate all domain and emails.
4, Create a bash script for copy the /var/mail/virtual to the new server and run that.
5, change the MX records
6, after some hours you must need to run the rsync again.

Quote from Nuxwin

Make possible to restore a dump under a specific database name, given either through the UI or on CLI is a feature. You're free to create a feature request on our bug tracker

Hello Nuxwin, this is a good idea

I understand that if a developer thinks this is a standard backup and loads it then this is his fault. However, I think that since a standard mysql dump does not include these lines, the developer will only later discover what he has done and we can prevent it. From the system point of view, this pair of lines is not necessary for restoration.

I think that the backup sql usualy used for two things :

- restore the database

- restore a part of the database or only some datas

If you use large databases then not too easy remove these lines from exported sqls and this is dangerous if somebody doesn't check the sql before load.

If somebody would like to restore the database then he could specify the database name if the export doesn't contains that, but if somebody forget to remove these lines then this will cause lot of problems.

Hello,

today I had to restore a backup of a database into another database and encountered an interesting problem. Although I provided the name of the new database in the command line, but the sql loaded into the original database and drop all data.

I checked the sql backup and found these lines:

CREATE DATABASE /*!32312 IF NOT EXISTS*/ `original_database` /*!40100 DEFAULT CHARACTER SET latin1*/;

USE `original_database`;

I recommend that you remove them from the backup because it is very dangerous, it is easy to accidentally drop the current live database and overwrite with the backup if you would like to load the backuped sql file into a new database.