[baserinia]

Originally Posted by strider

I have updated my Ubuntu to version 10.04 and suddenly I run into problems with CFX-Pre. I get the error:
p, li { white-space: pre-wrap; } ERROR
CCL validation failed with message:
Warning: Can't check parameter Message Type (/PHYSICS MESSAGES/PHYSICS MESSAGE:msg0000/Message Type): Can't find rule.
Warning: Can't check parameter Severity (/PHYSICS MESSAGES/PHYSICS MESSAGE:msg0000/Severity): Can't find rule.
Warning: Can't check parameter Message (/PHYSICS MESSAGES/PHYSICS MESSAGE:msg0000/Message): Can't find rule.
Warning: Can't check parameter Suppressed (/PHYSICS MESSAGES/PHYSICS MESSAGE:msg0000/Suppressed): Can't find rule.

Design modeler and mesher are working (thanks to irw).

Any idea?

Hi Everyone,

I have the same problem. Everything works fine but I cannot open the old .cfx file from version 11. I keep getting an error box like this in CFX-Pre:

-------------------------------------------------------------------------------------------------
p, li { white-space: pre-wrap; } ERROR
CCL validation failed with message:
Warning: Can't check parameter Message Type (/PHYSICS MESSAGES/PHYSICS MESSAGE:msg0000/Message Type): Can't find rule.
Warning: Can't check parameter Severity (/PHYSICS MESSAGES/PHYSICS MESSAGE:msg0000/Severity): Can't find rule.
Warning: Can't check parameter Message (/PHYSICS MESSAGES/PHYSICS MESSAGE:msg0000/Message): Can't find rule.
Warning: Can't check parameter Suppressed (/PHYSICS MESSAGES/PHYSICS MESSAGE:msg0000/Suppressed): Can't find rule.
-------------------------------------------------------------------------------------------------

Does anybody else has the same problem?

[carlosm]

I'm ubuntu 10.04 user and, after solve the MD and Meshing problems, now CFX-pre not works. Anyone with this problem ? anyone has run CFX-pre ?

[slydog]

To start, can anyone tell me if I can turn on high-verbosity debugging in Workbench?

I'm trying to use DesignModeler inside Workbench 2.0 (Ansys 12.1.1). I can launch Workbench (runwb2) and can drag a DesignModeler task onto the project schematic, but when I try to open a new geometry, DesignModeler never comes up. There are no error messages anywhere, and no indication as to why DesignModeler won't load.

I can successfully run Fluent through Workbench, or in standalone mode (fluent). Had no errors during Ansys 12.1.1 install (install.err), and RegSvr32 DLL registrations were all fine (install.log).

I have tried the LD_LIBRARY_PATH info mentioned earlier. Don't have problems with "uname" or "arch" commands in Fedora. Also tried launching using Mesa (runwb2 -oglmesa), which opens Workbench fine but does not resolve DesignModeler issue.

Info about my system:
OS: Fedora Core 8, 64 bit (x86_64)
Hardware: AMD Opteron 2216 dual-core, Tyan S2937 m/b, 32GB RAM, 2TB RAID 5 harddrives, ATI FireGL V3600 graphics card (with latest ATI linux drivers)
Ansys version: 12.1.1 for x86_64 (latest available download as of 10/14/2010)

Any thoughts would be much appreciated.

[carlosm]

Hey Slydog !

Look, just the past week I can make DM and meshing works...then I guess I can help you

tell me, when DM and Meshing doesn't starts, what messages you get in terminal ?

[slydog]

My problem is that there is no information anywhere about why Design Modeler won't start.

When I right-click on the DM and select "New geometry", I get a message in the lower left corner of the Workbench window saying "Starting Design Modeler...". The program thinks for about 30 sec and then says "Ready" without ever starting DM.

No messages appear in the "Messages" window in Workbench, or in the "Progress" window.

There are no messages in the terminal window that I launch Workbench from (runwb2).

[carlosm]

There's no messages...well, have you installed the rpm libraries and the mesa utilities ?

for rpm utilities : sudo apt-get install alien (in terminal window)

for mesa utils : aptitude install mesa-utils gamin

