Pulsar does not create /tmp/pulsar directory
Closed this issue · 5 comments
When I try to run pulsar i get following error:
cp: cannot create directory `/tmp/pulsar/conf-repo-2013-08-13-091924-s4537': No such file or directory
/home/vagrant/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/pulsar-0.3.2/lib/pulsar/helpers/shell.rb:22:in `run_cmd': Command cp -rp /home/vagrant/Deployment /tmp/pulsar/conf-repo-2013-08-13-091924-s4537 Failed (RuntimeError)
from /home/vagrant/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/pulsar-0.3.2/lib/pulsar/helpers/clamp.rb:64:in `fetch_directory_repo'
from /home/vagrant/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/pulsar-0.3.2/lib/pulsar/helpers/clamp.rb:53:in `fetch_repo'
from /home/vagrant/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/pulsar-0.3.2/lib/pulsar/commands/main.rb:27:in `block (2 levels) in execute'
from /home/vagrant/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/bundler-1.3.5/lib/bundler.rb:218:in `block in with_clean_env'
from /home/vagrant/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/bundler-1.3.5/lib/bundler.rb:205:in `with_original_env'
from /home/vagrant/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/bundler-1.3.5/lib/bundler.rb:211:in `with_clean_env'
from /home/vagrant/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/pulsar-0.3.2/lib/pulsar/commands/main.rb:25:in `block in execute'
from /home/vagrant/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/pulsar-0.3.2/lib/pulsar/commands/main.rb:24:in `each'
from /home/vagrant/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/pulsar-0.3.2/lib/pulsar/commands/main.rb:24:in `execute'
from /home/vagrant/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/clamp-0.6.1/lib/clamp/command.rb:67:in `run'
from /home/vagrant/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/clamp-0.6.1/lib/clamp/command.rb:125:in `run'
from /home/vagrant/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/pulsar-0.3.2/bin/pulsar:5:in `<top (required)>'
from /home/vagrant/.rbenv/versions/2.0.0-p247/bin/pulsar:23:in `load'
from /home/vagrant/.rbenv/versions/2.0.0-p247/bin/pulsar:23:in `<main>'
If I create folder mkdir /tmp/pulsar
that pulsar starts to work. Could pulsar automatically create this tmp folder?
Probably a problem with the permissions on your /tmp
directory.
I'm not a unix wizard so I could be wrong, but I think the /tmp
directory should be readable/writable by anyone.
Just in case, you could use the --tmp-dir
option to change the directory where pulsar writes to.
It's not a permission issue. The /tmp
folder is read and writable by everyone. If I run mkdir /tmp/pulsar
it works.
I also tried with --tmp-dir
and the problem is exactly the same.
I think the problem is that pulsar doesn't try to create a folder if it doesn't exists.
You are right. I just found the bug myself. It only comes up when using a local pulsar configuration repository.
Fix coming up!
I've just released version 0.3.3
with this fix.
Thanks for reporting this bug!
very nice. thx.