Some more research... If I run a fresh container with packaged mod_wsgi from my first post, I can start httd with the following wsgi-test.conf: Listen 8080 WSGIDaemonProcess example0verylongname processes=2 threads=2 WSGIScriptAlias /test /wsgi/wsgi-test.wsgi WSGIProcessGroup example0verylongname <Directory /wsgi> Require all granted </Directory> Note verylong process name.
But this one gives segfault: Listen 8080 WSGIDaemonProcess example.com processes=2 threads=2 WSGIScriptAlias /test /wsgi/wsgi-test.wsgi WSGIProcessGroup example.com <Directory /wsgi> Require all granted </Directory> And more to say, if I revert config back to "example0verylongname" after catching segfault, httpd will segfault with it too!!! Also I've noted that if I strip ".com" from your example leaving only "example" process name, it segfaults. If I use "example0" in your example, it starts. Do you think it's possible to fix this? Or should I forget the idea of running mod_wsgi with Alpine linux? -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
