Welcome Guest. Please Login or Register  
Client Area  |  Softaculous Cloud  |  Calendar  |  Quick Links  |  
   


You are here: Index > AMPPS > General Support > Topic : Ampps



Threaded Mode | Print  

 Ampps, Ampps is no longer working (11 Replies, Read 2983 times)
TopTop
Posted on # January 8, 2014, 9:39 pm
Group: Member
Post Group: Newbie
Posts: 6
Status:
Hello,

Ampps was working perfect until today.
Bilding a site with Wordpress (3.8), no problem.

note: C:/Program Files (x86)/Ampps
Apache Started but MySQl will not start anymore.
Can't make connection with wordpress

Looking in google says: ampps/ mysql/data remove ib_log file 0 and 1
Result is MySQl can start now, but still can not make any connetion to WP.

i am a starter with this so please help.

THX TopTop
IP: --   

Ampps
TopTop
Posted on # January 8, 2014, 9:59 pm | Post: 1
Group: Member
Post Group: Newbie
Posts: 6
Status:
To make the post complete see error log file:
2014-01-08 22:53:31 4580 [Note] Plugin 'FEDERATED' is disabled.
2014-01-08 22:53:31 4580 [Note] InnoDB: The InnoDB memory heap is disabled
2014-01-08 22:53:31 4580 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-01-08 22:53:31 4580 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-01-08 22:53:31 4580 [Note] InnoDB: Not using CPU crc32 instructions
2014-01-08 22:53:31 4580 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-01-08 22:53:31 4580 [Note] InnoDB: Completed initialization of buffer pool
2014-01-08 22:53:31 4580 [Note] InnoDB: Highest supported file format is Barracuda.
2014-01-08 22:53:31 4580 [Note] InnoDB: The log sequence numbers 1650710 and 1650710 in ibdata files do not match the log sequence number 1651600 in the ib_logfiles!
2014-01-08 22:53:31 4580 [Note] InnoDB: Database was not shutdown normally!
2014-01-08 22:53:31 4580 [Note] InnoDB: Starting crash recovery.
2014-01-08 22:53:31 4580 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-01-08 22:53:31 4580 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd. Cannot open tablespace wp789/wp_woocommerce_attribute_taxonomies which uses space ID: 1 at filepath: .\wp789\wp_woocommerce_attribute_taxonomies.ibd
InnoDB: Error: could not open single-table tablespace file .\wp789\wp_woocommerce_attribute_taxonomies.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.

thx in advance TopTop
IP: --   

Ampps
tidus
Posted on # January 9, 2014, 6:52 am | Post: 2
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

Please follow this post.


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

Ampps
TopTop
Posted on # January 9, 2014, 7:32 pm | Post: 3
Group: Member
Post Group: Newbie
Posts: 6
Status:
Thanks for the repay Tidus,

The line works for the part of starting MySQL,  that works but  :cry: i still can't start up my WP login page.  :cry:

The discription in the browser i got is like: Can't make contact too the localhost
Is the same message i got when MySQL won't start up

I hope jou have another suggestion for me.

thx in advance TopTop
IP: --   

Ampps
TopTop
Posted on # January 9, 2014, 8:47 pm | Post: 4
Group: Member
Post Group: Newbie
Posts: 6
Status:
This is the error log

2014-01-09 21:39:52 4572 [Note] Plugin 'FEDERATED' is disabled.
2014-01-09 21:39:53 4572 [Note] InnoDB: The InnoDB memory heap is disabled
2014-01-09 21:39:53 4572 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-01-09 21:39:53 4572 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-01-09 21:39:53 4572 [Note] InnoDB: Not using CPU crc32 instructions
2014-01-09 21:39:53 4572 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-01-09 21:39:53 4572 [Note] InnoDB: Completed initialization of buffer pool
2014-01-09 21:39:54 4572 [Note] InnoDB: Highest supported file format is Barracuda.
2014-01-09 21:39:57 4572 [Note] InnoDB: 128 rollback segment(s) are active.
2014-01-09 21:39:58 4572 [Note] InnoDB: Waiting for purge to start
2014-01-09 21:39:58 4572 [Note] InnoDB: 5.6.14 started; log sequence number 1651670
2014-01-09 21:40:01 4572 [Note] Server hostname (bind-address): '*'; port: 3306
2014-01-09 21:40:01 4572 [Note] IPv6 is available.
2014-01-09 21:40:01 4572 [Note]  - '::' resolves to '::';
2014-01-09 21:40:01 4572 [Note] Server socket created on IP: '::'.
2014-01-09 21:40:04 4572 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-01-09 21:40:04 4572 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2014-01-09 21:40:04 4572 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-01-09 21:40:04 4572 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-01-09 21:40:04 4572 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2014-01-09 21:40:05 4572 [Note] Event Scheduler: Loaded 0 events
2014-01-09 21:40:05 4572 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.14-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
IP: --   