also the libmotif : sudo aptitude install libmotif3

you should also :
make two scripts (rpm and runwb2) as describe in previous post.
set the LD_LIBRARY_PATH

let me know if you have made all the previous process...

[slydog]

Originally Posted by carlosm

There's no messages...well, have you installed the rpm libraries and the mesa utilities ?

for rpm utilities : sudo apt-get install alien (in terminal window)

for mesa utils : aptitude install mesa-utils gamin

also the libmotif : sudo aptitude install libmotif3

you should also :
make two scripts (rpm and runwb2) as describe in previous post.
set the LD_LIBRARY_PATH

let me know if you have made all the previous process...

Carlos,

I should clarify again that I'm using Fedora Core 8, not Ubuntu or Debian.

1) As far as I know, rpm utilities are fully installed in Fedora (I'm somewhat of a Linux newbie), and when I search the YUM updater repositories, I don't find anything called "alien". I have not had any problems or errors installing Ansys 12.1.1, especially with the "uname" command issue that's mentioned frequently in this thread.

2) I have installed all Mesa-related packages with no problems using the YUM updater, except for mesa-libGLw.x86_64, which gives me this error through YUM: "Missing Dependency: libGL.so.1()(64bit) is needed by package mesa-libGLw". The missing library is provided by mesa-libGL.i386, which is installed correctly, according to YUM updater. Furthermore, I can see the libGL.so.1 library (and symlinks) in /usr/lib64/ .

The package mesa-libGLw.x86_64 is "Xt / Motif OpenGL widgets"...do I really need that??

3) I cannot find anything related to libmotif or motif in the YUM install/update repositories. Any other name for that package?

4) What exactly should I set the LD_LIBRARY_PATH variable to? I have set it to all of the various options mentioned earlier in the thread, but no luck. Here's what it currently is:
LD_LIBRARY_PATH=/usr/lib64:/usr/lib:/ansys_inc/v121/aisol/lib/linx64:/ansys_inc/v121/aisol/mw/lib-amd64_linux_optimized:/ansys_inc/v121/aisol/dll/linx64:/ansys_inc/v121/Framework/bin/Linux64:/ansys_inc/v121/Framework/bin/Linux64/Mesa

5) I set up the rpm script in /usr/bin/ per post #15, but no luck.

6) I'm not exactly sure which "workbench" script you're referring to? In post #54 that script primarily sets the LD_LIBRARY_PATH variable, which I've already done...?

[carlosm]

the rpm script should be like that

#!/bin/bash
echo glibc-2.11.1

later, in terminal chmod +x /usr/bin/rpm (on the new script)

the wb2 script, placed in /usr/local/bin is

#!/bin/bash
RUNWB2CMD=`which runwb2`
RUNWB2DIR=`dirname $RUNWB2CMD`
if test -z "$LD_LIBRARY_PATH"; then
LD_LIBRARY_PATH=$RUNWB2DIR/Mesa:$RUNWB2DIR
else
LD_LIBRARY_PATH=$RUNWB2DIR/Mesa:$RUNWB2DIR:$LD_LIBRARY_PATH
fi
export LD_LIBRARY_PATH
export LANG=en_US.UTF8
runwb2 $@

for set the path

LD_LIBRARY_PATH="/usr/ansys_inc/v121/aisol/mw/lib-linux_optimized:/usr/ansys_inc/v121/aisol/lib/linia32::$LD_LIBRARY_PATH"

I also need to remove all the old graphic card drivers and install a new driver that support glx.

[slydog]

Originally Posted by carlosm

the rpm script should be like that



later, in terminal chmod +x /usr/bin/rpm (on the new script)

the wb2 script, placed in /usr/local/bin is



for set the path



I also need to remove all the old graphic card drivers and install a new driver that support glx.

Carlos,

I made both scripts, set the LD_LIBRARY_PATH variable (although my directories are slightly different than yours since I have an x86_64 installation), and launched Workbench with the wb2 script. I got no errors in the terminal window, and Workbench launched fine. Still can't get DesignModeler to open, though.

