Objects database error: connect ECONNREFUSED

[jmyxa]

Hallo allerseits,

seit heute stürtz der Admin-Adapter (und auch alle anderen) ohne "Fremdeinwirkung" permanent ab.
Die wohl ausschlaggebende Fehlermeldung lautet

2024-03-28 07:47:33.064  - ^[[31merror^[[39m: admin.0 (5015) Objects database error: connect ECONNREFUSED 0.0.0.0:9001
2024-03-28 07:47:33.094  - ^[[31merror^[[39m: shelly.0 (5063) Objects database error: connect ECONNREFUSED 0.0.0.0:9001
2024-03-28 07:47:33.102  - ^[[31merror^[[39m: tuya.0 (5048) Objects database error: connect ECONNREFUSED 0.0.0.0:9001
2024-03-28 07:47:33.123  - ^[[31merror^[[39m: tuya.0 (5048) States database error: connect ECONNREFUSED 0.0.0.0:9000
2024-03-28 07:47:33.152  - ^[[31merror^[[39m: zigbee.0 (5033) Objects database error: connect ECONNREFUSED 0.0.0.0:9001
2024-03-28 07:47:33.183  - ^[[31merror^[[39m: telegram.0 (5022) Objects database error: connect ECONNREFUSED 0.0.0.0:9001
2024-03-28 07:47:33.199  - ^[[31merror^[[39m: discovery.0 (5081) Objects database error: connect ECONNREFUSED 0.0.0.0:9001
2024-03-28 07:47:33.192  - ^[[31merror^[[39m: sonos.0 (5070) Objects database error: connect ECONNREFUSED 0.0.0.0:9001

Was läuft hier schief?

[arteck]

@jmyxa platte voll ?

[jmyxa]

@arteck sieht nicht danach aus

/dev/root       29768136 4255180  24271328  15% /
devtmpfs          340460       0    340460   0% /dev
tmpfs             472044       0    472044   0% /dev/shm
tmpfs             188820     988    187832   1% /run
tmpfs               5120       4      5116   1% /run/lock
/dev/mmcblk0p1    261108   51630    209478  20% /boot
tmpfs              94408       0     94408   0% /run/user/1000

[arteck]

@jmyxa

iob fix

dann

iob diag

und Ausgabe posten

[jmyxa]

@arteck bei fix:

==========================================================================
    Database maintenance (4/5)
==========================================================================

Checking for uncompressed JSONL databases... This might take a while!

Compressing /opt/iobroker/iobroker-data/states.jsonl
Cannot compress states.jsonl: Error: Failed to lock DB file "/opt/iobroker/iobroker-data/states.jsonl"!
    at JsonlDB.open (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@alcalzone/jsonl-db/build/lib/db.js:185:19)
    at async compressDB (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:37:9)
    at async main (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:78:17)
Compressing /opt/iobroker/iobroker-data/objects.jsonl
Cannot compress objects.jsonl: Error: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!
    at JsonlDB.open (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@alcalzone/jsonl-db/build/lib/db.js:185:19)
    at async compressDB (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:37:9)
    at async main (/home/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:93:17)
No relevant JSONL files found to compress, skip

bei diag:

======================= SUMMARY =======================
			v.2023-10-10


   Static hostname: raspberry
         Icon name: computer
  Operating System: Raspbian GNU/Linux 11 (bullseye)
            Kernel: Linux 6.1.21-v7+
      Architecture: arm

Installation: 		native
Kernel: 		armv7l
Userland: 		armhf
Timezone: 		Europe/Berlin (CET, +0100)
User-ID: 		1000
X-Server: 		false
Boot Target: 		multi-user.target

Pending OS-Updates: 	84
Pending iob updates: 	14

/home/iobroker/.diag.sh: line 486: nodejs: command not found
Nodejs-Installation: 	 	
			/usr/bin/node 		v18.17.1
			/usr/bin/npm 		9.6.7
			/usr/bin/npx 		9.6.7
			/usr/bin/corepack 	0.18.0

Recommended versions are nodejs  and npm 
*** nodejs is NOT correctly installed ***
Wrong installation path detected. This needs to be fixed.

Please check
https://forum.iobroker.net/topic/35090/howto-nodejs-installation-und-upgrades-unter-debian
for more information on how to fix these errors.

MEMORY: 
               total        used        free      shared  buff/cache   available
Mem:            921M        429M         92M        0.0K        399M        428M
Swap:            99M         14M         85M
Total:          1.0G        443M        178M

Active iob-Instances: 	8
Active repo(s): stable

ioBroker Core: 		js-controller 		5.0.19
			admin 			6.13.16

ioBroker Status: 	iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Status admin and web instance:
+ system.adapter.admin.0                  : admin                 : raspberry                                -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
  system.adapter.web.0                    : web                   : raspberry                                -  enabled, port: 8082, bind: 0.0.0.0, run as: admin

Objects: 		6710
States: 		5425

Size of iob-Database:

12M	/opt/iobroker/iobroker-data/objects.jsonl
36K	/opt/iobroker/iobroker-data/objects.jsonl.old2
6.8M	/opt/iobroker/iobroker-data/states.jsonl



=================== END OF SUMMARY ====================

[Thomas Braun]

@jmyxa sagte in Objects database error: connect ECONNREFUSED:

Pending OS-Updates: 84
Pending iob updates: 14

Dringend ran an den Update-Stau.

Zuvor:

iob nodejs-update

[jmyxa]

@thomas-braun

Es lag daran, dass der Zugriff auf states.jsonl und objects.jsons durch Locks verhindert war. Lock-Verzeichnisse löschen und rebooten.

[Thomas Braun]

@jmyxa

Den Update-Stau musst du aber dennoch beseitigen.

[Wildbill]

@jmyxa Dennoch hält man seine Installationen auf aktuellem Stand. Und das hier zeigt, dass bei Dir NodeJS eben falsch installiert ist:

Recommended versions are nodejs  and npm 
*** nodejs is NOT correctly installed ***
Wrong installation path detected. This needs to be fixed.
 

@Thomas-Braun hat Dir den nötigen Befehl zum Reparieren ja bereits genannt.

Gruss, Jürgen