Salome MECA 2010 - 32bits
- Claus
-
- Offline
- Moderator
-
- Posts: 670
- Thank you received: 34
This is activating ASTER and hitting 'run'
stuff stuff stuff that's too long for one post
Output of command : ssh -n -l claus claus-desktop /home/claus/Programs/SALOME-MECA-2010.1-x86_64/aster/bin/as_run --serv claus@claus-desktop:/home/claus/Stuff/CAD/meca-test/linear-static.export
JOBID=10704 QUEUE=interactif
EXIT_CODE=0
I have both 'rsh' and 'ssh' working password-less so I can login just by typing 'rsh claus-desktop' without a password, same with 'ssh' - this is important.<br /><br />Post edited by: Claus, at: 2010/05/07 22:12
Code_Aster release : STA11.4 on OpenSUSE 12.3 64 bits - EDF/Intel version
- Torben
- Topic Author
- Offline
- Premium Member
-
- Posts: 91
- Thank you received: 1
- Claus
-
- Offline
- Moderator
-
- Posts: 670
- Thank you received: 34
If related to tcp/ip and such it is strange that the Salome MECA 2009 is working fine but 2010 isn't. But I don't know the technical details of how jobs are submitted and I don't know if these protocols have changed since 2009. Re. the board eating posts ... when writing longer messages I occasionally hit ^A ^C to put a backup in the buffer.
I agree, it was/is a long shot on my part, but salome/aster is extremely pedantic with rsh/ssh.
Have you tried removing all the config files i.e. .astkrc.x, .salome* from you home folder and doing a fresh install of SM?
Does the 'postinstall' script raise any errors? Any [NO]s instead of [OK]s ?
Yes, this board actually taught me always to do a ctrl-a + ctrl-c everythime I post (anywhere) - just forgot it this time

Code_Aster release : STA11.4 on OpenSUSE 12.3 64 bits - EDF/Intel version
- Torben
- Topic Author
- Offline
- Premium Member
-
- Posts: 91
- Thank you received: 1
Maybe this info can provide a lead as to what has to be done/reconfigured to enable the output window, which is really a nice feature, especially for bigger jobs.
- Claus
-
- Offline
- Moderator
-
- Posts: 670
- Thank you received: 34
I just found out that the problem seems related to the output window. Unselecting "[ ] Interactive Follow up" in the Aster case definition enabled aster to complete the analysis. To make this the default choice for new cases, select the Aster module. Then in File -> Preferences -> Aster unselect "[ ] Interactive Follow up". And vupti, it worked.
Maybe this info can provide a lead as to what has to be done/reconfigured to enable the output window, which is really a nice feature, especially for bigger jobs.
I'll quote myself then

Had a similar problem with MECA today; after launching a simple case I would get a (_) instead of (ERROR) or (OK) - typical symptom of Xorg having the server-arg '-nolisten tcp' - have you made sure yours doesn't have that activated. Just in case.
In /etc/kde4/kdm/kdmrc you should look for -nolisten tcp and comment that string out with ###'s, then restart the X server. Likewise with gdm check /etc/gdm/custom.conf or google it, I don't have it installed here.
Code_Aster release : STA11.4 on OpenSUSE 12.3 64 bits - EDF/Intel version
- Torben
- Topic Author
- Offline
- Premium Member
-
- Posts: 91
- Thank you received: 1
