I am following this tuto to start openhab after beagle bone reboot:
http://tuxtec.blogspot.fr/2013/11/installing-openhab-on-beaglebone-black.html
($4. Autostart OpenHAB)
but It is not working, I got the following error:
root#beaglebone:~# systemctl status openhab.service
openhab.service - OpenHAB
Loaded: loaded (/lib/systemd/system/openhab.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri, 29 May 2015 12:26:39 +0200; 17s ago
Process: 1812 ExecStart=/usr/local/OpenHab1.7/start.sh (code=exited, status=127)
CGroup: name=systemd:/system/openhab.service
my beagle bone operating system is: "Debian GNU/Linux 7 (wheezy)"
any ideas why?
Thanks in advance for your help!
OpenHAB 1.7 (current as of this writing) has an apt-repo so that you can easily install the OpenHAB code and addons as one would install all software on Debian. Please follow these instructions for Beaglebone Black, which continue with the generic instructions for all Linux and OSX installations. When new stable releases come out, you will only have to
sudo apt-get update
sudo apt-get upgrade
in order to stay current.
Related
I installed virtualbox 5.2 from their website. And I ran this command..
docker-machine create -d virtualbox dev
then I got this..
Running pre-create checks...
Error with pre-create check: "We support Virtualbox starting with version 5. Your VirtualBox install is
"WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (4.14.3-300.fc27.x86_64) or it failed to
load. Please recompile the kernel module and install it by
sudo /sbin/vboxconfig
You will not be able to start VMs until this problem is fixed.\\n5.2.2r119230\".
Please upgrade at https://www.virtualbox.org"
I did as it suggested..
sudo /sbin/vboxconfig
then..
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
kernel-devel kernel-devel-4.14.3-300.fc27.x86_64
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
kernel-devel kernel-devel-4.14.3-300.fc27.x86_64
..and I don't understand anymore. Please help.
Install the kernel-devel package and it will continue. Btw, this is not a programming question, there are better forums for such questions...
This question already has answers here:
Error: NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver
(4 answers)
Closed 2 years ago.
I am running a cloud instance on a gpu node. I installed CUDA and nvidia-smi showed the driver details, memory utlilization. After a couple of days, I face this error
"NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running".
I installed the latest driver (Nvidia-375.39 for Tesla M40 Gpus). I still face the same issue. Is there any way to
i) debug why nvidia-smi is not able to communicate with the driver?
ii)check if the driver is running properly.
This is an operating system issue. The solution will depend on your operating system. For example, if you are running Ubuntu 16 the solution might be something like this:
Uninstall / purge all Nvidia drivers
sudo apt-get remove --purge nvidia* && sudo apt autoremove
Download Nvidia driver from Nvidia's website (.run file)
I met the same question as you, I solved this by modify the security option, the step is when I reboot the system,enter the bios,modify secure boot option as disabled,then reboot,It is ok!
I am having the following warning message when issueing docker commands: (ex: docker ps)
C:\Users\whha>docker ps
time="2017-01-24T23:17:36+01:00" level=warning msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
Any idea how can it be avoided?
I´m running docker using docker toolbox on windows 8.1.
Installing the last available version solved the problem for me (https://github.com/docker/toolbox/releases) :
BEFORE
minux#DESKTOP-OCQQ65T MINGW64 /c
$ docker --version
time="2017-04-05T17:56:55+02:00" level=info msg="Unable to use system
certificate pool: crypto/x509: system root pool is not available on Windows"
Docker version 17.03.1-ce, build c6d412e
AFTER
minux#DESKTOP-OCQQ65T MINGW64 /c
$ docker --version
Docker version 17.04.0-ce-rc2, build 2f35d73
I started having this problem today after updating to the docker toolbox version 1.13.1 of Docker Toolbox for windows.
Checking around the internet, and saw a github issue that this problem can't be fixed for windows.
https://github.com/docker/for-win/issues/422
Hence, probably has to follow #mayur_patil's suggestion to roll back to 1.12.x version. FYI, previous release can be found here: https://github.com/docker/toolbox/releases
I have installed docker toolbox version 1.13.1 for windows.
OS : Windows 10 Enterprise.
I solved the same issue with the v 1.12.6 instead 1.13.x.
You can change version series.
I was getting this error on Docker-toolbox 1.13.1
After that I downgraded to 1.12.2 and my problem solved.
OS: Windows 7 SP1
Check out and reply.
Had the same problem and solved it by download v1.12.6 from:
https://github.com/docker/toolbox/releases
We are running docker 1.7.1, build 786b29d on RHEL 6.7. Recently we have had multiple times when the docker daemon locked up and we had to reboot the machine to get it back.
A typical scenario is that a container that has been running fine for weeks suddenly starts throwing errors. Sometime we can restart the container and all is well. But other times all docker commands will hang, and restarting the daemon fails, and I see this in a ps:
4 Z root 4895 1 0 80 0 - 0 exit Aug23 ? 00:01:24 [docker]
Looking in the system log I've seen this:
device-mapper: ioctl: unable to remove open device docker-253:6-1048578-317bb6ad40cded3fbfd752d95551861c2e4ef08dffc1186853fea0e85da6b12b
INFO: task docker:16676 blocked for more than 120 seconds.
Not tainted 2.6.32-573.12.1.el6.x86_64 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
docker D 000000000000000b 0 16676 1 0x00000080
ffff88035ef13ea8 0000000000000082 ffff88035ef13e70 ffff88035ef13e6c
ffff88035ef13e28 ffff88062fc29a00 0000376c85170937 ffff8800283759c0
0000000000000400 00000001039d40c7 ffff8803000445f8 ffff88035ef13fd8
Call Trace:
[] _mutexlock_slowpath+0x96/0x210
[] ? wake_up_process+0x15/0x20
[] mutex_lock+0x2b/0x50
[] sync_filesystems+0x26/0x150
[] sys_sync+0x17/0x40
[] system_call_fastpath+0x16/0x1b
The latest docker version is 1.12.1 and we are on 1.7.1. Can or should I install a new version? 1.7.1 is the version yum installs. If I did want a new version how would I install that (sorry if that is a dumb question, I am not a sys admin).
Googling, I found on this on a Red Hat site "Red Hat does not recommend running any version of Docker on any RHEL 6 releases." We have been running docker on RHEL 6 for a few years, so this confuses me. Upgrading to RHEL 7 is not really an option for us right now.
Can anyone shed any light on these issue? We need docker to work reliably without having to reboot often.
Docker 1.7.1 is really old by today's standards. There have been hundreds of bugs fixed, enhancements to driver stacks, security patches, and valuable features added in the versions since. It looks like you're having a issue with your storage stack, and there is a good chance this is fixed in a newer version.
Docker has stated that default versions in package management systems like yum and apt can be way out of date, and that you should use their repo. The best way to do this is add their Yum repo information to your system so you can install it like other packages. The instructions are here: Installation on Red Hat Enterprise Linux.
Note: This will allow you to install Docker, and the service will be called docker, but the package is docker-engine. This has confused some people in the past.
yum install docker-engine
Docker has also provided a script that does this to make things easier (run as admin/root):
curl -fsSL https://get.docker.com/ | sh
Don't use a RHEL6 based system.
RHEL6 uses a 2.6 kernel with backported fixes to keep Docker working. Docker would normally require a 3.10+ kernel. Docker dropped support for RHEL6 from v1.8 on so it's unlikely there will be any more packages for it.
If you must use RHEL6, don't use the default loopback devicemapper for storage. Setup an LVM thin pool for Docker to use.
i installed https://github.com/docker/toolbox/releases/download/v1.9.1j/DockerToolbox-1.9.1j.exe as i need docker 1.9.
On starting the dockertools it detected that my boot2iso is old and updated the same to latest.For sure i had unchecked the auto upgrade option during installation "upgrade boot2docker VM"
I do not want to upgrade.Please help
Running pre-create checks... (default) Default Boot2Docker ISO is out-of-date, downloading the latest release ... (default) Latest release for github.com/boot2docker/boot2docker is v1.10.2 (default) Downloading C:\Users\akathaku\.docker\machine\cache\boot2docker.iso fr om github.com/boot2docker/boot2docker/releases/download/v1.10.2/… ker.iso...
I ran into this problem recently and solved it by running the following:
~$ docker-machine create -d virtualbox --virtualbox-boot2docker-url=https://github.com/boot2docker/boot2docker/releases/download/v1.9.1/boot2docker.iso default
For note, using this method currently suffers from the following issue: https://github.com/docker/machine/issues/2195
I hope it helps!