Deploy Error... Permission denied

[carrud]

Yes, I have successfully worked around this issue by putting a chmod in our build.xml.

However, this is just not right. This is a dangerous way to fix this and leaves us vulnerable if we were to need to reinstall, etc. But we are up and that is good.

It is just a same to spend so many hours chasing this and I'm interested to know what is the underlying cause of this.

[Travis Hoffman]

Originally Posted by carrud

Yes, I have successfully worked around this issue by putting a chmod in our build.xml.

However, this is just not right. This is a dangerous way to fix this and leaves us vulnerable if we were to need to reinstall, etc. But we are up and that is good.

It is just a same to spend so many hours chasing this and I'm interested to know what is the underlying cause of this.

I agree completely - I'd like the NI/WPILib people to at least investigate what might be causing this to occur and publish an endorsed method of dealing with the problem should it occur. If this happens to someone while at an event....

[Greg McKaskle]

If it makes you feel better, we have been talking about you, just not to you. We are engineers too, after all.

I had something similar happen to me during the beta, but I think I caused it by putting some things on the target using ftp and having a folder owned by admin that wouldn't allow other tools to write to their normal location.

Brad is looking to see if the tools may be creating something like this.

If you see the situation again and want to do some sleuthing, shell in and run the following...

find /home/lvuser ! -user lvuser -print

This will show all files under lvuser that are not owned by it. I have two files like that on my roboRIO, but nothing concerning. A directory could really foul up a deployment, and that would help the Eclipse-meisters know where to start looking. And that presumably is what you would chown to lvuser in order to get around it.

Greg McKaskle

[carrud]

Greg, I will try this out tomorrow. I didn't attend today's meeting but as of Sunday night my Permission denied problem was hard and reproducible. So I'll try this dump and see what we've got.

Thanks, Clark