Errors on Lokinet

I Installed Lokinet, seems ok.

https://aur.archlinux.org/packages/lokinet

But service seems reluctant.

~]$ systemctl start lokinet
Job for lokinet.service failed because the control process exited with error code.
See "systemctl status lokinet.service" and "journalctl -xeu lokinet.service" for details.
[sum@ordi1 ~]$ journalctl -xeu lokinet.service
nov. 07 19:33:11 ordi1 lokinet[64434]: [ERR] [](560) 2022-11-07 18:33:11.350 GM>
nov. 07 19:33:11 ordi1 lokinet[64434]: [ERR] [](560) 2022-11-07 18:33:11.350 GM>
nov. 07 19:33:11 ordi1 lokinet[64434]: [ERR] [](560) 2022-11-07 18:33:11.350 GM>
nov. 07 19:33:11 ordi1 systemd[1]: lokinet.service: Main process exited, code=e>
â–‘â–‘ Subject: Unit process exited
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: https://forum.manjaro.org/c/support
â–‘â–‘ 
â–‘â–‘ An ExecStart= process belonging to unit lokinet.service has exited.
â–‘â–‘ 
â–‘â–‘ The process' exit code is 'exited' and its exit status is 2.
nov. 07 19:33:11 ordi1 systemd[1]: lokinet.service: Failed with result 'exit-co>
â–‘â–‘ Subject: Unit failed
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: https://forum.manjaro.org/c/support
â–‘â–‘ 
â–‘â–‘ The unit lokinet.service has entered the 'failed' state with result 'exit-co>
nov. 07 19:33:11 ordi1 systemd[1]: Failed to start Lokinet: Anonymous Network l>
░░ Subject: L'unité (unit) lokinet.service a échoué
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: https://forum.manjaro.org/c/support
â–‘â–‘ 
░░ L'unité (unit) lokinet.service a échoué, avec le résultat failed.
lines 71-93/93 (END)

A nice soul could bring hints ? :nerd_face:

Im not sure how to help,you are aware the lokinet package hasnt been updated since July, right? You may have better luck with the lokinet-bin package, it was updated in September.

No luck with the -bin : doesn’t compile (Error)
It’s also an earlier versions, seemingly.

For now I’m still stuck.

Does anybody use Lokinet on Manjaro ?

binary packages are not compiled - just used as is
(they contain the already precompiled binary - just as every repo package, for instance)
… we are left to guess what the error might have been …


and, for what it’s worth:
I was curious to learn what that lokinet is all about

The website had a lot of words - which did not amount to any meaning to me.
So I dug a little deeper - meaning: not just on their website and FAQ

and found this:

A Review of Lokinet (Oxen): A Road to Nowhere?

which seems to give a bit more actual information

my personal conclusion:
I wouldn’t touch this with a ten feet pole - you’d have to pay me to even try and install it :wink:

Hi,
Thank you for caring.

The install fail happened with pamac GUI.

With yay, inbstall succeeds, but service doesn’t start:

[sum@ordi1 ~]$ yay -S lokinet-bin
:: VĂ©rification des conflits...
:: VĂ©rification des conflits internes...
[Repo:2]  fstrm-0.6.1-1  unbound-1.17.0-1
[Aur:1]  lokinet-bin-0.9.9-1

:: (1/1) PKGBUILD téléchargé : lokinet-bin
  1 lokinet-bin                      (Fichiers de compilation existants)
==> Afficher les diffs ?
==> [N]Aucun [A]Tous [Ab]Annuler [I]nstallés [No]nInstallés ou (1 2 3, 1-3, ^4)
==> 
:: (1/1) Lecture de SRCINFO : lokinet-bin
[sudo] Mot de passe de sum : 
résolution des dépendances…
recherche des conflits entre paquets…

Paquets (2) fstrm-0.6.1-1  unbound-1.17.0-1

Taille totale installée :  4,15 MiB

:: Procéder à l’installation ? [O/n] 
(2/2) vérification des clés dans le trousseau      [----------------------] 100%
(2/2) vérification de l’intégrité des paquets      [----------------------] 100%
(2/2) chargement des fichiers des paquets          [----------------------] 100%
(2/2) analyse des conflits entre fichiers          [----------------------] 100%
(2/2) vérification de l’espace disque disponible   [----------------------] 100%
:: Traitement des changements du paquet…
(1/2) installation de fstrm                        [----------------------] 100%
(2/2) installation de unbound                      [----------------------] 100%
DĂ©pendances optionnelles pour unbound
    expat: for unbound-anchor [installé]
    sh: for unbound-control-setup [installé]
    python: for python-bindings [installé]
