I have a Lenovo Thinkpad running Win7 Pro 64 bit, on which I've installed Wampserver 2.2E 64 bit. I've installed a copy of a Joomla 1.5 site which I want to upgrade; my plan is to test the upgrade process on the laptop. I can load the Localhost page and phpMyAdmin with no trouble, but when I try to load the Joomla site, it takes over 5 minutes to load (I timed it) and then displays a blank page.
Because I run IIS7.5 on port 80 to support another test site, I've configured Wampserver apache to run on port 8080, and the apache logs show that it is listening on that port. The error log doesn't actually show any errors, here's a typical Apache startup:
[Mon Nov 25 17:41:20 2013] [notice] Server built: May 13 2012 19:41:17
[Mon Nov 25 17:41:20 2013] [notice] Parent: Created child process 2680
[Mon Nov 25 17:41:20 2013] [notice] Child 2680: Child process is running
[Mon Nov 25 17:41:20 2013] [notice] Child 2680: Acquired the start mutex.
[Mon Nov 25 17:41:20 2013] [notice] Child 2680: Starting 64 worker threads.
[Mon Nov 25 17:41:20 2013] [notice] Child 2680: Starting thread to listen on port 8080.
The PHP error log is blank and always has been. The mySQL log also looks normal (latest startup):
131125 17:41:20 [Note] Plugin 'FEDERATED' is disabled.
131125 17:41:20 InnoDB: The InnoDB memory heap is disabled
131125 17:41:20 InnoDB: Mutexes and rw_locks use Windows interlocked functions
131125 17:41:20 InnoDB: Compressed tables use zlib 1.2.3
131125 17:41:20 InnoDB: Initializing buffer pool, size = 128.0M
131125 17:41:20 InnoDB: Completed initialization of buffer pool
131125 17:41:20 InnoDB: highest supported file format is Barracuda.
131125 17:41:20 InnoDB: Waiting for the background threads to start
131125 17:41:21 InnoDB: 1.1.8 started; log sequence number 1595685
131125 17:41:21 [Note] Server hostname (bind-address): '(null)'; port: 3306
131125 17:41:21 [Note] - '(null)' resolves to '::';
131125 17:41:21 [Note] - '(null)' resolves to '0.0.0.0';
131125 17:41:21 [Note] Server socket created on IP: '0.0.0.0'.
131125 17:41:21 [Note] Event Scheduler: Loaded 0 events
131125 17:41:21 [Note] wampmysqld: ready for connections.
Version: '5.5.24-log' socket: '' port: 3306 MySQL Community Server (GPL)
I've been researching this problem for several days and have tried a number of changes, none of which has had any effect. Here's my list of failed tries:
Made following changes to httpd.conf and php.ini:
EnableMMAP on
EnableSendfile on
Enable and set realpath_cache_size= 4m to your php.ini file
(It turns out I had only set the size; enabling means uncommenting the previous line in php.ini. I think. Uncommenting the line doesn't seem to have any effect.)
Uncommented this line in \etc\hosts: ::1 localhost (have since recommented as it had no effect.)
Adding the line 127.0.0.1 127.0.0.1 to \etc\hosts. Have since removed; had no effect.
Replacing localhost with 127.0.0.1 in httpd.conf
Verified that the system nameservers are not hardcoded and are being pulled from the DHCP server. For the record our router's nameservers are
68.94.156.1 dnsr1.sbcglobal.net and 68.94.157.1 dnsr2.sbcglobal.net
Configured mysql.default_host and mysqli.default_host (in php.ini) to localhost, then to 127.0.0.1; neither had any effect.
Can anyone suggest something that I haven't tried? This smells like a problem with php or mysql but neither one is logging any problems.
I am not sure if this is the problem in your case as I am not actually sure what you are doing, but Joomla installs normally take quite a chunk of processing time.
You normally need to increase the execution time to get them to complete properly.
Try setting max_execution_time = 300 in the php.ini file and restarting Apache
Of course if that works, remember to set max_execution_time back to something sensible, no more that 60.
Related
I am trying to run the MySQL server through XAMPP for connection with php and every time, I try to do so, this error is being shown. I have tried everything from reinstalling to changing port address but this still didn't work. How can I solve this error?
Error
Error: MySQL shutdown unexpectedly.
12:15:26 [mysql] This may be due to a blocked port, missing dependencies,
12:15:26 [mysql] improper privileges, a crash, or a shutdown by another method.
12:15:26 [mysql] Press the Logs button to view error logs and check
12:15:26 [mysql] the Windows Event Viewer for more clues
12:15:26 [mysql] If you need more help, copy and post this
12:15:26 [mysql] entire log window on the forums\
Error log :
2020-06-06 12:13:59 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-06-06 12:13:59 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2020-06-06 12:13:59 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-06-06 12:13:59 0 [Note] InnoDB: Setting file 'C:\XamppReintalled\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-06-06 12:13:59 0 [Note] InnoDB: File 'C:\XamppReintalled\mysql\data\ibtmp1' size is now 12 MB.
2020-06-06 12:13:59 0 [Note] InnoDB: 10.3.15 started; log sequence number 1804856; transaction id 209
2020-06-06 12:13:59 0 [Note] InnoDB: Loading buffer pool(s) from C:\XamppReintalled\mysql\data\ib_buffer_pool
2020-06-06 12:13:59 0 [Note] InnoDB: Buffer pool(s) load completed at 200606 12:13:59
2020-06-06 12:13:59 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-06-06 12:13:59 0 [Note] Server socket created on IP: '::'.
2020-06-06 12:13:59 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10048: Only one usage of each socket address (protocol/network address/port) is normally permitted.
2020-06-06 12:13:59 0 [ERROR] Do you already have another mysqld server running on port: 3308 ?
2020-06-06 12:13:59 0 [ERROR] Aborting
I have made a Wordpress website first hosted locally with local by Flywheel.
I am trying to fully self-host it with a personal server (running ubuntu 18.04), not using some online ftp. I have found no documentation online about the way to do it, only people trying to sell theirs ftp services with a ready-to-use Wordpress environment... I managed to install some things, and when I enter the static IP address of the website, it works!
The problem:
After some time, a message like this appears : Error while trying to connect to the database and the website is down.
If I run /etc/init.d/mysql start again, the website works again! 30 min later, it breaks again, displaying the message above...
This is what I have done:
I used Duplicator to made an image of the website, and transferred it to the server.
I have installed:
nginx (for reverse proxy)
php 7.2
mysql-server
mysql-client
php7.2-mysql and some other extensions
My logins in wp-config.php are correct
Can you help me please ?
Things that failed:
restarting the server and reinstall everything
sudo systemctl reload mysql
Failed to reload mysql.service: Job type reload is not applicable for unit mysql.service.
See system logs and 'systemctl status mysql.service' for details.
sudo systemctl force-reload mysql
Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xe" for details.
systemctl status mysql.service
mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2020-04-22 10:07:23 UTC; 24min ago
Process: 10681 ExecStart=/usr/sbin/mysqld —daemonize —pid-file=/run/mysqld/mysqld.pid (code=exited, status=1/FAILURE)
Process: 10659 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
Main PID: 10433 (code=exited, status=0/SUCCESS)
Apr 22 10:07:23 ewenvm systemd[1]: mysql.service: Failed with result 'exit-code'.
Apr 22 10:07:23 ewenvm systemd[1]: Failed to start MySQL Community Server.
Apr 22 10:07:23 ewenvm systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Apr 22 10:07:23 ewenvm systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
Apr 22 10:07:23 ewenvm systemd[1]: Stopped MySQL Community Server.
Apr 22 10:07:23 ewenvm systemd[1]: mysql.service: Start request repeated too quickly.
Apr 22 10:07:23 ewenvm systemd[1]: mysql.service: Failed with result 'exit-code'.
Apr 22 10:07:23 ewenvm systemd[1]: Failed to start MySQL Community Server.
journalctl -xe
— Support: http://www.ubuntu.com/support
—
— Unit mysql.service has failed.
—
— The result is RESULT.
Apr 22 10:07:23 name-of-my-server systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Apr 22 10:07:23 name-of-my-server systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
— Subject: Automatic restarting of a unit has been scheduled
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— Automatic restarting of the unit mysql.service has been scheduled, as the result for
— the configured Restart= setting for the unit.
Apr 22 10:07:23 name-of-my-server systemd[1]: Stopped MySQL Community Server.
— Subject: Unit mysql.service has finished shutting down
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— Unit mysql.service has finished shutting down.
Apr 22 10:07:23 name-of-my-server systemd[1]: mysql.service: Start request repeated too quickly.
Apr 22 10:07:23 name-of-my-server systemd[1]: mysql.service: Failed with result 'exit-code'.
Apr 22 10:07:23 name-of-my-server systemd[1]: Failed to start MySQL Community Server.
— Subject: Unit mysql.service has failed
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— Unit mysql.service has failed.
—
— The result is RESULT.
Apr 22 10:09:01 name-of-my-server CRON[10701]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 22 10:09:01 name-of-my-server CRON[10702]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Apr 22 10:09:01 name-of-my-server CRON[10701]: pam_unix(cron:session): session closed for user root
Apr 22 10:09:03 name-of-my-server systemd[1]: Starting Clean php session files...
— Subject: Unit phpsessionclean.service has begun start-up
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— Unit phpsessionclean.service has begun starting up.
Apr 22 10:09:04 name-of-my-server systemd[1]: Started Clean php session files.
— Subject: Unit phpsessionclean.service has finished start-up
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— Unit phpsessionclean.service has finished starting up.
—
— The start-up result is RESULT.
Apr 22 10:13:11 name-of-my-server sshd[10770]: Did not receive identification string from 182.182.22.159 port 52155
Apr 22 10:15:31 name-of-my-server systemd-timesyncd[2721]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com).
Apr 22 10:15:41 name-of-my-server systemd-timesyncd[2721]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com).
Apr 22 10:15:51 name-of-my-server systemd-timesyncd[2721]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com).
Apr 22 10:16:01 name-of-my-server systemd-timesyncd[2721]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).
Apr 22 10:17:01 name-of-my-server CRON[10779]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 22 10:17:01 name-of-my-server CRON[10780]: (root) CMD ( cd / && run-parts —report /etc/cron.hourly)
Apr 22 10:17:01 name-of-my-server CRON[10779]: pam_unix(cron:session): session closed for user root
Here are the logs in /var/log/mysql/error/log :
2020-04-22T09:46:51.409203Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use —explicit_defaults_for_timestamp server option (see documentation for more details).
2020-04-22T09:46:51.413886Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.29-0ubuntu0.18.04.1) starting as process 10312 ...
2020-04-22T09:46:51.480012Z 0 [Note] InnoDB: PUNCH HOLE support available
2020-04-22T09:46:51.480056Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-04-22T09:46:51.480062Z 0 [Note] InnoDB: Uses event mutexes
2020-04-22T09:46:51.480079Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-04-22T09:46:51.480086Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-04-22T09:46:51.480091Z 0 [Note] InnoDB: Using Linux native AIO
2020-04-22T09:46:51.480890Z 0 [Note] InnoDB: Number of pools: 1
2020-04-22T09:46:51.481899Z 0 [Note] InnoDB: Using CPU crc32 instructions
2020-04-22T09:46:51.487169Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2020-04-22T09:46:51.490733Z 0 [ERROR] InnoDB: mmap(137428992 bytes) failed; errno 12
2020-04-22T09:46:51.490760Z 0 [ERROR] InnoDB: Cannot allocate memory for the buffer pool
2020-04-22T09:46:51.490768Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2020-04-22T09:46:51.490778Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2020-04-22T09:46:51.492322Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2020-04-22T09:46:51.492337Z 0 [ERROR] Failed to initialize builtin plugins.
2020-04-22T09:46:51.492342Z 0 [ERROR] Aborting
2020-04-22T09:46:51.494236Z 0 [Note] Binlog end
2020-04-22T09:46:51.495643Z 0 [Note] Shutting down plugin 'CSV'
2020-04-22T09:46:51.508165Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
This is strange. MySQL installed on Ubuntu with sudo apt install mysql-server is usually bulletproof.
As I read your error logs, this is the root-cause of your failures.
2020-04-22T09:46:51.490733Z 0 [ERROR] InnoDB: mmap(137 428 992 bytes) failed; errno 12
When MySQL, specifically the InnoDB "access method", was starting, it could not map 137 some-odd megabytes of memory to a file in the file system.
Do you have enough RAM on your Ubuntu instance? Is the disk or SSD almost full? If you have a separate disk partition for your /tmp directory is it big enough? (Avoid RAMDISK for /tmp when you're running MySQL.) Does it have other heavy applications running on it?
If this were my project and I was working with a VM, I would erase it and start over at this point.
I'm a big fan of Digital Ocean's step by step tutorials. I know they're a server-rental company, but their tutorials work for local installs too. https://www.digitalocean.com/community/tutorials/how-to-install-wordpress-with-lamp-on-ubuntu-18-04
I using Plesk 17 onyx on CentOS 7. I have updated my server via plesk update manager and suddenly my database server stop working. I was using MariaDB as database server. Plesk is also not working.
When I tried to start, restart MariaDB, I found the following error as output.
Redirecting to /bin/systemctl status -l mariadb.service
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2016-12-13 13:41:00 PKT; 10min ago
Process: 8193 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=1/FAILURE)
Process: 8192 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS)
Process: 8164 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
Main PID: 8192 (code=exited, status=0/SUCCESS)
Dec 13 13:40:57 ns*.ip-19***** systemd[1]: Starting MariaDB database server...
Dec 13 13:40:57 ns*.ip-19***** mysqld_safe[8192]: 161213 13:40:57 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
Dec 13 13:40:57 ns*.ip-19***** mysqld_safe[8192]: 161213 13:40:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Dec 13 13:41:00 ns*.ip-19***** mysqld_safe[8192]: 161213 13:41:00 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
Dec 13 13:41:00 ns*.ip-19***** systemd[1]: mariadb.service: control process exited, code=exited status=1
Dec 13 13:41:00 ns*.ip-19***** systemd[1]: Failed to start MariaDB database server.
Dec 13 13:41:00 ns*.ip-19***** systemd[1]: Unit mariadb.service entered failed state.
Dec 13 13:41:00 ns*.ip-19***** systemd[1]: mariadb.service failed.
I also have tried to repair mysql via following command of plesk
plesk help repair mysql
Logs in /var/log/mariadb/mariadb.log
161213 14:01:15 Percona XtraDB (http://www.percona.com) 5.5.49-MariaDB-38.0 started; log sequence number 155782156
161213 14:01:15 [Note] Plugin 'FEEDBACK' is disabled.
161213 14:01:15 [ERROR] /usr/libexec/mysqld: unknown option '--safe-show-database'
161213 14:01:15 [ERROR] Aborting
161213 14:01:15 InnoDB: Starting shutdown...
161213 14:01:16 InnoDB: Shutdown completed; log sequence number 155782156
161213 14:01:16 [Note] /usr/libexec/mysqld: Shutdown complete
161213 14:01:16 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
There was safe-show-database in my.cnf. I removed safe-show-database and start MariaDB service again and it works.
Cause
This option is deprecated and does not do anything because there is a
SHOW DATABASES privilege that can be used to control access to
database names on a per-account basis. See Section 6.2.1, “Privileges
Provided by MySQL”. --safe-show-database was removed in MySQL 5.5.3.
I have to handle the finishing of a prestashop website that is almost done and it's the first time I ever use prestashop, and I'm not very familiar with PHP and MySQL.
I have downloaded the site in local but When I launch MAMP Pro, and get to
http://localhost:8888/www/<mysite>/index.php
I get only this :
Link to database cannot be established: SQLSTATE[HY000] [1045] Access denied for user 'pshop'#'localhost' (using password: YES)
Prestashop's email says :
MySQL admin account : root
MySQL admin password : <adminpw>
MySQL database for Prestashop : prestashop
MySQL account for the Prestashop base : pshop
Password for the Prestashop MySQL account : <accountpw>
and in config/settings.php I have :
<?php
define('_DB_SERVER_', 'localhost');
define('_DB_NAME_', 'ps5');
define('_DB_USER_', 'pshop');
define('_DB_PASSWD_', '<accountpw>');
Actually I can see in phpMyAdmin that there are 2 db, one called prestashop and one called ps5. From what I can see they have the same definitions (same users, same clients) so I just changed ps5 into prestashop in config/settings.php, but none of them works anyway.
Is there another file where this appears and I should change it to harmonize everything ?
Should I change the db account password "just in case it's different" in phpmyadmin ? I'm a bit worried about possible consequences if it's not the right thing to do and i can not go back.
Is there a way in phpmyadmin to just *check what are the current passwords for accounts or db's?
Inside phpmyadmin > left pannel > prestashop (or ps5, same result) > right bar, "privileges" :
User "pshop" on client "localhost", type "global", has all privileges, but has no "Grant", and I can not set it to yes :
GRANT ALL PRIVILEGES ON *.* TO 'pshop'#'localhost'WITH GRANT OPTION MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0;
#1045 - Access denied for user 'pshop'#'localhost' (using password: YES)
And,
mysql_error.log file in Mamp pro says :
160408 0:14:08 [Note] /Applications/MAMP/Library/bin/mysqld: Normal shutdown
160408 0:14:08 [Note] Event Scheduler: Purging the queue. 0 events
160408 0:14:08 InnoDB: Starting shutdown...
160408 0:14:09 InnoDB: Shutdown completed; log sequence number 50703588
160408 0:14:09 [Note] /Applications/MAMP/Library/bin/mysqld: Shutdown complete
160408 00:14:09 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
160408 10:10:21 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql
160408 10:10:21 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql/ is case insensitive
160408 10:10:21 [Note] Plugin 'FEDERATED' is disabled.
160408 10:10:21 InnoDB: The InnoDB memory heap is disabled
160408 10:10:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160408 10:10:21 InnoDB: Compressed tables use zlib 1.2.3
160408 10:10:21 InnoDB: Initializing buffer pool, size = 128.0M
160408 10:10:21 InnoDB: Completed initialization of buffer pool
160408 10:10:21 InnoDB: highest supported file format is Barracuda.
160408 10:10:22 InnoDB: Waiting for the background threads to start
160408 10:10:23 InnoDB: 5.5.42 started; log sequence number 50703588
160408 10:10:23 [Note] Event Scheduler: Loaded 0 events
160408 10:10:23 [Note] /Applications/MAMP/Library/bin/mysqld: ready for connections.
Version: '5.5.42' socket: '/Applications/MAMP/tmp/mysql/mysql.sock' port: 0 Source distribution
Apache error log says :
[Fri Apr 08 00:14:10 2016] [notice] caught SIGTERM, shutting down
[Fri Apr 08 10:05:20 2016] [notice] Digest: generating secret for digest authentication ...
[Fri Apr 08 10:05:20 2016] [notice] Digest: done
[Fri Apr 08 10:05:21 2016] [notice] FastCGI: process manager initialized (pid 492)
[Fri Apr 08 10:05:21 2016] [notice] Apache/2.2.29 (Unix) mod_wsgi/3.5 Python/2.7.10 PHP/5.6.10 mod_ssl/2.2.29 OpenSSL/0.9.8za DAV/2 mod_fastcgi/2.4.6 mod_perl/2.0.9 Perl/v5.22.0 configured -- resuming normal operations
and php error log says nothing about today where i still have my problem
can it be a problem in my mamp pro config ?
• In mamp pro there is a MySQL tab and there is a button "change the root password", should I do it ?
It says "for safety reasons the password of the "root" mysql user must be changed when you connect to the internet"
but I'm just trying to work locally so I don't think I should do this ?
• Still in Mamp pro, I have a choice:
Execute Apache/MySQL server as a user :
jeremieg (Apache) / jeremieg (MySQL)
(jeremieg is my name and my mac book name)
or :
www (Apache) / mysql (MySQL) > This one is choosen by default
(none of them works anyway)
• Still in Mamp Pro :
- Default Apache port for http connections : 8888
- Default Apache port for https connections (SSL) : 8890
- MySQL port : 8889
But still, today when I clicked on "start the servers" in Mamp, because Apache was on but MySQL was off after I launched Mamp,
I had an alert saying port 80 was already used (strange because I was not asking for port 80), and that it could cause conflict with one of my virtual machines and so I should change the port; but I chose "Start the servers anyway" and it launched MySQL.
I also tried loading the index.php after disabling little snitch, just in case (and emptying cache), but it didn't change.
WAMP
people having problem with both localhost and phpmyadmin loads blank which usually the port problem.
Mine is only phpmyadmin blank.
sqlbuddy and phpinfo no problem.
tried uninstall reinstalled wamp. tried xampp, same problem, all works well, not phpmyadmin.
mysql log:
120905 8:03:08 [Note] Plugin 'FEDERATED' is disabled.
120905 8:03:08 InnoDB: The InnoDB memory heap is disabled
120905 8:03:08 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120905 8:03:08 InnoDB: Compressed tables use zlib 1.2.3
120905 8:03:09 InnoDB: Initializing buffer pool, size = 128.0M
120905 8:03:09 InnoDB: Completed initialization of buffer pool
120905 8:03:09 InnoDB: highest supported file format is Barracuda.
120905 8:03:09 InnoDB: Waiting for the background threads to start
120905 8:03:10 InnoDB: 1.1.8 started; log sequence number 1595675
120905 8:03:11 [Note] Server hostname (bind-address): '(null)'; port: 3306
120905 8:03:11 [Note] - '(null)' resolves to '::';
120905 8:03:11 [Note] - '(null)' resolves to '0.0.0.0';
120905 8:03:11 [Note] Server socket created on IP: '0.0.0.0'.
120905 8:03:13 [Note] Event Scheduler: Loaded 0 events
120905 8:03:13 [Note] wampmysqld: ready for connections.
apache log
[Wed Sep 05 08:03:09 2012] [notice] Apache/2.2.22 (Win32) PHP/5.4.3 configured -- resuming normal operations
[Wed Sep 05 08:03:09 2012] [notice] Server built: May 13 2012 13:32:42
[Wed Sep 05 08:03:09 2012] [notice] Parent: Created child process 3812
[Wed Sep 05 08:03:09 2012] [notice] Child 3812: Child process is running
[Wed Sep 05 08:03:09 2012] [notice] Child 3812: Acquired the start mutex.
[Wed Sep 05 08:03:09 2012] [notice] Child 3812: Starting 64 worker threads.
[Wed Sep 05 08:03:09 2012] [notice] Child 3812: Starting thread to listen on port 80.
[Wed Sep 05 08:03:09 2012] [notice] Child 3812: Starting thread to listen on port 80.
[Wed Sep 05 08:04:14 2012] [error] [client 127.0.0.1] File does not exist: C:/wamp/www/favicon.ico
[Wed Sep 05 08:09:50 2012] [error] [client 127.0.0.1] File does not exist: C:/wamp/www/favicon.ico
[Wed Sep 05 08:41:03 2012] [error] [client 127.0.0.1] File does not exist: C:/wamp/www/phpMyAdmin
[Wed Sep 05 08:41:03 2012] [error] [client 127.0.0.1] File does not exist: C:/wamp/www/phpMyAdmin
I guess this shows why your phpmyadmin is blank?
Try to use SQL Yog, it's more powerful than PHPmyadmin.
URL : http://www.webyog.com/en/
Well, after trying to figure this out for 2 days, I finally got some answers as to why I kept getting a blank page after installing xampp and trying to visit the phpMyAdmin.
BE SURE TO LOG INTO YOUR SERVER AS ADMIN!!! I work for a company with a IT team which gave my account admin access and permissions and it still wasn't working. it only seems to work if we log into the server as admin.
or
Install Chrome or firefox on the server. if you use the internet explorer default browser you get a blank page.
windows server 2012
The PHPMyAdmin page is blank or an error page (404, 403, ...)?
The PHPMyAdmin folder is not inside the www folder of WampServer because WampServer use alias to point to the PHPMyAdmin folder in C:\wamp\apps\. You can check my guide in this article. Hope this help!
Install Apache service first and then start it and then go to phpMyAdmin page if you already tried the port solution and it didn't work!