I attempted to install D9-beta2 on my local machine (a Mac laptop) using the Drupal UI and encountered a failure.

  • MacOS 10.15.4 Catalina
  • MacPorts
  • Apache 2
  • PHP 7.3
  • MySQL 5.7
  • Drush 10

The install started normally.
Normal installation progressing

However, after the progress bar reached the end, the expected default page did not appear and the connection reset and failed. I checked the database and all the tables seem to be in there.
Connection Reset

I loaded the root page and got this. I then used drush to clear the cache, but there was no change.
Weird home page displaying The Requested Page Could Not Be Found message.

A quick check of the Apache error log showed no reported errors and there was nothing informative in the Watchdog table either.

I know there are alternative ways to install Drupal, but I am specifically testing as if I were a newbie installing for the first time, so please hold off on suggestions involving Composer for now.

CommentFileSizeAuthor
#6 Screen Shot 2020-04-07 at 6.11.15 PM.png851.44 KBryan osītis
#5 d9_access_log.txt9.82 KBryan osītis
Screen Shot 2020-04-07 at 2.20.12 PM.png541.05 KBryan osītis
Screen Shot 2020-04-07 at 2.19.31 PM.png670.8 KBryan osītis
Screen Shot 2020-04-07 at 2.18.52 PM.png2.1 MBryan osītis

Comments

rositis@gmail.com created an issue. See original summary.

cilefen’s picture

cilefen commented

Thanks for testing.

It would be interesting to see the web server error log.

Also I'm not sure but the screenshots seem to indicate perhaps bouncing between https and http, because in some there is the shield icon and in others the info icon in the address bar.

cilefen’s picture

cilefen commented
Issue tags: +Needs steps to reproduce

Duh, I just noticed what you wrote about the web server error log. Ignore that please. Sorry! What about the access log? The 404 should be logged somewhere.

Please add the steps to reproduce, in particular where it comes to system requirements, because it installs fine for me.

cilefen’s picture

cilefen commented

Also, is this something unique to Drupal 9 on the platform you set up, or is Drupal 8 also affected?

ryan osītis’s picture

ryan osītis commented
StatusFileSize
new d9_access_log.txt9.82 KB

This is a testing environment that I have already running a couple of instances of Drupal 8, though I haven't done a clean install of D8 for a while, at least since 8.7. I'll give it try to make sure.

How to Reproduce?

  1. Download Drupal 9.0.0-beta2 and place in the appropriate directory as per your Apache configuration.
  2. Create /sites/default/files directory and chmod 777.
  3. Copy default.settings.php and rename to settings.php, also setting it to chmod 777.
  4. Open browser to site root, which redirects to /core/install.php.
  5. In my case, the installation requirements verification step gets skipped as the environment meets the requirements.
  6. Enter database connection information.
  7. Observe installation, specifically at the end when the progress bar reaches completion.

Expected behavior: Installation completes and redirects to default opening home page.
Observed behavior: Browser displays "The connection was reset" message.

ryan osītis’s picture

ryan osītis commented
Issue summary: View changes
StatusFileSize
new Screen Shot 2020-04-07 at 6.11.15 PM.png851.44 KB

Also I'm not sure but the screenshots seem to indicate perhaps bouncing between https and http, because in some there is the shield icon and in others the info icon in the address bar.

I double-checked this and clicked on the info icon to see what I could learn. It appears to be Not Secure as I would expect.
Screenshot highlighting Not Secure connection

ryan osītis’s picture

ryan osītis commented

I have just done a clean install of Drupal 8 and can confirm similar behavior upon installation. The connection gets reset and I receive the "The website encountered an unexpected error. Please try again later." message upon going to the site root page. The error log is more helpful this time, with the following message:

[Tue Apr 07 18:19:37.759375 2020] [php7:notice] [pid 15510] [client 127.0.0.1:50387] Uncaught PHP Exception Symfony\\Component\\Routing\\Exception\\RouteNotFoundException: "Route "search.view_node_search" does not exist." at /Users/ryanositis/Sites/Contrib/drupal-8/drupal-8.8.5/core/lib/Drupal/Core/Routing/RouteProvider.php line 208

cilefen’s picture

cilefen commented

The 404 is interesting. But I can't reproduce this. On Drupal 8 (what actual version, by the way?), you receive both a connection reset and "The website encountered and unexpected error...". That doesn't seem possible on one request. Or is it a subsequent page reload?

There have been some inconclusive reports of that exception over time. What is the PHP configuration? What is the Apache integration (by that I mean mod_php or FPM)?

You may remove Apache web server from troubleshooting by running the built-in PHP web server by reading instructions in .ht.router.php.

ryan osītis’s picture

ryan osītis commented

I was able to narrow down the error to being something in PHP. Normally, Drupal loads the configuration page after completing the database installation step, but something in that script is causing Apache to throw a segmentation fault error and quit, causing the Connection Reset message.

To test, I went back to using PHP 7.2.29 and tried the install of Drupal 8 again. SUCCESS.

It looks like there is a bug in PHP 7.3.16 that is causing the segmentation fault on my machine, though I'm not yet sure of what the specific trigger is just yet.

Version: 9.0.0-beta2 » 9.0.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Version: 9.0.x-dev » 9.1.x-dev

Drupal 9.0.10 was released on December 3, 2020 and is the final full bugfix release for the Drupal 9.0.x series. Drupal 9.0.x will not receive any further development aside from security fixes. Sites should update to Drupal 9.1.0 to continue receiving regular bugfixes.

Drupal-9-only bug reports should be targeted for the 9.1.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.2.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Status: Active » Postponed (maintainer needs more info)
Issue tags: +Bug Smash Initiative

@Ryan Osītis, did you discover the root cause?

Version: 9.1.x-dev » 9.3.x-dev

Drupal 9.1.10 (June 4, 2021) and Drupal 9.2.10 (November 24, 2021) were the last bugfix releases of those minor version series. Drupal 9 bug reports should be targeted for the 9.3.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

borisson_’s picture

borisson_
Primary language Dutch
Location Mechelen, 🇧🇪
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

It's unclear how to reproduce this issue, and it would be very, very weird that a default php and apache setup would trigger this, there should be sufficient test coverage for this.

I think if this is a problem it would be something that the requirements step of the installation should check. Closing as cannot reproduce.