It’s it working for you?
Thanks, I´ll give it a try later today, cause I´ve run into a dead-end with all the tries I have done untill now.
Well… Sometimes I think the different opinions is due to different use. I dont consider my self unique, but when I hear from others, their systems isnt quiet as busy as mine.
I have 18 bindings running on my main system (Rpi3B+), beside that I have mqtt broker and Influxdb. It doesnt really sound as much, but I have alot of times, pollings etc going on. A single screen from frontail log will be filled within just a coupple of seconds, only events and openhab standard logging.
Due to my issues I tend to run into all the time, I have come to the fact, that my Rpi3B+ is running on overtime all the time, whcih may be part of my issues. I would also like to have the ipcamera binding running on the same system, and not splitt into two systems like I run it today.
I have tried to “upgrade” to Rpi4 (4Gb Ram). But I have seen too many issues with a fresh openhabian image, that it doesnt make sense to move everything to that system. My latest idea is to use my Odroid C2 (untill I get my C4), and get my main system “transfered” to that, today actually. Unfortunalty it means I´ll have to struggle with some manual installations. But I have to try, since I can no longer depend on the Rpi3B+ will be able to do its job, and the situation with the openhabian image for Rpi4 is not a solution atm… So now I have dietPi running on my Odroid C2 - ready to take over, (which infact is why I asked for the frontail installation, cause I cant get it to work, and I desperate need it. Frontail is my most used utillity, running all the time I´m working on the system. Sometimes I just sit there look at the frontail log, to see if everything is running as expected).
So now, it´s Odroid C2. Later it´s Odroid C4… I simply have to give up the Rpi.
Just tried your script… I´m not sure if it really was a good idea though, since I already had nodejs and nmp installed… I have no idea how linux will handle such an installation… Anyway, there is the outcome, (sorry for having changing the system language to danish).
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.
─────────────────────────────────────────────────────
DietPi v6.31.2 : 13:56 - søn 23-08-2020
─────────────────────────────────────────────────────
- Device model : Odroid C2 (aarch64)
- CPU temp : 48'C : 118'F (Optimal temperature)
- LAN IP : 10.4.28.183 (eth0)
- MOTD : Help testing the new RPi3/RPi4 64-bit image:
https://github.com/MichaIng/DietPi/issues/3570
─────────────────────────────────────────────────────
DietPi Team : MichaIng (lead), Daniel Knight (founder), Joulinar (support)
Image : DietPi Core Team (pre-image: Meveric)
Web : https://dietpi.com | https://twitter.com/dietpi_
Patreon Legends : Bryce
Donate : https://dietpi.com/#donate
DietPi Hosting : Powered by https://myvirtualserver.com
dietpi-launcher : All the DietPi programs in one place.
dietpi-config : Feature rich configuration tool for your device.
dietpi-software : Select optimized software for installation.
htop : Resource monitor.
cpu : Shows CPU information and stats.
root@openHAB2-C2:~# wget http://pcmus.com/openhab/scripts/install-frontail.sh
--2020-08-23 13:57:02-- http://pcmus.com/openhab/scripts/install-frontail.sh
Løser pcmus.com (pcmus.com)... 112.140.180.108
Tilslutter pcmus.com (pcmus.com)|112.140.180.108|:80... forbundet.
HTTP forespørgsel sendt, afventer svar... 200 OK
Længde: 87845 (86K) [application/x-sh]
Gemmer til: 'install-frontail.sh'
install-frontail.sh 100%[===================>] 85,79K 60,6KB/s in 1,4s
2020-08-23 13:57:05 (60,6 KB/s) - 'install-frontail.sh' gemt [87845/87845]
root@openHAB2-C2:~# nano install-frontail.sh
root@openHAB2-C2:~# sudo bash ./install-frontail.sh
Now installing Frontail
Havde:1 http://fuzon.co.uk/meveric all InRelease
Havde:2 http://fuzon.co.uk/meveric stretch InRelease
Ignorerer:3 https://deb.debian.org/debian stretch InRelease
Henter:4 https://deb.debian.org/debian stretch-updates InRelease [93,6 kB]
Ignorerer:5 https://dl.bintray.com/openhab/apt-repo2 stable InRelease
Henter:6 https://dl.bintray.com/openhab/apt-repo2 stable Release [6.051 B]
Havde:6 https://dl.bintray.com/openhab/apt-repo2 stable Release
Henter:7 https://deb.debian.org/debian-security stretch/updates InRelease [53,0 kB]
Henter:8 https://deb.debian.org/debian stretch-backports InRelease [91,8 kB]
Havde:9 https://deb.debian.org/debian stretch Release
Henter:11 https://deb.debian.org/debian-security stretch/updates/main arm64 Packages [535 kB]
Hentede 773 kB på 2s (296 kB/s)
Indlæser pakkelisterne... Færdig
Indlæser pakkelisterne... Færdig
Opbygger afhængighedstræ
Læser tilstandsoplysninger... Færdig
curl er allerede den nyeste version (7.52.1-5+deb9u11).
0 opgraderes, 0 nyinstalleres, 0 afinstalleres og 6 opgraderes ikke.
================================================================================
================================================================================
DEPRECATION WARNING
Node.js 8.x LTS Carbon is no longer actively supported!
You will not receive security or critical stability updates for this version.
You should migrate to a supported version of Node.js as soon as possible.
Use the installation script that corresponds to the version of Node.js you
wish to install. e.g.
* https://deb.nodesource.com/setup_10.x — Node.js 10 LTS "Dubnium"
* https://deb.nodesource.com/setup_12.x — Node.js 12 LTS "Erbium" (recommended)
* https://deb.nodesource.com/setup_14.x — Node.js 14 LTS "Fermium"
Please see https://github.com/nodejs/Release for details about which
version may be appropriate for you.
The NodeSource Node.js distributions repository contains
information both about supported versions of Node.js and supported Linux
distributions. To learn more about usage, see the repository:
https://github.com/nodesource/distributions
================================================================================
================================================================================
Continuing in 20 seconds ...
## Installing the NodeSource Node.js 8.x LTS Carbon repo...
## Populating apt-get cache...
+ apt-get update
Havde:1 http://fuzon.co.uk/meveric all InRelease
Havde:2 http://fuzon.co.uk/meveric stretch InRelease
Ignorerer:3 https://deb.debian.org/debian stretch InRelease
Havde:4 https://deb.debian.org/debian stretch-updates InRelease
Havde:5 https://deb.debian.org/debian-security stretch/updates InRelease
Havde:6 https://deb.debian.org/debian stretch-backports InRelease
Havde:7 https://deb.debian.org/debian stretch Release
Ignorerer:8 https://dl.bintray.com/openhab/apt-repo2 stable InRelease
Henter:9 https://dl.bintray.com/openhab/apt-repo2 stable Release [6.051 B]
Havde:9 https://dl.bintray.com/openhab/apt-repo2 stable Release
Indlæser pakkelisterne... Færdig
## Confirming "stretch" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_8.x/dists/stretch/Release'
## Adding the NodeSource signing key to your keyring...
+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
OK
## Creating apt sources list file for the NodeSource Node.js 8.x LTS Carbon repo...
+ echo 'deb https://deb.nodesource.com/node_8.x stretch main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src https://deb.nodesource.com/node_8.x stretch main' >> /etc/apt/sources.list.d/nodesource.list
## Running `apt-get update` for you...
+ apt-get update
Havde:1 http://fuzon.co.uk/meveric all InRelease
Havde:2 http://fuzon.co.uk/meveric stretch InRelease
Henter:3 https://deb.nodesource.com/node_8.x stretch InRelease [4.620 B]
Ignorerer:4 https://deb.debian.org/debian stretch InRelease
Havde:5 https://deb.debian.org/debian stretch-updates InRelease
Havde:6 https://deb.debian.org/debian-security stretch/updates InRelease
Havde:7 https://deb.debian.org/debian stretch-backports InRelease
Havde:8 https://deb.debian.org/debian stretch Release
Ignorerer:9 https://dl.bintray.com/openhab/apt-repo2 stable InRelease
Henter:10 https://dl.bintray.com/openhab/apt-repo2 stable Release [6.051 B]
Havde:10 https://dl.bintray.com/openhab/apt-repo2 stable Release
Henter:11 https://deb.nodesource.com/node_8.x stretch/main Sources [762 B]
Henter:12 https://deb.nodesource.com/node_8.x stretch/main arm64 Packages [1.007 B]
Hentede 6.389 B på 2s (2.324 B/s)
Indlæser pakkelisterne... Færdig
## Run `sudo apt-get install -y nodejs` to install Node.js 8.x LTS Carbon and npm
## You may also need development tools to build native addons:
sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt-get update && sudo apt-get install yarn
Indlæser pakkelisterne... Færdig
Opbygger afhængighedstræ
Læser tilstandsoplysninger... Færdig
Følgende NYE pakker vil blive installeret:
nodejs
0 opgraderes, 1 nyinstalleres, 0 afinstalleres og 6 opgraderes ikke.
13,3 MB skal hentes fra arkiverne.
Efter denne handling, vil 70,9 MB yderligere diskplads være brugt.
Henter:1 https://deb.nodesource.com/node_8.x stretch/main arm64 nodejs arm64 8.17.0-1nodesource1 [13,3 MB]
Hentede 13,3 MB på 1s (10,8 MB/s)
Vælger tidligere fravalgt pakke nodejs.
(Læser database ... 59911 filer og kataloger installeret i øjeblikket.)
Gør klar til at udpakke .../nodejs_8.17.0-1nodesource1_arm64.deb ...
Udpakker nodejs (8.17.0-1nodesource1) ...
Sætter nodejs (8.17.0-1nodesource1) op ...
Behandler udløsere for man-db (2.7.6.1-2) ...
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
/usr/local/bin/frontail -> /usr/local/lib/node_modules/frontail/bin/frontail
+ frontail@4.9.1
updated 1 package in 11.231s
╭────────────────────────────────────────────────────────────────╮
│ │
│ New minor version of npm available! 6.13.4 → 6.14.8 │
│ Changelog: https://github.com/npm/cli/releases/tag/v6.14.8 │
│ Run npm install -g npm to update! │
│ │
╰────────────────────────────────────────────────────────────────╯
./install-frontail.sh: linje 12: /usr/lib/node_modules/frontail/preset/openhab.json: Ingen sådan fil eller filkatalog
./install-frontail.sh: linje 36: /usr/lib/node_modules/frontail/web/assets/styles/openhab.css: Ingen sådan fil eller filkatalog
Congrats Frontail should now be installed if there were no errors.
root@openHAB2-C2:~# systemctl status frontail
● frontail.service - Frontail openHAB instance, reachable at http://openHAB2-C2:9001
Loaded: loaded (/lib/systemd/system/frontail.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2020-08-23 14:00:28 CEST; 56s ago
Docs: https://github.com/mthenw/frontail
Process: 10687 ExecStart=/usr/lib/node_modules/frontail/bin/frontail --ui-highlight --ui-highlight-preset /usr/lib/node_modules/frontail/preset/openhab.json -t openhab -l 2000 -n 200 /var/log/openhab2/open
hab.log /var/log/openhab2/events.log (code=exited, status=203/EXEC)
Main PID: 10687 (code=exited, status=203/EXEC)
aug 23 14:00:28 openHAB2-C2 systemd[1]: frontail.service: Unit entered failed state.
aug 23 14:00:28 openHAB2-C2 systemd[1]: frontail.service: Failed with result 'exit-code'.
aug 23 14:00:28 openHAB2-C2 systemd[1]: frontail.service: Service hold-off time over, scheduling restart.
aug 23 14:00:28 openHAB2-C2 systemd[1]: Stopped Frontail openHAB instance, reachable at http://openHAB2-C2:9001.
aug 23 14:00:28 openHAB2-C2 systemd[1]: frontail.service: Start request repeated too quickly.
aug 23 14:00:28 openHAB2-C2 systemd[1]: Failed to start Frontail openHAB instance, reachable at http://openHAB2-C2:9001.
aug 23 14:00:28 openHAB2-C2 systemd[1]: frontail.service: Unit entered failed state.
aug 23 14:00:28 openHAB2-C2 systemd[1]: frontail.service: Failed with result 'exit-code'.
root@openHAB2-C2:~# ^C
root@openHAB2-C2:~#
Ummmm, this may impact Node-RED that was happily running on that machine / image.
Is doesn’t look like you have got any further, based on what that Status page says.
How do you feel about having one instance of Frontail for openhab.log and another for events.log?
I’m wondering if this is an ARM64 issue?
Can you reach out to the author of Frontail?
Thats why I decided to re-flash my eMMC 
Correct, I just got another error code. Before this, I got the error status code 210/CHROOT.
This is hardly an arm64 issue. Frontail runs on my Rpi4, however it was installed through the openhabian image.
Maybe. Question is what exactly to ask for. I have very limited knowlededge on this linux stuff. And from what I can tell, there is something odd going on with the installation, depending on which liniux using. Running Debian(DietPi) it seems like installing Frontail ends up in different folders than running ubuntu or even the Rpi openhabian image… Having this problem, I would have no idea how to handle it. I think I have tried almost any kind of combination.
I have a slight feeling it all boils down to user permissions and “paths”. (that seem to my over-all difficulties with linux).
Remember what I said yesterday - Trying to understand Linux is like having a chinese telling me something. Now, I need to ask questions back, in chinese
Is your Pi4 an ARM64 device, or ArmHF ?
Curiously, it’s only failing when…
Asking to monitor 2 or more log files, when running in Daemon mode, either from a service file, or the command line.
As in
This works
frontail /var/log/openhab2/openHAB.log /var/log/openhab2/events.log
This also works
frontail /var/log/openhab2/*
But these do not
frontail -d /var/log/openhab2/openHAB.log /var/log/openhab2/events.log
frontail -d /var/log/openhab2/*
But these do work
frontail -p 9001 /var/log/openhab2/openHAB.log
frontail -p 9002 /var/log/openhab2/events.log
“When I run the {above commands} from a prompt, everything is fine, but from a service file, anything more than 1 log file causes a restart limit and the service stops”
Broadcom BCM2711, quad-core Cortex-A72 (ARM v8) 64-bit SoC @ 1.5GHz
Did you actually get one log to work from the service file?
Yes, hence the comment above 
I have it flashed and ready but have not tried it yet. Between work and family I haven’t much time but will hopefully start it up soon.
1 Like
Turns out that it’s some strange issue with DietPi.
It works perfectly on an Ubuntu based system
Should I not use DietPi and flash Ubuntu instead? If so, do you recommend the server or desktop version? I would like to have a browser for internet searches if it doesn’t slow or hang the system.
Thanks
It really doesn’t matter which OS you use, as Chromium works on both.
(Although Ubuntu uses a SNAP version called Chromium-Browser)
The only thing to consider is that a stand alone Chromium browser doesn’t have a sandbox, so it’s more exposed to the OS than a more secure “sandboxed” version.
(My previous comment was aimed at Kim, regarding Frontail)
1 Like
If you want best support, clean system and as less bad surprises as possible:
Odroid C4 still have some common low level issues common to all, which means even Armbian has them. Others can only have them more. Dietpi adds nothing to the hardware layer but add lots of branding (that doesn’t help users in any way) and unnecessary changes - nobody maintains - which are causing troubles in the user land … while in Armbian this stays clean and only slightly modified / fixed in relation to plain Debian or Ubuntu.
Then you should go with a good OS (not one-man-band Debian fork which is already quite buggy out of the box) and matured hardware. Having none is expecting impossible / walking on the edge … where occasional crash - that nobody will address - is a normal thing.
Absolutely it is an overkill and that solo is not the biggest problem. HW support is not matured → its not really deployment ready. Running a reliable service is much further from running Android / desktop apps.
Also those small and cheap devices are made for some specific purposes (except Rpi/Odroid C class - those are good for everything and nothing really good at the same time). If you want general purpose device to cover a lot of things, perhaps also run VMs, serve files … you need to look into much higher price range. Outside hobby general purpose program.
Upcoming Armbian build for C4 are becoming usable / stable. In Ubuntu Focal & Groovy or Debian Buster & Bullseye flavour …
Where are you getting that information from?
What makes you think they aren’t being supported?
DietPi’s image for C4 works perfectly.
1st hand.
Considering that OpenHab can also run as low as on Raspbian, this should not be hard. But why would one want to use OS that rebrands other projects work and adds security holes on user land? Not to mention that Diet provides “perfectly working” horribly outdated BSP 4.9.y kernel? Yeah right. 
@igorp does a lot of work on the Armbian project, thanks heaps 
as I am now running Armbian on an Odroid N2+ that is flawlessly running for a few weeks and openHAB 3.
What used to take 50% of my processor on a C2, now takes <10% load of the N2+
1 Like
so, you paid for a 90% of cpu that you don’t use! 
I’m jocking, I’m really curious about the N2+ but reading here on the forum and after a little bit of experience I think I will continue using a dedicated raspberry 3 for openhab and I will buy a N2+/RP4 for nextcloud, grafana, influx db and other stuff… I have a RP4/4gb and when I tried OH on that board I didn’t see difference.
If you have a big enough OH setup, then you will notice a difference. And specially when booting up the system, there is a huge difference…
I have both Rpi3B+ and Rpi4(4GB). My rpi3B+ is using an SSD, atm my Rpi4 is using SD card.
I can not recommed a Rpi3B+ anymore, if you plan on having a rather big OH setup.
I have proven that I REQUIRE the extra CPU in my N2+ because certain things I wanted to do failed to work in real time with a slower CPU. When you are talking about needing a real-time video stream processed within a certain time for a feature to work, it becomes a requirement. Just because you don’t hit 100% cpu load does not mean you don’t need a faster cpu. If a task has to happen in real-time there are cases where you need more cpu and simply waiting longer for a slower cpu to get the job done is not a solution that works, as it has to be delivered in real time.
As a real world example the 50% load I was speaking of is turning a MP4 stream into a MJPEG one for a single video camera. I had to compromise on video quality to even get it to run in real-time at that 50% load… Now I have more cpu power, I can use any qaulity and framerate I want (1080p and 20 frames a second) and I can actually do it in real-time at a 15% load ! I can now do multiple cameras should I wish and there are plenty of AI applications that I have on the todo list with the extra power.
Faster boot up times, faster responsive system and more applications are now actually possible to do that were not possible before. The C4 and N2+ is getting a lot of hardware acceleration support that may help some situations due to, openGL, panfrost / Bifrost support in newer Linux kernels so it is not just the bigger CPU but also the GPU can do number crunching.