RHEL 8.6 WebSphere 9 UI issues - websphere

I have been trying to install Websphere onto a VM running RHEL 8.6 and 8.5 but after several attempts and multiple VMs I`ve has no luck and keep running into the same issue.
The following screenshot is what I keep running into:
[1]
[1]: https://i.stack.imgur.com/uDLrD.png
[2]: https://i.stack.imgur.com/I8lVA.png
As you can see from the images the UI is broken and cannot be used for its intended purpose. There is no way (which I could find) to resize the windows or scroll.
Any help would be much appreciated.

I'm on VM RHEL 8.6 and able to resize the Profile Tool fine. It may be your VNC viewer problem.
I have used this to configure my VM for RHEL vnc.
https://www.ibm.com/support/pages/how-configure-vnc-server-red-hat-enterprise-linux-8

I managed to fix the problem by disabling gnome 3.0 and revert it back to gnome 2.0

Related

Docker on Windows 10 Crashing

I'm on windows 10 and I'm encountering Docker on Windows crashing on startup.
I just installed docker on windows and have a couple of containers spinning up (last night). I've been able to use it but after reboot, or shutdown, this was the behaviour ever since. Pretty unstable.
It looks like this and terminates after a while without any prompt of an error.
More info that I have Hyper-V installed on my machine and "Use the WSL 2 based engine" option enabled on docker.
On my end, I was able to solve this by:
Going to Apps & Features
Search for Ubuntu (or any linux distro you've installed)
Click on it and navigate to Advance options
Click on Reset button.
Also, try to trial and error which docker on windows version is stable with your system.
Hope that helps.

Docker causing VM's to fail - black screen

Windows 10 N Pro, version 2004
I had a few different OS VM's setup before I decided to try Docker out.
After installing it and realizing I better stick to VM's I went on my Virtualbox, tried starting my old VM's and couldn't get past the boot screen - the issue is it goes to a black screen.
I created a few new VM's all resulting in the same issue. I tried restarting the machine, Windows Restore, trying different BIOS settings, uninstalling docker, reinstalling Virtualbox, increasing VRAM to 128MB, uninstalling subsystem for Linux, disabling the Hypervisor and sandboxing. The only thing that let me interact with the VM was enabling EFI - although after choosing "boot" option I had the same black screen.
After trying all possible solutions on SO and Google I stumbled upon a comment (which unfortunately I can't find) which pinpointed that Docker installer explicitly overwrites VM/Hypoer registries or processes. I don't know if that's the issue however it is the case.
How can I get my VM's running again without reinstalling Windows?
It sounds like the problem is: 1) You were successfully running VMs with VirtualBox on Windows 10 Pro, 2) You installed Docker, 3) Docker broke VBox. Correct?
Look here:
https://superuser.com/questions/1290051/virtualbox-no-longer-works-after-uninstalling-docker-on-windows-10.
Control Panel -> Programs and Features
On the left side choose "Turn Windows features on or off
Uncheck Hyper-V
reboot
After reboot you have to reinstall/repair your installation of VirtualBox with the original installer!
Reboot again and it should work 🙂
In general, please try posting these kinds of questions on https://serverfault.com or https://superuser.com. StackOverflow is for "programming" questions.

debian 9 installation on HP DL20 Gen9

I have installed debian 9.3 on HP DL20 Gen9. When Debian 9.3 start, what happen is that the screen of the system appear like on the picture after the grub goes. any help?
Try booting your computer up in safe mode from Grub. Install updates and restart.
If it happens again you probably need to configure your graphics card for your installation.
Re-install Debian 9, when in the Software selection menu,
don't enable Debian Desktop Environment. If you need a desktop environment, simply enable certain Desktop environments.
In this case, I'm using Cinnamon. Until now there are no problems.
Thanks.
I find a solution. I used "nomodeset on the boot", and the screen appear normaly. I have used another tty2 and i get connected with the shell.
nano /etc/default/grub
i find this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
and i have changed it to this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset"

After installing RHEL in Parallels on my Mac how do I log in?

I installed RHEL 6.4 server under Parallels 7 on my Mac OS 10.8 just now from an iso file I just downloaded from RedHat. The installation seemed to proceed ok, but at the end I'm left with a screen with a gray bar followed by the text "RedHat Enterprise Linux Server 6.4" with no obvious way how to login.
If I shut down the machine I see it running the shutdown scripts. If I boot it I see the boot scripts and they all look ok. But I always end up at that same screen with no way to login.
I can enter characters in the screen, but there is no Linux prompt at all.
Anybody know what to do next? I couldn't glean anything fro the RedHat install manual.
Thanks,
doug
I had the same problem. The issue is the X-win server will not start because Parallels tools breaks the framebuffer with the RHEL 6.4 update. This is especially easy to see because a fresh install works fine until you install Parallels tools.
When you see the "select system to boot" message, hit the key that allows you to edit the boot arguments. Add a "3" to the end to force the startup to runlevel 3 (which is a console login without the GUI).
After logging in, type the command "starts" and you will see that it fails. Once you are able to fix this problem, the normal bootup into the GUI login will also work.
I had to downgrade the video driver subsystem back to 6.3 for it to start working, and you also have to add an exclusion to yum to prevent it from updating and removing the fix. This will be necessary until Parallels releases an updated tools that addresses this issue. There is a procedure I found in the CentOS forums for how to do this, sorry I don't have the link.

TeamCity and YouTrack in under 1GB

I am trying to setup YouTrack and TeamCity on a VM with less than 1GB running on Windows. There will be a very low usage (both users and requests). This is a POC environment, if it works I may push it onto an extra-small or small Azure or Amazon VM instance.
Anyone has got this to work?
PS: I understand that this is way below JetBrains recommended settings.
I have a running YouTrack instance with only 256MB RAM allocated (never tried a smaller value), on an old server with only 1GB RAM, under Debian. It feels pretty responsive, but I'm the only user so far :D
If you're using Windows XP, it might work ok, if Team City would run with only 256MB RAM.
Is there a specific need for using TeamCity, or you need it only for integrating YouTrack with Git/Mercurial/SVN?
I tried installing WARs under TomCat and I could not get TeamCity to play nice in TomCat 7. I ended up using the out of the box installers provided by JetBrains and all worked fine.
I have resolved same problem in the next way:
Installed application on VM with more than 1 GB memory.
Configured my application.
Reduced size(memory) of the VM to 700 Mb available
As application was used JetBrains YouTrack 6.0 with 250 issues and 3 users. It was failing to install from msi package on VM with 700 Mb of memory. After processing mentioned steps it works fine.

Resources