This affects FreeBSD 11.2 with nginx and the passenger module:
On firing up nginx I keep getting
nginx: [alert] Unable to start the Phusion Passenger watchdog: it seems to have been killed with signal SIGABRT during startup (-1: Unknown error)
There seems to be a serious problem with FreeBSD-nginx-passenger stack.
I dont't have a solution, but at least the problem is being discussed here:
https://github.com/phusion/passenger/issues/2097
Please do not delete this post, because there are really not many resources dealing with this passenger problem.
Related
The com.canonical.multipassd service is constantly logging errors on my Mac and multipass won't work at all, even after reinstalling, rebooting, and updating my Mac.
In an attempt to use my GPU in a Linux VM through multipass, I tried to install the AMDGPU driver for my card (Radeon Pro 5300 4GB). I had installed multipass through brew and made some progress, but the ./amdgpu-install process was returning various errors as a result of missing dependencies. Having started to resolve the missing dependencies, in an attempt to build the driver again, the build just stopped halfway through and I couldn't terminate the process or get the VM to respond at all (didn't take a screenshot sorry).
Because of this, I closed the VM shell and tried to get multipass to shut down the VM. Multipass stopped responding altogether - the application just spun, and it didn't respond at all in terminal. I force quit multipass in Activity Monitor. That still didn't fix it, so I (somewhat stupidly) force quit 'hyperkit' and 'multipassd'. This is where everything went really wrong.
Having force quit 'multipassd', I tried to re-open multipass, but it returned the error below
list failed: cannot connect to the multipass socket
Please ensure multipassd is running and '/var/run/multipass_socket' is accessible
I looked this up and tried a few suggested solutions. I uninstalled multipass with Brew. I deleted the application, and reinstalled with brew. I also tried brew remove multipass, and tried installing using the .pkg from the multipass website. When that didn't fix it, I restarted my computer and reset NVRAM on startup. That also didn't make a difference, so I have just updated my Mac to MacOS 11.4, and it is still not fixed.
The console logs suggest that multipassd is still doing something, as it is continually logging in the system.log:
May 26 09:39:15 <myName> com.apple.xpc.launchd[1] (com.canonical.multipassd[2131]): Service exited with abnormal code: 1
May 26 09:39:15 <myName> com.apple.xpc.launchd[1] (com.canonical.multipassd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
In the multipass log, this message is also being generated about once every 10 seconds:
[error] [daemon] Caught an unhandled exception: Invalid MAC address
[warning] [Qt] QMutex: destroying locked mutex
These messages are being generated even after resetting NVRAM and rebooting. I think they're the cause of my issue launching multipass, but I haven't found any solution to stop them, and I can't identify any process that is still running related to multipass. As far as brew is concerned, multipass is not installed, but it's logs are still filling up...
Happy to provide console or terminal output if needed - nothing else on my Mac seems to be broken, I just can't use multipass now. I do have a time machine backup, so if that is guaranteed to fix it, I might just resort to the backup, but I'm not sure that would necessarily fix it, and I would rather find an alternative solution.
As this has probably made clear, I'm very new to Linux and VMs... any solutions greatly appreciated!
Fixed it!! I hadn't properly uninstalled it - the 'proper' uninstall script can be run using
sudo sh "/Library/Application Support/com.canonical.multipass/uninstall.sh"
Reinstalling multipass after running this command worked fine.
every time a enable a module in Drupal 7, refresh the page, i get this
This page isn’t working
localhost didn’t send any data.
ERR_EMPTY_RESPONSE
my local dev is homebrew's Apache2.4, php7 on a mac osx 10.11
Switching back to homebrew's php56 solved this, and now i don't have any SIGFPE in my apache logs. Now i can enable any Druapl7 module, and works like charm!.
Problem: Yes, i had homebrew's php71, i think Maybe one of the php scripts is broken, either by design or a subtly corrupt file hence getting apache logging SIGFPE ("exit signal Floating point exception (8)")
You can install sphp to switch from php71 back and forth to php56. click here to read about sphp
I haven't been able to find previous answered questions on this, unless I'm missing one. Anyways, when I try starting a rails server:
vagrant [accounts]> rails s
=> Booting WEBrick
=> Rails 4.2.1 application starting in development on http://localhost:3000
=> Run `rails server -h` for more startup options
=> Ctrl-C to shutdown server
[2015-06-06 02:38:50] INFO WEBrick 1.3.1
[2015-06-06 02:38:50] INFO ruby 2.2.2 (2015-04-13) [i686-linux]
[2015-06-06 02:38:50] INFO WEBrick::HTTPServer#start: pid=23016 port=3000
But that's all I ever get, no error messages or anything. Of course localhost:3000 produces 'no data received'
As you can see I'm using Ruby 2.2.2 and Rails 4.2.1
I'm in the root for the app, have tried updating bin.
I'm using the sqlite3 gem, I've created and migrated the db.
I am convinced it has nothing to do with this particular rails app because I've gone back and tried to open old projects that are now having the same problem. Recently I've upgraded from Ubuntu 12.04 to 14.04 on my vm. I've also recently upgraded ruby (I manage with rvm) and rails. I've also recently put some stuff on heroku. All of this has messed with $PATH (I'm not sure if this is related, I'm pretty new to all this stuff). Just wanted to detail everything I could think of that might have an effect.
Thanks!
I ran into the following problem recently, could this be your issue also?
If so try
rails s -b 0.0.0.0
3.3 Default Host for rails server Due to a change in Rack, rails server now listens on localhost instead of 0.0.0.0 by default. This
should have minimal impact on the standard development workflow as
both http://127.0.0.1:3000 and http://localhost:3000 will continue to
work as before on your own machine.
However, with this change you will no longer be able to access the
Rails server from a different machine, for example if your development
environment is in a virtual machine and you would like to access it
from the host machine. In such cases, please start the server with
rails server -b 0.0.0.0 to restore the old behavior.
If you do this, be sure to configure your firewall properly such that
only trusted machines on your network can access your development
server.
See the release notes here for the details.
I was trying to deploy Redmine to Apache with mod_passenger on CentOS 6.3 but having the error :
The application spawner server exited unexpectedly: Connection closed
I installed the latest version (3.0.18) of passenger using gem.
After various failed attempts I decided to delete passenger from "gem uninstall passenger" and install it again using "yum install rubygem-passenger" instead. The installed version was "3.0.17"
Then it started working. Still don't know why exactly.
I also had same issue and figured out.
You may have RailsBaseURI directives in your apache config file. If you're using Rails 3, it should be changed to RackBaseURI.
See these
Passenger error - PhusionPassenger::ClassicRails::ApplicationSpawner::Error
http://wiki.railsplayground.com/railsplayground/show/How+To+use+Phusion+Passenger
http://www.modrails.com/documentation/Users%20guide%20Apache.html
What other errors do you see in the log file?
Can you also try Phusion Passenger 4 beta from github's master branch?
I recently had major permission problems using Lion Server where permissions would change on folders at will. During this time I had started getting the following error when trying to do a rake db:migrate command:
rake aborted!
could not connect to server: Permission denied
Is the server running locally and accepting
connections on Unix domain socket "/var/pgsql_socket/.s.PGSQL.5432"?
This had been working before when I first created a Rails 3.2.3 application while running 10.7.2. All of a sudden I started having this error come up. I read many blogs about this error and tried to remove it but with no success.
I decided to call Apple Enterprise Support to see what I could do. I suspected that Lion Server had gotten corrupted but wanted to confirm with the support team before wiping my server clean and starting over. They confirmed that is what I needed to do in order to straighten it out. I did this on Friday and only installed what I needed to rebuild my Rails app. I still got the error. I tried again some of the other solutions that were posted but still none of them worked. We continued to look for solutions.
After continuing to search for blog posts we were able to find one that dealt with Lion 10.7.4. What I did not know that something had changed between 10.7.2 when I started writing my Rails application and now with PostgreSQL. We found the following blog post which helped me solve the problem I had for several days.
http://www.mactasia.co.uk/revisited-using-postgresql-in-lion-server
I ended up logging in as root and doing the following:
Made the following changes in /System/Library/LaunchDaemons/org.postgresql.postgres.plist
listen_addresses=127.0.0.1
unix_socket_permissions=0777
Changed the permissions of /var/psql_socket
sudo chmod 755 /private/var/pgsql_socket
Afterwards I logged out of root and logged in as I normally do as a server admin. I no longer got the permission error.
which psql will most likely show /bin/psql
I'm guessing we want to call /usr/local/bin/psql
So either we change the $PATH to include /local/bin prior to /bin, which I don't think is a very good solution (security and such), or
We remove /usr/bin/psql by either rm-ing (or mv-ing) the file, (and symlinking to /usr/local/bin)
or uninstalling the psql client.