/Usr/Bin/Env Ruby_Noexec_Wrapper Fails with No File or Directory

/usr/bin/env ruby_noexec_wrapper fails with no file or directory

make sure all the variables all set correctly, especially PATH and GEM_PATH, you can use this code to set the environment for you:

source /usr/local/rvm/environments/ruby-1.9.3-p194

add it in the service before chef-solr is run

env: ruby_noexec_wrapper: No such file or directory error

this same thing happened to me, i fixed it according to this comment: https://github.com/sstephenson/rbenv/issues/337#issuecomment-13235367

by running these commands

gem install rubygems-bundler
rubygems-bundler-uninstaller
gem uninstall rubygems-bundler

env: ruby_noexec_wrapper: No such file or directory' error in PhpStorm SASS compilation on Mac

On Mac it may be required to perform additional steps outlined in this answer to make the environment the same as in Terminal for the GUI applications.

Most likely PATH is different.

Another workaround is to start PhpStorm from the Terminal:

open -a /Applications/PhpStorm.app/

cannot load such file -- bundler/setup (LoadError)

It could be that there was a previous Ruby env installed on your system prior to your installation of 2.0? This might have had an existing GEM_PATH that lead to the /1.8 directory which the installation of version 2.0 simply kept.

The problem you where likely having, then, was that Passenger/Apache was looking in the /2.0 directory when in fact the gems were in the /1.8 directory. Your explicitly telling apache to use the /1.8 directory thus makes sense to fix the problem.

SetEnv GEM_HOME /usr/lib/ruby/gems/1.8

You might also try using the Ruby Version Manager to handle multiple Ruby envs.

Some things I found in Google:

• New to Ruby and am having trouble with LOAD_PATH
• http://weblog.rubyonrails.org/2009/9/1/gem-packaging-best-practices/
• http://guides.rubygems.org/faqs/

Segmentation fault error with ruby 1.9.3 when doing bundle install for Rails 3.2 app

I had a petty messed up ruby install at one point that was giving segmentation faults. I did

rvm implode

And started from scratch and in about an hour everything was working again

mktemp: failed to create file via template ‘/tmp/virtualenvwrapper-initialize-hook-XXXXXXXXXX’: Read-only file system

The error you're getting indicates that you're trying to write on a file system that's read only. If you look at the mount output for /, then the ro mount option indicates that it's read only.

There are usually a couple reasons that your file system is read only, but in this case, it's likely the behavior of an ext4 file system when it encounters a file system error. The default is to remount the file system read only to avoid further damage but allow the system to continue. The alternatives in this case are to ignore the error and panic, both of which are generally less desirable.

You can verify this by running dmesg in order to see whether the kernel has reported any file system errors and remounted the file system. If so, you can generally reboot the system and an fsck will occur automatically. You may need to boot from a different medium (such as a live CD) to perform the fsck (by running e2fsck -f /dev/sda2) in some cases, since not all errors can be fixed when the file system is mounted.

PHP of Phpmyadmin does not execute but other php scripts work

First of all, what is the version of PHP?

If other .php scripts work except for phpMyAdmin, the is pretty safe to assume something is wrong with phpMyAdmin installation. (either with the files or the Virtual Host)

---

Troubleshoot:

1. Can you run another script in phpMyAdmin directory? Try with a file containing phpinfo(); If it does not work then the problem is in your apache configuration.

2. If the above is true, then the parser is not recognising phpMyAdmin/index.php as a php file, for some reason. Try reinstalling phpMyAdmin.

---

Thoughts:

Remove AddType application/x-httpd-php .php. You should not need it.

In PHP 5.4 magic_quotes_gpc was removed. If you're running PHP5, remove that line.

As of PHP 4.0.3, track_vars is always turned on, so remove it also.

As of PHP 4.2.0, register_globals this directive defaults to off. In PHP5.3 register_globals is deprecated, as of PHP5.4 register_globals was removed. SO if running PHP > 4.2.0 remove that line.

---

Related Topics