333.i2p

Такие дела.

Лог установки из штатной репы Bullsee:

# apt install i2pd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
libboost-filesystem1.74.0 libboost-program-options1.74.0 libminiupnpc17
Suggested packages:
minissdpd
The following NEW packages will be installed:
i2pd libboost-filesystem1.74.0 libboost-program-options1.74.0 libminiupnpc17
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,899 kB of archives.
After this operation, 9,547 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian bullseye/main amd64 libboost-filesystem1.74.0 amd64 1.74.0-9 [283 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 libboost-program-options1.74.0 amd64 1.74.0-9 [356 kB]
Get:3 http://deb.debian.org/debian bullseye/main amd64 libminiupnpc17 amd64 2.2.1-1 [34.7 kB]
Get:4 http://deb.debian.org/debian bullseye/main amd64 i2pd amd64 2.36.0-1 [1,226 kB]
Fetched 1,899 kB in 0s (7,997 kB/s)
Selecting previously unselected package libboost-filesystem1.74.0:amd64.
(Reading database ... 33269 files and directories currently installed.)
Preparing to unpack .../libboost-filesystem1.74.0_1.74.0-9_amd64.deb ...
Unpacking libboost-filesystem1.74.0:amd64 (1.74.0-9) ...
Selecting previously unselected package libboost-program-options1.74.0:amd64.
Preparing to unpack .../libboost-program-options1.74.0_1.74.0-9_amd64.deb ...
Unpacking libboost-program-options1.74.0:amd64 (1.74.0-9) ...
Selecting previously unselected package libminiupnpc17:amd64.
Preparing to unpack .../libminiupnpc17_2.2.1-1_amd64.deb ...
Unpacking libminiupnpc17:amd64 (2.2.1-1) ...
Selecting previously unselected package i2pd.
Preparing to unpack .../i2pd_2.36.0-1_amd64.deb ...
Unpacking i2pd (2.36.0-1) ...
Setting up libboost-program-options1.74.0:amd64 (1.74.0-9) ...
Setting up libboost-filesystem1.74.0:amd64 (1.74.0-9) ...
Setting up libminiupnpc17:amd64 (2.2.1-1) ...
Setting up i2pd (2.36.0-1) ...
adduser: Warning: The home directory `/var/lib/i2pd' does not belong to the user you are currently creating.
invoke-rc.d: policy-rc.d denied execution of start.
Created symlink /etc/systemd/system/multi-user.target.wants/i2pd.service → /lib/systemd/system/i2pd.service.
/usr/sbin/policy-rc.d returned 101, not running 'start i2pd.service'
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+deb11u4) ...

И сразу:
adduser: Warning: The home directory `/var/lib/i2pd' does not belong to the user you are currently creating.
invoke-rc.d: policy-rc.d denied execution of start.
/usr/sbin/policy-rc.d returned 101, not running 'start i2pd.service'

Вывод статуса после старта программы из репы:

~# systemctl status i2pd
● i2pd.service - I2P Router written in C++
Loaded: loaded (/lib/systemd/system/i2pd.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Sun 2022-10-09 18:03:15 MSK; 27min ago
Docs: man:i2pd(1)
https://i2pd.readthedocs.io/en/latest/
Process: 360476 ExecStart=/usr/sbin/i2pd $DAEMON_OPTS (code=exited, status=0/SUCCESS)
Main PID: 360477 (code=killed, signal=SEGV)
CPU: 22ms

Oct 09 18:01:03 systemd[1]: Starting I2P Router written in C++...
Oct 09 18:01:03 systemd[1]: i2pd.service: Can't open PID file /run/i2pd/i2pd.pid (yet?) after start: Operation not permitted
systemd[1]: Started I2P Router written in C++.
Oct 09 18:03:15 systemd[1]: i2pd.service: Main process exited, code=killed, status=11/SEGV
Oct 09 18:03:15 systemd[1]: i2pd.service: Failed with result 'signal'.

После неудачи с пакетом из репы, качнул i2pd_2.43.0-1bullseye1_amd64.deb из latest-releases на Гитхабе, лог установки:

# apt install /root/i2pd_2.43.0-1bullseye1_amd64.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'i2pd' instead of '/root/i2pd_2.43.0-1bullseye1_amd64.deb'
The following additional packages will be installed:
libboost-filesystem1.74.0 libboost-program-options1.74.0 libminiupnpc17
Suggested packages:
minissdpd
The following NEW packages will be installed:
i2pd libboost-filesystem1.74.0 libboost-program-options1.74.0 libminiupnpc17
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 673 kB/1,841 kB of archives.
After this operation, 9,005 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 /root/i2pd_2.43.0-1bullseye1_amd64.deb i2pd amd64 2.43.0-1bullseye1 [1,167 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 libboost-filesystem1.74.0 amd64 1.74.0-9 [283 kB]
Get:3 http://deb.debian.org/debian bullseye/main amd64 libboost-program-options1.74.0 amd64 1.74.0-9 [356 kB]
Get:4 http://deb.debian.org/debian bullseye/main amd64 libminiupnpc17 amd64 2.2.1-1 [34.7 kB]
Fetched 673 kB in 0s (3,351 kB/s)
Selecting previously unselected package libboost-filesystem1.74.0:amd64.
(Reading database ... 41193 files and directories currently installed.)
Preparing to unpack .../libboost-filesystem1.74.0_1.74.0-9_amd64.deb ...
Unpacking libboost-filesystem1.74.0:amd64 (1.74.0-9) ...
Selecting previously unselected package libboost-program-options1.74.0:amd64.
Preparing to unpack .../libboost-program-options1.74.0_1.74.0-9_amd64.deb ...
Unpacking libboost-program-options1.74.0:amd64 (1.74.0-9) ...
Selecting previously unselected package libminiupnpc17:amd64.
Preparing to unpack .../libminiupnpc17_2.2.1-1_amd64.deb ...
Unpacking libminiupnpc17:amd64 (2.2.1-1) ...
Selecting previously unselected package i2pd.
Preparing to unpack .../i2pd_2.43.0-1bullseye1_amd64.deb ...
Unpacking i2pd (2.43.0-1bullseye1) ...
dpkg: warning: unable to delete old directory '/etc/i2pd/tunnels.d': Directory not empty
Setting up libboost-program-options1.74.0:amd64 (1.74.0-9) ...
Setting up libboost-filesystem1.74.0:amd64 (1.74.0-9) ...
Setting up libminiupnpc17:amd64 (2.2.1-1) ...
Setting up i2pd (2.43.0-1bullseye1) ...
Installing new version of config file /etc/default/i2pd ...
Installing new version of config file /etc/i2pd/i2pd.conf ...
Installing new version of config file /etc/i2pd/tunnels.conf ...
Installing new version of config file /etc/init.d/i2pd ...
invoke-rc.d: policy-rc.d denied execution of restart.
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+deb11u4) ...
N: Download is performed unsandboxed as root as file '/root/i2pd_2.43.0-1bullseye1_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

Показало "Unit i2pd.service is masked.". Решил снова удалить и сделать третью попытку затянув версию из репы r4sas или как там его:

~# systemctl start i2pd
Failed to start i2pd.service: Unit i2pd.service is masked.
~# apt remove libboost-filesystem1.74.0 libboost-program-options1.74.0 libminiupnpc17 i2pd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
i2pd libboost-filesystem1.74.0 libboost-program-options1.74.0 libminiupnpc17
0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
After this operation, 9,005 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 41249 files and directories currently installed.)
Removing i2pd (2.43.0-1bullseye1) ...
invoke-rc.d: policy-rc.d denied execution of stop.
Removing libboost-filesystem1.74.0:amd64 (1.74.0-9) ...
Removing libboost-program-options1.74.0:amd64 (1.74.0-9) ...
Removing libminiupnpc17:amd64 (2.2.1-1) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+deb11u4) ...
~# apt-get install apt-transport-https
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
apt-transport-https is already the newest version (2.2.4).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
~# wget -q -O - https://repo.i2pd.xyz/.help/add_repo | bash -s -
Importing signing key
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
OK
Adding APT repository
~# apt update
Get:1 http://security.debian.org/debian-security bullseye-security InRelease [48.4 kB]
Hit:2 http://deb.debian.org/debian bullseye InRelease
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Hit:4 http://neilalexander.s3.dualstack.eu-west-2.ama... debian InRelease
Get:5 https://repo.i2pd.xyz/debian bullseye InRelease [25.3 kB]
Get:6 https://repo.i2pd.xyz/debian bullseye/main Sources [3,489 B]
Get:7 https://repo.i2pd.xyz/debian bullseye/main amd64 Packages [4,297 B]
Fetched 126 kB in 1s (205 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
~# apt install i2pd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
libboost-filesystem1.74.0 libboost-program-options1.74.0 libminiupnpc17
Suggested packages:
minissdpd
The following NEW packages will be installed:
i2pd libboost-filesystem1.74.0 libboost-program-options1.74.0 libminiupnpc17
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,841 kB of archives.
After this operation, 9,005 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian bullseye/main amd64 libboost-filesystem1.74.0 amd64 1.74.0-9 [283 kB]
Get:2 http://deb.debian.org/debian bullseye/main amd64 libboost-program-options1.74.0 amd64 1.74.0-9 [356 kB]
Get:3 http://deb.debian.org/debian bullseye/main amd64 libminiupnpc17 amd64 2.2.1-1 [34.7 kB]
Get:4 https://repo.i2pd.xyz/debian bullseye/main amd64 i2pd amd64 2.43.0-1bullseye1 [1,167 kB]
Fetched 1,841 kB in 0s (4,522 kB/s)
Selecting previously unselected package libboost-filesystem1.74.0:amd64.
(Reading database ... 41194 files and directories currently installed.)
Preparing to unpack .../libboost-filesystem1.74.0_1.74.0-9_amd64.deb ...
Unpacking libboost-filesystem1.74.0:amd64 (1.74.0-9) ...
Selecting previously unselected package libboost-program-options1.74.0:amd64.
Preparing to unpack .../libboost-program-options1.74.0_1.74.0-9_amd64.deb ...
Unpacking libboost-program-options1.74.0:amd64 (1.74.0-9) ...
Selecting previously unselected package libminiupnpc17:amd64.
Preparing to unpack .../libminiupnpc17_2.2.1-1_amd64.deb ...
Unpacking libminiupnpc17:amd64 (2.2.1-1) ...
Selecting previously unselected package i2pd.
Preparing to unpack .../i2pd_2.43.0-1bullseye1_amd64.deb ...
Unpacking i2pd (2.43.0-1bullseye1) ...
Setting up libboost-program-options1.74.0:amd64 (1.74.0-9) ...
Setting up libboost-filesystem1.74.0:amd64 (1.74.0-9) ...
Setting up libminiupnpc17:amd64 (2.2.1-1) ...
Setting up i2pd (2.43.0-1bullseye1) ...
invoke-rc.d: policy-rc.d denied execution of restart.
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+deb11u4) ...
~# systemctl start i2pd
Failed to start i2pd.service: Unit i2pd.service is masked.
~#

