Ubuntu Java 18 Jdk
Rapheal Charlton
There are many different ways to install Java on Ubuntu, but if all you need is the ability to run a Java program or even develop and compile some Java source code, the apt-based installation path is the easiest one to follow.
If the java -version command outputs information about the version of Java installed, along with information about the JVM and runtime environment, then you successfully installed Java on Ubuntu with apt.
This keeps everything outside of the operating system's package management system and dependencies, which is why ubuntu is trying to load all those extra packages. It also means that you don't have to worry about breaking your java when you update your Ubuntu. You just need to make sure you keep java reasonable upto date yourself.
I have installed the Zotero from APT, placing the folder on /opt. I have problems with the Java environment (JRE). On this post, it is said that one needs to run sudo apt install default-jre and sudo apt install libreoffice-java-common. But I already have them:
Your LibreOffice installation is a container installation, right? Ask your distributor how to configure that f***ing container to access system libraries such as JRE.
Better install LibreOffice directly into your system: Java Runtime in 24.2 - #4 by Villeroy
Snaps are containerised software packages that are simple to create and install. They auto-update and are safe to run. And because they bundle their dependencies, they work on all major Linux systems without modification.
You don't need to install Processing. You just download the tar file, untar in some folder of your choosing, then go into this folder and search for the processing-java file and run it. I will make sure you have reading and writing privileges in this folder and that the processing-java file has the executable flag set. This is what I remember I did when I ran it last time in linux.
Hoping someone can shed some light on this. We're preparing to move to JAMF Cloud and have to upgrade our JAMF Pro server from 10.12 to the latest release (10.22.1). To do that, we have to go to 10.14 and then to 10.22.1.
10.14 requires Java 11, which requires Ubuntu 18 LTS so I had to upgrade our server from 14 to 16 to 18 and also upgraded to Java 11. Everything seemed fine until I tried to do the manual JAMF Pro upgrade.
I copied the root.war file over and when I went to start tomcat, it just fails. Code=exited status=1/FAILURE Then it says failed to start LSB: Start tomcat. That's it. I can't find any other details about why it fails to start anywhere. I reset JAVA_HOME after the java upgrade and confirmed its pointing to the right folder so I have no idea what else to check at this point. I have a ticket in with support but also posted here in case anyone has any ideas that may come faster.
I rolled back my snapshot to just before the Java 11 upgrade and tomcat stops and starts without an issue so it seems that the Java 11 upgrade caused the issue, but I'm still not sure what specifically.
I'm seeing a similar issue, both with the installer and doing it manually with root.war. Strangely, the JAMF installer seems to be the only thing that can't see $JAVA_HOME. Tomcat sees it, but fails to start. Right now, I'm stuck at 10.12 until I can figure this out.
I have a support ticket with JAMF. Since we've been doing manual upgrades (even before I was hired), tomcat hasn't been getting updated. Our servers are still on tomcat7 and JAMF support thinks that may be part of the problem because tomcat 8.5.40 is recommended and possibly required for 10.14. If you use Jamf's installer instead of the manual process, tomcat is automatically updated. Great. So if you're also on tomcat7, you're probably in the exact same boat as me.
I assume your SQL is on a separate VM? If so, Jamf Pro Tomcat VMs are disposable - bring up a new VM, shutdown old Tomcat VM & move IP, install Jamf Pro using the installer (don't do a manual upgrade) & Install Java 11, point it to your database & start Tomcat.
My environment is clustered (though I really don't know why because it seems like overkill) so I would have to rebuild 3 more servers, which isn't ideal. I tried installing Tomcat8 using the instructions JAMF has floating around, but it still wouldn't start even though I pointed it to the correct JAVA_HOME directory. I'm going to upgrade the SQL server to see if that's part of the problem.
I assume all Tomcat VMs are upgraded to Ubuntu 18.0? Why not just stop all tomcat services on the 3 nodes, uninstall Jamf Pro and Java on the master node and re-install using the packaged installer from Jamf Nation. Then start the master node and see if it comes up, then do the same for the other 2 nodes. To me, this sounds like a corrupted install of Tomcat having to do with a mix os OS upgrades on the VMs and manual install of Jamf Pro over the years. Just my two cents.
All of the VMs were upgraded to Ubuntu 18 this week in preparation for the move to 10.22.1. I asked support if I could do what you suggested and they told me since the upgrade process has been manual on these servers, it needs stay manual. It does sound like a corrupt Tomcat install but Tomcat starts on all 3 servers with 10.12, even after the Ubuntu upgrades. The web application is accessible and I can use it normally. The Java 11 update kills it.
I disagree with support there - it should not make a difference whether it is a manual upgrade or upgrade via installer. It is all pointing at the same database. I would stop Tomcat, stop SQL, snap all 3 VMs, take a DB backup, and then try the above (removing Jamf Pro Web App & Java & re-install using installers).
They claim that since we're ultimately going to the cloud, it could make a difference because the manual upgrade and upgrade via installer do different things to the server environment in general. They didn't specify what though. I guess I can talk to our migration specialist to confirm that. I've snap shotted all 4 servers so I can at least try it. If it works but the migration specialist says it could be a problem, I can revert back.
@jared_f Your suggestion of uninstalling JAMF Pro and reinstalling with JAMF's installer package seems to be working! Thanks so much for the suggestion. I'm just going to say for people who come across this post in the future, make sure you save your server.xml file somewhere on the server so you can copy the 8443 settings into the new server.xml file.
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
Hello,I have a problem with MATLAB 2018b in ubuntu 16.04: it hangs on splash screen. Previously I had MATLAB 2016b and everything worked fine.I am currently able to run matlab only with the -nodesktop option. A test log output created during the splash screen hanging reports:
I have LO 7.0.1.2. I think the problem was that I first ran a sudo apt-get install libreoffice libreoffice-writer libreoffice-java-common jabref java-common to check whether the right java stuff was present. this command installed a LO 6 that interfered with the communication. When I purged LO and re-installed it, the problem was solved.
I tested with the versions of libreoffice in the ubuntu repos anche the upstream ppa, and they both work automatically, detecting the correct paths.
Check that the snap is not still lauched by running which libreoffice. That should return /usr/bin/libreoffice
I have modified the /etc/default/jenkins file but I think that is not the one I should use as it has no effect.
Same with this command. sudo systemctl edit jenkins and added Environment="JAVA_ARGS=-Xmx4g -Djava.awt.headless=true"
This document is intended as a reference for tuning and troubleshooting the Java Virtual Machine within which Jenkins runs, using current best practices as well as a troubleshooting guide for performance issues for Jenkins Administrators.
I reply to myself - maybe it could be useful for others. After turning on security debug ("-Djava.security.debug=all") I find out that the process failed to load "java.home/lib/security/java.security " with "Permission denied". Then, I find out that in my installation all the files inside "java.home/lib/security/" where actually symlinced to /etc/java-8-oracle/security/; and that all the real files had only "-w------" permission. So elasticsearch user could not read them. I add "r" permission to those files and - voil - elasticsearch now starts up.
This tutorial describes how to install various versions of OpenJDK as well as Oracle Java on Ubuntu 18.04. The same instructions apply for Ubuntu 16.04 and any Ubuntu-based distribution, including Kubuntu, Linux Mint and Elementary OS.
Java is distributed in three different editions, Standard Edition (SE), Enterprise Edition (EE), and Micro Edition (ME). This tutorial covers the installation of the Java SE (Standard Edition) edition.
If you only want to run Java programs, then you need JRE, which contains only the Java Runtime Environment. Java developer should install JDK, which also includes the development/debugging tools and libraries.
The images above are offered for both amd64 and arm64 architectures. Your container runtime shall pull the right image based on your environment. To force a pull of an image for a specific architecture, use the following:
The distroless images are based on the CBL-Mariner 2.0 distribution by Microsoft. They require a different approach to deploying an application. Because the distroless images do not contain a complete Linux distribution, there is no shell, for example.
d3342ee215