:: Exécution des crochets (« hooks ») de post-transaction…
(1/4) Creating system user accounts...
(2/4) Reloading system manager configuration...
(3/4) Creating temporary files...
(4/4) Arming ConditionNeedsUpdate...
==> Création du paquet lokinet-bin 0.9.9-1 (jeu. 10 nov. 2022 08:57:55)
==> Récupération des sources…
  -> Téléchargement de lokinet-0.9.9.tar.xz…
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 3807k  100 3807k    0     0  1616k      0  0:00:02  0:00:02 --:--:-- 1616k
  -> lokinet.conf trouvé
  -> lokinet.service trouvé
  -> lokinet-vpn.service trouvé
  -> lokinet-bootstrap.service trouvé
  -> lokinet-default-config.service trouvé
  -> lokinet-resume.service trouvé
  -> lokinet.sysusers trouvé
  -> lokinet.tmpfiles trouvé
  -> lokinet.pkla trouvé
  -> lokinet.rules trouvé
  -> Téléchargement de LICENSE…
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 35148  100 35148    0     0   115k      0 --:--:-- --:--:-- --:--:--  115k
==> Validation des fichiers source avec sha256sums…
    lokinet-0.9.9.tar.xz ... RĂ©ussite
    lokinet.conf ... Ignoré
    lokinet.service ... RĂ©ussite
    lokinet-vpn.service ... RĂ©ussite
    lokinet-bootstrap.service ... RĂ©ussite
    lokinet-default-config.service ... RĂ©ussite
    lokinet-resume.service ... RĂ©ussite
    lokinet.sysusers ... RĂ©ussite
    lokinet.tmpfiles ... RĂ©ussite
    lokinet.pkla ... RĂ©ussite
    lokinet.rules ... RĂ©ussite
    LICENSE ... RĂ©ussite
 -> unbound dépendance non satisfaite, suppression de la file d'attente
==> Création du paquet lokinet-bin 0.9.9-1 (jeu. 10 nov. 2022 08:57:59)
==> Vérification des dépendances pour l’exécution…
==> Vérification des dépendances pour la compilation…
==> Récupération des sources…
  -> lokinet-0.9.9.tar.xz trouvé
  -> lokinet.conf trouvé
  -> lokinet.service trouvé
  -> lokinet-vpn.service trouvé
  -> lokinet-bootstrap.service trouvé
  -> lokinet-default-config.service trouvé
  -> lokinet-resume.service trouvé
  -> lokinet.sysusers trouvé
  -> lokinet.tmpfiles trouvé
  -> lokinet.pkla trouvé
  -> lokinet.rules trouvé
  -> LICENSE trouvé
==> Validation des fichiers source avec sha256sums…
    lokinet-0.9.9.tar.xz ... RĂ©ussite
    lokinet.conf ... Ignoré
    lokinet.service ... RĂ©ussite
    lokinet-vpn.service ... RĂ©ussite
    lokinet-bootstrap.service ... RĂ©ussite
    lokinet-default-config.service ... RĂ©ussite
    lokinet-resume.service ... RĂ©ussite
    lokinet.sysusers ... RĂ©ussite
    lokinet.tmpfiles ... RĂ©ussite
    lokinet.pkla ... RĂ©ussite
    lokinet.rules ... RĂ©ussite
    LICENSE ... RĂ©ussite
==> Suppression du répertoire $srcdir/ existant…
==> Extraction des sources…
  -> Extraction de lokinet-0.9.9.tar.xz avec bsdtar
==> Les sources sont prĂŞtes.
==> Création du paquet lokinet-bin 0.9.9-1 (jeu. 10 nov. 2022 08:58:00)
==> Vérification des dépendances pour l’exécution…
==> Vérification des dépendances pour la compilation…
==> ATTENTION : Utilisation de l’arbre $srcdir/ existant
==> Entre dans l’environnement fakeroot…
==> Lancement de package()…
==> Nettoyage de l’installation…
  -> Suppression des fichiers libtool…
  -> Suppression des fichiers indésirables…
  -> Suppression des fichiers de bibliothèques statiques…
  -> Nettoyage des symboles inutiles dans les fichiers binaires et les bibliothèques…
  -> Compression des pages de man/info…
