1.37.0 -> 1.38.0 upgrade problems

[preeve9534]

Just did an upgrade from within Signal K from v1.37 to 1.38.

After upgrade and reboot:

1. My previously installed plugins are no longer detected. The only plugins detected by Signal K are those shipped with 1.38.

2. Actisense NGT-1 (canboat) provider fails to start entirely with the error

3/11/2021, 9:45:25 AM: ERROR 2021-03-11T08:45:25.446Z [actisense-serial] DLE followed by unexpected char 00, ignore message ERROR 2021-03-11T08:45:25.446Z [actisense-serial] Ignore short command len = 0

Previously error of this sort (which appear to derive from NMEA messages that canboat cannot parse) were flagged in the dashboard but did not kill the provider.

I'll report again when I have more information on what has gone awry.

P

[preeve9534]

Update

Problem 1 is because the content of ~/.signalk/node_modules/ has been overwritten. Does mean that the practice of placing or linking plugins into this directory is no longer supported?

Problem 2 is fixed by a hard system reboot. It is not sufficient to simply restart the server using the Dashboard "Restart" feature. At least it is not sufficient on Venus OS Large and it is not sufficient on Ubuntu 16.04.5 LTS.

P

[tkurki]

No change to plugin installation mechanisms or location.

I sincerely doubt that the upgrade from the Admin UI was the cause for ~/.signalk/node_modules/ being overwritten. The upgrade literally spawns npm install, which naturally modifies and adds to node_modules, but does not wipe it. Might it be that you had done something manually earlier and it was picked up in this restart?

Also when you say overwritten do you mean that there is something else than plugin modules there, or just that it was emptied?

The plugins that you have installed are included in ~/.signalk/package.json and can be reinstalled by running npm install there.

During my use of NGT-1 I have never encountered the kind of problems that you have with it. DLE followed... is not how unknown PGNs are shown, not in canboat nor in canboatjs. To me it is indicative of corrupt input data.

[preeve9534]

Hi Teppo,

I hadn't taken any actions to modify ~/.signalk/node_modules. This problem was on my production server - i.e. the one that runs my ship and I tend not to touch it. When I do touch it I use the Signal K as the preferred interaction route. Before the upgrade the directory had just symbolic links to my installed modules. After the upgrade, this content - hence my use of the term "overwritten". I restored the deleted symbolic links and all is working as before.

$> ls -1
balanced-match
base64-js
bl
brace-expansion
buffer
buffer-from
callback-stream
commist
concat-map
concat-stream
core-util-is
debug
duplexify
end-of-stream
extend
fs.realpath
glob
glob-parent
glob-stream
help-me
ieee754
inflight
inherits
is-absolute
isarray
is-extglob
is-glob
is-negated-glob
is-relative
is-unc-path
is-windows
json-stable-stringify-without-jsonify
leven
minimatch
minimist
mqtt
mqtt-packet
ms
once
ordered-read-streams
path-dirname
path-is-absolute
process-nextick-args
pump
pumpify
readable-stream
reinterval
remove-trailing-separator
safe-buffer
signalk-controller
signalk-panel
signalk-renotifier
signalk-venus-plugin
split2
sprintf-js
stream-shift
string_decoder
through2
through2-filter
to-absolute-glob
typedarray
unc-path-regex
unique-stream
util-deprecate
wrappy
ws
xtend

The only thing worth noting is that I did the Signal K upgrade and an upgrade to the "venus" plugin as consecutive actions (well they were both offered by the GUI), then re-booted.

As for the canboat issue. It is present with both of my Actisense NGT-1s. Neither Actisense Reader+NGT-1 nor Maretron's N2K Analyzer+Maretron USB Gateway report data corruption on the N2K bus itself and my home-brew N2K monitor runs directly at the CAN level without reporting errors. When I have a minute I'll try swapping my production server onto a different PC with a different OS in the hope that this will highlight/eliminate any possible issues with serial hardware / OS drivers.

P

On Thu, 11 Mar 2021 at 16:18, Teppo Kurki @.***> wrote:

No change to plugin installation mechanisms or location.

I sincerely doubt that the upgrade from the Admin UI was the cause for ~/.signalk/node_modules/ being overwritten. The upgrade literally spawns npm install, which naturally modifies and adds to node_modules, but does not wipe it. Might it be that you had done something manually earlier and it was picked up in this restart?

Also when you say overwritten do you mean that there is something else than plugin modules there, or just that it was emptied?

The plugins that you have installed are included in ~/.signalk/package.json and can be reinstalled by running npm install there.

During my use of NGT-1 I have never encountered the kind of problems that you have with it. DLE followed... is not how unknown PGNs are shown, not in canboat nor in canboatjs. To me it is indicative of corrupt input data.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/SignalK/signalk-server/issues/1290#issuecomment-796856870, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE2BPMIRTVOZTKWWJNHUY23TDDUODANCNFSM4Y73PCZQ .

-- Paul Reeve

Email: @.*** UK mobile: +44.7786.528092 NL mobile: +31.630.242748

[tkurki]

Closing as no longer actionable.