UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[kristfrizh]

Hello
I'm very new with this application.
I have a problem with my installation. I cannot enter the admin page with mine port 8081.

i follow this intruction for the installation :
installation pages

I have configure the port in my VM for port 8081.
I use linux debian buster with VM.

I have been searching the answer from here.

• iobroker troubleshooting

• iobroker community (off course with google translate)

I have also tried this code.

sudo node node_modules/iobroker.js-controller/controller.js --logs

and the outputs are always (even i changes the port from 9000 and 9001 to others) :

2021-06-07 12:22:38.027  - info: host.try1 iobroker.js-controller version 3.2.16 js-controller starting
2021-06-07 12:22:38.031  - info: host.try1 Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-06-07 12:22:38.032  - info: host.try1 hostname: try1, node: v12.22.1
2021-06-07 12:22:38.032  - info: host.try1 ip addresses: 10.184.0.2 fe80::4001:aff:feb8:2
2021-06-07 12:22:38.145  - info: host.try1-Server  Error inMem-objects listening on port 8011: Error: listen EADDRINUSE: address already in use 127.0.0.1:8011
^[[A^[[B2021-06-07 12:23:08.065  - error: host.try1 No connection to databases possible, restart
2021-06-07 12:23:08.068  - info: host.try1 iobroker _restart
2021-06-07 12:23:08.273  - info: host.try1 iobroker Starting node restart.js

anyone can help me please?
am i do something wrong?
thank you very much for your kindness
regards

[Homoran]

@kristfrizh sagte in Configuring IOBROKER for the first time problem:

am i do something wrong?

sorry to hear that!
I'm not familiar with VM and especially containers.
But I do an iobroker installation on debian in a proxmox VM too.
I didn`t have to do anything with the ports

Port 8081 ist the port to reach the admin webUI, port 8082 the port of the webinterface for visualizations

Port 9000 and 9001 are ports for internal use of databases for objects and states an shouldn't been altered or used for other services.

the installation procedure is made much easier.

• install debian
• configure timezone and language
• call curl -sLf https://iobroker.net/install.sh | bash -
  • on a brandnew system all necessary packages incl. latest recommended node, will be installed
• open <IP>:8081

the troubleshooting page is fairly old and possibly outdated, should/can work.

What is the output for iobroker list instances

[kristfrizh]

@homoran
thank you for your reply

+ system.adapter.admin.0                  : admin                 : try1                                     -  enabled, port: 8089, bind: 8081, run as: admin

+ instance is alive

I have added a new admin in 8089 but still not working
I have doubt with the version of my dependencies.
Is it because the NPM, nodejs,node, and js-controller?
my NPM version is 6.14.13
nodejs is 12.22.1
node is 12.22.1

[Homoran]

@kristfrizh sagte in Configuring IOBROKER for the first time problem:

I have added a new admin in 8089

I see!

But you have entered 8081 as IP
here should be 0.0.0.0 (listen on all interfaces)

And there is no other instance running at all.

I guess it would be the easiest way at this stage to delete the VM, and start from anew, as I described in the last post

node and npm look good.

BTW - what debian image did you use - on/for what hardware?

[kristfrizh]

@homoran
thank you for the reply again!!

ok will do that
I'll inform you after i start a new VM

my debian is
debian-10-buster-v20210512

[kristfrizh]

@homoran

should be the port and bind in iobroker list instances be like this?

 system.adapter.admin.0                  : admin                 : try1                                     -  enabled, port: 8081, bind: 0.0.0.0, run as: admin

+ instance is alive

i follow some code from the forum to changes the instances

cd /opt/iobroker

iobroker set admin.0 --bind 0.0.0.0

iobroker set admin.0 --port 8081

thank you

[Homoran]

@kristfrizh sagte in Configuring IOBROKER for the first time problem:

my debian is
debian-10-buster-v20210512

for what architecture?

Beware!
for 64bit Arch you need AMD64 even if you have an Intel CPU; not x386!

@kristfrizh sagte in Configuring IOBROKER for the first time problem:

should be the port and bind in iobroker list instances be like this?

partly yes!
Now it's correct for the admin, but there should be at least info and discovery too

[kristfrizh]

@homoran

I'm using this VM for server
but it's totally new because every time i tried a new language i create a new one then combine it to fix server i want.
I have tried php,nodejs,mqtt,python so far and all works (for learning purposes).

I'm not quite know about the AMD64 because there is not option for me to choose the type in google cloud. but here is the overall system i get from the google cloud.

Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
Address sizes:       46 bits physical, 48 bits virtual
CPU(s):              2
On-line CPU(s) list: 0,1
Thread(s) per core:  2
Core(s) per socket:  1
Socket(s):           1
NUMA node(s):        1
Vendor ID:           GenuineIntel
CPU family:          6
Model:               85
Model name:          Intel(R) Xeon(R) CPU @ 2.00GHz
Stepping:            3
CPU MHz:             2000.104
BogoMIPS:            4000.20
Hypervisor vendor:   KVM
Virtualization type: full
L1d cache:           32K
L1i cache:           32K
L2 cache:            1024K
L3 cache:            39424K
NUMA node0 CPU(s):   0,1

I have tried run iobroker (with the instances above) but still the same error said that EADDRINUSE
even i changed it back to 9001 and 9000

Right now i will try to create a new VM

thank you for your hospitality
regards

[Homoran]

@kristfrizh sagte in Configuring IOBROKER for the first time problem:

Model name: Intel(R) Xeon(R) CPU @ 2.00GHz

there has been reported issues when using XEON!
I do not remember fully what kind of issue - sorry!

@kristfrizh sagte in Configuring IOBROKER for the first time problem:

but still the same error said that EADDRINUSE

what Address is in Use?
in your initial log it was 8011.
I do not know what this ist used for.

@kristfrizh sagte in Configuring IOBROKER for the first time problem:

I'm not quite know about the AMD64 because there is not option for me to choose the type in google cloud

download netinstall from debian:
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-10.9.0-amd64-netinst.iso

[kristfrizh]

@homoran
i have tried 8011 and 8000 also tried 9000 and 9001.
but still the same problem.

wow, i just knew that XEON compatibility issues with iobroker.

ok will try to changes the XEON (I still not know how but will figure it out).
I'll update my trial with a new CPU asap.
thank you very much for the knowledge.
regards!

[Homoran]

@kristfrizh sagte in Configuring IOBROKER for the first time problem:

i have tried 8011 and 8000 also tried 9000 and 9001.
but still the same problem.

please don`t change anything!
To find out what is going wrong we need the standard settings.

If you start up the next try, please wait until the setup by curl... has finished completely with the line

open <IP>:8081 and start configuring
(or anything like this ;-) )

Afterwards you have to re-login into the console

[kristfrizh]

@homoran

thank your for your hospitality

I have build a new system with I7 and linux ubuntu 18.04.

IObroker works wonderfully
thank you once again
regards

[Homoran]

@kristfrizh Thank you for the update!
good to hear it works and good luck and have fun!