Posts by Starlight

@Nuxwin, could it be, that the encrypted database string in /etc/imscp/imscp.conf has the extra chars already? How to I decrypt or create a new encrypted string without re-running the installation?

It is re-producible after every update.

I added my vlogger host file in the ticket. Should be no derivation from the standard. However, I changed the hostname to IP (temporary fix) to make it work again.

If vlogger is not eating up the apache workers, what could do this? I started after the upgrade.

Since upgrading vlogger to v1.9, I had a strange phenomena: The apache workers got eaten up even in idle times.

Checking the apache server log, I saw hundreds of those entries:

Interestingly, since the connect sting was not mis-configured. If mis-configured, vlogger would complain on start up and turn the feature off:

Checking vloggers line 494, leads me to the sub routine dumpTracker's connect string:

I replaced the hostname with the server's IP address in /etc/imscp/apache/vlogger.conf and it works. I do not know, why this connect string is not working with domain names (anymore).

Two things should be done now:
1) fix the error string
2) close open sessions to avoid workers getting eaten up

I opened a Bug request: IP-1638

Regarding V1.1.1 of Mailgraph

The directory /var/www/imscp/gui/plugins/Mailgraph/tmp_graph is not generated on update of Mailgraph. The corresponding error message in the front end and in the log files is:

Dear @Nuxwin,

the file "/etc/imscp/mysql/imscp.cnf" has the right content:

Did you try passwords with #~()?

Version: i-MSCP 1.3.0
SQL Server: MySQL / MariaDB (remote server)

Problem
On installation / upgrade, in I-MSCP 1.3.0 a new config file will be created for mysqldump: /etc/mysql/conf.d/imscp.cnf. Inside this config file, the Password is escaped:

The escaping might be done due to special characters such as "#[([])}~^-+", however, it makes the dump stop working with following error message:

Quote

An error has been raised while executing function main::run in/var/www/imscp/engine/backup/imscp-backup-all:iMSCP::Database::mysql::dumpdb: mysqldump: Got error: 1045: Access deniedfor user 'imscp_user'@'<host>' (using password: YES) when trying toconnect

Workaround
Delete additional single quotes (') inside the password string.

Fix
Remove escapeShell() all from line 188 in Servers::sqld::remote_server.pm.

I would suggest an even more complicated, but also more flexible Layout:

• Multiple front ends for high availability

• Separated nodes for services and storage of customer data or databases
• Back end services on all necessary nodes
  
  
  Code

  1. [ i-MSCP front end 1 ] <--- heart beat / load balancing --> [ i-MSCP front end 2 ]
  2. | |
  3. +-----------------------------+-----------------------------+
  4. |
  5. +--------+--------+----------+----+--+------+-------+------+---------+
  6. | | | | | | | | |
  7. V V V V V V V V V
  8. [HTTPD1]<->[HTTPD2] [NAMED1]<->[NAMED2] [DB1]<->[DB2]<->[DB3] [MAIL1]<->[MAIL2]
  9. [- be ] [- be ] [-be ] [- be ] | | | [-spam] [-spam]
  10. [- ftp ] [- ftp ] | | | | | [- av ] [- av ]
  11. | | | | | | | | |
  12. +--------+--------+----------+-------+------+-------+------+---------+
  13. | | | | |
  14. V V V V V
  15. [storage1]<------->[storage2]<------->[storage3]<------->[...]<------>[storageN]

  Display More

  
  

Thanks for explanation @Nuxwin. I will try the listener. Would be great, if you could set it on the feature list for future releases.

I recently changed from external to internal DNS and I recognised, that the DNS is configured quite strange.

I was expecting, that I update all domains' ns-record with the new ns IPs and that's it. However, I need to update each domain to ns1.<domain.tld> and ns2.<domain.tld> with the corresponding IPs where the website is running on (i. e. not the server Base IP).

Example:

It would be a great enhancement, to have all DNS records like nsX.base-domain.tld or a freely chosen domain name.

@mrpink

Could you please explain, how you connected the hook to the database? Would be great to have a short howto.

Quote from mrpink

Today I finished my automated letsencrypt rollout tests and I created about 60 certificates against the test (acme-staging) server.

I'm using the bash script letsencrypt.sh for the certificate requests and a listener file which creates the domains.txt file for the bash script.
The rest will be done with letsencrypt.sh -c (also the renew, if only 30 days are left) to request the certificate from the letsencrypt server.

The entries in the i-MSCP database are made by the hook file of the bash script and then the i-MSCP request manager is called. So far all is working fine.