Skip to content

Passenger v5.3.3 in SmartOS 2018Q3 is not working #156

Description

@jfqd

I tried passenger-5.3.3 with ruby24 and ruby25 in a SmartOS 2018Q3 minimal 64bit image. Both packages are failing to server ruby webapps with the following error in the Apache error.log, sadly no core dumps were produced.

[Thu Nov 01 16:51:06.954101 2018] [core:error] [pid 31792] [client 10.10.10.10:12843] End of script output before headers: 
[ W 2018-11-01 16:51:06.9676 31769/T3 age/Wat/AgentWatcher.cpp:97 ]: Passenger core (pid=31781) crashed with signal SIGSEGV, restarting it...

May that have anything to do with the latest gcc updates? passenger-5.3.2 in 2018Q2 is working fine.

Activity

  1. jfqd commented on Nov 2, 2018

    @jfqd
    Author

    And is that the reason why passenger is not in trunk?

  2. jfqd commented on Nov 2, 2018

    @jfqd
    Author

    I did a build for latest passenger version 5.3.5 for ruby25 (ruby25-passenger and ap24-ruby25-passenger). Build went fine, but packages are failing to server ruby webapps with the same error message.

    So maybe it is an gcc7 related issue?

  3. jfqd commented on Nov 2, 2018

    @jfqd
    Author

    @mamash Do you haven idea how to fix it?

  4. jfqd commented on Dec 5, 2018

    @jfqd
    Author

    passenger is missing in trunk.

  5. added a commit that references this issue on Dec 21, 2018
  6. jperkin commented on Jan 28, 2019

    @jperkin
    Collaborator

    Could you try this again in either trunk or 2018Q4? I think this was caused by the GCC exceptions issue that I've fixed in those releases. Thanks.

  7. self-assigned this
    on Jan 28, 2019
  8. jfqd commented on Feb 19, 2019

    @jfqd
    Author

    @jperkin Passenger seems to be working fine in trunk. Deployed a big app without any issues.

    But the packages are missing in 2018Q4. Are you able to backport them?

    So only issue #170 stops me from migrating to trunk.

  9. jfqd commented on Feb 19, 2019

    @jfqd
    Author

    Sorry, forgot to say thank you Jonathan!

  10. added a commit that references this issue on Mar 26, 2019
  11. 127 remaining items

  12. added a commit that references this issue on Jul 30, 2026
  13. added a commit that references this issue on Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions