This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Error 'malformed entry in openplotterNodejs.list' when installing signalk-installer
#1
When I try to install signalk-server, I get a bunch of errors in the log (below).  openplotter-settings shows signalk-server installed, but it won't run.

The first significant error in log is:
Code:
E: Malformed entry 1 in list file /etc/apt/sources.list.d/openplotterNodejs.list (Component)
E: The list of sources could not be read.

And afterwards, when I manually run 'sudo apt update', I continue to get that error as well.

Looking in that file, I find:
Code:
deb https://deb.nodesource.com/node_16.x  main
deb-src https://deb.nodesource.com/node_16.x  main

And I can make the APT error go away by changing it to
Code:
deb https://deb.nodesource.com/node_16.x  bullseye main
deb-src https://deb.nodesource.com/node_16.x  bullseye main

But that, by itself, doesn't fix signalk-server, of course. 

If I remove signalk-server in openplotter-settings and refresh, the broken install goes away, but that removes the sources.list file that I fixed, too.  So when I run signalk server setup again, it fails the same way, and I'm stuck.

I'm about to dive into the sources and see if I can fix it myself.  But if there's already a fix or known workaround, I'd appreciate hearing about it in the meantime.



Installed:

openplotter-doc/bullseye,bullseye,now 3.4.0-alpha all [installed]
openplotter-network/bullseye,bullseye,now 3.1.2-beta all [installed]
openplotter-settings/bullseye,bullseye,now 3.3.1-beta all [installed]
openplotter-signalk-installer/bullseye,bullseye,now 3.1.6-beta all [installed]



Log installingl signalk-server:


Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
 openplotter-signalk-installer
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 38.8 kB of archives.
After this operation, 288 kB of additional disk space will be used.
Get:1 https://dl.cloudsmith.io/public/openplot...deb/debian bullseye/main arm64 openplotter-signalk-installer all 3.1.6-beta [38.8 kB]
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 38.8 kB in 0s (215 kB/s)
Selecting previously unselected package openplotter-signalk-installer.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 85747 files and directories currently installed.)
Preparing to unpack .../openplotter-signalk-installer_3.1.6-beta_all.deb ...
Unpacking openplotter-signalk-installer (3.1.6-beta) ...
Setting up openplotter-signalk-installer (3.1.6-beta) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for gnome-menus (3.36.0-1) ...
Processing triggers for mailcap (3.69) ...


Reading package lists...
Building dependency tree...
Reading state information...
Package 'nodejs' is not installed, so not removed
Package 'npm' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.


E: Malformed entry 1 in list file /etc/apt/sources.list.d/openplotterNodejs.list (Component)
E: The list of sources could not be read.


E: Malformed entry 1 in list file /etc/apt/sources.list.d/openplotterNodejs.list (Component)
E: The list of sources could not be read.
E: Malformed entry 1 in list file /etc/apt/sources.list.d/openplotterNodejs.list (Component)
E: The list of sources could not be read.
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: websocket-client in /usr/local/lib/python3.9/dist-packages (1.3.2)
Collecting websocket-client
 Using cached https://www.piwheels.org/simple/websocke...ne-any.whl (54 kB)
 Downloading https://www.piwheels.org/simple/websocke...ne-any.whl (54 kB)
Failed to stop signalk.service: Unit signalk.service not loaded.
Failed to stop signalk.socket: Unit signalk.socket not loaded.
sh: 1: npm: not found
Checking sources...
DONE
Installing python packages...
DONE
Installing/Updating signal K server...
FAILED: [Errno 2] No such file or directory: 'npm'
Setting version...
DONE
Reply
#2
Delete /etc/apt/sources.list.d/openplotterNodejs.list file, then open openplotter-settings and update to the last version. finally click "add sources" and reinstall signal k installer
Reply
#3
Thanks, this worked!

I found the thread under General / Version 3 Roadmap where this issue was first reported and fixed, so I'm sorry for the duplicate post.

I will suggest that we start reporting V 3 issues in individual threads on the forum rather than tacking them all onto the (exceedingly long) single thread, that would have made my search much easier in the first place...

But thanks as always for the hard work of integrating the pieces into a great solution!
Reply
#4
Next week we will go from alpha to beta and we will use the bugs forum.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)