Can not update to version 6.4

[nakulbende]

Issue:

I can not update to 6.4. I have run all the apt commands to get any dependencies, made sure I have internet and I can ping dietpi.com. Here is the output:

DietPi-Update
─────────────────────────────────────────────────────
 Mode: Checking for DietPi updates

[ INFO ] Checking Mirror : http://dietpi.com/downloads/dietpi-update_mirror/master/server_version-6
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100     4  100     4    0     0     12      0 --:--:-- --:--:-- --:--:--    12
[  OK  ] Using update server: http://dietpi.com/downloads/dietpi-update_mirror/master/server_version-6

[  OK  ] Update available
[ INFO ] Current Version : 6.1
[ INFO ] Server Version  : 6.4
[ INFO ] Detecting drives, please wait...
[ INFO ] Detected PARTUUID mount: /dev/mmcblk0p1 > /boot
[ INFO ] Detected PARTUUID mount: /dev/mmcblk0p2 > /
[ INFO ] Processing drive information, please wait...
[ INFO ] Checking available free space on RootFS, please wait...
[  OK  ] 5327 MB available, 500 MB required

 DietPi-Services
─────────────────────────────────────────────────────
 Mode: stop

[  OK  ] stop : cron
[  OK  ] stop : proftpd
[  OK  ] stop : apache2
[  OK  ] stop : lighttpd
[  OK  ] stop : php7.0-fpm
[  OK  ] stop : noip2
[  OK  ] stop : dnsmasq
[  OK  ] stop : pihole-FTL
[  OK  ] stop : openvpn
[  OK  ] stop : avahi-daemon
[  OK  ] stop : netdata
[  OK  ] stop : plexmediaserver
[  OK  ] stop : qbittorrent
[  OK  ] stop : blynkserver
[  OK  ] stop : motioneye
[  OK  ] stop : cups
[  OK  ] stop : plexpy
[  OK  ] stop : RaspimJpeg

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:19 --:--:--     0curl: (6) Could not resolve host: dietpi.com
[FAILED] Download failed, unable to run update. Please try running dietpi-update again.

 DietPi-Update
─────────────────────────────────────────────────────
 Mode: Completed

[ INFO ] Current Version : 6.1
[ INFO ] Server Version  : 6.4
[  OK  ] Update completed

Please reboot your system now, using the command reboot

System Information:

• DietPi Version | 6.1
• RPi 3
• 5v 2.5A
• Sandisk ultra

Possible error?

If you notice, the update script can connect to dietpi.com initially, but not the second time around. Any thoughts? Can somebody tell me how to download the update manually and install it locally?

[k-plan]

@nakulbende

If you notice, the update script can connect to dietpi.com initially, but not the second time around. Any thoughts?

Yes.

• DietPi Version | 6.1

DietPi-Services
─────────────────────────────────────────────────────
 Mode: stop
...
[  OK  ] stop : dnsmasq

...

curl: (6) Could not resolve host: dietpi.com
[FAILED] Download failed, unable to run update. Please try running dietpi-update again.

Is fixed with DietPi v6.2 update.

https://github.com/Fourdee/DietPi/commit/640ff4f03300772be2f694ef371e75ba5070b0f9

To get dietpi-update running now, please edit as root:

root@Odroid-C1:~# nano /DietPi/dietpi/dietpi-services

and rem out (#) line 53:

        'ympd'
        'minidlna'
        'noip2'
            #'dnsmasq' #: https://github.com/Fourdee/DietPi/issues/1501
        'pihole-FTL'
        'subsonic'
        'webiopi'
                 ...

Save file, and start dietpi-update

[nakulbende]

Commented out line 53 - still got the same error. I tried rebooting and restarting the update file. Here is a screenshot of the file:

[k-plan]

@nakulbende

... - still got the same error.

1.) - Can you please share the output again?

---

DietPi-Services
─────────────────────────────────────────────────────
 Mode: stop

....
[  OK  ] stop : openvpn
...

2.) - Is WAN (internet) connection of your RPi via a VPN Tunnel Provider?

---

3.) - Can you please show:

• ping ip address of your default gateway (router): root@RPi:~# ping "ip-address-of-your-router"

• look at you RPi ip address: root@RPi:~# ip address

• look at your RPi Kernel IP routing table: root@RPi:~# route

• look at your RPi DNS server: root@RPi:~# cat /etc/resolv.conf

[nakulbende]

My Ethernet connection is directly from the router - the openvpn client actually uses RPi as a host for me to VPN into my network from outside.

Here is the ping output:

--- 192.168.0.1 ping statistics ---
32 packets transmitted, 32 received, 0% packet loss, time 32159ms
rtt min/avg/max/mdev = 0.363/0.446/0.529/0.041 ms

IP address output (my DCHP gives static address to alll):

root@DietPi:~# ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b8:27:eb:ed:fc:2e brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.201/24 brd 192.168.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::ba27:ebff:feed:fc2e/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b8:27:eb:b8:a9:7b brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.200/24 brd 192.168.0.255 scope global wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::ba27:ebff:feb8:a97b/64 scope link
       valid_lft forever preferred_lft forever
