{"id":1874,"date":"2017-05-20T16:34:19","date_gmt":"2017-05-20T15:34:19","guid":{"rendered":"https:\/\/www.f5uii.net\/?p=1874"},"modified":"2017-05-20T17:35:08","modified_gmt":"2017-05-20T16:35:08","slug":"automatic-start-service-mmdvm-mmdvmhost-restart-boot","status":"publish","type":"post","link":"https:\/\/www.f5uii.net\/en\/automatic-start-service-mmdvm-mmdvmhost-restart-boot\/","title":{"rendered":"Automatic start of MMDVMHost"},"content":{"rendered":"

In this article, you will learn how to make MMDVMHost automatically start when your Raspberry Pi is turned on.<\/p>\n

The automatic start of MMDVMHost<\/h2>\n

On the Raspberry Pi, there are two solutions (the ones I know) to automatically launch software when the Raspbeery Pi is turned on (or rebooted), running under Raspbian.<\/p>\n

Simple startup<\/h3>\n

To start MMDVMHost automatically, the easiest solution is to edit this startup file and add the command line to start MMDVMHost before the statement exit 0<\/em><\/p>\n

sudo nano \/etc\/rc.local\r\n<\/pre>\n
#!\/bin\/sh -e\r\n#\r\n# rc.local\r\n#\r\n# This script is executed at the end of each multiuser runlevel.\r\n# Make sure that the script will \"exit 0\" on success or any other\r\n# value on error.\r\n#\r\n# In order to enable or disable this script just change the execution\r\n# bits.\r\n#\r\n# By default this script does nothing.\r\n\r\n# Print the IP address\r\n_IP=$(hostname -I) || true\r\nif [ \"$_IP\" ]; then\r\n  printf \"My IP address is %s\\n\" \"$_IP\"\r\nfi\r\n\r\nsudo  \/opt\/MMDVMHost\/MMDVMHost \/opt\/MMDVMHost\/MMDVM.ini\r\n\r\nexit 0\r\n\r\n<\/pre>\n
Starting with declaring a MMDVMHost service<\/h3>\n
Another solution, a little more elegant is to create a service.<\/p>\n
Prerequisites<\/h4>\n
Installation of screen<\/em><\/p>\n
sudo apt-get install screen<\/pre>\n
Creating the service file<\/h4>\n
sudo nano \/lib\/systemd\/system\/mmdvmhost.service<\/pre>\n
[Unit]\r\nDescription=MMDVM Host Service\r\nAfter=syslog.target network.target\r\n\r\n[Service]\r\nUser=root\r\nWorkingDirectory=\/opt\/MMDVMHost\r\nExecStart=\/usr\/bin\/screen -S MMDVMHost -D -m \/opt\/MMDVMHost\/MMDVMHost \/opt\/MMDVMHost\/MMDVM.ini\r\nExecStop=\/usr\/bin\/screen -S MMDVMHost -X quit\r\nRestart=always\r\nRestartSec=10\r\n\r\n[Install]\r\nWantedBy=multi-user.target\r\n<\/pre>\n
In the [Service]\u00a0<\/em>section, the last two lines make it possible to restart MMDVMHost in the event of a crash. It should be noted that it is very rare to be confronted with unexpected stops of MMDVMHost. We will test the proper functioning of the restart further down in the article.<\/p>\n
The MMDVMHost launch directories shown here correspond to those used during the MMDVMHost install tutorial<\/a>.<\/p>\n
Creating the launch timer file<\/h4>\n
The start of the service is delayed after 60 seconds after startup<\/p>\n
sudo nano \/lib\/systemd\/system\/mmdvmhost.timer<\/pre>\n
[Timer]\r\nOnStartupSec=60\r\n\r\n[Install]\r\nWantedBy=multi-user.target\r\n\r\n\r\n<\/pre>\n
Enforcement and service<\/h4>\n
sudo chmod 755 \/lib\/systemd\/system\/mmdvmhost.service\r\nsudo chmod 755 \/lib\/systemd\/system\/mmdvmhost.timer\r\nsudo ln -s \/lib\/systemd\/system\/mmdvmhost.service \/etc\/systemd\/system\/mmdvmhost.service\r\nsudo ln -s \/lib\/systemd\/system\/mmdvmhost.timer \/etc\/systemd\/system\/mmdvmhost.timer\r\n<\/pre>\n
We can restart the service manager<\/p>\n
sudo systemctl daemon-reload<\/pre>\n
Now the MMDVMHost service is ready to start. At this point, we can start the service without restarting.<\/p>\n
sudo systemctl start mmdvmhost.service<\/pre>\n
Verification of Service Operation<\/h4>\n
You can verify that the service launch MMDVMHost, by appearing in processes (ps) with the following statement. Must be displayed 3 rows.<\/p>\n
sudo ps aux | grep MMDVMHost\r\n<\/pre>\n
root      9657  1.0  0.6   5192  2684 ?        Ss   16:19   0:00 \/usr\/bin\/SCREEN -S MMDVMHost -D -m \/opt\/MMDVMHost\/MMDVMHost \/opt\/MMDVMHost\/MMDVM.ini\r\nroot      9662 18.2  1.2  15140  5436 pts\/0    Ssl+ 16:19   0:00 \/opt\/MMDVMHost\/MMDVMHost \/opt\/MMDVMHost\/MMDVM.ini\r\npi        9777  0.0  0.4   4268  1956 pts\/1    S+   16:19   0:00 grep --color=auto MMDVMHost\r\n<\/pre>\n
For verify the operation of the service, you will have access to the MMDVMHost log with the following command<\/p>\n
sudo screen -r MMDVMHost\r\n<\/pre>\n
The operating status of the service is returned with this command<\/p>\n
sudo systemctl status mmdvmhost.service<\/pre>\n
\u25cf mmdvmhost.timer\r\n   Loaded: loaded (\/lib\/systemd\/system\/mmdvmhost.timer; enabled)\r\n   Active: active (elapsed) since Sat 2017-05-20 16:33:10 CEST; 13min ago\r\n\r\nMay 20 16:33:10 raspberrypi systemd[1]: Starting mmdvmhost.timer.\r\nMay 20 16:33:10 raspberrypi systemd[1]: Started mmdvmhost.timer.<\/pre>\n
Let’s now test the automatic restart.<\/p>\n
Step 1: The service is running, MMDVMHost is present in the list of processes:<\/p>\n
sudo ps aux | grep MMDVMHost\r\n<\/pre>\n
root      9657  1.0  0.6   5192  2684 ?        Ss   16:19   0:00 \/usr\/bin\/SCREEN -S MMDVMHost -D -m \/opt\/MMDVMHost\/MMDVMHost \/opt\/MMDVMHost\/MMDVM.ini\r\nroot      9662 18.2  1.2  15140  5436 pts\/0    Ssl+ 16:19   0:00 \/opt\/MMDVMHost\/MMDVMHost \/opt\/MMDVMHost\/MMDVM.ini\r\npi        9777  0.0  0.4   4268  1956 pts\/1    S+   16:19   0:00 grep --color=auto MMDVMHost\r\n<\/pre>\n
Step 2: We will kill the MMDVMhost process with<\/p>\n
sudo killall MMDVMHost<\/pre>\n
Step 3: Immediately check the list of processes.<\/p>\n
sudo ps aux | grep MMDVMHost\r\n<\/pre>\n
pi 6360 0.0 0.4 4268 1828 pts\/0 S+ 16:37 0:00 grep --color=auto MMDVMHost<\/pre>\n
There is only one line left … But 10 seconds later, the same command again displays the 3 lines. MMDVMHost has been restarted!<\/p>\n
root      6609  0.0  0.6   5192  2812 ?        Ss   16:37   0:00 \/usr\/bin\/SCREEN -S MMDVMHost -D -m \/opt\/MMDVMHost\/MMDVMHost \/opt\/MMDVMHost\/MMDVM.ini\r\nroot      6613  6.4  1.3  16712  5920 pts\/2    Ssl+ 16:37   0:03 \/opt\/MMDVMHost\/MMDVMHost \/opt\/MMDVMHost\/MMDVM.ini\r\npi        7852  0.0  0.4   4268  1856 pts\/0    S+   16:38   0:00 grep --color=auto MMDVMHost<\/pre>\n
Other command<\/h4>\n
To stop the service<\/p>\n
sudo systemctl stop mmdvmhost.service<\/pre>\n
Conclusion<\/h2>\n
Vous aurez compris que la seconde solution pr\u00e9sent\u00e9e et qui consiste \u00e0 d\u00e9marrer MMDVMHost en tant que service est plus robuste gr\u00e2ce \u00e0 la fonction offerte par le service de red\u00e9marrer automatiquement MMDVMHost sur arr\u00eat intempestif.<\/p>\n
Au besoin les commentaires sont ouverts ci-dessous pour vos remarques, ou questions.<\/p>","protected":false},"excerpt":{"rendered":"
This tutorial shows you how to start MMDVMHost automatically on your Raspberry Pi. There are two solutions. Lire plus …<\/a><\/p>\n","protected":false},"author":1,"featured_media":1891,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[24],"tags":[],"class_list":["post-1874","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mmdvm"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t