Permission denied when pushing code

[SuperBK]

I did put on updates and after that the error occurred. I thought it was just WPI plugins, but it looks like at some point between Feb 13 and Feb 29, the update also updated Eclipse to 4.5.2 4.5.2.20160218-0600

[Astropolly]

I'm having the same problem. Everything worked previously when I had Mars 1 installed. Now I have Mars 2 and I can't deploy code. I can't actually say if that is the problem though.
I used PuTTY to ssh into the roboRIO, and I used the chmod command as explained on these threads. I then tried to deploy code - without resetting anything, but I got the error
..\wpilib.cpp\current\ant\buil.xml:78: server indicted an error: scp: /home/lvuser//robotCommand: Permission denied .

the results of the ls -lah /home/lvuser/ command show
admin@roboRIO-1138-FRC:~# ls -lah /home/lvuser/
total 10292
drw-r--r-- 4 lvuser ni 656 Mar 1 10:39 .
drwxr-xr-x 5 admin administ 416 Jun 5 2015 ..
-rwxrwxrwx 1 lvuser ni 410 Apr 30 2015 .bashrc
-rwxrwxrwx 1 lvuser ni 152 Apr 30 2015 .profile
-rw-r--r-- 1 lvuser ni 10.0M Mar 1 10:39 FRCUserProgram
lrwxrwxrwx 1 admin ni 42 Dec 17 10:34 FRC_UserProgram.log -> /var/local/natinst/log/FRC_UserProgram.log
lrwxrwxrwx 1 admin ni 22 Dec 17 10:31 README_File_Paths.txt -> /README_File_Paths.txt
drwxrwxrwx 3 lvuser ni 232 Dec 17 10:34 frc
drwxrwxrwx 4 lvuser ni 296 Dec 17 10:35 natinst


I will try making the changes to the build.xml file, but I was expecting this to work at least the first time

I am so lost. Please help

[SuperBK]

log in with putty and issue the chmod 777 /home/lvuser/ command again. Then make the change to the build.xml file before trying to deploy code.

Add
<sshexec host="${target}"
username="admin"
password="${password}"
trust="true"
failonerror="false"
command="chmod 777 /home/lvuser"/>


right before this line:
<scp file="${wpilib.ant.dir}/robotCommand" todir="${username}@${target}:/home/lvuser/" password="${password}" trust="true"/>

[taichichuan]

OK, so based on the inputs from several on this thread, I've created a new build.xml that solves all of the permission problems and successfully deploys code from within Eclipse. I've attached it to this post.

Simply, copy the build.xml.txt file to:

c:\Users\<username>\wpilib\cpp\current\ant\build.x ml

(Make sure to substitute your user name and it should be build.xml -- for some reason the formatting is inserting what looks like a space between the x and the ml)

And the deploy will start working again. This does 2 chmods and that seems to correct the problem until Brad & Co. can find the real fix.

HTH,

Mike A.
FRC #116

[BradAMiller]

We just published an update to the eclipse plugins, both the release and stable versions.

Can anyone with the problem with the C++ permissions please try to update your version of the eclipse plugins and verify that it's working for you? If you could reimage the roboRIO just to make sure that everything is reset back to the way it should be that would be helpful. The new version copies some of the files to the roboRIO slightly differently than before.

FYI: there is also an updated C++ camera server class and the version number has been bumped up from 4 to 5. Otherwise this and the previous version should be the same.

Brad

[taichichuan]

Originally Posted by BradAMiller

We just published an update to the eclipse plugins, both the release and stable versions.

Can anyone with the problem with the C++ permissions please try to update your version of the eclipse plugins and verify that it's working for you? If you could reimage the roboRIO just to make sure that everything is reset back to the way it should be that would be helpful. The new version copies some of the files to the roboRIO slightly differently than before.

FYI: there is also an updated C++ camera server class and the version number has been bumped up from 4 to 5. Otherwise this and the previous version should be the same.

Brad

Hi Brad,

Sorry, the fix didn't seem to fix the problem. I'm using the Mars.2 release of Eclipse, BTW. Here's the output of the "Run as" output:


Buildfile: C:\Users\mike\workspace-2016\ExampleBoard\build.xml
Trying to override old definition of task classloader
get-target-ip:
[echo] Trying Target: roboRIO-116-FRC.local
[echo] roboRIO found via mDNS
dependencies:
[echo] roboRIO image version validated
deploy:
[sshexec] Connecting to roboRIO-116-FRC.local:22
[sshexec] cmd : rm -f /home/lvuser/FRCUserProgram
[sshexec] Could not chdir to home directory /home/lvuser: Permission denied
[sshexec] rm: can't stat '/home/lvuser/FRCUserProgram': Permission denied
[sshexec] Remote command failed with exit status 1
[echo] [athena-deploy] Copying code over.
[scp] Connecting to roboRIO-116-FRC.local:22

BUILD FAILED
C:\Users\mike\wpilib\cpp\current\ant\build.xml:67: server indicated an error: scp: /home/lvuser/FRCUserProgram: Permission denied

Total time: 5 seconds


Anything else you need to help debug the issue?

HTH,

MikeA
FRC #116

[fsilberberg]

Mike,

If the permissions were broken originally, the update likely won't fix them. It should prevent it from happening in future deploys, but if /home/lvuser doesn't have exec permissions currently, nothing in this update will fix it. Does manually running a chmod +x /home/lvuser as admin, then trying to redeploy fix it?

[taichichuan]

Originally Posted by fsilberberg

Mike,

If the permissions were broken originally, the update likely won't fix them. It should prevent it from happening in future deploys, but if /home/lvuser doesn't have exec permissions currently, nothing in this update will fix it. Does manually running a chmod +x /home/lvuser as admin, then trying to redeploy fix it?

OK, if I manually chmod the /home/lvuser directory to 0777, then the new plug-ins work.

Next, I reformatted and reinstalled V19 firmware and then reloaded V 3.0.0F0 firmware on the RoboRIO. I then tried the deploy and everything seems to work. So, you need to make sure that the RoboRIO is back to a pristine state and the new plugins seem to work.

Good work gang!

Thanks,

MikeA

[BradAMiller]

Glad to hear it's working for you now. There was a hiccup with the Java part of the install, something broke in our build, and a new version is posted that should fix that issue. Just waiting to hear some confirmation that everything is OK now.

Brad

[rod@3711]

Looks good, thanx