4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100
    link/none
    inet 10.8.0.1/24 brd 10.8.0.255 scope global tun0
       valid_lft forever preferred_lft forever
    inet6 fe80::d245:6841:f527:2d67/64 scope link flags 800
       valid_lft forever preferred_lft forever

Routing table:

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         Archer50        0.0.0.0         UG    0      0        0 eth0
10.8.0.0        0.0.0.0         255.255.255.0   U     0      0        0 tun0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 wlan0

Namesevers: (First one is raspPi itself, as I use pi-hole. But the second one is quad-8)

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.0.201
nameserver 8.8.8.8

Here is the dietpi-update output:

[  OK  ] Root access verified.
[ INFO ] Checking RootFS R/W access. Please wait...
[  OK  ] RootFS R/W access.

 DietPi-Update
─────────────────────────────────────────────────────
 Mode: Checking for DietPi updates

[ INFO ] Checking Mirror : http://dietpi.com/downloads/dietpi-update_mirror/master/server_version-6
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100     4  100     4    0     0     10      0 --:--:-- --:--:-- --:--:--    10
[  OK  ] Using update server: http://dietpi.com/downloads/dietpi-update_mirror/master/server_version-6

[  OK  ] Update available
[ INFO ] Current Version : 6.1
[ INFO ] Server Version  : 6.4
[ INFO ] Detecting drives, please wait...
[ INFO ] Detected PARTUUID mount: /dev/mmcblk0p1 > /boot
[ INFO ] Detected PARTUUID mount: /dev/mmcblk0p2 > /
[ INFO ] Processing drive information, please wait...
[ INFO ] Checking available free space on RootFS, please wait...
[  OK  ] 5356 MB available, 500 MB required

 DietPi-Services
─────────────────────────────────────────────────────
 Mode: stop

[  OK  ] stop : cron
[  OK  ] stop : proftpd
[  OK  ] stop : apache2
[  OK  ] stop : lighttpd
[  OK  ] stop : php7.0-fpm
[  OK  ] stop : noip2
[  OK  ] stop : pihole-FTL
[  OK  ] stop : openvpn
[  OK  ] stop : avahi-daemon
[  OK  ] stop : netdata
[  OK  ] stop : plexmediaserver
[  OK  ] stop : qbittorrent
[  OK  ] stop : blynkserver
[  OK  ] stop : motioneye
[  OK  ] stop : cups
[  OK  ] stop : plexpy
[  OK  ] stop : RaspimJpeg

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:19 --:--:--     0curl: (6) Could not resolve host: dietpi.com
[FAILED] Download failed, unable to run update. Please try running dietpi-update again.

 DietPi-Update
─────────────────────────────────────────────────────
 Mode: Completed

[ INFO ] Current Version : 6.1
[ INFO ] Server Version  : 6.4
[  OK  ] Update completed

Please reboot your system now, using the command reboot

[nakulbende]

Oh wait, I just removed DNS servers from my router settings, and it worked! Looked like it was forced to take the fist DNS name server, and did not go to the backup one.

[nakulbende]

Actually, should not have spoken so soon. I got an error, and when it rebooted, it is on v6.2. Once I get home, I will get the error dump.

I guess as far as this issue goes, we can close it (?) I will open a new one for my update woes.

[Fourdee]

@nakulbende

Actually, should not have spoken so soon. I got an error, and when it rebooted, it is on v6.2. Once I get home, I will get the error dump. I guess as far as this issue goes, we can close it (?) I will open a new one for my update woes.

Continue with this ticket, we can edit the title if needed 😃

[k-plan]

@nakulbende

You have several problems. But point by point.

---

Here is the dietpi-update output:

DietPi-Services
─────────────────────────────────────────────────────
 Mode: stop
....

Looks good for now.
dnsmasq will not be stopped any more, while dietpi-update is running. You have edit /DietPi/dietpi/dietpi-services correct and it is working. :+1:

---

My Ethernet connection is directly from the router - the openvpn client actually uses RPi as a host for me to VPN into my network from outside.

Okay. OpenVPN tunnelling is not you problem at the moment. :+1:

---

--- 192.168.0.1 ping statistics --- 0% packet loss

Okay, you default gateway is reachable :+1: and if I see it correct, it's aTP Link Archer 50

---

2: eth0: ... state UP ...
    inet 192.168.0.201/24 brd 192.168.0.255 scope global eth0

3: wlan0: ... state UP ...
    inet 192.168.0.200/24 brd 192.168.0.255 scope global wlan0

1.) - you have to disable WiFi via dietpi-config so wlan0 don't get a IP address any more.

2.) - you have to set Wired Connection (eth0) via dietpi-config to STATIC eg. 192.168.0.201

Change Mode    STATIC                                 
Copy           Copy Current address to Static         
Static Ip      192.168.0.201                         
Static Mask    255.255.255.0                          
Static Gateway 192.168.0.1                            
Static DNS     8.8.8.8                          
Disable        Disable Ethernet adapter              
Apply          Save Changes (Restart Networking) 