I'm pretty sure the ATI driver supports glx (command 'glxinfo' returns "direct rendering: Yes", along with a bunch of other stuff not containing any errors), and I can run 'glxgears' successfully.

Does anyone know if there is a way to try to launch DesignModeler in stand-alone mode (i.e., NOT through the workbench interface)?

[folo]

Originally Posted by slydog

Carlos,

I made both scripts, set the LD_LIBRARY_PATH variable (although my directories are slightly different than yours since I have an x86_64 installation), and launched Workbench with the wb2 script. I got no errors in the terminal window, and Workbench launched fine. Still can't get DesignModeler to open, though.

I'm pretty sure the ATI driver supports glx (command 'glxinfo' returns "direct rendering: Yes", along with a bunch of other stuff not containing any errors), and I can run 'glxgears' successfully.

Does anyone know if there is a way to try to launch DesignModeler in stand-alone mode (i.e., NOT through the workbench interface)?

Slydog,
i found the same problem on my Ubuntu 9.10 , I also don't get any error in terminal, but DM doesn't launch. Please let know if you found any workaround or solution...

[slydog]

Sorry, I haven't yet found a solution or workaround. I'll post it if I find one, but without any errors being listed, it's going to be hard to track down.

[carlosm]

Slydog,

I tell you i've got this same problem (DM and Meshing that doesn't start, and no messages) after updating my ubuntu from 10.04 to 10.10

I really try to fix it, but I really can't.

Then, I have to go back to ubuntu 10.04 again and, my wb and his applications are working properly.

For fix the ubuntu 10.04 problem I just have to :

mesa-utils, libmotif3 and alien (rpm) packages install

and, to redefine the path for libGL.so.1 glx package to /usr/lib

hope this help you guys for something...

but your problem -without terminal or another information, it's hard to resolve.

have you try in previous releases for fedora ?

[slydog]

Carlos,

I installed Ansys 12.1.1 on Fedora Core 4 and it works great (Workbench opens, DesignModeler opens). I didn't have to do any of the scripts mentioned in this thread; Workbench and Design Modeler started right up the first time.

I don't have time right now to track down what exactly is different about Fedora 4 vs Fedora 8, but hopefully someone can comment on anything they know...?

[mhsr]

I just had a very unnerving time with the DM after freshly installing on a notebook running debian testing and acting as license server. I had the same issue with a non starting DesignModeler (and Meshing Tool) as described by you, slydog.

Since ubuntu is basing on debian the problem may be caused by the default setup of the system file /etc/hosts. By default it resolves the IP 127.0.0.1 not only to 'localhost' but also to the hostname of your PC, which confuses the DesignModeler, the Meshing Tool and last but not least the parallel messaging library pvm. In that case move hostname of your PC from the 'localhost' line to a new line with the correct IP of your network interface.

Unfortunately, some automated network managers reset the hosts-file after rebooting.

[slydog]

Originally Posted by mhsr

I just had a very unnerving time with the DM after freshly installing on a notebook running debian testing and acting as license server. I had the same issue with a non starting DesignModeler (and Meshing Tool) as described by you, slydog.

Since ubuntu is basing on debian the problem may be caused by the default setup of the system file /etc/hosts. By default it resolves the IP 127.0.0.1 not only to 'localhost' but also to the hostname of your PC, which confuses the DesignModeler, the Meshing Tool and last but not least the parallel messaging library pvm. In that case move hostname of your PC from the 'localhost' line to a new line with the correct IP of your network interface.

Unfortunately, some automated network managers reset the hosts-file after rebooting.

Martin,

Thanks very much for the suggestion. I looked at the /etc/hosts file in Fedora 8 and it did not have the hostname in the 'localhost' line, just:

 
127.0.0.1  localhost.localdomain  localhost

However, on the Fedora 4 machine where DM works correctly, the /etc/hosts file is:

 
127.0.0.1  localhost.localdomain  localhost  hostname

where hostname is the computer's hostname.

I tried changing the /etc/hosts file for the Fedora 8 machine to look just like the Fedora 4 machine, but no luck launching DesignModeler.

