The process has been signaled with signal "11"

Check you directory permissions on the host..

Thanks for replying. Which directory and what level of permissions are likely to resolve this.

Check who is owning the directories to start with .. Is it the same as the webserver process?

Well it appears that the error is being thrown due to a timeout when it is trying to write the invoice. I cant see where it is trying to 'write' it to, to be able to change the permissions.

Well ive hit a wall with this one. If anyone can suggest a solution you will be helping me out a lot. Thanks.

I've never used the cashier code, so not entirely sure how it works - but sig11 is known as a 'segfault' - the process is trying to access memory it's not allowed to (usually). How is the code trying to write the invoice?

Im basically using a simple command as detailed in the docs to download an invoice. It's strange as its working on my local homestead box and on another live server. Just the server it needs to work on it doesn't.

I had a look through the directories on both live servers and cant see any differences in permissions either.

Its probably something really obvious.

This happens when? You are downloading the invoice as what? :)

pdf. I dont know if it makes a difference but the server it doesnt work on is using https whereas it is working on the others that only use http.

Okay, so I have looked over the Cashier source code... Take a look and compare your file permissions on storage directory (and sub folders). Unless otherwise specified, it will generate the file in the fully qualified storage path + '/framework'

I have tried setting permissions of app/storage to 777. It didnt make a difference. On both servers they are currently 755.

When it fails the url in the browser is MY_DOMAIN/invoices/in_16f7ovBeIlODGlGiq4QXKhtr

Do your webserver/system/laravel logs have any more information?

Barry, on Homestead, the default is 777 on all the folders and files in /your_project/storage..

Btw, Cashier uses /your_project/storage/framework if nothing else is specified.

This question is really old, but if you ever get a The process has been signaled with signal "11" exception, a common source for this is an infinite loop. In my case, I encountered this exception when running a test that was stuck in a self-calling recursion.

More generally speaking, a signal 11 is a segmentation fault, and the exception is raised by the Symfony Process class. A segmentation fault is usually an illegal memory access and can be caused by a buffer or stack overflow.

In my case, the infinite recursion caused the stack overflow.