Всего сделано 3 попытки установить программу 3 разными способами на самом популярном серверном дистре. Ни одной удачной.

Или не в программе дело, а в настройках моей ВПСки? Обычный европейский KVM-хостинг.

Собери сам да запусти.

orignal wrote:

Собери сам да запусти.

Чтобы была понятна ситуация - в моём случае это значит "перечитай кучу манов и сделай кучу телодвижений на работающем сервере с неочевидным итогом". Как два пальца об асфальт, хуле.

А починить хотя бы один пакет (например гитхабовский в крайних версиях, хер с ними с дебиановскими репами) никак не получится? Ведь всё равно рано или поздно это надо будет сделать. Тогда и я сделаю 4 подход к снаряду.

Оригинал, если это пригодится: роутер i2pd комплекта I2PdBrowser https://github.com/PurpleI2P/i2pdbrowser/releas... работает нормально (пишу сейчас это с него), может имеет смысл просто перетащить то что работает из комплекта в основную ветку на Гитхаб и обозвать это версией 2.36.1 например.

Ниже 2.41 будет все время падать

В попытках установки и запуска № 2 (latest-releases из Гитхаба) и № 3 (репа r4sas) устанавливалась версия 2.43, итог обоих попыток
~# systemctl start i2pd
Failed to start i2pd.service: Unit i2pd.service is masked.
~#

