Closed Fourdee closed 6 years ago
Puhh,
reading, Debian Stretch will start over after Kernel 4.10 is released.
https://wiki.debian.org/DebianStretch
If I see the timeline, it will be end of 2017 until official Stretch release. But good to know, you have a milestone.
Till then, let's go for hunting and fixing some bugs in Dietpi. π
dietpi-drive_manager
hangs at start with Stretch for roughly 30 seconds.
auto
entries for non-existent drives are enabled in /etc/fstab
, in combination with x-systemd.automount
ext4
for each drive resolves the issue. Which is unexpected?SystemD, hangs commands such as df
(which our script uses), until systemD times out waiting for drives.
dropbear
now supports SCP/SFTP by default (YAY!)Jessie testing:
Stretch testing:
I think I'll hold off on my projects until this is implemented. Otherwise it requires a reformat.
@Zone22
This wont be ready for a while, need to test and fix every installation. I may release the image under alpha, but wont be for a few weeks.
@k-plan Many thanks for testing results π , i've updated the list in first post and i'll get those fixed.
Note to self: test RoonBridge installer and dietpi-justboom
Typical, trying to do some RPi testing and http://archive.raspberrypi.org
is unstable/offline lol:
The following packages will be upgraded:
libraspberrypi-bin libraspberrypi0 raspberrypi-bootloader raspberrypi-kernel
4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 34.5 MB of archives.
After this operation, 33.8 kB of additional disk space will be used.
Err:1 http://archive.raspberrypi.org/debian jessie/main armhf raspberrypi-kernel armhf 1.20161215-1
500 Internal Server Error [IP: 46.235.227.11 80]
Err:2 http://archive.raspberrypi.org/debian jessie/main armhf libraspberrypi-bin armhf 1.20161215-1
500 Internal Server Error [IP: 46.235.227.11 80]
HiFi:
E: Package 'libavcodec56' has no installation candidate
E: Package 'libavformat56' has no installation candidate
E: Unable to locate package libavresample2
E: Package 'libavutil54' has no installation candidate
E: Package 'libbinio1ldbl' has no installation candidate
E: Unable to locate package libjson-c2
E: Package 'libnfs4' has no installation candidate
E: Unable to locate package libvpx1
E: Package 'libwildmidi1' has no installation candidate
E: Unable to locate package libx264-142
libavcodec57
libavformat57
libavresample3
libavutil55
May make more sense to change our installation to:
apt-get install mpd
nb: arm64 mpd does not exist in repo yet.
Which pulls in all the required packages, then dpkg -i
our latest mpd.deb (as of today, stretch installs 0.19.19 which is the same as our compiled version)
@Fourdee
New Alpha testing DietPi v140:
http://dietpi.com/phpbb/viewtopic.php?f=9&t=986&p=4455#p4455
You DietPi fixes are well done! π
Put this stuff to the forum, to get some more user and concern for Stretch alpha testing. But if you prefer it, I can put it as well on github. π
@k-plan
But if you prefer it, I can put it as well on github.
Forums are fine, please keep giving me a nudge on here (notification) so I don't miss it π
Great testing, thanks @k-plan. Stretch is a long road, lots of testing as you know, but with your help (and hopefully others), we'll get there much quicker π
@k-plan Merry Xmas! π π
Looks like the bluetooth issue exists on jessie aswell. lacking pi-bluetooth
packages. Will get that patched.
https://github.com/Fourdee/DietPi/issues/693
Ok thats done, still having issues with bluetooth on stretch:
root@DietPi:~# bluetoothctl
Waiting to connect to bluetoothd...
root@DietPi:~# systemctl status hciuart.service -l
β hciuart.service - Configure Bluetooth Modems connected by UART
Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2017-01-04 17:36:19 UTC; 2min 15s ago
Jan 04 17:36:19 DietPi systemd[1]: Starting Configure Bluetooth Modems connected by UART...
Jan 04 17:36:19 DietPi hciattach[344]: Can't open serial port: No such file or directory
Jan 04 17:36:19 DietPi hciattach[344]: Can't initialize device: No such file or directory
Jan 04 17:36:19 DietPi systemd[1]: hciuart.service: Control process exited, code=exited status=1
Jan 04 17:36:19 DietPi systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
Jan 04 17:36:19 DietPi systemd[1]: hciuart.service: Unit entered failed state.
Jan 04 17:36:19 DietPi systemd[1]: hciuart.service: Failed with result 'exit-code'.
WiFi:
root@DietPi:~# dmesg | grep brcm
[ 7414.760610] usbcore: registered new interface driver brcmfmac
[ 7414.761782] brcmfmac_sdio mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.bin failed with error -2
[ 7415.765022] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 7416.777708] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
/lib/firmware/brcm/brcmfmac43430-sdio.bin # does not exist
apt-get update
apt-get dist-upgrade -y
root@DietPi:~# dmesg | grep brcm
[ 3.291745] usbcore: registered new interface driver brcmfmac
[ 3.317270] brcmfmac_sdio mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.txt failed with error -2
[ 4.323907] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 5.333980] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
wget https://raw.githubusercontent.com/RPi-Distro/firmware-nonfree/master/brcm80211/brcm/brcmfmac43430-sdio.txt -O /lib/firmware/brcm/brcmfmac43430-sdio.txt
works.
Base package:
apt-get install neovim
Optional desktop GUI:
apt-get install neovim-qt
vi
RPi 3 onboard WiFi, not functional after reboot: http://dietpi.com/phpbb/viewtopic.php?f=9&t=986&p=5434#p5407
VNC4, and tightvnc server changed to tigervnc:
ii tigervnc-standalone-server 1.7.0+dfsg-2 armhf Standalone virtual network computing server
ii vnc4server 4.1.1+X4.3.0+t-1 armhf transitional package
root@DietPi:~# vncpasswd
-bash: vncpasswd: command not found
systemctl status vncserver.service -l
Feb 05 15:05:35 DietPi bash[1445]: vncserver: Couldn't find "tigervncpasswd" on your PATH.
Feb 05 15:05:35 DietPi bash[1445]: Please install the tigenvnc-common package, i.e., sudo apt-get install tigenvnc-common.
apt-get install tigervnc-common
tigervncpasswd
Seems to run, unable to connect...
I'd like to note that(although I'm using a manually updated PineA64) v145 produced an error with Fail2Ban for me. Apt-get has failed: β - Apt string = fail2ban --no-install-recommends β - Error code = 100 the console produced this: Job for fail2ban.service failed because the control process exited with error code. See "systemctl status fail2ban.service" and "journalctl -xe" for details. invoke-rc.d: initscript fail2ban, action "start" failed. Process: 7398 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)
ToDo:
@kronflux
Looks like an issue with apt, or a bug with the fail2ban
package. Fails to install on RPi 3, at a basic apt-get install
level:
Setting up fail2ban (0.9.6-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/fail2ban.service β /lib/systemd/system/fail2ban.service.
Job for fail2ban.service failed because the control process exited with error code.
See "systemctl status fail2ban.service" and "journalctl -xe" for details.
invoke-rc.d: initscript fail2ban, action "start" failed.
β fail2ban.service - Fail2Ban Service
Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2017-03-10 13:50:55 UTC; 29ms ago
Docs: man:fail2ban(1)
Process: 4390 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)
Mar 10 13:50:55 DietPi systemd[1]: fail2ban.service: Unit entered failed state.
Mar 10 13:50:55 DietPi systemd[1]: fail2ban.service: Failed with result 'exβ¦de'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package fail2ban (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.24-9) ...
Processing triggers for systemd (232-18) ...
Errors were encountered while processing:
fail2ban
E: Sub-process /usr/bin/dpkg returned an error code (1)
@Fourdee As a suggestion, as I don't know if you're using a custom build for ffmpeg, but if yes; it may be worthy to include the openmax functionality to include hardware assisted encoding (as in https://github.com/legotheboss/YouTube-files/wiki/(RPi)-Compile-FFmpeg-with-the-OpenMAX-H.264-GPU-acceleration)
@WolfganP
it may be worthy to include the openmax functionality to include hardware assisted encoding (as in
Legend π this should help Emby server performance which uses FFmpeg. https://github.com/Fourdee/DietPi/issues/869
I faced two problems with this image:
During dietpi-software installation process some warning is shown about "--force-yes is deprecated
" and options with "allow
" should be used instead.
I use dietpi to run nextcloud on my pi2. Chose LAAP webserver stack to assure that mariadb will be used. It is not yet possible to chose preferred database like webserver itself -> Separate issue already opened about that. Nevertheless depending or that or not, dietpi-services no tries to handle two database services "mysql" AND "mariadb". Actually mysql is not installed, at least not via apt and it does not show up in dietpi-software either. So I can't remove it. dietpi-services starts "mysql" first successfully and tries to start "mariadb" afterwards which fails after long trial time. Nextcloud works fine, using the available service. It IS actually mariadb, which can be seen via modules, version check and nextcloud web ui. I am wondering about this "mariadb" service. DietPi-Process_Tool also shows one entry about that beside : Webserver MariaDB (1086)
Never saw mariadb running as another service name than mysql. Did something change there or is it just some typing bug introduced with this dietpi image?
mysql/error.log shows, that indeed the two services seem to disturb each other:
2017-06-02 18:22:57 1995976704 [ERROR] mysqld: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
2017-06-02 18:23:28 1995976704 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/var/lib/mysql/aria_log_control'
2017-06-02 18:23:28 1995976704 [ERROR] Plugin 'Aria' init function returned error.
2017-06-02 18:23:28 1995976704 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-06-02 18:23:28 1995976704 [Note] InnoDB: The InnoDB memory heap is disabled
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-06-02 18:23:28 1995976704 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Using Linux native AIO
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Using generic crc32 instructions
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Completed initialization of buffer pool
2017-06-02 18:23:28 1995976704 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-06-02 18:23:28 1995976704 [Note] InnoDB: Retrying to lock the first data file
2017-06-02 18:23:29 1995976704 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-06-02 18:23:30 1995976704 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-06-02 18:23:31 1995976704 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-06-02 18:23:32 1995976704 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
...
2017-06-02 18:25:07 1995976704 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-06-02 18:25:08 1995976704 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-06-02 18:25:08 1995976704 [Note] InnoDB: Unable to open the first data file
2017-06-02 18:25:08 76f83000 InnoDB: Operating system error number 1 in a file operation.
InnoDB: Error number 1 means 'Operation not permitted'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2017-06-02 18:25:08 1995976704 [ERROR] InnoDB: Can't open './ibdata1'
2017-06-02 18:25:08 1995976704 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to $
2017-06-02 18:25:08 1995976704 [ERROR] Plugin 'InnoDB' init function returned error.
2017-06-02 18:25:08 1995976704 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-06-02 18:25:08 1995976704 [Note] Plugin 'FEEDBACK' is disabled.
2017-06-02 18:25:08 1995976704 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-06-02 18:25:08 1995976704 [ERROR] Aborting
dietpi-bugreport Reference CODE: bce03d8e-9e30-406c-95ff-07df36fd1f9e-1
β¬: Moved 2. problem into an own issue: https://github.com/Fourdee/DietPi/issues/1000 β¬β¬: Moved 1. to here: https://github.com/Fourdee/DietPi/issues/1018
About missing apc.php
with PHP7+, which results in some dummy file will be used instead:
7317
# - PHP7+ - File does not exist
7318else
7319 7320wget http://dietpi.com/downloads/conf/apc.php -O /var/www/apc.php
There is some apc.php
on github which is working well with my dietpi rpi stretch PHP7 setup: https://github.com/krakjoe/apcu/blob/master/apc.php
@MichaIng
There is some apc.php on github which is working well with my dietpi rpi stretch PHP7 setup:
Thanks for this π I've tested with Jessie and seems compatible. I'll update the code with new link.
Is there a beta image for the Asus Tinker Board by any chance? :P
@xanview
Is there a beta image for the Asus Tinker Board by any chance? :
Yep: http://dietpi.com/downloads/images/DietPi_AsusTinkerBoard-armv7-(Stretch).7z
Image is named Jessie, however its Stretch.
E: Package 'chromium' has no installation candidate
That's awesome, thank you! - I'm using it as a headless server and so far latest image is working beautifully.
Regarding the fail2ban issue, what solved it for me was simple:
$ sudo touch /var/log/auth.log
before the install, then it went through successfully π
(you might need to $ sudo apt-get purge fail2ban
if you're in a half-complete state)
@noplanman
$ sudo touch /var/log/auth.log before the install, then it went through successfully π
Legend π Many thanks for the fix. I'll get this added to dietpi-software
. Works with Jessie aswell, so we'll add for all distros.
Hi Fourdee, many thanks for your work.
I install webmin and the Module webminstats v2.16, if i open this Module ''Historic System Statistics" i get the Error Message "Error - Missing Content-Type Header"
I could solve this problem while I install apt-get install libcgi-pm-perl
many thanks again
I install DietPi_RPi-armv6-(Stretch) image, and install over dietpi-software Fail2Ban, after that the service don't start
$ /etc/init.d/fail2ban status Failed to start server : Starting fail2ban (via systemctl): fail2ban.serviceJob for fail2ban.service failed because the control process exited with error code. See "systemctl status fail2ban.service" and "journalctl -xe" for details. failed!
$ journalctl -xe -- -- Unit fail2ban.service has finished shutting down. Jul 08 16:08:04 nc-raspi2 systemd[1]: Starting Fail2Ban Service... -- Subject: Unit fail2ban.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit fail2ban.service has begun starting up. Jul 08 16:08:05 nc-raspi2 fail2ban-client[1739]: ERROR Failed during configuration: While reading from '/etc/fail2ban/jail.conf' [line 52]: option 'port' in section 'pam-generic' Jul 08 16:08:05 nc-raspi2 systemd[1]: fail2ban.service: Control process exited, code=exited status=255 Jul 08 16:08:05 nc-raspi2 systemd[1]: Failed to start Fail2Ban Service. -- Subject: Unit fail2ban.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit fail2ban.service has failed. -- -- The result is failed. Jul 08 16:08:05 nc-raspi2 systemd[1]: fail2ban.service: Unit entered failed state. Jul 08 16:08:05 nc-raspi2 systemd[1]: fail2ban.service: Failed with result 'exit-code'. Jul 08 16:08:05 nc-raspi2 systemd[1]: fail2ban.service: Service hold-off time over, scheduling restart. Jul 08 16:08:05 nc-raspi2 systemd[1]: Stopped Fail2Ban Service. -- Subject: Unit fail2ban.service has finished shutting down -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit fail2ban.service has finished shutting down. Jul 08 16:08:05 nc-raspi2 systemd[1]: fail2ban.service: Start request repeated too quickly. Jul 08 16:08:05 nc-raspi2 systemd[1]: Failed to start Fail2Ban Service. -- Subject: Unit fail2ban.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit fail2ban.service has failed. -- -- The result is failed. Jul 08 16:08:05 nc-raspi2 systemd[1]: fail2ban.service: Unit entered failed state. Jul 08 16:08:05 nc-raspi2 systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Solution: apt-get purge fail2ban && apt-get install fail2ban
$ /etc/init.d/fail2ban status fail2ban.service - Fail2Ban Service Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2017-07-08
V153 | RPi 2 Model B (armv7l)
https://github.com/Fourdee/DietPi/issues/475#issuecomment-285673712
Please, update berryboot testing image. Last one in http://dietpi.com/downloads/testing/ is from December.
Finally Stretch became stable for Raspbian: https://www.raspberrypi.org/downloads/raspbian/
Will it change anything in Dietpi? I'm under the impression that @Fourdee updated kernel components a while ago (or maybe I messed with my system a lot :-)
Yeah the kernel is updated together with dietpi regularly, but this has not much to do with the Distro version.
Raspbian still based on Debian Jessie until yesterday, thus DietPi for RPi did the same, if you didn't flash the beta above. Stretch brings a lot of new package major versions, that were frozen in Jessie, most importantly for my use cases PHP7.0 (instead of PHP5.6), which also changes locations of configuration files etc. This will be the same for some other packages I guess. So after full upgrade all DietPi images to Stretch, much code about distro version checks etc. can be cleaned up π .
@MichaIng
Finally Stretch became stable for Raspbian: https://www.raspberrypi.org/downloads/raspbian/
Nice one π
For now, we'll keep the Stretch as a beta image, Kodi and a few other items need testing and confirmed functional, before we replace our default Jessie image.
Can you provide DietPi testing build for Pine64? I'll give it a shot and test.
stretch will have to be installed from scratch, or an update from jessie will be possible?
@molnarti
stretch will have to be installed from scratch, or an update from jessie will be possible?
Stretch installs, will require a clean installation with the Stretch image.
Its not feasible for us to distro upgrade existing systems, as we have no way of knowing if the user has applied manual changes to Linux settings. User input is also required for distro upgrade, which again, could change depending on what the user has installed/configured (we cant predict outcome enough, to ensure 100% success).
@Fourdee
πΊ RPi Monitor: Memory missing: http://dietpi.com/phpbb/viewtopic.php?f=9&t=986 (external bug)
Where is a new upcoming version: RPi-Monitor v2.12-r0
https://github.com/XavierBerger/RPi-Monitor-deb/tree/master/packages
Tested with 2017-08-16-raspbian-stretch.img
and it work.
Because of new strech ethernet interface naming enx(+mac-address)
, user have to edit /etc/rpimonitor/template/network.conf
but it works as desired.
I upgraded my Pine64 install to Stretch and then, since it is my experimental build, went up to sid. Works fine overall but I don't have a bunch of packages installed, so it might be a premature 'works fine'.
I find the Stretch ethernet naming a bit gross but I'm sure there is a good reason for it.
@atiensivu
I find the Stretch ethernet naming a bit gross but I'm sure there is a good reason for it.
We revert to wlanx/ethx naming in DietPi v155: https://github.com/Fourdee/DietPi/blob/master/dietpi/patch_file#L2733-L2734
Is it possible to boot with DietPi Stretch for the first time with an enabled wifi configuration ?
With DietPi Jessie the dietpi.txt
file managed to do that but I don't manage to activate wifi on first boot with Stretch ? Am I missing something ?
@Bridouz
With DietPi Jessie the dietpi.txt file managed to do that but I don't manage to activate wifi on first boot with Stretch ?
Thanks for the report, i'll try to replicate π
DietPi Stretch (v151) installed with ethernet connexion. Wifi is not working out of the box.
By enabling wifi in DietPi-Config Raspbian wants to install netplug
A reboot after the installation of netplug
and WIFI SSID are available.
However I tried (after the wifi setting) to disable Ethernet. By doing it it removes netplug
and the Pi is now not accessible from either Ethernet or Wifi.
Edit: OK Wifi working with netplug. Scanning for SSID juste after the package installation fails. A reboot is mandatory to ne able to scan through available SSID
@Fourdee
Certbot is now packaged on Stretch and I can confirm it works with the webroot
plugin out of the box.
Would you authorize me to propose a PR with changes reflecting that ?
Certbot is now packaged on Stretch and I can confirm it works with the webroot plugin out of the box. Would you authorize me to propose a PR with changes reflecting that ?
Yep by all means π
Yes certbot from repo also working well for me on raspbian stretch.
I use python-certbot-apache and did the automated apache configuration with it. This creates a quite nice ssl/cipher config in a separate config file. Same exist for nginx: python-certbot-nginx
Images now Stretch by default:
ADMIN EDIT: All images are now Buster by default, hence invalid links have been removed.
Stretch Status Odroid C2: https://github.com/Fourdee/DietPi/issues/1032
Stretch Status Raspberry Pi:
π―οΈ Now live and default image for DietPi on RPi.
Hardware
DietPi-Software status:
Desktops:
/etc/chromium-browser.d/custom_flags
no effect. Sandbox.DietPi-Config:
DietPi-JustBoom
DietPi-Drive_Manager
π―οΈ v145 : https://github.com/Fourdee/DietPi/issues/751#issuecomment-280850954
Why Stretch?
This will allow for more "recent" software version installations through apt, that our users are requesting.