• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

PleskMainDBException issue

SigveR

New Pleskian
Hi.

I can't access my Plesk panel because of the following error:

Code:
ERROR: PleskMainDBException: No connection could be made because the target machine actively refused it.
(db.php:435)

Search for related Knowledge Base articles

I clicked the link at the bottom that referred me to the knowledge base, but I can't figure out how to complete the provided steps.

For example "Resolution: Start the "Plesk SQL Server"". How do i start the Plesk SQL Server..?

I also tried to use the Plesk Reconfigurator, but the following message applies: "Can't connect to database on localhost(0)".

Any ideas..?
 
Last edited:
For example "Resolution: Start the "Plesk SQL Server"". How do i start the Plesk SQL Server..?

Just click on "Parallels Plesk Panel Service Monitor" icon in Windows Tray (near clock in right-down corner), select "Plesk SQL Server" and click Start button.
 
Just click on "Parallels Plesk Panel Service Monitor" icon in Windows Tray (near clock in right-down corner), select "Plesk SQL Server" and click Start button.


Hm.. I did and got this error message: "The process terminated unexpectedly Error code 1067. "
 
Looks like something wrong with SQL server. Contact Support Team if you can't troubleshoot it by yourself.
 
I´m experiencing today exactly the same problem. Any help?
ERROR: PleskMainDBException: No connection could be made because the target machine actively refused it.
(db.php:435)

The log file say these:
141201 10:16:17 [Note] Plugin 'FEDERATED' is disabled.
141201 10:16:25 InnoDB: The InnoDB memory heap is disabled
141201 10:16:25 InnoDB: Mutexes and rw_locks use Windows interlocked functions
141201 10:16:25 InnoDB: Compressed tables use zlib 1.2.3
141201 10:16:26 InnoDB: Initializing buffer pool, size = 16.0M
141201 10:16:27 InnoDB: Completed initialization of buffer pool
141201 10:16:28 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
141201 10:16:29 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
141201 10:17:44 InnoDB: Waiting for the background threads to start
141201 10:17:45 InnoDB: 5.5.37 started; log sequence number 144312421
141201 10:17:45 [Note] Server hostname (bind-address): '0.0.0.0'; port: 8306
141201 10:17:45 [Note] - '0.0.0.0' resolves to '0.0.0.0';
141201 10:17:45 [Note] Server socket created on IP: '0.0.0.0'.
141201 10:17:54 [Note] Event Scheduler: Loaded 0 events
141201 10:17:54 [Note] C:\Program Files (x86)\Parallels\Plesk\MySQL\bin\mysqld.exe: ready for connections.
Version: '5.5.37' socket: '' port: 8306 MySQL Community Server (GPL)
141201 10:22:31 InnoDB: Operating system error number 6 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File operation call: 'flush'.
InnoDB: Cannot continue operation.



Best regards,
Horacio
 
Last edited:
Back
Top