Framework: An error occurs when starting the queue: The process has been signaled with signal "11

[zhanseitaliev]

• Laravel Version: 5.7.24
• PHP Version: 7.2
• Database Driver & Version: MYSQL: 5.7.24-0ubuntu0.18.04.1

Description:

An error occurs when starting the queue php artisan queue:listen:

Symfony\Component\Process\Exception\ProcessSignaledException : The process has been signaled with signal "11".

`[2019-02-01 13:19:11][1] Processing: App\Jobs\CreateOrUpdateWebhooks

Symfony\Component\Process\Exception\ProcessSignaledException : The process has been signaled with signal "11".

at /mnt/c/Users/User/Documents/kedrapps/kedr-cross-sell-and-up-sell/vendor/symfony/process/Process.php:426
422| usleep(1000);
423| }
424|
425| if ($this->processInformation['signaled'] && $this->processInformation['termsig'] !== $this->latestSignal) {

426| throw new ProcessSignaledException($this);
427| }
428|
429| return $this->exitcode;
430| }

Exception trace:

429|         return $this->exitcode;
430|     }

Exception trace:

1 Symfony\Component\Process\Process::wait()
/mnt/c/Users/User/Documents/kedrapps/kedr-cross-sell-and-up-sell/vendor/symfony/process/Process.php:235

2 Symfony\Component\Process\Process::run(Object(Closure))
/mnt/c/Users/User/Documents/kedrapps/kedr-cross-sell-and-up-sell/vendor/laravel/framework/src/Illuminate/Queue/Listener.php:175`

[matt-allan]

This generally means there was a fatal error in the spawned process (the queue worker). There should be an error in the log file that shows the actual error.

If you run the queue worker with queue:work instead of queue:listen it won't spawn a process so you should see the actual error message instead of what you are seeing now.

[zhanseitaliev]

@yuloh Thank you for your reply. I tried to start the queue with the command - "php artisan queue:work". And after that another error is displayed - Segmentation fault (core dumped). What does this mean? Logs are empty.

[matt-allan]

That is most likely an error in your install of PHP itself or one of your extensions. It's very unlikely that it's specifically related to Laravel. A good place to start would be disabling any unnecessary PHP extensions.

Since this issue tracker is for issues with Laravel you will probably have better luck getting help with one of these resources: https://github.com/laravel/framework/blob/0682ecbf65346b4fd7e5d9b3b3f8aa2be527232c/.github/ISSUE_TEMPLATE/2_Support_question.md

[mfn]

@improck as a quick, since you seem to be on Ubuntu, you may find a crash file in /var/crash. This one you could debug yourself (google is your friend) and it may hint quickly _which_ extension is the problem.

[GhostCoding1]

I have this same issue, im upgrading from 5.6 to 5.7.24.

For me, queue is working, but this crash happens after one job execution.

In this point i think this is related to symfony somehow?

https://github.com/symfony/symfony/issues/20988

Im running local with mamp and php 7.2.10

Update: Removed sentry library and get it working.

[zhanseitaliev]

@GhostCoding1 It's fantastic!!!
After removed sentry library, no errors. You saved a lot of time for me!!! Now everything works without errors. Many thanks for your recommendation. And thanks to everyone who decided to help)))

[mfn]

@GhostCoding1 @improck would you mind sharing which _exact_ Sentry version you did have installed before removing it?

[zhanseitaliev]

@mfn Of cource. Version: "sentry/sentry-laravel": "1.0.0-beta2". Probably need to inform the developers of the library?

[GhostCoding1]

In 5.6 i have sentry-laravel 0.9.2, but laravel won’t upgrade to 5.7 whit this, so then i upgraded to 1.0.0-beta1 or beta2 and this segment fault appears.

[driesvints]

Hi there,

Looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

• Laracasts Forums
• Laravel.io Forums
• Discord
• Larachat
• IRC
• StackOverflow