IP address output (my DCHP gives static address to alll):

Please disable this for 192.168.0.201

---

Routing table:

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         Archer50        0.0.0.0         UG    0      0        0 eth0
10.8.0.0        0.0.0.0         255.255.255.0   U     0      0        0 tun0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 wlan0

It should now look like this:

root@RPi-Zero:~# route -n

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.0.1        0.0.0.0         UG    0      0        0 eth0
10.8.0.0        0.0.0.0         255.255.255.0   U     0      0        0 tun0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0

---

Namesevers: (First one is raspPi itself, as I use pi-hole.

Your/etc/resolv.conf with running pihole should look like this:

root@RPi-Zero:~# cat /etc/resolv.conf

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1

But to simple edit the file will not do the trick.

• Check if pihole is up and running correct:

root@RPi-Zero:~# pihole status

  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled

Then as root:

## Backup lighttpd.conf
mv /etc/lighttpd/lighttpd.conf /etc/lighttpd/lighttpd.conf.bak

## Reconfigure or Repair Pi-hole subsystems
pihole -r

## Restore lighttpd.conf
cp /etc/lighttpd/lighttpd.conf.bak /etc/lighttpd/lighttpd.conf

## Restart all running services
dietpi-services restart

## Display the running status of Pi-hole subsystems
pihole status

## check resolv.conf
cat /etc/resolv.conf

## finished

Now DNS, routing and dietpi-update should work.

[nakulbende]

Hey @k-plan , thanks a lot. I will go home and redo this (for some reason, my VPN client is not working, so I can't VPN in and do changes from work. I remember restarting the pi after update to 6.2, so we will see).

Some small questions:

2.) - you have to set Wired Connection (eth0) via dietpi-config to STATIC eg. 192.168.0.201

So only here? Change Mode STATIC

Copy Copy Current address to Static
Static Ip 192.168.0.201
Static Mask 255.255.255.0

And Manually set this? Static Gateway 192.168.0.1

Static DNS 8.8.8.8
Disable Disable Ethernet adapter
Apply Save Changes (Restart Networking) IP address output (my DCHP gives static address to alll):

Please disable this for 192.168.0.201

Will do. Out of curiosity, DHCP is giving the pi a static address, so why does it matter that we need to remove this, and have pi setup as static.

As far as the pihole goes, Do i still use sudo nano to open this file, change nameserver to localhost and save it, follow your steps to make it permanent?

root@RPi-Zero:~# cat /etc/resolv.conf Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1

Would I have to change it back? or should the nameserver for pi be always localhost?

[k-plan]

@nakulbende

So only here?

Yes! It is whiptail menu. Move with courser keys and press enter to edit.

After this and hit Save Changes (Restart Networking)

your settings should look like this and #Please use DietPi-Config to modify network settings.:

root@RPi-Zero:~# cat /etc/network/interfaces

#/etc/network/interfaces
#Please use DietPi-Config to modify network settings.

...
# Ethernet
allow-hotplug eth0
iface eth0 inet static
address 192.168.0.201
netmask 255.255.255.0
gateway 192.168.0.1
dns-nameservers 8.8.8.8

# Wifi
#allow-hotplug wlan0
...

so why does it matter that we need to remove this, and have pi setup as static.

Pi-Hole installation told you to set a static ip to get work properly.

This is a little bit outdated, but overall you can see some nice screen shots: https://jacobsalmela.com/2015/08/26/a-new-easy-installation-method-for-the-ad-blocking-pi-hole/ It shows, what dietpi-software shows you before it will start the pihole installer

As far as the pihole goes, Do i still use sudo nano to open this file, change nameserver to ...

Sorry I read in the file :

Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

dietpi-config, dietpi-software, pihole installer ... use whiptail menus to set and edit config files.

So please use this menu and do not edit config files they need or set by hand. Yes you can do this, but only if you know what you are doing.

or should the nameserver for pi be always localhost?

pihole did this since some past version. It's needed for pihole to work correct. But pihole installer did it for you while install pihole, pihole-FTL, dnsmasq, and many other packets.

[nakulbende]

So, not sure what just happened. I tried to login with SSH, and this is what I got.

login as: root
root@192.168.0.201's password:

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
grep: /DietPi/dietpi.txt: No such file or directory
-bash: gettext.sh: No such file or directory
-bash: /DietPi/dietpi/func/dietpi-globals: No such file or directory
-bash: /DietPi/dietpi/login: No such file or directory

None of the dietpi-xxx commands work. What is wrong with my dietpi? I did take a backup using dietpi-backup, if needed.

[Fourdee]

@nakulbende

Please paste results:

systemctl status dietpi-ramdisk -l

[nakulbende]

Hey all,

So - I basically lost access to SSH altogether after i posted last time. When I connected it to the a screen, I saw a Ext4-fs error (something like can not find itable). I powered off my Pi, and tried to open the SD card on my computer, but it was corrupted. I can see some files, but even config.txt and contents of dietpi folder were missing! Seems like my SD card was corrupted while I had to pull the plug on my Pi, due to unresponsiveness which happened a couple of times during update. It seems like the issue I had was much alike this one.

I decided that I gotta just start with a fresh installation - buti did run into some problems (seems like the default webserver changed in 6.4 - failed installation of webserver prevented a successful pi-hole admin webadmin, so i uninstalled lighttpd and installed apache. Seems to work fine for now). I have a screnshot on my home desktop for the error - will post here if you guys are interested.

In short - the new installation was not as error free as my other dietpi installations, but I think it has been working. I am hoping that it was a read/ write intteruption that caused my SD card to go. Will update!

Thanks a lot for both of your help!

PS: for my education: what does this do?

systemctl status dietpi-ramdisk -l

[nakulbende]

Sorry - this was scrolling really fast, so I could only capture this much.

[k-plan]

@nakulbende

PS: for my education: what does this do?

• you can check status of the essential service, which must run in the background, to get all dietpi scripts to work:

root@RPi-Zero-W:~# systemctl status dietpi-ramdisk -l

● dietpi-ramdisk.service - DietPi-RAMdisk
   Loaded: loaded (/etc/systemd/system/dietpi-ramdisk.service; enabled; vendor preset: enabled)
   Active: active (exited) since Sun 2018-03-18 23:04:24 CET; 1 day 9h ago
   CGroup: /system.slice/dietpi-ramdisk.service

Mar 18 23:04:22 RPi-Zero-W systemd[1]: Starting DietPi-RAMdisk...
Mar 18 23:04:24 RPi-Zero-W systemd[1]: Started DietPi-RAMdisk.

or you can proof it with:

root@RPi-Zero-W:~# service dietpi-ramdisk status

● dietpi-ramdisk.service - DietPi-RAMdisk
   Loaded: loaded (/etc/systemd/system/dietpi-ramdisk.service; enabled; vendor preset: enabled)
   Active: active (exited) since Sun 2018-03-18 23:04:24 CET; 1 day 9h ago
   CGroup: /system.slice/dietpi-ramdisk.service

Mar 18 23:04:22 RPi-Zero-W systemd[1]: Starting DietPi-RAMdisk...
Mar 18 23:04:24 RPi-Zero-W systemd[1]: Started DietPi-RAMdisk.

Can't explain it better when in the header comments of the script.:

https://github.com/Fourdee/DietPi/blob/master/dietpi/dietpi-ramdisk#L3-L21

    #////////////////////////////////////
    # DietPi RAMDISK Script
    #
    #////////////////////////////////////
    # Created by Daniel Knight / daniel.knight@dietpi.com / dietpi.com
    #
    #////////////////////////////////////
    #
    # Info:
    # - Copies dietpi files from /boot to /DietPi (ram)
    # - /DietPi is mounted as tmpfs (ram)
    # - This allows us to vastly reduce filesystem IO across DietPi.
    # - Creates a file when active (/DietPi/.ramdisk)
    #
    # Usage:
    # - Called from /DietPi/dietpi/conf/dietpi-service
    # - /DietPi/dietpi/dietpi-ramdisk 0             = Copy from /boot (disk) to /DietPi (ram)
    # - /DietPi/dietpi/dietpi-ramdisk 1             = Copy from /DietPi (ram) to /boot (disk)
    #////////////////////////////////////

and the result:

root@RPi-Zero-W:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       7.3G  969M  6.1G  14% /
devtmpfs        237M     0  237M   0% /dev
tmpfs           241M     0  241M   0% /dev/shm
tmpfs           241M  3.3M  238M   2% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           241M     0  241M   0% /sys/fs/cgroup
tmpfs            10M  1.5M  8.6M  15% /DietPi
tmpfs            20M   24K   20M   1% /var/log
tmpfs           490M     0  490M   0% /tmp
/dev/mmcblk0p1   42M   23M   19M  54% /boot

I decided that I gotta just start with a fresh installation - ....

A good decision. After your previous post ... No such file or directory we normally advise to start with a fresh image on a full formated sd card, because your file system is corrupt. But most user don't want do hear this and get instantly acidify. They all have irreplaceable data on a cheap 20 $ device with the cheapest 5 $ sd card out of Sen Shen market and no backup ... sorry. So I have decided to leave well alone, to get around this excruciating discussion. It's the downside of sd card flash technology, not a issue of any distro or DietPi itself. Use the best sd card you can get and never pull power down while running.

DietPi try to get this more robust and reliable and this is, what dietpi-ramdisk does. But miracle are usually impossible.

[k-plan]

@Fourdee

buti did run into some problems (seems like the default webserver changed in 6.4 - failed installation of webserver

We have to take a look on it.

#       Webserver Preference Selection:
#       NB: This will get ignored, if you have manually selected any WEBSERVER_Stacks.
#               0=Apache2
#               -1=Nginx
#               -2=Lighttpd
AUTO_SETUP_WEB_SERVER_INDEX=-1

Uppps ...

[nakulbende]

Hey all,

I soon went with ngix, I wish I chose that in the config file as you said - because now I keep getting this error when i install some apps (I was installing iptraf and some other network monitoring things when this happened). It seems like it does not remember that I uninstalled Lighttpd and installed ngix.

Any way to choose default webservers? Is it form the whiptail menu you showed in last post? If so, I will check it as soon as I get back - pretty sure it was set to ngix.

[nakulbende]

We have to take a look on it.

@k-plan and @Fourdee : If it helps, here is a partial log for my installation, during which I believe webserver was creating issues. I might be wrong.

[  OK  ] DietPi-Services | dietpi_controlled : qbittorrent
[  OK  ] DietPi-Services | dietpi_controlled : blynkserver
[  OK  ] DietPi-Services | dietpi_controlled : motioneye
[  OK  ] DietPi-Services | dietpi_controlled : cups
[  OK  ] DietPi-Services | dietpi_controlled : plexpy
[  OK  ] DietPi-Services | dietpi_controlled : raspimjpeg
[ SUB2 ] DietPi-Set_Hardware > gpumemsplit (128)
[  OK  ] gpumemsplit 128 | Completed
[  OK  ] DietPi-Software | DietPi-Software installation completed.
[ SUB2 ] DietPi-Services > start
[  OK  ] DietPi-Services | start : cron
[  OK  ] DietPi-Services | start : proftpd
[  OK  ] DietPi-Services | start : apache2
[  OK  ] DietPi-Services | start : lighttpd
[  OK  ] DietPi-Services | start : php7.0-fpm
[  OK  ] DietPi-Services | start : noip2
[  OK  ] DietPi-Services | start : pihole-FTL
[  OK  ] DietPi-Services | start : avahi-daemon
[  OK  ] DietPi-Services | start : netdata
[  OK  ] DietPi-Services | start : plexmediaserver
[  OK  ] DietPi-Services | start : qbittorrent
[  OK  ] DietPi-Services | start : blynkserver
[  OK  ] DietPi-Services | start : motioneye
[  OK  ] DietPi-Services | start : cups
[  OK  ] DietPi-Services | start : plexpy
[  OK  ] DietPi-Services | start : raspimjpeg
[ SUB3 ] DietPi-Process_tool > Apply
[FAILED] DietPi-Process_tool | NetData (23028) : Nice      19
[FAILED] DietPi-Process_tool | NetData (23028) : Affinity  0-3
[FAILED] DietPi-Process_tool | NetData (23028) : Scheduler SCHED_OTHER 0
[FAILED] DietPi-Process_tool | NetData (23029) : Nice      19
[FAILED] DietPi-Process_tool | NetData (23029) : Affinity  0-3
[FAILED] DietPi-Process_tool | NetData (23029) : Scheduler SCHED_OTHER 0
[FAILED] DietPi-Process_tool | NetData (23030) : Nice      19
[FAILED] DietPi-Process_tool | NetData (23030) : Affinity  0-3
[FAILED] DietPi-Process_tool | NetData (23030) : Scheduler SCHED_OTHER 0
[FAILED] DietPi-Process_tool | Pi-hole FTL (22873) : Nice      0
[FAILED] DietPi-Process_tool | Pi-hole FTL (22873) : Affinity  0-3
[FAILED] DietPi-Process_tool | Pi-hole FTL (22873) : Scheduler SCHED_OTHER 0
[FAILED] DietPi-Process_tool | Webserver Apache2 (23362) : Nice      0
[FAILED] DietPi-Process_tool | Webserver Apache2 (23362) : Affinity  0-3
[FAILED] DietPi-Process_tool | Webserver Apache2 (23362) : Scheduler SCHED_OTHER 0
[FAILED] DietPi-Process_tool | Webserver Php-fpm (22803) : Nice      0
[FAILED] DietPi-Process_tool | Webserver Php-fpm (22803) : Affinity  0-3
[FAILED] DietPi-Process_tool | Webserver Php-fpm (22803) : Scheduler SCHED_OTHER 0
[FAILED] DietPi-Process_tool | Webserver Php-fpm (22804) : Nice      0
[FAILED] DietPi-Process_tool | Webserver Php-fpm (22804) : Affinity  0-3
[FAILED] DietPi-Process_tool | Webserver Php-fpm (22804) : Scheduler SCHED_OTHER 0
[FAILED] DietPi-Process_tool | Webserver Php-fpm (22805) : Nice      0
[FAILED] DietPi-Process_tool | Webserver Php-fpm (22805) : Affinity  0-3
[FAILED] DietPi-Process_tool | Webserver Php-fpm (22805) : Scheduler SCHED_OTHER 0
[FAILED] DietPi-Process_tool | Webserver Php-fpm (22806) : Nice      0
[FAILED] DietPi-Process_tool | Webserver Php-fpm (22806) : Affinity  0-3
[FAILED] DietPi-Process_tool | Webserver Php-fpm (22806) : Scheduler SCHED_OTHER 0
[FAILED] DietPi-Process Tool | An issue has occured
[ INFO ] DietPi-Patchfile | APT installation for: dirmngr, please wait...

[MichaIng]

@nakulbende Hui, sorry for late reply from our side. Did you managed it in between?

From both of your logs I see at least two webservers installed at the same time. dietpi-software should warn to just select one webserver stack, recommending to just select the webserver preference and the frontend software you need, letting DietPi automatically choose the right webserver stack. But it does not block parallel webserver installations, which then break each other. How did you install your software? Looks like not via dietpi-software whiptail gui?

If I got it right, you want to use nginx? No database with it?

Try the following:

1. Uninstall all non-nginx webservers + stacks: dietpi-software uninstall 75 76 81 82 83 84
2. Reinstall nginx and PHP: dietpi-software reinstall 84 89

[k-plan]

@MichaIng

... not block parallel webserver installations, which then break each other.

Hmm... habe da einmal ein wenig herum gespielt. Der zweite webserver lighttpd kommt von pihole Installer. Spielt auch keine Rolle, ob man via dietpi-software installiert oder nicht.

Test:

• Frisches Images ohne jegliche Zusatzsoftware

• in dietpi-software =>> nun Webserver Preference : Nginx ausgewählt

• via dietpi-software =>> pihole installieren

1. dietpi-software installiert Nginx.
2. dietpi-software lädt und startet den pihole installer und dieser installiert dann lighttpd

=>> wir haben nun auf dem System 2x webserver laufen, von denen einer chrashed.

... und anders herum:

• Frisches Images ohne jegliche Zusatzsoftware

• in dietpi-software =>> als Standard Vorgabe ist Webserver Preference : Lighttpd ausgewählt

• via dietpi-software =>> pihole installieren

1. dietpi-software installiert lighttpd.
2. dietpi-software lädt und startet den pihole installer und alles ist schick. (bis auf die Update Problematik)

Aber wenn man nun Webserver Preference nachträglich noch einmal ändern möchte, funktioniert das nicht (dauerhaft).

Die 2x webserver "Problematik" taucht auch auf, wenn man Software zur Installation auswählt, die einen andern Webserver als lighttpd wie nginx tomcat oder apache benötigt.

---

pihole mit Nginx läuft zwar, aber man muss dann auch bei jedem pihole Update wieder per Hand dran herum machen. Gerade noch einmal geprüft.

───────────────────────────────────────
 DietPi     | 13:00 | Sat 07/04/18
 ───────────────────────────────────────
 v6.6       | RPi Zero W (armv6l)
 ───────────────────────────────────────

root@RPi-Zero-W:~# pihole -v
  Pi-hole version is v3.3 (Latest: v3.3.1)
  AdminLTE version is v3.3 (Latest: v3.3)
  FTL version is v3.0 (Latest: v3.0)

root@RPi-Zero-W:~# pihole -up
  [i] Checking for updates...
  [i] Pi-hole Core:     update available
  [i] FTL:              up to date
  [i] Web Interface:    up to date

  [i] Pi-hole core files out of date
  [✓] Check for existing repository in /etc/.pihole
  [✓] Update repo in /etc/.pihole

  [✓] Root user check

        .;;,.
        .ccccc:,.
         :cccclll:.      ..,,
          :ccccclll.   ;ooodc
           'ccll:;ll .oooodc
             .;cll.;;looo:.
                 .. ','.
                .',,,,,,'.
              .',,,,,,,,,,.
            .',,,,,,,,,,,,....
          ....''',,,,,,,'.......
        .........  ....  .........
        ..........      ..........
        ..........      ..........
        .........  ....  .........
          ........,,,,,,,'......
            ....',,,,,,,,,,,,.
               .',,,,,,,,,'.
                .',,,,,,'.
                  ..'''.

  [i] Performing unattended setup, no whiptail dialogs will be displayed
  [✓] Disk space check

  [✓] Update local cache of available packages

  [✓] Checking apt-get for upgraded packages... 1 updates available
  [i] It is recommended to update your OS after installing the Pi-hole!

  [i] Installer Dependency checks...
  [✓] Checking for apt-utils
  [✓] Checking for dialog
  [✓] Checking for debconf
  [✓] Checking for dhcpcd5
  [✓] Checking for git
  [✓] Checking for iproute2
  [✓] Checking for whiptail

  [i] Performing reconfiguration, skipping download of local repos
  [✓] Resetting repository within /etc/.pihole...
  [✓] Resetting repository within /var/www/html/admin...
  [i] Main Dependency checks...
  [✓] Checking for bc
  [✓] Checking for cron
  [✓] Checking for curl
  [✓] Checking for dnsmasq
  [✓] Checking for dnsutils
  [✓] Checking for iputils-ping
  [✓] Checking for lsof
  [✓] Checking for netcat
  [✓] Checking for sudo
  [✓] Checking for unzip
  [✓] Checking for wget
  [✓] Checking for idn2
  [i] Checking for sqlite3 (will be installed)
  [i] Checking for lighttpd (will be installed)
  [✓] Checking for php-common
  [✓] Checking for php-cgi
  [✓] Checking for php-sqlite3
  [✓] Installing scripts from /etc/.pihole

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf

  [i] Creating log and changing owner to dnsmasq... log already exists!

  [i] Installing blocking page...
  [✓] Creating directory for blocking page, and copying files
  [✓] Backing up index.lighttpd.html

  [✓] Installing sudoer file

  [✓] Installing latest Cron script

  [✓] Installing latest logrotate script

  [i] FTL Checks...
  [✓] Detected ARM-hf architecture (armv6 or lower) Using ARM binary
  [i] Checking for existing FTL binary...
  [i] Latest FTL Binary already installed (v3.0). Confirming Checksum...
  [i] Checksum correct. No need to download!
  [i] Restarting services...

  [✓] Starting dnsmasq service

  [✓] Enabling dnsmasq service to start on reboot

  [✓] Starting lighttpd service

  [✓] Enabling lighttpd service to start on reboot

  [✓] Starting pihole-FTL service

  [✓] Enabling pihole-FTL service to start on reboot

  [i] Preparing to run gravity.sh to refresh hosts...
  [i] Cleaning up previous install (preserving whitelist/blacklist)
  [i] Running gravity.sh
  [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range

  [i] Target: raw.githubusercontent.com (hosts)
  [✓] Status: Retrieval successful

  [i] Target: mirror1.malwaredomains.com (justdomains)
  [✓] Status: Retrieval successful

  [i] Target: sysctl.org (hosts)
  [✓] Status: Retrieval successful

  [i] Target: zeustracker.abuse.ch (blocklist.php?download=domainblocklist)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_tracking.txt)
  [✓] Status: Retrieval successful

  [i] Target: s3.amazonaws.com (simple_ad.txt)
  [✓] Status: Retrieval successful

  [i] Target: hosts-file.net (ad_servers.txt)
  [✓] Status: Retrieval successful

  [✓] Consolidating blocklists
  [✓] Extracting domains from blocklists
  [i] Number of domains being pulled in by gravity: 144815
  [✓] Removing duplicate domains
  [i] Number of unique domains trapped in the Event Horizon: 121803
  [i] Number of whitelisted domains: 6
  [✓] Parsing domains into hosts format
  [✓] Cleaning up stray matter

  [✓] Force-reloading DNS service
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled

  [i] The install log is located at: /etc/pihole/install.log
  Update Complete!

root@RPi-Zero-W:~# cat /etc/pihole/install.log
  [✓] Installing scripts from /etc/.pihole

  [i] Installing configs from /etc/.pihole...
  [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf

  [i] Creating log and changing owner to dnsmasq... log already exists!

  [i] Installing blocking page...
  [✓] Creating directory for blocking page, and copying files
  [✓] Backing up index.lighttpd.html

  [✓] Installing sudoer file

  [✓] Installing latest Cron script

  [✓] Installing latest logrotate script

  [i] FTL Checks...
  [✓] Detected ARM-hf architecture (armv6 or lower) Using ARM binary
  [i] Checking for existing FTL binary...
  [i] Latest FTL Binary already installed (v3.0). Confirming Checksum...
  [i] Checksum correct. No need to download!

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

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

[  OK  ] DietPi-Services | php7.0-fpm   active (running) since Mon 2018-04-02 23:45:39 CEST; 4 days ago
[  OK  ] DietPi-Services | nginx        active (running) since Mon 2018-04-02 23:45:50 CEST; 4 days ago
[FAILED] DietPi-Services | lighttpd     failed (Result: exit-code) since Sat 2018-04-07 13:08:22 CEST; 5min ago
● lighttpd.service - Lighttpd Daemon
   Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2018-04-07 13:08:22 CEST; 5min ago
  Process: 17591 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (code=exited, status=255)
  Process: 17572 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)
 Main PID: 17591 (code=exited, status=255)

Apr 07 13:08:22 RPi-Zero-W systemd[1]: lighttpd.service: Unit entered failed state.
Apr 07 13:08:22 RPi-Zero-W systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Apr 07 13:08:22 RPi-Zero-W systemd[1]: lighttpd.service: Service hold-off time over, scheduling restart.
Apr 07 13:08:22 RPi-Zero-W systemd[1]: Stopped Lighttpd Daemon.
Apr 07 13:08:22 RPi-Zero-W systemd[1]: lighttpd.service: Start request repeated too quickly.
Apr 07 13:08:22 RPi-Zero-W systemd[1]: Failed to start Lighttpd Daemon.
Apr 07 13:08:22 RPi-Zero-W systemd[1]: lighttpd.service: Unit entered failed state.
Apr 07 13:08:22 RPi-Zero-W systemd[1]: lighttpd.service: Failed with result 'exit-code'.
[  OK  ] DietPi-Services | pihole-FTL   active (running) since Sat 2018-04-07 13:08:06 CEST; 5min ago
[  OK  ] DietPi-Services | cron active (running) since Mon 2018-04-02 23:45:51 CEST; 4 days ago
[  OK  ] DietPi-Services | dropbear     active (running) since Mon 2018-04-02 23:45:16 CEST; 4 days ago
[  OK  ] DietPi-Services | dnsmasq      active (running) since Sat 2018-04-07 13:07:46 CEST; 6min ago
[  OK  ] DietPi-Services | dietpi-boot  active (exited) since Mon 2018-04-02 23:45:34 CEST; 4 days ago
[  OK  ] DietPi-Services | dietpi-postboot      active (exited) since Mon 2018-04-02 23:45:34 CEST; 4 days ago

Uppps ... dann sollte man das fixen mit:

root@RPi-Zero-W:~# apt purge lighttpd* && apt autoremove -y

Danach Gegenprobe:

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

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

[  OK  ] DietPi-Services | php7.0-fpm   active (running) since Mon 2018-04-02 23:45:39 CEST; 4 days ago
[  OK  ] DietPi-Services | nginx        active (running) since Mon 2018-04-02 23:45:50 CEST; 4 days ago
[  OK  ] DietPi-Services | pihole-FTL   active (running) since Sat 2018-04-07 13:08:06 CEST; 12min ago
[  OK  ] DietPi-Services | cron active (running) since Mon 2018-04-02 23:45:51 CEST; 4 days ago
[  OK  ] DietPi-Services | dropbear     active (running) since Mon 2018-04-02 23:45:16 CEST; 4 days ago
[  OK  ] DietPi-Services | dnsmasq      active (running) since Sat 2018-04-07 13:07:46 CEST; 12min ago
[  OK  ] DietPi-Services | dietpi-boot  active (exited) since Mon 2018-04-02 23:45:34 CEST; 4 days ago
[  OK  ] DietPi-Services | dietpi-postboot      active (exited) since Mon 2018-04-02 23:45:34 CEST; 4 days ago
root@RPi-Zero-W:~#

Läuft ... alles schick! 😃

[MichaIng]

@k-plan Hmm, this is new... Looks like we need to block the installation of PiHole, if another webserver than Lighttpd is installed. The other way round, we need to force Lighttpd installation (ignoring user preference) via dietpi-software (so we can track) as pre-req for PiHole, as long as there is no possibility to convince PiHole on installation/update, that another webserver is already present...

Also: [i] Checking for dhcpcd5 (will be installed)

• Why a DHCP client is installed, if static IP is needed anyway? And it's not the one, DietPi uses (isc-dhcp-client), thus two different DHCP clients will be installed, while non of them will be used 😕.

I installed LAAP stack, PiHole afterwards and then purged dhcpcd5 + lighttpd. PiHole, including web interface, works still great 🤔. I mean on our install script we can purge those during configuration, but we cannot control what pihole -up does. Does it actually replace the lighttpd config as well? At least I guess if web ui update is available... But if I remember, it is a known issue, that PiHole update breaks our installation, or was this fixed somehow?

BAM, found a method that might solve all this problems:

root@DietPi:~# cat /etc/systemd/system/pihole-FTL.service.d/dietpi.conf
[Service]
ExecStartPre=/bin/bash -c 'echo YEEEEEEEEEEEEEEEEEES'
root@DietPi:~# systemctl restart pihole-FTL.service
root@DietPi:~# systemctl status pihole-FTL.service
● pihole-FTL.service - LSB: pihole-FTL daemon
   Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
  Drop-In: /etc/systemd/system/pihole-FTL.service.d
           └─dietpi.conf
   Active: active (running) since Mon 2018-04-09 16:15:47 CEST; 11s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 5777 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
  Process: 5792 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
  Process: 5789 ExecStartPre=/bin/bash -c echo YEEEEEEEEEEEEEEEEEES (code=exited, status=0/SUCCESS)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/pihole-FTL.service
           └─5812 /usr/bin/pihole-FTL

Apr 09 16:15:47 DietPi systemd[1]: Starting LSB: pihole-FTL daemon...
Apr 09 16:15:47 DietPi bash[5789]: YEEEEEEEEEEEEEEEEEES
Apr 09 16:15:47 DietPi pihole-FTL[5792]: Not running
Apr 09 16:15:47 DietPi pihole-FTL[5792]: rm: cannot remove '/var/run/pihole/FTL.sock': No such file or directory
Apr 09 16:15:47 DietPi su[5808]: Successful su for pihole by root
Apr 09 16:15:47 DietPi su[5808]: + ??? root:pihole
Apr 09 16:15:47 DietPi su[5808]: pam_unix(su:session): session opened for user pihole by (uid=0)
Apr 09 16:15:47 DietPi pihole-FTL[5792]: FTL started!
Apr 09 16:15:47 DietPi su[5808]: pam_unix(su:session): session closed for user pihole
Apr 09 16:15:47 DietPi systemd[1]: Started LSB: pihole-FTL daemon.

By this we should be able to check for lighttpd, dhcpcd5 installations, purge in case, and recover our lighttpd config in other case? But we could clarify, why actually lighttpd is preinstalled (maybe just, as it's too high effort to configure more webservers) as well as dhcpcd5.

[MichaIng]

Close in favour of https://github.com/Fourdee/DietPi/issues/1696