On my fresh install, it works so wonder what’s wrong with yours.
Stop the service and try starting manually (see ExecStart line in /etc/systemd/system/frontail.service).
Experiment with NODE_PATH environment (like export NODE_PATH=/opt/frontail until you have manual start working, then
eventually add setting it to frontail.service (do not forget systemctl daemon-reload).
i downloaded the latest Openhab Image from Release openHABian v1.7.4b · openhab/openhabian · GitHub
wrote it with balena etcher on a sd-card.
waited until the first login page on myip:8080 is available. but stillnothing on myip:9001.
I am experiencing exactly the same problem as @DaDen with a fresh install on my raspberry pi 3 v2. The frontail service fails to start with the same errors in the log as in the previous messages.
The image name is openhabian-pi-raspios32-202208151955-gitbe9d23e-crc075defd9.img
The relevant part of the log of the first boot of openhabian with DEBUG=maximum is appended here (I removed thre parts of the log containgn image data I think that made the mesage too long) .
EDIT: I also tried to switch branch from openhabian-config from OPENHAB3 to main and install again frontail (option 21) but the journalctl error remain the same.
I relaunched openhabian-config, that was already set on the openhabian branch “main”, and it updated itself.
I relaunched option 21 to install frontail and I can confirm that now frontail is starting regularly.
Thank you for your assistance,
Lionello Marrelli
no, they are not related. Frontail was not working because of the version of nodejs vs. the packages that were required for frontail. Frontail is comletely ( apart of the hardware it runs on ) separated from openhab.
Not for the basic/native/bare openhab installation.
In case you install something like frontail or node-red then you will need it but all these are not part of the basis installation but third party additions.
You should be able to see if nodejs is used on your system by running e.g.
Hello,
After downloading newest version 1.7 i have exactly the same problem as coleague above.
Could anybody help?
[...[
+ npm audit fix --force
npm WARN using --force Recommended protections disabled.
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN audit Updating jsdom to 20.0.3, which is a SemVer major change.
npm WARN audit Updating mocha to 10.1.0, which is a SemVer major change.
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated debug@3.2.6: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated formidable@1.2.1: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated superagent@3.8.3: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>.
npm WARN deprecated buster-core@0.6.4: No longer maintained
added 505 packages, and audited 506 packages in 4m
43 packages are looking for funding
run `npm fund` for details
# npm audit report
engine.io 4.0.0 - 6.2.0
Severity: high
Uncaught exception in engine.io - https://github.com/advisories/GHSA-r7qp-cfhv-p84w
fix available via `npm audit fix --force`
Will install socket.io@4.5.4, which is a breaking change
node_modules/engine.io
socket.io 3.0.0-rc1 - 4.4.1
Depends on vulnerable versions of engine.io
node_modules/socket.io
2 high severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
+ return 1
+ echo 'FAILED (install)'
FAILED (install)
http://openhabian:9001 → doesn’t show any frontail.
sudo systemctl status frontail → “Unit frontail.service could not be found.”
Re-install frontail with sudo openhabian-config and then option 21 “Log Viewer” failes with: "There was an error or interruption during the execution of: | “20 | Optional Components” "
Found a lot of different solutions from the past years (mainly old ones from 2020, 2021), but none of them could help so far…
Which version of the package nodejs is installed in the cases where frontail is not running ?
You may use the command dpkg -l nodejs to identify the installed version.
Command nodejs --version should return the same version information.
||/ Name Version Architektur Beschreibung
++±==============-========================-============-=================================================
ii nodejs 16.18.1-deb-1nodesource1 armhf Node.js event-based server-side javascript engine
||/ Name Version Architecture Description
++±==============-========================-============-=================================================
ii nodejs 16.18.1-deb-1nodesource1 armhf Node.js event-based server-side javascript engine
I just upgraded nodejs in an existing VM that contains debian 11 / bullseye from 16.17.0 to 16.18.1.
The nodejs package itself is not the problem - frontail still works.
login to your OH system via putty/ssh/telnet/any other way that you offers a shell
sudo bash
pay attention you have a root shell now; take care what you do; in case of errors read them; in case of an error stop instead of just continuing
cd /opt/frontail
npm audit fix --force
systemctl start frontail
systemctl status frontail should show that frontail is online alternatively you may connect using the bowser
Root cause of the problem was/is that there is a breaking change in an npm module. openhabian-config does not continue to install that breaking change. This is done manually with the above commands.