npm start Problem

[Lockslay]

Hello everyone,

After a few months I wanted to

sudo npm start
/usr/local/bin/node: 1: Syntax error: “)” unexpected
What does this mean and how can I solve it?

[sdetweil]

@Lockslay NEVER use sudo

cd ~/MagicMirror
npm start

[Lockslay]

@sdetweil

stefan@smartmirror:~ $ cd MagicMirror/
stefan@smartmirror:~/MagicMirror $ npm start
/usr/local/bin/node: 1: Syntax error: ")" unexpected](Link Adresse)

Unfortunately, that doesn’t work either

[sdetweil]

@Lockslay can you do
node - v

[Lockslay]

@sdetweil
node - v

-bash: /usr/local/bin/node: cannot execute binary file: Exec format error

[sdetweil]

@Lockslay

when was the last update to the system or MagicMirror?

do

nvm
and
n

see if either respond… because node is in the local folder

[Lockslay]

@sdetweil

Hello,

I did an apt update && apt upgrade today.
Everything else did not work after a reboot.

n
and nvm

command not found

[sdetweil]

@Lockslay

little more debug

uname -a
lsb_release -a
file /bin/bash
file /usr/local/bin/node

[Lockslay]

@sdetweil

uname -a
Linux smartmirror 6.1.21-v7+ #1642 SMP Mon Apr 3 17:20:52 BST 2023 armv7l GNU/Linux

lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye

file /bin/bash
/bin/bash: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, BuildID[sha1]=f12e6d40fb262ad0037b6ec43162208b76d4da71, for GNU/Linux 3.2.0, stripped

[sdetweil]

@Lockslay note I added an additional line

[Lockslay]

@sdetweil

file /usr/local/bin/node
/usr/local/bin/node: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=d6aa6eb3474758fb4e621dac8db78891d4f4c0ef, for GNU/Linux 3.2.0, with debug_info, not stripped, too many notes (256)

Sorry,
I hadn’t seen the message

[sdetweil]

@Lockslay yeh, something installed the 64 bit v of node on your 32 bit system.

let’s try this

sudo apt-get remove nodejs

then

 node - v

[Lockslay]

@sdetweil said in npm start Problem:

node - v

sudo apt-get remove nodejs
__

dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/man/man7’ not empty so not removed
dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/man/man5’ not empty so not removed
dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/man/man1’ not empty so not removed
dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/lib/utils’ not empty so not removed
dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/docs/output/using-npm’ not empty so not removed
dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/docs/output/configuring-npm’ not empty so not removed
dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/docs/output/commands’ not empty so not removed
dpkg: warning: while removing nodejs, directory ‘/usr/lib/node_modules/npm/bin’ not empty so not removed
Processing triggers for man-db (2.9.4-2) …
stefan@smartmirror:~ $ node - v
-bash: /usr/local/bin/node: cannot execute binary file: Exec format error

[sdetweil]

@Lockslay ok, next

sudo rm -rf /usr/lib/node_modules/npm
sudo rm  /usr/local/bin/node
which node  
sudo apt-get remove nodejs
hash -r
which node
node -v

[Lockslay]

@sdetweil Thanks for your help, isn’t it better to reinstall?
I just realised that the config is no longer there either

[sdetweil]

@Lockslay yes, probably.

flash SD card
boot
skip updates
use my script

if u back up w my other script
I will restore the config, css, and modules on top.of the new mm after install