samba and lighttpd won't start automatically (v6.4) [solved]

Troubleshooting
1

Hi,

Recently I’ve installed dietpi on my rpi 2 b+, all works well, very happy :smiley: :smiley: !
However after installing samba server and lighttpd/mariadb (using dietpi-software), I noticed they won’t start automatically.
After boot I first have to ssh into the rpi and start both services, after which both run flawlessy !

How (and were) can I set the way they start up ? I prefer both services start direclty after booting.

Any hints greatly appreciated !

-ben

Solution:
It turns out there is a delayed start voor dietpi-services, after a while they seems to be running.
Still didn’t figure out how long after boot the services are running but they do after a while.

2

Hi,

After reboot, please check service status results (paste results):

dietpi-services status
3

First command after boot :

root@myPi:~# dietpi-services status
[ OK ] Root access verified.

DietPi-Services
─────────────────────────────────────────────────────
Mode: status

[ INFO ] DietPi-Services | cron inactive (dead)
[ INFO ] DietPi-Services | smbd inactive (dead)
[ INFO ] DietPi-Services | nmbd inactive (dead)
[ INFO ] DietPi-Services | lighttpd inactive (dead)
[ INFO ] DietPi-Services | php7.0-fpm inactive (dead)
[ INFO ] DietPi-Services | mysql inactive (dead)
[ OK ] DietPi-Services | dietpi-boot activating (start) since Fri 2018-03-16 21:19:22 GMT; 18h ago
[ INFO ] DietPi-Services | dietpi-postboot inactive (dead)
root@MyPi:~#

Any thoughts ?

4

After dietpi-services start :

root@MyPi:~# dietpi-services start
[ OK ] Root access verified.

DietPi-Services
─────────────────────────────────────────────────────
Mode: start

[ OK ] DietPi-Services | start : cron
[ OK ] DietPi-Services | start : smbd
[ OK ] DietPi-Services | start : nmbd
[ OK ] DietPi-Services | start : lighttpd
[ OK ] DietPi-Services | start : php7.0-fpm
[ OK ] DietPi-Services | start : mysql
[ SUB1 ] DietPi-Process_tool > Apply
grep: /tmp/.dietpi-process_tool_ps_list: No such file or directory
grep: /tmp/.dietpi-process_tool_ps_list: No such file or directory
grep: /tmp/.dietpi-process_tool_ps_list: No such file or directory
grep: /tmp/.dietpi-process_tool_ps_list: No such file or directory
grep: /tmp/.dietpi-process_tool_ps_list: No such file or directory
grep: /tmp/.dietpi-process_tool_ps_list: No such file or directory
grep: /tmp/.dietpi-process_tool_ps_list: No such file or directory
grep: /tmp/.dietpi-process_tool_ps_list: No such file or directory
[ OK ] DietPi-Process Tool | Completed
rm: cannot remove ‘/tmp/.dietpi-services_installed’: No such file or directory
root@MyPi:~#

I assume these services should start automatically but how ?

-ben

5

Hi,
Still don’t know how to setup dietpi so that all services start automatically, please help!
-ben

6

I am having this same issue. basically, all of my services do not start after reboot… all show inactive (dead)… I can enable all and everything starts working just fine… I can probably fix it with a scheduled task, but I’d like to know what is actually going on…

7

oldirtdog
I believe it’s due to a known bug in v6.21, resolved with v6.22 ETA this weekend.

Please try to resolve:

sed -i '/After=/s/[[:blank:]]multi-user.target//' /etc/systemd/system/dietpi-postboot.service
systemctl daemon-reload
systemctl enable dietpi-postboot