The terminal window on the Fedora 4 machine prints the following when I launch Workbench and start DesignModeler:

 
igamma=45455
igamma=45455
Entered DesignModelerHelper::SetSystemName
Entered DesignModelerHelper::SetSystemId

Any idea if that will help me track down the problem in Fedora 8?

[mhsr]

Originally Posted by mechanicaldesign

Hi all,

Yours advice is very useful to understand how can be made to work Workbench on uncertified distro. However, I installed ANSYS 11 64biti on CentOS5.4 64biti. Everithings works ok, but when I want to launch workbench, I encountered the next message:

>su
>password
>./runwb
>./runwb: line 24: 5827 Segmentation fault $DS_INSTALL_DIR/workbench -StartPage $*

Because ANSYS is made to work well for Red Hat, means that on CentOS must work well to. But how I see is not so simple to made it work on recomanded distros ( CentOS, RedHat). I think missing some library from my installation, these is the reason because I cant use it.

What means this error ? How I can fixed? Have somebody any ideea ?

I waiting much early is possible your suggestion, ideea or opinion referring to my problem.

Thank you very much for support and understanding.

Best regards.

As I remember, ANSYS 11 is supported von RHEL 4.x (and also on CentOS 4.x) therefore it may help to test it on a former CentOS release. Unfortunately, my experience with ANSYS 11 + CentOS 4.4 is limited to the 32bit distro only.

[mhsr]

Originally Posted by slydog

 
igamma=45455
igamma=45455
Entered DesignModelerHelper::SetSystemName
Entered DesignModelerHelper::SetSystemId

Any idea if that will help me track down the problem in Fedora 8?

This is just normal debug output, which is not related to the errors

I do think, the problem is related to some graphic libraries of the system, which are too recent - Fedora 8 is using much later lib versions than RHEL 5.x does.

I had similar trouble with ANSYS 10 and 11 after upgrading debian. Thus, I'm not sure whether there's a way to make ANSYS 12 run on quite recent distros unless there's a possibility to install backport libraries and pointing ANSYS to those.

[filippo.aero]

Hello, I've just installed Ansys 12 on OpenSuse 11.2 64 bit. The installation and licensing are perfect, I can start the ansys launcher, cfx, fluent etc.. however the command runwb2 doesn't work:
when I launch it, the windows of Ansys shows up, saying is loading, but then it arrives at ans.fluent.gui.addin loaded and freezes. If i click on it the windows disappears and nothing happens. Do you have any idea? where can I find a log of the startup?

[slydog]

For Ubuntu 10 users (with NVIDIA graphics?), here's a workaround involving a symlink that my Linux admin found for the issue of DesignModeler not opening:

https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/589250


I don't have Ubuntu or NVIDIA so can't check it out, but it worked for my admin on a Ubuntu 10 box with Ansys 12.1 Workbench.

[Yankee]

Originally Posted by mhsr

I just had a very unnerving time with the DM after freshly installing on a notebook running debian testing and acting as license server. I had the same issue with a non starting DesignModeler (and Meshing Tool) as described by you, slydog.

Since ubuntu is basing on debian the problem may be caused by the default setup of the system file /etc/hosts. By default it resolves the IP 127.0.0.1 not only to 'localhost' but also to the hostname of your PC, which confuses the DesignModeler, the Meshing Tool and last but not least the parallel messaging library pvm. In that case move hostname of your PC from the 'localhost' line to a new line with the correct IP of your network interface.

Unfortunately, some automated network managers reset the hosts-file after rebooting.

Thank you once again, mhsr, your post #74 made me find how to make DM & Meshing work again after an upgrade to ubuntu 10.10 (I tried two days long before that...)

Here is the procedure I use to install ansys 12.1 on ubuntu 10.10 64bits :

# 1. enter root session for steps 1-6 (assuming you're allowed to do that, it will ask YOUR passwd and not the one of root)
sudo -s

# 2. add "rpm" and "uname" custom commands to make the installer happy (supposing /usr/local/bin is in the PATH)
cat > /usr/local/bin/uname <<'eof'
#!/bin/bash
  if [ "$1" = "-i" ]; then
    echo `/bin/uname -m | sed -e 's/i686/i386/' `
  else
    /bin/uname $1
  fi
