Softaculous <![CDATA[My Sql not Start when restart my PC!]]>
AMPPS Control Panel --> MySQL --> Configuration.

under [mysqld] section add following line.

innodb_force_recovery = 1

save it and restart MySQL.]]>
Thu, 11 Feb 2016 08:39:27 GMT
<![CDATA[Updating ownCloud from 8.1.3 -> 8.2.2?]]>
"There is no direct update available from version 8.1.x to version 8.2.x of ownCloud. Although, there is a workaround. You can update your installation from 8.1.3 to 8.2.0 and then from 8.2.0 to 8.2.2.

In order to do so, please download the ownCloud version 8.2.0 package from:

Unzip the package at: /var/softaculous/owncloud

Now you can see the upgrade icon in front of your ownCloud installation. You can upgrade to 8.2.0 using the guide here:

Once your installation is upgraded to version 8.2.0, delete the owncloud package from /var/softaculous directory.

Now execute the cron from here:

Visit the All Installations page of Softaculous and you will be able to see the upgrade icon again. Upgrade once again using the above guide and now your installation shall be upgraded to version 8.2.2."

Thu, 11 Feb 2016 08:13:30 GMT
<![CDATA[Hello to Everyone]]>
Thanks to all for warm welcome. I hope will enjoy the community. ]]>
Thu, 11 Feb 2016 08:11:05 GMT
<![CDATA[Additional IP not working KVM]]>
Quote From : jevingala Today at 6:12 am

After adding the ip, did you power off and power on the vps ?

That's solved the issue , i reckon i made restart vps

but power off/on did the job

Thu, 11 Feb 2016 06:48:00 GMT
<![CDATA[Additional IP not working KVM]]>
After adding the ip, did you power off and power on the vps ?
Do the ips have mac added ?
Thu, 11 Feb 2016 06:12:24 GMT
<![CDATA[500 Internal Server Error, even only 1 php file]]> ]]> Wed, 10 Feb 2016 19:56:10 GMT <![CDATA[STRONG SECURITY ISSUE on Exim 4.72 (last supported by Webuzo)]]>
A BUG has been opened

so now we have to wait, also Webuzo team seems ... cannot do nothing until a solution is not found from RedHat.]]>
Wed, 10 Feb 2016 16:04:53 GMT
<![CDATA[Security Issue EXIM 4.72]]>
A BUG has been opened

so now we have to wait, also Webuzo team seems ... cannot do nothing until a solution is not found from RedHat.

This topic is now closed for me, future updates will maybe posted here:

Thank you.
Wed, 10 Feb 2016 16:04:28 GMT
<![CDATA[My Sql not Start when restart my PC!]]> i installed ammps 3.4 on win8.1 . sometime mysql not starting i seen error in log error:
2016-02-10 17:45:17 3548 [Warning] You need to use --log-bin to make --binlog-format work.
2016-02-10 17:45:17 3548 [Note] Plugin 'FEDERATED' is disabled.
2016-02-10 17:45:17 3548 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-02-10 17:45:17 3548 [Note] InnoDB: The InnoDB memory heap is disabled
2016-02-10 17:45:17 3548 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-02-10 17:45:17 3548 [Note] InnoDB: Memory barrier is not used
2016-02-10 17:45:17 3548 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-02-10 17:45:17 3548 [Note] InnoDB: Not using CPU crc32 instructions
2016-02-10 17:45:17 3548 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-02-10 17:45:17 3548 [Note] InnoDB: Completed initialization of buffer pool
2016-02-10 17:45:17 3548 [Note] InnoDB: Highest supported file format is Barracuda.
2016-02-10 17:45:17 3548 [Note] InnoDB: The log sequence numbers 1600637 and 1600637 in ibdata files do not match the log sequence number 2946005 in the ib_logfiles!
2016-02-10 17:45:17 3548 [Note] InnoDB: Database was not shutdown normally!
2016-02-10 17:45:17 3548 [Note] InnoDB: Starting crash recovery.
2016-02-10 17:45:17 3548 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-02-10 17:45:17 3548 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace dehshahri/yoi9h_associations uses space ID: 2 at filepath: .\dehshahri\yoi9h_associations.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

Wed, 10 Feb 2016 14:32:11 GMT

Wed, 10 Feb 2016 14:30:12 GMT