- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Segmentation fault (core dumped) on Magento 2.2.4 update
@mousepad got any solution for this ?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Segmentation fault (core dumped) on Magento 2.2.4 update
Hello @mousepad
Check server log for same.
Problem solved? Click Kudos & Accept as Solution!
Sunil Patel
Magento 2 Certified Professional Developer & Frontend Developer
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Segmentation fault (core dumped) on Magento 2.2.4 update
just check error log or read core dump file
MagenX - Magento and Server optimization
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Segmentation fault (core dumped) on Magento 2.2.4 update
Nothing in the error log but where would I find the core dump file ?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Segmentation fault (core dumped) on Magento 2.2.4 update
No. Looks like it's a common bug but I have not been able to upgrade. I think it has to do with my data that was converted from 1.9.x a long time ago.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Segmentation fault (core dumped) on Magento 2.2.4 update
Hi Mousepad,
I've just had the same issue and finally worked out a fix,
the crash is coming from the upgrade failing to fill the quote_address_id in table sales_order_address - I solved it by entering a value into every row (I just put 100 in every one).
It isn't the most correct of fixes but it's allowed the update to complete and as far as I can see Magento is working correctly!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Segmentation fault (core dumped) on Magento 2.2.4 update
There's now a proper fix for this issue here
https://github.com/magefan/module-blog/issues/169
check rauberdaniel's SQL near the bottom or wait and it will be sorted in 2.2.7 release
- « Previous
-
- 1
- 2
- Next »