Yes, I had QTL in case.in2. Thank you very much Prof. Blaha for the
explanation, the problem was in vec2old. The condition in line 10 seems to be
too weak to handle my case. It only looks for rsh, while my $remote is called
"pbs_remsh", which does the same job but the inner workings are suited to my
cluster. Easy and quick fix.
Thank you once again,
Best regards
Maciej Polak
W dniu 12/10/17 04:28 Maciej Polak <maciej.po...@pwr.edu.pl> napisał:
>
> Sorry, the first sentence should read lapwso: why does "x lapw0 -p", "x lapw1
> -p" and "x lapwso -p" work every time?
>
> W dniu 12/10/17 04:25 Maciej Polak <maciej.po...@pwr.edu.pl> napisał:
> >
> > Thank you for your answer, but do you know then why does "x lapw0 -p", "x
> > lapw1 -p" and "x lapw2 -p" work every time? run_lapw, also works very well.
> > I have set the "$REMOTE" variable to "pbs_remsh", which is what my cluster
> > uses, and everything works perfectly, except for "x lapw2 -p", which used
> > to run no problems on version 14.2.
> >
> > Best regards
> >
> > Maciej Polak
> >
> > W dniu 11/10/17 21:12 Laurence Marks <l-ma...@northwestern.edu> napisał:
> > >
> > >
> > > This is local to your cluster. You almost need to talk to your sysadmins.
> > > There are many possible solutions, but without knowing how your
> > > OS/ssh/jobs are setup nobody will be able to do more than guess.
> > >
> > >
> > >
> > > On Oct 11, 2017 8:36 PM, "Maciej Polak" <maciej.po...@pwr.edu.pl
> > > <maciej.po...@pwr.edu.pl>> wrote:
> > >
> > > >
> > > > Dear WIEN2k community,
> > > >
> > > > I am faced with a problem, where the "x lapw2 -p" procedure on my
> > > > cluster asks me for passwords to all the nodes it uses:
> > > >
> > > >
> > > >
> > > >
> > > > calculating QTL's from parallel vectors
> > > > 10.27.75.188(javascript:main.compose('new',
> > > > 't=mpo...@wn0125.ib.trojan.kdm.wcss.pl')" iwc-bad-attr=""
> > > > >mpo...@wn0125.ib.trojan.kdm.wcss.pl's password:
> > > >
> > > >
> > > > no matter what I do after i get:
> > > >
> > > >
> > > >
> > > > Received disconnect from
> > > >
> > > >
> > > > And it repeats for all the nodes that are used.
> > > >
> > > >
> > > > This only happens when i invoke "x lapw2 -p" by itself, the lapw2
> > > > within the flow of "run_lapw" correctly uses the passwordless command
> > > > for communicating between nodes that is specified as a part of the
> > > > ./siteconfig_lapw for compilaton.
> > > >
> > > > I am not allowed to log in directly into nodes, so no password works,
> > > > and even if it did, I want the job to run without my input, like all
> > > > the other do, and use the ssh method provided with the compilation.
> > > >
> > > > Is there a fix to this? If i'm not mistaken, this issue started
> > > > with WIEN2k 16.1 and persists through version 17.1. All other parts i
> > > > use (lapw0,1 and lapwso) work as expected with no problems.
> > > >
> > > > I would really appreciate help in this matter.
> > > >
> > > > Best regards
> > > >
> > > > Maciej Polak
> > > >
> > > >
> > > >
> > > >
_______________________________________________
Wien mailing list
Wien@zeus.theochem.tuwien.ac.at
http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien
SEARCH the MAILING-LIST at:
http://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/index.html
