Occasionally when stopping a systemd service with systemctl stop test-server it will fail mentioning that the job was canceled:
Unable to stop service test-server: Job for test-server.service canceled.
What could cause stopping of the service to be canceled?
Note: The stop is actually initiated from an Ansible playbook, but can't see how that would be related.
When deploying applications onto servers, there is typically a separation between what the application bundles with itself and what it expects from the platform (operating system and installed packages) to provide. One point of this is that the platform can be updated independently of the application. This is useful for example when security updates need to be applied urgently to packages provided by the platform without rebuilding the entire application.
Traditionally security updates have been applied simply by executing a package manager command to install updated versions of packages on the operating system (for example "yum update" on RHEL). But with the advent of container technology such as Docker where container images essentially bundle both the application and the platform, what is the canonical way of keeping a system with containers up to date? Both the host and containers have their own, independent, sets of packages that need updating and updating on the host will not update any packages inside the containers. With the release of RHEL 7 where Docker containers are especially featured, it would be interesting to hear what Redhat's recommended way to handle security updates of containers is.
Thoughts on a few of the options:
So none of these approaches seems satisfactory.
It seems that the GlassFish project itself does not provide RPM packages, and neither does JPackage (http://jpackage.org/). Is someone else providing ready-built RPM packages for RHEL/CentOS?
On a related note: why are RPM packages so conspicuously missing for GlassFish v3? Don't people install it using packaging systems?
Where does output from cloud-init (automatically runs scripts when starting up a virtual machine in the cloud, for example at Amazon EC2) go? I would like to know that my initialization scripts executed successfully.
There is a /var/log/cloud-init.log file, but it seems to contain only partial output (namely from the SSH key initialization).