NULL value for web/secure/base_url generates a SEGSERV error

[hd-jeroen]

Preconditions (*)

1. Magento 2.4.2
2. PHP 7.3 or PHP 7.4 through FPM
3. MySQL 8.0

Steps to reproduce (*)

1. Set the value for web/secure/base_url in core_config_data table to NULL
2. Flush all Magento caches
3. Refresh the website

Expected result (*)

1. An exception being thrown telling the store URL is invalid

Actual result (*)

1. PHP-FPM runs into an error and throws a SEGSERV exception

[25-Mar-2021 13:46:59] NOTICE: [pool www] child 2842 started
[25-Mar-2021 13:47:07] WARNING: [pool www] child 2839 exited on signal 11 (SIGSEGV) after 13.986447 seconds from start

Additional info

In our case, due to a human error the database field for web/secure/base_url got set to NULL. I agree that this shouldn't usually happen, but it did.

I spent ages looking into the issue, since Magento CLI as well as the webpage, started throwing SIGSERV errors, meaning that PHP was trying to access an invalid memory pointer. This has been traced back to the erroneous configuration setting.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [x] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @dehaan-jeroen. Thank you for your report. To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[ihor-sviziev]

Hi @dehaan-jeroen, From the first look, it seems like you're just not providing one of the mandatory configuration options, which is OK to be failing. Could you provide additional info? What is the use case of not defining the base URL?

[m2-assistant[bot]]

Hi @ihor-sviziev. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[hd-jeroen]

@ihor-sviziev in our case, due to a human error the database field for web/secure/base_url got set to NULL. I agree that this shouldn't usually happen, but it did.

I spent ages looking into the issue, since Magento CLI as well as the webpage, started throwing SIGSERV errors, meaning that PHP was trying to access an invalid memory pointer. This has been traced back to the erroneous configuration setting.

[ihor-sviziev]

Now I got it. Could you please add this info to the issue description? It wasn't clear at all what the issue you had any why should we fix it.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[m2-assistant[bot]]

Hi @engcom-Hotel. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

@engcom-Hotel Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• [ ] Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again. Thanks!

[magento-engcom-team]

@m2-community-project[bot] Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• [ ] Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again. Thanks!

[engcom-Hotel]

Hi @dehaan-jeroen ,

This issue has been reproducible. After performing the steps mentioned in the ticket, we are getting following error in apache error_log:

[magento-engcom-team]

@engcom-Hotel Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• [ ] Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again. Thanks!

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-Hotel Thank you for verifying the issue. Based on the provided information internal tickets MC-42675 were created

Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[engcom-November]

As the issue is quite old, we verified this issue on latest 2.4-develop branch and it is still reproducible.

When the value for web/secure/base_url in core_config_data table is set to NULL, we get the below error in apache error_log:

[Thu Oct 17 14:43:48.892693 2024] [core:notice] [pid 47682] AH00052: child pid 15677 exit signal Segmentation fault (11)
[Thu Oct 17 14:43:48.898451 2024] [core:notice] [pid 47682] AH00052: child pid 15656 exit signal Segmentation fault (11)
[Thu Oct 17 14:43:48.898614 2024] [core:notice] [pid 47682] AH00052: child pid 15345 exit signal Segmentation fault (11)

Hence reconfirming this issue.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-879