==> Recherche des erreurs d’empaquetage…
==> Création du paquet « lokinet-bin »…
  -> Génération du fichier .PKGINFO…
  -> Génération du fichier .BUILDINFO…
  -> Ajout du fichier install…
  -> Génération du fichier .MTREE…
  -> Compression du paquet…
==> Quitte l’environnement fakeroot.
==> Création terminée : lokinet-bin 0.9.9-1 (jeu. 10 nov. 2022 08:58:01)
==> Nettoyage…
chargement des paquets…
résolution des dépendances…
recherche des conflits entre paquets…

Paquets (1) lokinet-bin-0.9.9-1

Taille totale installée :  10,22 MiB

:: Procéder à l’installation ? [O/n] 
(1/1) vérification des clés dans le trousseau                                                                                  [-----------------------------------------------------------------------------] 100%
(1/1) vérification de l’intégrité des paquets                                                                                  [-----------------------------------------------------------------------------] 100%
(1/1) chargement des fichiers des paquets                                                                                      [-----------------------------------------------------------------------------] 100%
(1/1) analyse des conflits entre fichiers                                                                                      [-----------------------------------------------------------------------------] 100%
(1/1) vérification de l’espace disque disponible                                                                               [-----------------------------------------------------------------------------] 100%
:: Traitement des changements du paquet…
(1/1) installation de lokinet-bin                                                                                              [-----------------------------------------------------------------------------] 100%
avertissement : les permissions pour le répertoire /usr/share/polkit-1/rules.d/ sont différentes
système de fichiers : 750, paquet : 755
  To generate default config (optional, will be invoked by lokinet service if needed):
    systemctl start lokinet-default-config
  To adjust upstream DNS servers and other options, edit /var/lib/lokinet/lokinet.ini
  To start lokinet:
    systemctl start lokinet
  To get .loki domains resolve, enable systemd-resolved: https://wiki.archlinux.org/index.php/Systemd-resolved
  Alternatively, replace /etc/resolv.conf contents with:
    nameserver 127.3.2.1
:: Exécution des crochets (« hooks ») de post-transaction…
(1/4) Creating system user accounts...
(2/4) Reloading system manager configuration...
(3/4) Creating temporary files...
(4/4) Arming ConditionNeedsUpdate...
[sum@ordi1 ~]$ 
[sum@ordi1 ~]$ systemctl start lokinet-default-config
[sum@ordi1 ~]$ systemctl start lokinet
Job for lokinet.service failed because the control process exited with error code.
See "systemctl status lokinet.service" and "journalctl -xeu lokinet.service" for details.
[sum@ordi1 ~]$ systemctl status lokinet.service
â—Ź lokinet.service - LokiNET: Anonymous Network layer thingydoo
     Loaded: loaded (/usr/lib/systemd/system/lokinet.service; disabled; preset: disabled)
     Active: activating (auto-restart) (Result: exit-code) since Thu 2022-11-10 09:00:27 CET; 517ms ago
    Process: 15210 ExecStart=/usr/bin/lokinet lokinet.ini (code=exited, status=2)
   Main PID: 15210 (code=exited, status=2)
        CPU: 14ms
