|
Don, With your help I am definitly making progress. I can connect now, but I have trouble with authentication. I am using the default settings now for the connection. Port is not specified and the user account is set to inherited. When I am prompted for the login information i use my linux id, all lowercase, username and password. I receive the following "Authentication with HLIDEV failed because the password or user ID is not correct." HLIDEV is the host name. How does the daemon authenticate users? Did I miss something somewhere, I am very close to having this working now! I have no problem with authentication using any type of remote shell! Help! "Don Yantzi" <yantzi@xxxxxxxxxx> wrote in message news:OF96305D47.1D03AA59-ON85256D39.0052BBE9@xxxxxxxxxxxxxxxxxx > Rod, > > When you are using the daemon you do not need to set the port for the RSE > connection. At connect time the RSE connection queries the daemon (on port > 4035) which in turn starts the RSE linux server on a new port. The port > you specify for the RSE connection is this new port that the RSE linux > server runs on. > > If you specify port 4035 in the RSE connection properties then it will not > start because it conflicts with the daemon. Try to leave the port as 0 for > the RSE connection, this tells the daemon to start the RSE linux server on > any available port. > > As for logging, the daemon writes log statements to standard out / err, so > you should redirect those to a file when starting the daemon. > > Don Yantzi > WebSphere Development Studio Client for iSeries > IBM Toronto Lab > Phone: (905) 413-4476 > IBM internal: IBMCA(yantzi) - Internet: yantzi@xxxxxxxxxx > > > > > "Rod Smith" > <rbsmith@xxxxxxxx To: wdsci-l@xxxxxxxxxxxx > ltg.com> cc: > Sent by: Subject: [WDSCI-L] Re: Re: Linux server daemon > wdsci-l-bounces@x > idrange.com > > > 02/06/2003 10:50 > AM > Please respond to > Websphere > Development > Studio Client for > iSeries > > > > > > Yes, I found the missing class in dstore.jar which existed in my > /home/rbsmith/wdsc folder. I issued a "jar xf dstore_core.jar" to expand > it > and issued the ./daemon.linux script again, the server is running now, > however I have a problem with the connection. > > On the linux system the response to starting running ./daemon.linux is: > Daemon running on: hlidev, port: 4035 > > I have set the properties of the "Files" subsystem in rse to specify port > 4035 and my user profile. However when I right client and select connect, > I > am prompted for my password. After entering the password I get: "Connect > failed: Host freebsd not found or not responding". > > I have verfied the ability to connect with telnet to the host on port 4035. > Why is the connection refused, is there a log on the linux system to > review? > > > "Don Yantzi" <yantzi@xxxxxxxxxx> wrote in > message news:OF54FF6E1A.7E3DC799-ON85256D39.004EF1BF=r0JSptLoWH2LmzkN7vd/Rq1cXZ9k6wl g@xxxxxxxxxxxxxxxx > > Rod, > > > > The daemon.linux script sets up the CLASSPATH environment variable so it > > can find the server code. To do this it assumes the directory where you > > run the script from is the same directory where the server .jar files > > exist. The class you are getting an error on should be in the > > dstore_core.jar file. > > > > If you want to move the script to a different directory then you can > change > > the following line from > > > > $dir= $ENV{PWD}; > > > > to > > > > $dir=/home/.... > > > > Do you see the dstore_core.jar file in the same directory as the > > daemon.linux? Does it contain the ServerLauncher class (you can use jar > > -tf dstore_core.jar to get a list of the classes.) > > > > Don Yantzi > > WebSphere Development Studio Client for iSeries > > IBM Toronto Lab > > Phone: (905) 413-4476 > > IBM internal: IBMCA(yantzi) - Internet: > yantzi@xxxxxxxxxx > > > > > > > > > > "Rod Smith" > > <rbsmith@xxxxxxxx To: > wdsci-l@xxxxxxxxxxxx > > ltg.com> cc: > > Sent by: Subject: [WDSCI-L] Re: > Linux server daemon > > wdsci-l-bounces@x > > idrange.com > > > > > > 02/06/2003 09:24 > > AM > > Please respond to > > Websphere > > Development > > Studio Client for > > iSeries > > > > > > > > > > > > > OK, first error resolved, I discovered after expanding the jar, that the > > script and property files contain the wrong line ending characters, I am > > using ee to correct them. I am working on the following classpath > problem, > > > > Exception in thread "main" java.lang.NoClassDefFoundError: > > com/ibm/etools/systems/dstore/core/server/ServerLauncher > > > > Rod > > > > > > "Rod Smith" <rbsmith@xxxxxxxxxxxxxxx> wrote in > > message > news:bbfhig$591$1@xxxxxxxxxxxxxxxxx > > > Has anyone tried to setup and run the rseserver code on Redhat linux > or > > > freebsd. I followed the instructions in the help text and copied the > > > rseserver.jar file to a folder /home/rbsmith/wdsc on my redhat machine > > and > > > freebsd machine from > > > > > C: > > > \WDSC\iseries\eclipse\plugins\com.ibm.etools.systems.universal_5.0.1\serve > > > rruntime. I executed jar xf rseserver.jar and expanded the jar file I > > have > > > executed the chmod 755 on the daemon.linux, auth.pl and server.linux > > files. > > > I have tried to start the server with both the daemon.linux and > > server.linux > > > scripts. Both have failed with a similar message. "bash: > ./daemon.linux: > > No > > > such file or directory". Does anyone have an idea how to fix this? > > > > > > > > > > > > _______________________________________________ > > > This is the Websphere Development Studio Client for iSeries (WDSCI-L) > > mailing list > > > To post a message email: WDSCI-L@xxxxxxxxxxxx > > > To subscribe, unsubscribe, or change list options, > > > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l > > > or email: WDSCI-L-request@xxxxxxxxxxxx > > > Before posting, please take a moment to review the archives > > > at http://archive.midrange.com/wdsci-l. > > > > > > > > > > > _______________________________________________ > > This is the Websphere Development Studio Client for iSeries (WDSCI-L) > > mailing list > > To post a message email: WDSCI-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l > > or email: WDSCI-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/wdsci-l. > > > > > > > > _______________________________________________ > > This is the Websphere Development Studio Client for iSeries (WDSCI-L) > mailing list > > To post a message email: WDSCI-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l > > or email: WDSCI-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/wdsci-l. > > > > > > _______________________________________________ > This is the Websphere Development Studio Client for iSeries (WDSCI-L) > mailing list > To post a message email: WDSCI-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l > or email: WDSCI-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/wdsci-l. > > > > _______________________________________________ > This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list > To post a message email: WDSCI-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l > or email: WDSCI-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/wdsci-l. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.