[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ptp-user] Permission denied error
|
Oops. I have no idea why I was running it as root (that's what comes of trying to replicate an error in a hurry I guess), but I went and changed the source file to an application and it works fine now. (It still won't automatically start the proxy though). Thanks a LOT for figuring that out.
This:
> (Eclipse:26420): libgnomevfs-WARNING **: Failed to open session DBUS
> connection: Did not receive a reply. Possible causes include: the
> remote application did not send a reply, the message bus security
> policy blocked the reply, the reply timeout expired, or the network
> connection was broken.
> Volume monitoring will not work.
didn't show up again when I wasn't running as root.
However, I tried launching a non-executable file again, not as root this time, to address this issue:
"Trying to launch a non-executable shouldn't cause the control system to be disabled though.
I'll open a bug on this."
Here's the output again:
nafreed@Nomini-desktop:~/workspace/eclipse$ ./eclipse
In getResourceManagerFactories
retrieved factory: Simulation, org.eclipse.ptp.simulation.core.resourcemanager
leaving getResourceManagerFactories
Your Control System Choice: '<UNDEFINED CS>'
Your Monitoring System Choice: '<UNDEFINED MS>'
No previous (or invalid) control or monitoring system selected.
Default systems set to Open Runtime Environment (ORTE). To change, use the Window->Preferences->PTP preferences page.
Your Default Control System Choice: 'Open Runtime Environment (ORTE)'
Your Default Monitoring System Choice: 'Open Runtime Environment (ORTE)'
In retrieveConfigurationWizardPageFactories
wizard page factory:
org.eclipse.ptp.simulation.ui.wizards.SimulationRMConfigurationWizardPageFactory@2e1b6c for class: class org.eclipse.ptp.rmsystem.SimulationResourceManagerFactory
leaving retrieveConfigurationWizardPageFactories
XXXXXXXXXXX refreshRuntimeSystems(false), isInitialized():false
XXXXXXXXXXX refreshRuntimeSystems calling initialize(), force:false, isInitialized():false
refreshRuntimeSystems
SHUTTING DOWN CONTROL/MONITORING/PROXY systems where appropriate
User selected 1 simulated machines.
SimPreferences: Machine 0 = 1 nodes
ModelManager.runtimeNodeGeneralName - #keys = 2, #values = 2
Unknown machine ID (machine0), adding to the model.
Unknown node number (0), adding to the model.
XXXXXXXXXXX refreshRuntimeSystems(false), isInitialized():true
XXXXXXXXXXX refreshRuntimeSystems(true), isInitialized():true
XXXXXXXXXXX refreshRuntimeSystems calling initialize(), force:true, isInitialized():true
refreshRuntimeSystems
SHUTTING DOWN CONTROL/MONITORING/PROXY systems where appropriate
OMPIProxyRuntimeClient - firing up proxy, waiting for connecting. Please wait! This can take a minute . . .
ORTE_SERVER path = ''
OS = 'linux', Architecture = 'x86', OS_ARCH combo = 'org.eclipse.ptp.linux.x86'
PTP Version = 1.1.0
All Found Fragments:
update@plugins/org.eclipse.ptp.linux.ppc/ [137]
update@plugins/org.eclipse.ptp.linux.x86/ [138]
update@plugins/org.eclipse.ptp.linux.x86_64/ [139]
update@plugins/org.eclipse.ptp.macosx.ppc/ [140]
update@plugins/org.eclipse.ptp.macosx.x86/ [141]
Testing fragment 1 with this OS/arch - path: '/home/nafreed/workspace/eclipse/plugins/org.eclipse.ptp.linux.ppc/'
Testing fragment 2 with this OS/arch - path: '/home/nafreed/workspace/eclipse/plugins/org.eclipse.ptp.linux.x86/'
Correct fragment for our OS & arch
Searching for file in '/home/nafreed/workspace/eclipse/plugins/org.eclipse.ptp.linux.x86/bin/ptp_orte_proxy'
**** FOUND IT!
sessionCreate(0,0)
bind(
0.0.0.0/0.0.0.0:0)
port=38604
Waiting on accept.
OMPIProxyRuntimeClient waiting on {201, 210}
RUNNING PROXY SERVER COMMAND: '/home/nafreed/workspace/eclipse/plugins/org.eclipse.ptp.linux.x86/bin/ptp_orte_proxy --port=38604'
accept thread starting...
OMPIProxyRuntimeClient got event: EVENT_RUNTIME_CONNECTED
OMPIProxyRuntimeClient notifying...
OMPIProxyRuntimeClient awoke!
<0000000b STARTDAEMON>
OMPIProxyRuntimeClient waiting on {200, 201, 211}
++++++++++ ptp_orte_proxy: proxy_svr_connect returned.
++++++++++ ptp_orte_proxy: StartDaemon(orted orted --scope public --seed --persistent --no-daemonize --universe PTP-ORTE-6879 --report-uri 5)
++++++++++ ptp_orte_proxy: CHILD: Starting execvp now!
++++++++++ ptp_orte_proxy: proxy_svr_connect returned.
++++++++++ ptp_orte_proxy: PARENT: orted_pid = 6879
accept thread exiting...
event thread starting...
++++++++++ ptp_orte_proxy: PARENT: URI = 0.0.0;tcp://129.219.33.247:47880
++++++++++ ptp_orte_proxy: ORTEInit (PTP-ORTE-6879)
OMPIProxyRuntimeClient got event: EVENT_RUNTIME_OK
OMPIProxyRuntimeClient notifying...
OMPIProxyRuntimeClient awoke!
OMPIMonitoringSystem startup()
OMPIMonitoringSystem: initiateDiscovery phase
<00000008 DISCOVER>
++++++++++ ptp_orte_proxy: Start daemon returning OK.
++++++++++ ptp_orte_proxy: Hostname = 'Nomini-desktop'
++++++++++ ptp_orte_proxy: Username = 'nafreed'
++++++++++ ptp_orte_proxy: Groupname = 'nafreed'
++++++++++ ptp_orte_proxy: DISCOVERY PHASE: end
OMPIProxyRuntimeClient got event: EVENT_RUNTIME_NODEATTR [Ljava.lang.String;@11c0b76 : [Ljava.lang.String;@347cdb
ModelManager.runtimeNodeGeneralName - #keys = 7, #values = 7
Unknown machine ID (0), adding to the model.
Unknown node number (0), adding to the model.
XXXXXXXXXXX refreshRuntimeSystems(false), isInitialized():true
XXXXXXXXXXX refreshRuntimeSystems(false), isInitialized():true
OS = 'linux', Architecture = 'x86', OS_ARCH combo = 'org.eclipse.ptp.linux.x86'
PTP Version = 1.1.0
All Found Fragments:
update@plugins/org.eclipse.ptp.linux.ppc/ [137]
update@plugins/org.eclipse.ptp.linux.x86/ [138]
update@plugins/org.eclipse.ptp.linux.x86_64/ [139]
update@plugins/org.eclipse.ptp.macosx.ppc/ [140]
update@plugins/org.eclipse.ptp.macosx.x86/ [141]
Testing fragment 1 with this OS/arch - path: '/home/nafreed/workspace/eclipse/plugins/org.eclipse.ptp.linux.ppc/'
Testing fragment 2 with this OS/arch - path: '/home/nafreed/workspace/eclipse/plugins/org.eclipse.ptp.linux.x86/'
Correct fragment for our OS & arch
Searching for file in '/home/nafreed/workspace/eclipse/plugins/org.eclipse.ptp.linux.x86/bin/sdm'
**** FOUND IT!
XXXXXXXXXXXX Waiting for Universe to Populate
MODEL MANAGER: newJob(1)
ModelManager.run() - new JobID = 1
JAVA OMPI: run() with args:
name: max.c
path: /home/nafreed/workspace/Max
cwd: /home/nafreed/workspace/Max
machineName: Machine0
#procs: 6
#proc/node: 1
firstNode#: 0
isDebug? false
<0000014f RUN 6:6a6f62494400 2:3100 9:657865634e616d6500 6:6d61782e6300 b:70617468546f4578656300 1c:2f686f6d652f6e6166726565642f776f726b73706163652f4d617800 b:6e756d4f6650726f637300 2:3600 d:70726f63735065724e6f646500 2:3100 d:66697273744e6f64654e756d00 2:3000 b:776f726b696e6744697200 1c:2f686f6d652f6e6166726565642f776f726b73706163652f4d617800>
OMPIProxyRuntimeClient got event: EVENT_RUNTIME_ERROR 1202 Permission denied
Fatal error from proxy: 'Permission denied'
Fatal error from proxy: 'Permission denied'
On 3/28/07, Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
Hi Natalie,
Are you running Eclipse as root? I see the following:
> ++++++++++ ptp_orte_proxy: Start daemon returning OK.
> ++++++++++ ptp_orte_proxy: Hostname = 'Nomini-desktop'
> ++++++++++ ptp_orte_proxy: Username = 'root'
> ++++++++++ ptp_orte_proxy: Groupname = 'root'
> ++++++++++ ptp_orte_proxy: DISCOVERY PHASE: end
Also, when you launch the job, it picks up the following location for
the workspace:
> path: /root/workspace/Max
> cwd: /root/workspace/Max
I'm also puzzled about this:
> name: max.c
This seems to indicate you're trying to launch '
max.c', which is the
source file, as an application. I suspect this is where the
permission denied error is coming from. Trying to launch a non-
executable shouldn't cause the control system to be disabled though.
I'll open a bug on this.
Finally, there is this error from Eclipse:
> (Eclipse:26420): libgnomevfs-WARNING **: Failed to open session DBUS
> connection: Did not receive a reply. Possible causes include: the
> remote application did not send a reply, the message bus security
> policy blocked the reply, the reply timeout expired, or the network
> connection was broken.
> Volume monitoring will not work.
This is probably not related, but I've never seen it before.
Greg