Jump to content

A simple oversight install latest MySQL, Apache & PHP


Go to solution Solved by yshua,

Recommended Posts

Dear readers:

 

Am complying 100%, even for dumping the package (compiler) my programs are written in!!!! Now installed MySQL 5.5.36, latest reliable offered on MySQL site, along with the latest V11 Apache 2.4.7 and PHP5.5.9 VC11 on Windows 8, 8.1. MySQL and Apache are fine with all the aforementioned 2012 R2 30 day trial version packages above uninstalled and only vcredist_x64.exe and vcredist_x86.exe of Microsoft Visual C++ 2012 Redistributable files installed. Would some other files from those redistributable ones need installing as well, do you think?

 

At any rate, Apache returns "It Works!" but when the php5apache2_4.dll logic is included, "Waiting for localhost," goes on on the websbrowser tab indefinitely.... Would more Visual C++ Redistributable package files downloaded do the trick?

 

Ready for the bare truth,

Yshua

New discovery, friends:

 

Just finished checking the Task Manager to find two (2) Apache HTTP Server (32 bit) tasks running EVERY TIME THE APACHE SERVER IS RESTARTED from the little red/green flag in the hidden icons, lower right corner. So, with zero Apache Server tasks running, the refresh button on the browser quickly returns again with, "It Works." However, index.php is programmed ahead of index.html in httpd.conf file line and the single line in index.php of <?php phpinfo(); ?> seemingly should pull up. Php5apache2_4.dll was used from the Apachelounge.com download of versions 5.4 and the one selected was for version 5.4.7 to match the version of PHP 5.4.7 which is downloaded.

 

So perhaps the main question now is why does Starting the Apache server from an icon start the server twice??

 

Thanks for all the help,

Yshua

Something else to report:

 

The phpinfo.php screen keeps flashing up once, and then connection fails. The access.log has zero lines added and the error.log is only source code failures to load back to back php extensions such as Curl, bz2, openssl, etc.

 

Yshua

More evidence:

 

      Ch0cu3r just helped me over some basic PHP ext. emsgs.  Now these may be stopping phpinfo from appearing longer than a brief flash and then the browser goes out of connection.   Here are the remaining emsgs:

 

[Mon Feb 24 06:43:40.671299 2014] [:error] [pid 6948:tid 924] [client ::1:55072] PHP Warning:  phpinfo(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in C:\\Apache24\\htdocs\\index.php on line 1
[Mon Feb 24 06:43:40.936938 2014] [mpm_winnt:notice] [pid 4492:tid 416] AH00428: Parent: child process 6948 exited with status 255 -- Restarting.
[Mon Feb 24 06:43:41.015067 2014] [mpm_winnt:notice] [pid 4492:tid 416] AH00455: Apache/2.4.7 (Win32) configured -- resuming normal operations
[Mon Feb 24 06:43:41.015067 2014] [mpm_winnt:notice] [pid 4492:tid 416] AH00456: Apache Lounge VC11 Server built: Nov 21 2013 20:13:01
[Mon Feb 24 06:43:41.015067 2014] [core:notice] [pid 4492:tid 416] AH00094: Command line: 'C:\\Apache24\\bin\\httpd.exe -d C:/Apache24'
[Mon Feb 24 06:43:41.015067 2014] [mpm_winnt:notice] [pid 4492:tid 416] AH00418: Parent: Created child process 940
[Mon Feb 24 06:43:41.421338 2014] [mpm_winnt:notice] [pid 940:tid 412] AH00354: Child: Starting 64 worker threads.

 

Could any of these be the cause?

Yshua
 

The PHP Warning message can be solved by setting date.timezone to your timezone in the php.ini
 
Find

;date.timezone =

And change it to

date.timezone = Place/Your/Timezone/Here

 Save php.ini and restart Apache.
 
But what I don't get is. Apache is restarting itself immediately after serving phpinfo.php

[Mon Feb 24 06:43:40.671299 2014] [:error] [pid 6948:tid 924] [client ::1:55072] PHP Warning:  ....
[Mon Feb 24 06:43:40.936938 2014] [mpm_winnt:notice] [pid 4492:tid 416] AH00428: Parent: child process 6948 exited with status 255 -- Restarting.
...

Edited by Ch0cu3r

Dear Ch0cu3r:

 

        Oooops!  Left the semicolon in front of the line!  You were right again.  Here are the remaining emsgs:

 

[Mon Feb 24 08:18:07.788595 2014] [mpm_winnt:notice] [pid 12436:tid 392] AH00354: Child: Starting 64 worker threads.
[Mon Feb 24 08:18:15.522485 2014] [mpm_winnt:notice] [pid 14416:tid 500] AH00428: Parent: child process 12436 exited with status 255 -- Restarting.
[Mon Feb 24 08:18:15.600613 2014] [mpm_winnt:notice] [pid 14416:tid 500] AH00455: Apache/2.4.7 (Win32) configured -- resuming normal operations
[Mon Feb 24 08:18:15.600613 2014] [mpm_winnt:notice] [pid 14416:tid 500] AH00456: Apache Lounge VC11 Server built: Nov 21 2013 20:13:01
[Mon Feb 24 08:18:15.600613 2014] [core:notice] [pid 14416:tid 500] AH00094: Command line: 'C:\\Apache24\\bin\\httpd.exe -d C:/Apache24'
[Mon Feb 24 08:18:15.600613 2014] [mpm_winnt:notice] [pid 14416:tid 500] AH00418: Parent: Created child process 836
[Mon Feb 24 08:18:16.147519 2014] [mpm_winnt:notice] [pid 836:tid 412] AH00354: Child: Starting 64 worker threads.

 

Thank you,

Yshua
 

I have been goggling Apache exit status 255, which appears to mean that Apache is crashing.

 

Seeing as it immediately crashes after serving a php file. it would appear PHP is causing this. What is causing this I do not know as I have never experienced this behaviour with Apache and PHP on Windows. It could be a Windows8 specific bug (I cannot confirm this as I only have Windows 7).

 

What I think could be the cause is a php extension. Try disabling all extensions you have enabled in the php.ini (making sure apache after editing the php.ini). Then try index.php again. If it does not crash then enable one extension at a time until you do get a crash. Post here what extensions are causing this.

Dear Ch0cu3r:

 

        Just checked on error, "[core notice]...  AH00094," and googling says something about the SSL Certificate which has yet to be installed.  Will do it now, but that normally takes me a day or so to install from the past.  Will let you know....

 

Thank you,

Yshua

Dear Ch0cu3r:

 

         Took all but one of the extensions out with semicolons, but same errors.  Perhaps this website is the same bug?

 

comments.gmane.org/gmane.comp.apache.httpd.bugs/7298   

 

Am still awaiting installation after verification by the SSL Cert. provider....

 

Thanks,

Yshua

  • 2 months later...
  • Solution

Dear Ch0cu3r:

 

        Found the problem.  All x86 php and/or Apache installs need to be installed in the Program Files (x86) directory, instead of the C:/ directory!!!!!  And while you're at it, you might as well install the MySQL directory in the Program Files (x86) directory as well.  To make it clearer, ANY php or Apache install with the Win32 feature in it are "odds on" candidates to be installed in the Program Files (x86) directory!  Forego the x64 versions if at all possible, especially when you realize VERY DEEP discrepancies in coding exist for the Win32 vs. Win64 logic.  But you may still have A CHANCE to install Win32-x64 versions with your Windows 32 OS, but ONLY in the Program Files (x86) directory!!!

 

Thanks for the helpful and informative advice on the way to the light going on,

Yshua

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.