I want to start and stop WildFly 15 on Linux SUSE 11 together with the machine. I'm not expert in Linux and this is my first experience with SUSE. I found WildFly comes with init.d scripts for 2 Linux distributions: Debian and Red Hat.
docs/contrib/scripts/init.d/wildfly-init-debian.sh
docs/contrib/scripts/init.d/wildfly-init-redhat.sh
I found that in older versions of JBoss there was a SUSE script (jboss_init_suse.sh).
Why is not there a SUSE script in newer WildFly releases? Is there an easy way to create them from the other ones?
SUSE uses systemd. Use the scripts and in docs/contrib/scripts/systemd to get started. The README goes into details. Newer Ubuntu and Debian environments also use systemd.
And as it has bit me multiple times - do not forget the very last line in the README - it enables it for reboot. I tend to start Wildfly and then forget to enable the service and on the first reboot I wonder what happened.
Related
I'm moving an existing VxWorks 6.9 build system from Windows to RedHat Linux. In theory this should be easy but it seems that if I install VxWorks 6.9, from the same CD, on Linux then the dcom-2.3 library (and a couple of others) are not installed - installing from the same CD on Windows does install them.
Anyone know what I am? This is a cross-compiler environment for an embedded system so I can't see any reason that the installed libraries should be different between the two host systems.
We are currently provisioning a physical server as our automation server. We are making considerations as far as what our native operating system should be on this physical machine.
We are going to use a Linux OS as our operating system. From the Jenkins download page, I can see that Jenkins’ package distribution is available to Red Hat / Fedora / CentOS (which we will not be using), as well as Ubuntu / Debian. I also notice that a Generic Java package (WAR) distribution is available.
Am I correct in assuming that if we use a non-Ubuntu / non-Debian
operating system, we can still install Jenkins via the WAR
distribution without issue?
If we are not able to install via WAR without issue, are we relegated
to using Debian / Ubuntu if we’re going to install Jenkins on a Linux
machine (with the possibility of Red Hat / Fedora / CentOS ruled
out)?
It should probably be noted that we will likely install / upgrade on the Jenkins LTS release schedule.
Thanks for any guidance from anybody who may have experience installing / maintaining a Jenkins instance on a Linux machine!
I'm currently trying to install an oracle server (11g) in a linux container on ubuntu (following this tutorial (http://www2.hawaii.edu/~lipyeow/ics321/2014fall/installoracle11g.html).
When I try to change the file handler with sysctl, the modifications doesn't save into my container. Moreover, when I make the modification in the main ubuntu kernel, it propagates to the containers, so my question is as follow:
How can I modify the file handlers only in my oracle container ?
Thanks.
Try out the Orabuntu-LXC project code. It supports Ubuntu 16.04, 17.04, 17.10 and is purpose-built for running Any Oracle on Any Linux, including Ubuntu Linux. Note that as you probably already know, Oracle Corp does not formally support or certify Oracle on Ubuntu Linux.
As far as you question about the file handlers, some sysctl values can only be set at the LXC host level, and some can be set in the container.
https://sites.google.com/site/nandydandyoracle/oracle-rac-in-lxc-linux-containers/oracle-lxc-vlc#TOC-Install-the-etc-sysctl.conf-File-Required-for-Oracle
https://github.com/gstanden/orabuntu-lxc
https://sites.google.com/site/nandydandyoracle/
Please note that the step-by-step guides are quite old and that the basic LXC infrastructure together with OpenvSwitch, an LXC-containerized DNS/DHCP, and an optional SCST Linux SAN can all be installed on Ubuntu 16.04, 17.04 and 17.10 with one command:
./anylinux-services.sh
after completion of which all you would need do is download your Oracle database installtion media and install.
few months ago I got access to a VPS with installed Debian 8 Jessie.
The strange thing for me was that after perform some action (like service [stop|start|restart], debian not notify me (ex: Restarting nginx: nginx, like old debian 7 wheezy).
Yesterday, i installed on my virtual machine Debian 8 Jessie, but the "bug" persists.
Should I install something extra library, or to set up them?
Thanks in advance.
Debian uses systemd now.
systemctl start example1
Investigate why systemd hangs on startup or on reboot/shutdown.
Increase verbosity via cmdline: Add "systemd.log_target=kmsg systemd.log_level=debug"
[ /etc/default/grub ]
GRUB_CMDLINE_LINUX="systemd.log_target=kmsg systemd.log_level=debug" <--- Add here (by uncommenting you can easily switch to debug)
# update-grub
Systemd is not as verbose as the old SysV scripts, so your described "bug" is intended behaviour.
The old commands, like "service" are just simple symlinks / script which delegate the work to systemd.
As far as I know this is the same for the /etc/init.d scripts.
I want to install Gitlab on the suse linux OS.
Could some one please suggest me which OS supported Gitlab installer from the available ones on Gitlab site : Ubuntu, Debian and Centos can be used to install Gitlab on Suse linux ?
OS details :
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 4
I'm afraid that Suse is a complete different system. They use a package manager called YaST that won't be compatible with any of the proposed OS on the GitLab website.
Alternatively, you can try installation via Docker (Hopefully your system is 64bits):
https://gitlab.com/gitlab-org/gitlab-ce/tree/master/docker
Or the hard way, manually:
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md
Or even pop an instance somewhere in the cloud but this would involve some costs.
For all other OSs it has packages to install all the required components, but for SUSE there is no package, so you will have to install all the required components like ruby, redis, mysql and other dependent libs on your own.
You may like to try this :
https://gist.github.com/rriemann/5163741
or
https://gist.github.com/jniltinho/5565606
Since I found this answer while looking for the installation on SUSE 12 (SP3), there is one of the currently working options (2021).
First, check the version supported on the system, (Gitlab 12.1 in case of SUSE 12 SP3, which corresponds to OpenSUSE 42.3)
After that, get the proper .rpm file using wget.
Install with
sudo EXTERNAL_URL="http://gitlab.my.domain" rpm -ivh path/to/file/filename
That's it. Some Versions of Omnibus for SUSE are supported directly, but it really depends on the host system version.