I'm trying to set up mosquitto under RPi - Debian Stretch.
sudo service mosquitto giving me following returncode:
Failed to start mosquitto.service: Unit mosquitto.service is masked.
sudo service mosquitto status:
● mosquitto.service
Loaded: masked (/dev/null; bad)
Active: inactive (dead)
Can somebody give me a hint how to fix it?
Thank you!
Fix it with
sudo systemctl unmask mosquitto service
sudo service mosquitto stop
sudo service mosquitto start
Its running now! – Andreas
Related
I have Microsoft Windows 10 Pro version 10.0.19041 N/A Build 19041 and I follow steps here https://learn.microsoft.com/en-us/windows/wsl/install-win10 to install Ubuntu 20.04 LTS on it using WLS2 , I'm doing so to install docker by following steps here https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository
but when I try to run sudo docker run hello-world it gives me this error docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See 'docker run --help'. I know that a similar question asked here Cannot connect to the Docker daemon at unix:/var/run/docker.sock. Is the docker daemon running? ,and I try to run systemctl daemon-reload and systemctl start docker but al the solutions does not worked for me it gives me another errors like System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down and Also try to fix it but I can't, So I need your help.
Note : I have already install Docker in windows and It works fine.
I have been solving this problem by following these steps
Purge the Grub package Linux command according this issue https://github.com/microsoft/WSL/issues/4903
Stop Docker Desktop from Windows
Run sudo dockerd which is the daemon service for Docker containers
https://i.stack.imgur.com/qgbwE.png
Open new Ubuntu shell session
Run docker run hello-world
and it's work fine with me https://i.stack.imgur.com/6TJ3u.png
I try to install Conjure-Up on my Ubuntu 18.04 virtual machine with
$sudo snap install conjure-up --classic
But it always says:
error: cannot install "conjure-up": Post https://api.snapcraft.io/v2/snaps/refresh: proxyconnect
tcp: EOF
I have successfully set up my http and https proxy in /etc/environments
need help.
It will help.
Example
sudo snap set system proxy.http=http://127.0.0.1:3128
sudo snap set system proxy.https=http://127.0.0.1:3128
Looks like snapd doesn't apply the /etc/environment proxy settings as of 18.04. You can apply an override to snapd service to get around this though.
sudo systemctl edit snapd.service
Add in the following:
[Service]
Environment=http_proxy=http://proxy:port
Environment=https_proxy=http://proxy:port
Save then reload:
sudo systemctl daemon-reload
sudo systemctl restart snapd.service
Snap installs should now go through specified proxy.
try this:
sudo snap set system proxy.http=socks5://127.0.0.1:1080
sudo snap set system proxy.https=socks5://127.0.0.1:1080
then you see the download speed is much faster:
47% 2.19MB/s 7.37s
I installed elasticsearch on Ubuntu 16.04.
When I enter sudo service elasticsearch start, everything works.
But the service is not running on startup. Before starting it manually, sudo service elasticsearch status gives me:
elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vend
Active: inactive (dead)
Docs: http://www.elastic.co
I tried to add it to startup with:
sudo update-rc.d elasticsearch defaults and sudo update-rc.d elasticsearch enable, but this changes nothing.
What could be the problem, and how can I debug this?
The answer to your problem is running this:
sudo systemctl enable elasticsearch.service
Elasticsearch on Ubuntu 16.04 uses SystemD not System V anymore.
For some reason when (as of 9th Jan 2016) you install ES 5.1 (not sure if other versions are affected) from APT by default this service does not start.
Did not find the error. Just reinstalled it with dpkg. Works, and the data and config hasn`t been overwritten.
I working on CentOS7 and I install ceph by manual build
./autogen.sh
./configure
make
make install
and manual deploy by follow this link http://ceph.com/docs/master/install/manual-deployment/
but ceph doesn't exist in directory /etc/rc.d/init.d/
Failed to issue method call: Unit ceph.service failed to load: No such
file or directory
So, I can't start service.
In document of manual deploy it's said I have to use command
sudo /etc/rc.d/init.d/ceph start mon.node1
In CentOS7 use systemd
So, use command sudo systemctl start ceph-osd#0 will work!!!
You can run systemctl status ceph* as a quick way to show any services on the box or systemctl list-units --type=service | grep ceph the service name syntax is ceph-mon#<hostname>.service or ceph-osd#<osd_num>.service
Please run systemctl list-unit-files and you can list all ceph services and you must find OSD number with ceph osd tree and put in this command systemctl status ceph-osd#{OSD_NUM}.target
Hi I am trying to install apache mesos in my ubuntu based system. I have installed zookeeper and marathon along with this setup.
apt-get install mesos marathon
it says its success but when i try to see available services systems does not show mesos-master or slaves as available services. also
service mesos-master/slave start
says unrecognized service. any idea?
I had the same issue, so after trying multiple tricks .. I found that you can start the mesos-master using the following command:
mkdir ~/workdir; sudo mesos master --work_dir=/home/azureuser/wokdir&
Some documentation has not matched actual installations for me - Mesos may installed to be managed by upstart/systemd kinds of commands rather than service. Most recently for me, a CentOS 6.6 install of Mesos has landed in upstart-managed territory, e.g.:
start mesos-master
stop mesos-master
status mesos-master
YMMV, but that's what I've recently seen.
I faced same issue, I was not able to start mesos-master on UBUNTU-14.04 although I double checked installation and zookeeper service started successfully and tested well.
I found work around to start mesos-master service.
$ cd /usr/sbin/
$ sudo ./mesos-master --work_dir=/var/lib/mesos --log_dir=/home/rajeev/logs/mesos/
above command run mesos-master service successfully [But sudo service mesos-master start command failed to start mesos master node]