This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 268699 - Unable to connect to C++ remote linux buildhost. Same configuration works in netbeans 7 but not in >8
Summary: Unable to connect to C++ remote linux buildhost. Same configuration works in ...
Status: RESOLVED WORKSFORME
Alias: None
Product: cnd
Classification: Unclassified
Component: Remote (show other bugs)
Version: 8.2
Hardware: PC Windows 10
: P3 normal (vote)
Assignee: Vladimir Kvashin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-26 21:24 UTC by avikohn
Modified: 2017-04-05 11:32 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE Log generated with enhanced logging (177.15 KB, application/octet-stream)
2016-10-27 13:31 UTC, avikohn 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description avikohn 2016-10-26 21:24:19 UTC 
Product Version = NetBeans IDE 8.2 (Build 201609300101)
Operating System = Windows 10 version 10.0 running on amd64
Java; VM; Vendor = 1.8.0_101
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.101-b13

Reproducibility: Happens every time
Steps:
Add a build host enter password and user name info


I verified that the pty file is present and proper permissions
I tried clearning the entire dlight directory and restarting netbeans
I tried uninstalling and reinstalling netbeans

	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1443)
	at org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:68)
	at org.openide.util.lookup.Lookups.executeWith(Lookups.java:303)
	at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2058)
INFO [nativeexecution.support.logger]: [350676 ms.] bash: null: command not found
WARNING [nativeexecution.support.logger]: [369648 ms.] Failed to upload pty
WARNING [nativeexecution.support.logger]: [369648 ms.] File /var/tmp/dlight_root/923fc6a6/1232457321/pty doesnt exist, and cannot be uploaded. Do you have enough privileges?
WARNING [nativeexecution.support.logger]: [369648 ms.] You could try to use -J-Dcnd.tmpbase=<other base location> to re-define default one.
SEVERE [org.openide.util.Exceptions]
Comment 1 avikohn 2016-10-26 21:36:59 UTC 
I also tried using just /tmp/ which is completely writable. I received the same message with the changed path.
Comment 2 avikohn 2016-10-26 21:37:42 UTC 
Also I have true root access on the machine so there shouldn't be any limitiations. Additionally I am able to ssh into the machine without issue
Comment 3 Vladimir Kvashin 2016-10-27 11:38:38 UTC 
Could you launch the IDE with the additional command line options
-J-Dnativeexecution.support.logger.level=0 -J-Dremote.support.logger.level=0
and attach IDE log?
(please note that there will be host and user names and some paths there, which you would probably like to strip)
Comment 4 avikohn 2016-10-27 13:31:24 UTC 
Created attachment 162660 [details]
IDE Log generated with enhanced logging
Comment 5 Vladimir Kvashin 2017-03-30 12:25:59 UTC 
In the IDE log I see the following:

File /var/tmp/dlight_root/923fc6a6/1232457321/pty doesnt exist, and cannot be uploaded. Do you have enough privileges?

NetBeans was not able to upload a tiny binary utility (pty) to your remote host. Without pty NetBeans is not able to launch processes on your remote host.

There are two possible workarounds:
1) set up your host so that executable files uploading and launching in /var/tmp/dlight_root/* is possible or 
2) set alternative location for such uploads via -J-Dcnd.tmpbase=<path> command line parameter.

I also think we should make error processing better: in the case of such error, IDE should tell user what I wrote above.
Comment 6 Vladimir Kvashin 2017-03-30 13:46:02 UTC 
(In reply to avikohn from comment #1)
> I also tried using just /tmp/ which is completely writable. I received the
> same message with the changed path.

I'm sorry, I missed this important comment.

I think this could also happen not because of lack of write permission, but because of lack of the execution permission. I know that on some systems execution of binaries from /tmp and /var/tmp is forbidden (even if ls -l shows rwxrwxrwx).

What if you try setting not /tmp, but something in your home directory as tempbase (via -J-Dcnd.tmpbase=<path> command line parameter) - will it help?