eof
  chmod +x /usr/local/bin/uname
cat > /usr/local/bin/rpm <<'eof'
#!/bin/bash
  echo glibc-2.12-1
eof
  chmod +x /usr/local/bin/uname

# 3. be sure that your hostname appears in only 1 uncommented line of /etc/host (else edit it manually)
  grep `hostname` /etc/hosts

# 4. download linx64_dvd.iso from ansys customer portal into /tmp (not described)

# 5. install ansys (choosing its installation directory, and the products for which you have licenses)
#    at the end of install you should provide the name of your license server and verify its ports
#    don't be afraid of the 12 messages "[: 335: xxx.so: unexpected operator" in /ansys_inc/install.err
  mkdir /mnt/iso
  mount -o loop -t iso9660 /tmp/linx64_dvd.iso /mnt/iso
  cd /mnt/iso
  ./INSTALL
  cd /
  umount /mnt/iso
  rmdir /mnt/iso

# 6. define environement variables for all users (assuming they use bash) - adapted from "post-install procedures" in ai_unix_2828.pdf
  cat > /etc/profile.d/ansys_config.sh << 'eof'

  SYSVAR=`uname -m` # to choose between 32bit or 64bit pathes
  if [ ${AWP_ROOT121:-undefined}  = undefined ]; then export AWP_ROOT121=/ansys_inc/v121 ; fi
  if [ ${ANSYS121_DIR:-undefined} = undefined ]; then export ANSYS121_DIR=${AWP_ROOT121}/aisol ; fi
  if [ ${SYSVAR} = 'x86_64' ]; then
    if [ ${ICEM_ACN:-undefined}   = undefined ]; then export ICEM_ACN=${AWP_ROOT121}/icemcfd/linux64_amd ; fi
    RUNWB2_DIR=${AWP_ROOT121}/Framework/bin/Linux64 ;
  else
    if [ ${ICEM_ACN:-undefined}   = undefined ]; then export ICEM_ACN=${AWP_ROOT121}/icemcfd/linux ; fi
    RUNWB2_DIR=${AWP_ROOT121}/Framework/bin/Linux32 ;
  fi
  if [ ${ANSYSLIC_DIR:-undefined} = undefined ]; then export ANSYSLIC_DIR=/ansys_inc/shared_files/licensing ; fi
  if [ -d ${ANSYS121_DIR} ]; then              export PATH=${PATH}:${ANSYS121_DIR} ; fi
  if [ -d ${RUNWB2_DIR} ]; then                export PATH=${PATH}:${RUNWB2_DIR} ; fi                # path to runwb2
  if [ -d ${AWP_ROOT121}/fluent/bin ]; then    export PATH=${PATH}:${AWP_ROOT121}/fluent/bin ; fi    # path to fluent
  if [ -d ${AWP_ROOT121}/CFX/bin ]; then       export PATH=${PATH}:${AWP_ROOT121}/CFX/bin ; fi       # path to cfx5
  if [ -d ${AWP_ROOT121}/TurboGrid/bin ]; then export PATH=${PATH}:${AWP_ROOT121}/TurboGrid/bin ; fi # path to cfxtg
  if [ -d ${ICEM_ACN}/bin ]; then export PATH=${PATH}:${ICEM_ACN}/bin ; fi                           # path to icemcfd
  if [ -d ${ANSYSLIC_DIR}/lic_admin ]; then export PATH=${PATH}:${ANSYSLIC_DIR}/lic_admin ; fi       # path to anslic_admin
eof

# 7. quit root session entered in 1.
 exit

# 8. For each user, verify the license (clic on "View Status/Diagnostic Options" then "display the license status")
#    and eventually choose your prefs ("Set License Preferences for user xxx" then v12.1 then, ie "Use Academic Licenses" if you have some...)
 anslic_admin

# 9. logout, login (to activate /etc/profile.d/ansys_config.sh), run ansys and enjoy!
 runwb2

Of course, Fluent worked directly, all that is just needed because of those damned DM and meshing (adapted from windows, it seems...)