cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Help us improve the PTC Community by taking this short Community Survey! X

Launching PTC Solution Installer in Linux Environment

RK_10805837
10-Marble

Launching PTC Solution Installer in Linux Environment

Hello,

 

Does anybody has suggestion on how to launch PSI in Linux Environment? I try to launch it using the setup file in the installer but it fails. I have previously launched it in Windows using the same setup file and it launches the GUI without any problem. Any suggestions on the same would be helpful,

 

Thanks,

Ramsha

 

 

ACCEPTED SOLUTION

Accepted Solutions

The issue was the correct permissions were not given to the folder where the PSI was installed. AFter changing the permissions using chmod 777, the PSI GUI was launched.

 

Thanks,

Ramsha Kamal

View solution in original post

10 REPLIES 10
avillanueva
22-Sapphire II
(To:RK_10805837)

You need to port the graphics back to your Windows system. This will require installing some additional packages. I dug these up from my notes:

https://superuser.com/questions/806637/xauth-not-creating-xauthority-file

https://blog.mobatek.net/post/how-to-keep-X11-display-after-su-or-sudo/

https://unix.stackexchange.com/questions/215558/why-am-i-getting-this-message-from-xauth-timeout-in-locking-authority-file-ho

https://byteshiva.medium.com/how-to-do-x11-forwarding-in-linux-a-beginners-guide-438ed7e56602#:~:text=X11%20forwarding%20is%20a%20powerful,or%20managing%20a%20remote%20server.

 

Here is my yum packages related to this:

xorg-x11-drv-fbdev.x86_64                     0.5.0-2.el8                                 @rhel-8-for-x86_64-appstream-rpms
xorg-x11-drv-libinput.x86_64                  0.29.0-1.el8                                @rhel-8-for-x86_64-appstream-rpms
xorg-x11-drv-vesa.x86_64                      2.4.0-3.el8                                 @rhel-8-for-x86_64-appstream-rpms
xorg-x11-font-utils.x86_64                    1:7.5-41.el8                                @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-100dpi.noarch                  7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-75dpi.noarch                   7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-ISO8859-1-100dpi.noarch        7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-ISO8859-1-75dpi.noarch         7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-ISO8859-14-100dpi.noarch       7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-ISO8859-14-75dpi.noarch        7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-ISO8859-15-100dpi.noarch       7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-ISO8859-15-75dpi.noarch        7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-ISO8859-2-100dpi.noarch        7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-ISO8859-2-75dpi.noarch         7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-ISO8859-9-100dpi.noarch        7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-ISO8859-9-75dpi.noarch         7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-Type1.noarch                   7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-cyrillic.noarch                7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-ethiopic.noarch                7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-fonts-misc.noarch                    7.5-19.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-server-Xorg.x86_64                   1.20.11-15.el8                              @rhel-8-for-x86_64-appstream-rpms
xorg-x11-server-common.x86_64                 1.20.11-15.el8                              @rhel-8-for-x86_64-appstream-rpms
xorg-x11-utils.x86_64                         7.5-28.el8                                  @rhel-8-for-x86_64-appstream-rpms
xorg-x11-xauth.x86_64                         1:1.0.9-12.el8                              @rhel-8-for-x86_64-appstream-rpms
xorg-x11-xkb-utils.x86_64                     7.7-28.el8                                  @rhel-8-for-x86_64-appstream-rpms

Hi @avillanueva ,

 

Thank you for the reply. I cannot run it on my local machine since I dont have the permission to do that. This Linux server is a VM on Hyper V. Can you please suggest how can I run it on the VM itself?

 

Thanks,

 

avillanueva
22-Sapphire II
(To:RK_10805837)

You will need to get your IT admins to install those packages first on the linux VM. I would ensure that the test with something like xterm or xclock to make sure it functions. What client are you using to connect? 

We use Hyper-V to connect to the VM

avillanueva
22-Sapphire II
(To:RK_10805837)

Not sure that matters but I have no experience with Hyper-V:

https://www.reddit.com/r/pcmasterrace/comments/7iw8x3/how_to_windows_and_linux_in_perfect_harmony/

Is X11 forwarding enabled for SSH?

we use Windows RDP to connect to the remote Linux boxes which are all running xrdp

rleir
17-Peridot
(To:RK_10805837)

We use ssh forwarding and the Cygwin XWin server.

https://x.cygwin.com/docs/ug/using-remote-apps.html#using-remote-apps-ssh

A short answer for your question, and I left out many details. This is the best solution for us.

MobaXterm is another solution that provides ssh and an X11 Server for a windows client.:

https://mobaxterm.mobatek.net/

The issue was the correct permissions were not given to the folder where the PSI was installed. AFter changing the permissions using chmod 777, the PSI GUI was launched.

 

Thanks,

Ramsha Kamal


@RK_10805837 wrote:

The issue was the correct permissions were not given to the folder where the PSI was installed. AFter changing the permissions using chmod 777, the PSI GUI was launched.

 


I always do the following to run the PSI to get around tmp folder permission and or size limitation surprises:

 

\rm -r /opt/ptc/Windchill/tmp_install
mkdir /opt/ptc/Windchill/tmp_install
chmod 777 /opt/ptc/Windchill/tmp_install
export IATEMPDIR=/opt/ptc/Windchill/tmp_install

 

<run psi>

 

So remove and recreate a /opt/ptc/Windchill/tmp_install directory that is outside of the /tmp. Sometimes there are permission and size limits to the /tmp. I am removing it in case there is some existing content (eg old psi stuff...).

Set perms to 777

Set the environment variable  IATEMPDIR to the just created /opt/ptc/Windchill/tmp_install directory

Announcements

Top Tags