Сегодня ещё поискал в сети что делать когда
Failed to start *.service: Unit *.service is masked.
и решил проблему.

Оказалось надо просто размаскировать демон:
# systemctl unmask i2pd.service
Removed /etc/systemd/system/i2pd.service.
~# systemctl start i2pd
~# systemctl status i2pd
● i2pd.service - I2P Router written in C++
Loaded: loaded (/lib/systemd/system/i2pd.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-10-13 15:39:13 MSK; 17s ago
Docs: man:i2pd(1)
https://i2pd.readthedocs.io/en/latest/
Process: 36537 ExecStart=/usr/sbin/i2pd --conf=/etc/i2pd/i2pd.conf --tunconf=/etc/i2pd/tunnels.conf --tunnelsdir=/etc/i2pd/tunnels.conf.>
Main PID: 36538 (i2pd)
Tasks: 14 (limit: 9509)
Memory: 7.1M
CPU: 89ms
CGroup: /system.slice/i2pd.service
└─36538 /usr/sbin/i2pd --conf=/etc/i2pd/i2pd.conf --tunconf=/etc/i2pd/tunnels.conf --tunnelsdir=/etc/i2pd/tunnels.conf.d --pidf>

Oct 13 15:39:13 systemd[1]: Starting I2P Router written in C++...
Oct 13 15:39:13 systemd[1]: i2pd.service: Can't open PID file /run/i2pd/i2pd.pid (yet?) after start: Operation>
Oct 13 15:39:13 systemd[1]: Started I2P Router written in C++.

~#

Надо после размаскировки заново стартануть, и усё работает. Оригинал, прошу прощения за беспокойство. И хорошо бы где-нибудь типа i2pd-вики записать что при установке на Дебиан 11 возможно возникновение такой проблемы, и как её решить, чтобы нубы типа меня не падали духом.

И тем не менее:
i2pd.service: Can't open PID file /run/i2pd/i2pd.pid (yet?) after start: Operation>
Это ничего что не открывается этот PID file? На работоспособность i2pd это как-то влияет?

Состояние masked - устанавливается в результате каких-то проблем при запуске...

Я на что-то подобное наступал, но потом разными disable|enable это дело исправлял.

anton wrote:

i2pd.service: Can't open PID file /run/i2pd/i2pd.pid (yet?) after start:

~$ ls -la /run/i2pd/i2pd.pid
-rw------- 1 i2pd i2pd 8 Sep 20 12:51 /run/i2pd/i2pd.pid

~$ cat /etc/issue.net
Debian GNU/Linux 11

anton wrote:

Это ничего что не открывается этот PID file? На работоспособность i2pd это как-то влияет?