I installed AWX version 19.2.2 on my machine which is ubuntu 18.04.5
It got installed without any error and I can see the AWX web page at https://my machine ip:8043/#/login. I installed AWX using docker. for AWX port 8043 is opened. From AWX page I tried running playbooks but i am not able to see the /var/lib/awx/projects/ directory in my machine after successfully installing AWX.Also i tried changing the path of the directory by changing the path in /awx/awx/settings/defaults.py.i changed path to /home/ubuntu/exmp/awx/projects.but no use.
so can anyone help me regarding this playbook directory to appear in my machine
Related
Problem with starting minikube 1.1.1 on Ubuntu 19.04:
X Unable to start VM
* Error: [VBOX_HOST_ADAPTER] start: Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue
I've seen this question: How to fix VM issue with minikube start ? however I'm running ubuntu 19.04, not OSX. I've also done Minikube not starting on Ubuntu, throwing errors a couple of times too.
Now, I've installed the dkms package, I've modprobed vbox-dkms into the kernel, UEFI secure boot is set up as part of the dkms installation, but I still can't get minikube to start
Anyone have any ideas where to look next or what the problem might be?
Ps. I'm running virtualbox 6.0.6_Ubuntu r129722
I've got a problem in installing the newest version of Zabbix agent on Windows Server via vm boxes in Linux, since the old version of zabbix has not been uninstalled perfectly. Zabbix agent service is existed however the system cannot file the file related to specified address in services.
Uninstall the Windows service:
zabbix_agentd.exe --config c:\zabbix_agentd.conf --uninstall
You might also want to use the zabbix_agentd.win.conf example file, if the config file isn't a copy of that one already.
I have Vagrant 1.6.3 and VirtualBox 4.3.12 on Windows 8.1 Pro(64 bits). Vagrant was working fine till yesterday.
Suddenly, it started giving this error on vagrant up (in powershell):
The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:
Vagrant has detected that you have a version of VirtualBox installed
that is not supported. Please install one of the supported versions
listed below to use Vagrant:
4.0, 4.1, 4.2, 4.3
I have tried following:
Uninstall both Vagrant and VirtualBox (5-6 times) and reinstall. I rebooted after every install/uninstall.
Tried different (latest as well as older) versions of both Vagrant and VirtualBox. I have tried Vagrant 1.6.3 and Vagrant 1.6.5, VirtualBox 4.3.16, 4.3.12, 4.3.10.
Disabling anti virus and firewall. (Both Vagrant and VirtualBox are added to exclusion list)
Checking that VirtualBox is added in Environment Path.
Anything that I am missing? I tried searching and only two relevant links I found were: Vagrant has detected that you have a version of VirtualBox installed that is not supported (does not work), Vagrant has detected that the VirtualBox installed is not supported (fixed in Vagrant 1.5)
Any should I do now?
The problem was with Firewall. I recently switched to Comodo firewall and it was causing the issue.
I have installed artifactory 3.0.3 on a debian 7 virtual machine. When I reboot the virtual machine using vSphere artifactory is not restarted. I originally started artifactory as root with
service artifactory start
which worked fine. There is also an artifactory script here:
/etc/init.d/artifactory
why is that script not picked up on reboot?
Did you make sure that /etc/init.d/artifactory service was added to the default runlevels?
You should see symbolic links to the service in the /etc/rcX.d/ directories (where X is the runlevel number).
To add the service to the default runlevels use update-rc.d:
update-rc.d artifactory defaults
I have a (dv) server from mediatemple running CentOS.
I am trying to convert .doc or .ppt to .pdf files using php shell_exec
After searching through stackoverflow and dozens of sites I ran this command under root through ssh.
yum install openoffice.org-headless
Then I ran, soffice -headless -accept="socket,host=127.0.0.1,port=8100;urp;" -nofirststartwizard & which I thought was supposed to run it headless on the server.
I keep running into this error.
# javaldx: Could not find a Java Runtime Environment!
How can I install this Java Runtime Environment and then what should I be using for the shell_exec command?
Any help appreciated.
You might have to upgrade your DV. I was running into the same issue after I installed Open Office. I was running the 512MB virtual server. I upgraded to the 2048MB virtual server and was able to run open office headless without any issues.
You do not have to install the java runtime as it is already installed.