how to install RHEL AS3 on PVS without XF86?
I am trying to install JES05Q4 on RHEL AS3 that is a hosted private virtual server (PVS) at my ISP.
I have succesfully installed many times on my own AS3.
I get the following error when trying on a private virtual server hosted by my ISP
<a href="mailto:[root@rupture" target="_blank">[root@rupture</a> Linux_x86]# ./installer -nodisplay
Attach to native process failed
It is RHEL AS
<a href="mailto:[root@rupture" target="_blank">[root@rupture</a> Linux_x86]# uname -a
Linux rupture 2.4.20-021stab028.17.777-enterprise #1 SMP Tue Jul 19 19:31:27 MSD 2005 i686 i686 i386 GNU/Linux
I have only done one unusual thing....
Since I do not have a XF86 install, I did the following
# touch /usr/X11R6/bin/xdpyinfo
# chmod +x /usr/X11R6/bin/xdpyinfo
... in order to eliminate the following error
<a href="mailto:[root@rupture" target="_blank">[root@rupture</a> Linux_x86]# ./installer -nodisplay
None of the following are executable
/usr/openwin/bin/xdpyinfo
/usr/X11R6/bin/xdpyinfo
None of the following are executable
/usr/openwin/bin/xdpyinfo
/usr/X11R6/bin/xdpyinfo
Attach to native process failed
How do I install JES without XF86 installed? It fails as above out the box without my first attempt at a workaround. Is there likely some other problem in my configuration causing the native process failure - other than XF86 absence? If I get the script modification right to avoid the check for xdpyinfo, will jes work without XF86 (except DS console)? Does x-view/openwin install on RHEL AS3 as alternative to XF86?
XF86 install problem - why I cannot use XF86
-
My X86 install fails due to kernel modifications by the virtual host provider
I get following problem trying to install modutils-2.4.25-14.EL.i386.rpm for /sbin/insmod.static that is required by mkinitrd-3.5.13-1.i386.rpm that is required by kernel-2.4.21-27.EL.i686.rpm that is required for kernel-drm that is needed by XFree86-4.3.0-78.EL.
It seems ISP is using modified kernel vzdummyrhas3-3.0-1.swsoft
# rpm -i modutils-2.4.25-14.EL.i386.rpm
warning: modutils-2.4.25-14.EL.i386.rpm: V3 DSA signature: NOKEY, key ID db42a60e
file /sbin/insmod from install of modutils-2.4.25-14.EL conflicts with file from package vzdummyrhas3-3.0-1.swsoft
file /sbin/lsmod from install of modutils-2.4.25-14.EL conflicts with file from package vzdummyrhas3-3.0-1.swsoft
file /sbin/modprobe from install of modutils-2.4.25-14.EL conflicts with file from package vzdummyrhas3-3.0-1.swsoft
[2748 byte] By [
] at [2007-11-26 6:14:41]
# 1
reading the release notes helps a little
after installing java 1.5 and compatibility rpms as follows still get cryptic error on running #./installer -nodisplay
Attach to native process failed
updated configuration and results
<a href="mailto:[root@rupture" target="_blank">[root@rupture</a> jesrqmts]# java -version
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Server VM (build 1.5.0_06-b05, mixed mode)
<a href="mailto:[root@rupture" target="_blank">[root@rupture</a> Linux_x86]# rpm -qa | grep jdk
jdk-1.5.0_06-fcs
<a href="mailto:[root@rupture" target="_blank">[root@rupture</a> jesrqmts]# rpm -qa | grep compat
compat-glibc-7.x-2.2.4.32.6
compat-libstdc++-7.3-2.96.128
compat-gcc-7.3-2.96.128
compat-libstdc++-devel-7.3-2.96.128
compat-gcc-c++-7.3-2.96.128
still get error without XF86
<a href="mailto:[root@rupture" target="_blank">[root@rupture</a> Linux_x86]# ./installer -nodisplay
Attach to native process failed
still fails if undo crude workaround - no xdpyinfo to start with
<a href="mailto:[root@rupture" target="_blank">[root@rupture</a> Linux_x86]# rm /usr/X11R6/bin/xdpyinfo
rm: remove regular empty file `/usr/X11R6/bin/xdpyinfo'? y
<a href="mailto:[root@rupture" target="_blank">[root@rupture</a> Linux_x86]# ./installer -nodisplay
None of the following are executable
/usr/openwin/bin/xdpyinfo
/usr/X11R6/bin/xdpyinfo
None of the following are executable
/usr/openwin/bin/xdpyinfo
/usr/X11R6/bin/xdpyinfo
Attach to native process failed
at 2007-7-6 13:52:48 >
# 2
Please help anyone?
I have not yet modified the jes install script (can I do this?) ...
....but I have configured XF86 using stubs for the kernel-drm rpm that is the source of conflicts with the VPS kernel ...
... yet I abandoned XF86 since have no device (/dev/tty0) and have configured and used vnc over ssh -X tunnel instead. I can successfully create windows from virtual X-server session but still fail to install JES with or without -nodisplay option. I still get the same error in all cases
<a href="mailto:[root@rupture" target="_blank">[root@rupture</a> Linux_x86]# ./installer -nodisplay
Attach to native process failed
or from VNC session that successfully creates new xterm windows fine (without -nodisplay)
<a href="mailto:[root@rupture" target="_blank">[root@rupture</a> Linux_x86]# ./installer
Attach to native process failed
So this failure to attach to native process maybe an unrelated problem to x-windows. Can anyone explain why may not be able install jes from vnc session?
So my ISP's PVS server has:
1) stubbed kernel that I have had to stub around to get XF86 installed and vnc working.
2) no tty0 device
3) what else? - causing attach failure.
To get XF86 installed despite my restricted PVS, I installed a stub for kernel-drm from ximian that does not offer proper X-windows behavior, but it was simple way to get XF86 dependencies out the way. My question is no longer why I cannot do JES install without XF86, but why cannot I do an install from vnc virtual X server session that is otherwise working, whether using -nodisplay option or not?
I used the following stub for kernel-drm
<a href="mailto:[kenw@rupture" target="_blank">[kenw@rupture</a> kenw]$ rpm -qa | grep ximian
kernel-drm-stub-4.1.0-0.ximian.1
I was then able to install XF86.
<a href="mailto:[kenw@rupture" target="_blank">[kenw@rupture</a> kenw]$ rpm -qa | grep XFr
XFree86-font-utils-4.3.0-78.EL
XFree86-xdm-4.3.0-78.EL
XFree86-devel-4.3.0-78.EL
XFree86-base-fonts-4.3.0-78.EL
XFree86-truetype-fonts-4.3.0-78.EL
XFree86-4.3.0-78.EL
XFree86-Mesa-libGL-4.3.0-78.EL
XFree86-xfs-4.3.0-78.EL
XFree86-doc-4.3.0-78.EL
XFree86-libs-4.3.0-78.EL
XFree86-xauth-4.3.0-78.EL
XFree86-Mesa-libGLU-4.3.0-78.EL
XFree86-twm-4.3.0-78.EL
XFree86-libs-data-4.3.0-78.EL
Vnc server installed (works OK to create xterm windows and xdpyinfo)
<a href="mailto:[kenw@rupture" target="_blank">[kenw@rupture</a> kenw]$ rpm -qa | grep vnc
vnc-server-4.1.1-7.0.rhel3
vnc-4.1.1-7.0.rhel3
However my PVS may not have terminal device for XFree86 configuration and get error cannot open /dev/tty0 when tryiing to configure Fatal server error: xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory).
<a href="mailto:[root@rupture" target="_blank">[root@rupture</a> root]# XFree86 -configure
XFree86 Version 4.3.0 (Red Hat Enterprise Linux 3 release: 4.3.0-78.EL)
...
Module Loader present
OS Kernel: Linux version 2.4.20-021stab028.17.777-enterprise (<a href="mailto:moruga@current.eng.sw.ru" target="_blank">moruga@current.eng.sw.ru</a>) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)) #1 SMP Tue Jul 19 19:31:27 MSD 2005 ...
Fatal server error:
xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
...
This is not surprising
<a href="mailto:[root@rupture" target="_blank">[root@rupture</a> Linux_x86]# ls -la /dev/tty0
ls: /dev/tty0: No such file or directory
<a href="mailto:[root@rupture" target="_blank">[root@rupture</a> Linux_x86]# ls -a /dev
.ptyc7 ptypd ptyt3 ptyw9 ptyzfttycd ttyq3 ttyt9 ttywf
..ptyc8 ptype ptyt4 ptywa ramttyce ttyq4 ttyta ttyx0
MAKEDEV ptyc9 ptypf ptyt5 ptywb ram1ttycf ttyq5 ttytb ttyx1
....
<a href="mailto:[kenw@rupture" target="_blank">[kenw@rupture</a> kenw]$ tty
/dev/pts/0
I am not very familiar with X-windows. Should I use MAKEDEV for /dev/tty0 or get XFree86 to use another device or should I create a screen by hand? How does one create a virtual X-server? This is why I just configured vnc and logged in remotely with vnc's X-server to try to install JES.
Any advice welcome? Is it time to abandon this ISP and private virtual server? Most ISPs do not claim RHEL AS3 support... so I guess I am going to unsupported Fedora IV kernels anyway.
Has anyone successfully deployed JES to an ISP's private virtual server? Is there any solaris container's out there yet?
at 2007-7-6 13:52:48 >
# 3
Hi Ken,I'd really appreciate you to share your recipe installing JES on RHEL3/4.I can't thank you enuogh for that.Al