[sum@ordi1 ~]$ journalctl -xeu lokinet.service
â–‘â–‘ Support: https://forum.manjaro.org/c/support
â–‘â–‘ 
░░ L'unité (unit) lokinet.service a échoué, avec le résultat failed.
nov. 10 09:00:37 ordi1 systemd[1]: lokinet.service: Scheduled restart job, restart counter is at 16.
░░ Subject: Le redémarrage automatique d'une unité (unit) a été planifié
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: https://forum.manjaro.org/c/support
â–‘â–‘ 
░░ Le redémarrage automatique de l'unité (unit) lokinet.service a été planifié, en
░░ raison de sa configuration avec le paramètre Restart=.
nov. 10 09:00:37 ordi1 systemd[1]: Stopped LokiNET: Anonymous Network layer thingydoo.
░░ Subject: L'unité (unit) lokinet.service a terminé son arrêt
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: https://forum.manjaro.org/c/support
â–‘â–‘ 
░░ L'unité (unit) lokinet.service a terminé son arrêt.
nov. 10 09:00:37 ordi1 systemd[1]: Starting LokiNET: Anonymous Network layer thingydoo...
░░ Subject: L'unité (unit) lokinet.service a commencé à démarrer
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: https://forum.manjaro.org/c/support
â–‘â–‘ 
░░ L'unité (unit) lokinet.service a commencé à démarrer.
nov. 10 09:00:37 ordi1 lokinet[15242]: [NFO] [lokinet](830) 2022-11-10 08:00:37.589 GMT [+0.000s] /daemon/lokinet.cpp:238        Using config file: "lokinet.ini"
nov. 10 09:00:37 ordi1 lokinet[15242]: [NFO] [lokinet](830) 2022-11-10 08:00:37.589 GMT [+0.000s] /llarp/context.cpp:64        lokinet-0.9.9-release Gluten Free Edition
nov. 10 09:00:37 ordi1 lokinet[15242]: [NFO] [lokinet](830) 2022-11-10 08:00:37.589 GMT [+0.000s] /llarp/context.cpp:65        starting up
nov. 10 09:00:37 ordi1 lokinet[15242]: [NFO] [lokinet](830) 2022-11-10 08:00:37.590 GMT [+0.001s] /llarp/router/router.cpp:1196        Bound RPC server to tcp://127.0.0.1:1190
nov. 10 09:00:37 ordi1 lokinet[15242]: [NFO] [lokinet](830) 2022-11-10 08:00:37.590 GMT [+0.001s] /llarp/router/router.cpp:700        Loaded 3 bootstrap routers
nov. 10 09:00:37 ordi1 lokinet[15242]: [NFO] [lokinet](830) 2022-11-10 08:00:37.590 GMT [+0.001s] /llarp/router/router.cpp:772        router profiling enabled
nov. 10 09:00:37 ordi1 lokinet[15242]: [NFO] [lokinet](830) 2022-11-10 08:00:37.590 GMT [+0.001s] /llarp/router/router.cpp:775        no profiles file at "/var/lib/lokinet/profiles.dat" skipping
nov. 10 09:00:37 ordi1 lokinet[15242]: [NFO] [lokinet](830) 2022-11-10 08:00:37.590 GMT [+0.001s] /llarp/handlers/tun.cpp:168        endpoint:yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy.loki setting to>
nov. 10 09:00:37 ordi1 lokinet[15242]: [NFO] [lokinet](830) 2022-11-10 08:00:37.591 GMT [+0.002s] /llarp/handlers/tun.cpp:344        endpoint:yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy.loki skipping l>
nov. 10 09:00:37 ordi1 lokinet[15242]: [ERR] [](830) 2022-11-10 08:00:37.593 GMT [+0.004s] /llarp/ev/ev_libuv.cpp:323        failed to bind and start receiving on 127.3.2.1:53: address already in use
nov. 10 09:00:37 ordi1 lokinet[15242]: [ERR] [](830) 2022-11-10 08:00:37.593 GMT [+0.004s] /llarp/handlers/tun.cpp:989        endpoint:epxz9xypmuebh6drogur7yg8kuku9mmpto3ufcujuewdsxyza8py.loki failed to start D>
nov. 10 09:00:37 ordi1 lokinet[15242]: [ERR] [](830) 2022-11-10 08:00:37.593 GMT [+0.004s] /llarp/service/context.cpp:153        default failed to start
nov. 10 09:00:37 ordi1 lokinet[15242]: [ERR] [](830) 2022-11-10 08:00:37.593 GMT [+0.004s] /llarp/router/router.cpp:1308        Failed to start hidden service context
nov. 10 09:00:37 ordi1 systemd[1]: lokinet.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
â–‘â–‘ Subject: Unit process exited
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: https://forum.manjaro.org/c/support
â–‘â–‘ 
â–‘â–‘ An ExecStart= process belonging to unit lokinet.service has exited.
â–‘â–‘ 
â–‘â–‘ The process' exit code is 'exited' and its exit status is 2.
nov. 10 09:00:37 ordi1 systemd[1]: lokinet.service: Failed with result 'exit-code'.
â–‘â–‘ Subject: Unit failed
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: https://forum.manjaro.org/c/support
â–‘â–‘ 
â–‘â–‘ The unit lokinet.service has entered the 'failed' state with result 'exit-code'.
nov. 10 09:00:37 ordi1 systemd[1]: Failed to start LokiNET: Anonymous Network layer thingydoo.
░░ Subject: L'unité (unit) lokinet.service a échoué
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: https://forum.manjaro.org/c/support
â–‘â–‘ 
░░ L'unité (unit) lokinet.service a échoué, avec le résultat failed.
lines 817-871/871 (END)

I explore as a user the distributed solutions I2P - IPFS - Zeronet…