Ampps
tidus
Posted on # January 10, 2014, 1:42 pm | Post: 5
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

Delete the C:/Program Files (x86)/Ampps/mysql/data/ibdata1 file from MySQL Data folder. And restart MySQL.


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

Ampps
TopTop
Posted on # January 10, 2014, 7:41 pm | Post: 6
Group: Member
Post Group: Newbie
Posts: 6
Status:
THX Tidus but now MySQL won't start or restart.

Error log:

2014-01-10 20:37:08 4860 [Note] Binlog end
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'partition'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_METRICS'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_CMPMEM'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_CMP'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_LOCKS'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'INNODB_TRX'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'BLACKHOLE'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'ARCHIVE'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'MRG_MYISAM'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'MyISAM'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'MEMORY'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'CSV'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'sha256_password'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'mysql_old_password'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'mysql_native_password'
2014-01-10 20:37:08 4860 [Note] Shutting down plugin 'binlog'
2014-01-10 20:37:08 4860 [Note] mysql\bin\mysqld.exe: Shutdown complete
IP: --   

Ampps
jigar
Posted on # January 11, 2014, 9:14 am | Post: 7
Group: Member
Post Group: Newbie
Posts: 27
Status:
Hi,

This part of log does not have the error. Can you attach the whole file and mail us at support@ampps.com and provide the link to this post in the ticket.

File should be located at Ampps/mysql/data/<your-machine-name>.err
IP: --   

Ampps
pluscss
Posted on # January 13, 2014, 10:25 am | Post: 8
Group: Member
Post Group: Newbie
Posts: 5
Status:
you see more and more people are facing these problems !


there is eally soemthing wrong with the MXSQL server, only creating temporary datdabases, because of unreach / usable basic tables of the MYSQL server.

MYSQL has basic databases, which are as well hidden in this MYSQL version..  don´t knwo why but I think this is part of the problem !
IP: --   

Ampps
TopTop
Posted on # January 13, 2014, 8:02 pm | Post: 9
Group: Member
Post Group: Newbie
Posts: 6
Status:
Thanks all for the support and reply but is too complicated and takes too long to fix so i quit Ampps. I removed program and reinstalled it but same result. Started Xampp from the bottom up and this is working fine. THX and good luke
IP: --   

Ampps
tidus
Posted on # January 15, 2014, 12:23 pm | Post: 10
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Quote From : TopTop January 13, 2014, 8:02 pm
Thanks all for the support and reply but is too complicated and takes too long to fix so i quit Ampps. I removed program and reinstalled it but same result. Started Xampp from the bottom up and this is working fine. THX and good luke


Hi,

Sorry for the inconvenience. Can you provide me the Ticket number in our Support Center ? We will look into it.


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

Ampps
tidus
Posted on # March 25, 2014, 6:17 am | Post: 11
Group: Member
Post Group: Super Member
Posts: 1121
Status:
Hi,

This reply is for users who are being redirected on this post on search.

Please do not delete anything without taking backup.

And
deleting ibdata*, ib_log*, etc files from mysql data directory is not a
fix for every problem. Please open a ticket, if you are not able to
start MySQL or facing any issues related to MySQL.


-----------------------
Follow AMPPS on,
Twitter : https://twitter.com/AMPPS_Stack
Facebook :  http://www.facebook.com/softaculousampps
Google+ : https://plus.google.com/+AmppsStack
IP: --   

« Previous    Next »

Threaded Mode | Print  



Jump To :


Users viewing this topic
1 guests, 0 users.


All times are GMT. The time now is April 20, 2024, 3:18 am.

  Powered By AEF 1.0.8 © 2007-2008 Electron Inc.Queries: 11  |  Page Created In:0.034