I have several servers running centOS 6 and centOS 7. I am working in an inventory system, and for that I am using ohai, which is installed in all the machines.
When I do ssh myuser#myserver.com ohai it returns a json object with all the information but the network section empty.
However, if I ssh into the server and I run ohai I get the proper network attributes.
Someone has any idea what can be happening? Thanks!
I solved, the problem was that ohai needs root rights to check the nics properties.
Related
So I'm trying to connect to a gcloud instance where I've installed several packages and started to develop my code with no problem. During the week, I use a certificate and putty to login since I work with a windows machine.
However now that I'm home, I tried to connect to the instance using my mac where I installed the Google Cloud SDK and after configuring all the parameters using
gcloud init
I get logged to an empty instance that doesn't have all of the packages and scripts I mentioned above.
What am I doing wrong? I can confirm that I'm connecting to an instance with the same name, in the same region and all, but it is completely different.
Cheers!
As you are connecting from a different machine, that's a different user.
Go to /home, and check if there is a folder with the "other" username. Note that you might not be able to access. You would need to become superuser.
I am using 2 computers and both are running fedora 23. In computer A I have installed ovirt engine 4.0 and in computer B I installed ovirt node 4.0.3 on a virtual machine manager and both the computer are in a same network.
When I login to the engine admin account using web interface, I tried to setup a host, but always gives error as install failed as shown below, any idea whats going wrong here?
Engine Host setup error picture
I thought it might be due to node storage issue, I tried to setup a node shared storage, again it gives error. Can anyone help how to setup a shared storage for node?
Node storage setup issue
in the lower panel you can see a message telling you that it failed to verify power management configuration.
You can see more messages if you'll go to the events tab.
For full details you can check the host installation log.
I have installed odoo 9 on a windows 7 machine..
All working well when i try to access like localhost:8069 or 192.168.1.11:8069
But the same dosnt work when i try to access from locally connected computers.. I am trying to access odoo from computers connected through lan..
trying to access 192.168.1.11:8069
However If I try to access Xampp Server using the ip it works well..
when I ping 192.168.1.11:8069 from any network computers it shows 'unknown host'
I am relatively new to this kind of network config thing.. Hope if anyone had similar issue and have sorted it out??
PS. Same thing happens when I install odoo on an Ubuntu 14.04 based computer..
Looking Forward to a solution.
Thanks in Advance.
VJ
There is a number of reasons that can cause this. What you are describing is a network issue and not a odoo issue. You cannot ping xxx.xxx.xxx.xxx:port number. I would start with some of the obvious tests:
Disable the firewall and anti-virus
If it is the firewall, set it up to open port 8069 and make sure that the firewall allows connections from other computers.
I'm running on BlueMix some test VM. Since today, it is impossible to even connect to the virtual machines (ssh, or running applications).
In the bluemix console, machines are running. I even tested to reboot one, without success.
Any idea or problem currently running ?
Were you able to ssh in before? Can you try using your ssh key with another VM to make sure its not an issue with your key
Since yesterday I can't connect through ssh to all of my Debian wheezy instances on my google cloud. I can connect only through the web console. When the web console tries to negotiate the session, there's a message telling me to update the Linux guest environment. But for wheezy, there is no Linux guest environment package.
Do you have any idea to resolve this issue ?
Debian 7 images were deprecated a while a go and as there are no update packages for the Guest Environment, the best approach would be to migrate to Debian 8 or 9.
To access your VMs you might try one of the following options:
1) According to this public issue the old guest environment still work with deprecated keys. If you have an SSH client configured with an old private key, you might still have access to your VMs through it.
2) Accessing the VM via the serial console
3) Mounting, as secondary, the original disk or a copy of it in a VM you do have access to. The steps are very similar to the section “Inspect an instance without shutting it down” on this document". That would allow you to recover your data.