If I feel it’s not mature, at least I know and can follow.

The analysis you indicate is certainly frightening (as any obscure cryptomining projet) : I’ll on ly test on my VM’s :wink:

Thats how I came to GNU/Linux frow W$: I waited till about 2010 to find user friendly distros :slight_smile:

Read and explore errors then. They are written right here:

I’d start with first one - what is already listening there? Some other instance of lokinet or whatever…

Hi, thank you for caring.
As said : I explore as a user, not as a dev.
Now I also can check when properly directed.

Here, could we have NextDNS as suspect ?

~]$ sudo ss -tunlp
Netid   State    Recv-Q   Send-Q     Local Address:Port      Peer Address:Port  Process                                                                         
udp     UNCONN   0        0                0.0.0.0:53664          0.0.0.0:*      users:(("dat-fox-helper",pid=8783,fd=29))                                      
udp     UNCONN   0        0                0.0.0.0:5353           0.0.0.0:*      users:(("dat-fox-helper",pid=8783,fd=25))                                      
udp     UNCONN   0        0                0.0.0.0:5353           0.0.0.0:*      users:(("avahi-daemon",pid=631,fd=12))                                         
udp     UNCONN   0        0                0.0.0.0:55073          0.0.0.0:*      users:(("firefox",pid=8548,fd=172))                                            
udp     UNCONN   0        0                0.0.0.0:38713          0.0.0.0:*      users:(("firefox",pid=8548,fd=178))                                            
udp     UNCONN   0        0                0.0.0.0:33096          0.0.0.0:*      users:(("avahi-daemon",pid=631,fd=14))                                         
udp     UNCONN   0        0                0.0.0.0:59921          0.0.0.0:*      users:(("dat-fox-helper",pid=8783,fd=26))                                      
udp     UNCONN   0        0                0.0.0.0:51961          0.0.0.0:*      users:(("firefox",pid=8548,fd=118))                                            
udp     UNCONN   0        0                   [::]:5353              [::]:*      users:(("avahi-daemon",pid=631,fd=13))                                         
udp     UNCONN   0        0                      *:53                   *:*      users:(("nextdns",pid=694,fd=11))                                              
udp     UNCONN   0        0                      *:1716                 *:*      users:(("kdeconnectd",pid=1215,fd=13))                                         
udp     UNCONN   0        0                   [::]:34816             [::]:*      users:(("avahi-daemon",pid=631,fd=15))                                         
tcp     LISTEN   0        128            127.0.0.1:631            0.0.0.0:*      users:(("cupsd",pid=690,fd=9))                                                 
tcp     LISTEN   0        4096             0.0.0.0:80             0.0.0.0:*      users:(("docker-proxy",pid=1903,fd=4))                                         
tcp     LISTEN   0        128                [::1]:631               [::]:*      users:(("cupsd",pid=690,fd=8))                                                 
tcp     LISTEN   0        512                    *:9117                 *:*      users:(("jackett",pid=691,fd=205))                                             
tcp     LISTEN   0        4096                [::]:80                [::]:*      users:(("docker-proxy",pid=1909,fd=4))                                         
tcp     LISTEN   0        4096                   *:53                   *:*      users:(("nextdns",pid=694,fd=10))                                              
tcp     LISTEN   0        50                     *:1716                 *:*      users:(("kdeconnectd",pid=1215,fd=14))                                         
tcp     LISTEN   0        511                    *:3051                 *:*      users:(("dat-fox-helper",pid=8783,fd=27))                                      
tcp     LISTEN   0        511                    *:3282                 *:*      users:(("dat-fox-helper",pid=8783,fd=24)) 
1 Like

configuring programs you want to use is not the job of a developer. It is the job of the user or the admin that maintains your systems.

You can’t configure two programs to listens on the same port.

1 Like

Looks like it.

You’ll have to create lokinet conf and use some alternative port. :man_shrugging: (This is also mentioned in your logs: that there is no lokinet configuration detected)

@ this stage, i didn’t configure anything !
Just happens their conf uses this 53 port.
I’ll check how to amend one or the other :wink:

Your are responsible for software you installed.

Port 53 is a standardized port by IANA for the Domain Name System. There is probably a reason why port 53 is used.

1 Like

This is exactly what I mean as being a “user exploring” : to a user anything should be plug’n play.

I get the 53 stuff. I’ll test a new. conf and I’ll stock Lokinet in the “remind it exists” slot.