latest release install issue

Question

latest release install issue

Bystrykha opened this issue 2 years ago · 19 comments

Hello, Dino! I'm student from Kazakhstan, and I have been interested in this project for some time now. For file "how-to-install-linux.txt" latest commit says "Remove cherrypy from instructions and replace with cheroot.", but when I build the project (version 0.589) on ubuntu 20.04, I get the error "Install NOT complete for ['cherrypy']" and I don't understand why...
Grazie !

Answer 1 · 2023-01-20T19:37:02.000Z

Thanks for reporting this. I will fix it in the next release. If you want to get release announcement, I can add you to ***@***.*** Please let me know. Dino

…

On Jan 20, 2023, at 1:35 AM, Bystrykh Alexey ***@***.***> wrote: Hello, Dino! I'm student from Kazakhstan, and I have been interested in this project for some time now. For file "how-to-install-linux.txt" latest commit says "Remove cherrypy from instructions and replace with cheroot.", but when I build the project (version 0.589) on ubuntu 20.04, I get the error "Install NOT complete for ['cherrypy']" and I don't understand why... Grazie ! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.

Answer 2 · 2023-01-23T10:14:28.000Z

Hello, Dino! Thanks for the new release no more problems with cherrypy.
I don't tink that it is necessary add me to @.***, because I check the repository regularly.
I have some problems with MSMR: when I execute RESTART-LISP, and check result with pslisp, I see this:

root@AlexeyBs-VB:/home/alexeybs/gitClone/lispers.net/build/latest# ./pslisp
--- lispers.net release 0.590 installed (py2) ---
PID %CPU %MEM MEM Process
14419 0.0 0.4 1.2G -O ./lisp-core.pyo
14455 0.0 0.3 237M lisp-mr.pyo
14467 0.0 0.3 384M lisp-ms.pyo

and when I follow the "https://10.0.2.15:8080/lisp/login", I can login as a root without password.
But when I go to the "https://10.0.2.15:8080/lisp/show/site", I have: "Internal Server Error". Can You say, why it happens?

Answer 3 · 2023-01-23T20:27:44.000Z

Hello, Dino! Thanks for the new release no more problems with cherrypy.

Okey doke. Thanks for confirming the issue resolved. Appreciate it.

I don't tink that it is necessary add me to @.***, because I check the repository regularly. I have some problems with MSMR: when I execute RESTART-LISP, and check result with pslisp, I see this: ***@***.***:/home/alexeybs/gitClone/lispers.net/build/latest# ./pslisp --- lispers.net release 0.590 installed (py2) --- PID %CPU %MEM MEM Process 14419 0.0 0.4 1.2G -O ./lisp-core.pyo 14455 0.0 0.3 237M lisp-mr.pyo 14467 0.0 0.3 384M lisp-ms.pyo

The above output looks normal.

and when I follow the "https://10.0.2.15:8080/lisp/login", I can login as a root without password. But when I go to the "https://10.0.2.15:8080/lisp/show/site", I have: "Internal Server Error". Can You say, why it happens?

I'll need more info to help you. Send me your lisp.config file on 10.0.2.15 as well as the logs/*.log. Also check in the logs directory for a lisp-traceback.log in case something crashed. Dino

…

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.

Answer 4 · 2023-01-24T05:23:14.000Z

This is my config file:

lisp enable {
itr = no
etr = no
rtr = no
map-server = yes
map-resolver = yes
ddt-node = no
}
lisp debug {
etr = no
core = no
map-resolver = yes
ddt-node = no
rtr = no
map-server = yes
itr = no
}
lisp user-account {
username = root
super-user = yes
}
lisp site {
site-name = Site-1
authentication-key = some-key
allowed-prefix {
accept-more-specifics = yes
eid-prefix = 192.168.129.0/24
}
}

This is logs from lisp-ms.log

01/24/23 11:56:20.401: ms: lispers.net LISP Map-Server starting up 2023-01-24 11:56:20.401255, version 0.590, hostname ^[[1mAlexeyBs-VB^[[0m
01/24/23 11:56:20.401: ms: Local addresses are IPv4: ^[[1m^[[91m10.0.2.15^[[0m^[[0m, IPv6: ^[[1m^[[91mnone^[[0m^[[0m from device ^[[1menp0s3^[[0m, iid 0
01/24/23 11:56:21.286: ms: ^[[1mReceive^[[0m 36 bytes ^[[1mfrom lisp-core^[[0m no-port, command: 'lisp debug'
01/24/23 11:56:21.286: ms: ^[[1mEnable^[[0m process debug logging
01/24/23 11:56:21.286: ms: ^[[1mReceive^[[0m 230 bytes ^[[1mfrom lisp-core^[[0m no-port, command: 'lisp site'
01/24/23 11:56:21.287: ms: Send IPC 251-out-of-251 byte to lisp-core succeeded
01/24/23 11:56:21.291: ms: ^[[1mReceive^[[0m 36 bytes ^[[1mfrom lisp-core^[[0m no-port, command: 'lisp debug'
01/24/23 11:56:21.291: ms: ^[[1mEnable^[[0m process debug logging
01/24/23 11:56:21.291: ms: ^[[1mReceive^[[0m 162 bytes ^[[1mfrom lisp-core^[[0m no-port, command: 'lisp site'
01/24/23 11:56:21.291: ms: Send IPC 183-out-of-183 byte to lisp-core succeeded
01/24/23 11:56:48.671: ms: ^[[1mReceive^[[0m 9 bytes ^[[1mfrom lisp-core^[[0m no-port, command: 'show site'
01/24/23 11:56:48.671: ms: Send IPC 1500-out-of-2209 byte to lisp-core succeeded
01/24/23 11:56:48.671: ms: Send IPC 709-out-of-2209 byte to lisp-core succeeded

This is logs from lisp-mr.log

01/24/23 11:56:19.368: mr: lispers.net LISP Map-Resolver starting up 2023-01-24 11:56:19.367997, version 0.590, hostname ^[[1mAlexeyBs-VB^[[0m
01/24/23 11:56:19.368: mr: Local addresses are IPv4: ^[[1m^[[91m10.0.2.15^[[0m^[[0m, IPv6: ^[[1m^[[91mnone^[[0m^[[0m from device ^[[1menp0s3^[[0m, iid 0
01/24/23 11:56:21.286: mr: ^[[1mReceive^[[0m 38 bytes ^[[1mfrom lisp-core^[[0m no-port, command: 'lisp debug'
01/24/23 11:56:21.286: mr: ^[[1mEnable^[[0m process debug logging
01/24/23 11:56:21.291: mr: ^[[1mReceive^[[0m 38 bytes ^[[1mfrom lisp-core^[[0m no-port, command: 'lisp debug'
01/24/23 11:56:21.291: mr: ^[[1mEnable^[[0m process debug logging

This is logs from lisp-core.log

/home/alexeybs/gitClone/lispers.net/build/releases/release-0.590/poly1305.py:40: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in the next release.
01/24/23 11:56:19.237: core: lispers.net LISP core-process starting up 2023-01-24 11:56:19.237722, version 0.590, hostname ^[[1mAlexeyBs-VB^[[0m
01/24/23 11:56:19.240: core: Local addresses are IPv4: ^[[1m^[[91m10.0.2.15^[[0m^[[0m, IPv6: ^[[1m^[[91mnone^[[0m^[[0m from device ^[[1menp0s3^[[0m, iid 0
01/24/23 11:56:19.275: core: Listen on 0::0, port 4342
01/24/23 11:56:19.276: core: Listen on 0::0, port 4341
01/24/23 11:56:19.277: core: Processing configuration file ./lisp.config
Bottle v0.12.23 server starting up (using iiIiiII1II1ii(fast=True))...
Listening on http://0.0.0.0:8080/
Hit Ctrl-C to quit.

01/24/23 11:56:19.279: core: Process the 'lisp enable' command
01/24/23 11:56:19.280: core: Start process 'lisp-mr' on Вт 24 янв 2023 11:56:19 +07
Exception in thread Thread-7:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 754, in run
self.__target(*self.__args, **self.__kwargs)
File "/usr/local/lib/python2.7/dist-packages/cheroot/ssl/builtin.py", line 63, in _loopback_for_cert_thread
server, do_handshake_on_connect=True, server_side=True,
File "/usr/lib/python2.7/ssl.py", line 369, in wrap_socket
_context=self)
File "/usr/lib/python2.7/ssl.py", line 557, in init
socket.init(self, _sock=sock._sock)
AttributeError: '_socket.socket' object has no attribute '_sock'

/home/alexeybs/gitClone/lispers.net/build/releases/release-0.590/poly1305.py:40: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in the next release.
01/24/23 11:56:20.278: core: *** Process 'lisp-mr' has come up ***
01/24/23 11:56:20.283: core: Start process 'lisp-ms' on Вт 24 янв 2023 11:56:20 +07
/home/alexeybs/gitClone/lispers.net/build/releases/release-0.590/poly1305.py:40: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in the next release.
01/24/23 11:56:21.285: core: Process the 'lisp debug' command
01/24/23 11:56:21.286: core: Suppress sending IPC to lisp-etr
01/24/23 11:56:21.286: core: ^[[1mDisable^[[0m process debug logging
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/bottle.py", line 876, in _handle
return route.call(**args)
File "/usr/local/lib/python2.7/dist-packages/bottle.py", line 1756, in wrapper
rv = callback(*a, **ka)
File "lisp-core.py", line 1425, in O0o0oo0oOO0oO
File "lispconfig.py", line 1589, in lisp_process_show_command
File "lispconfig.py", line 196, in lisp_show_wrapper
UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 4310: ordinal not in range(128)

Answer 5 · 2023-01-24T21:58:02.000Z

A couple of comments: (1) Please show me output of *.log using "more -R" so its more readable. (2) Is the lisp.config have indents for the commands inside of the curly brackets? (3) You must use the exact format as in lisp.config.example. Meaning you need to have comment lines in there and more importantly the last line being #- - - -. Copy lisp.config.example and put your changes on top of it. Thanks, Dino

…

On Jan 23, 2023, at 9:23 PM, Bystrykh Alexey ***@***.***> wrote: This is my config file: lisp enable { itr = no etr = no rtr = no map-server = yes map-resolver = yes ddt-node = no } lisp debug { etr = no core = no map-resolver = yes ddt-node = no rtr = no map-server = yes itr = no } lisp user-account { username = root super-user = yes } lisp site { site-name = Site-1 authentication-key = some-key allowed-prefix { accept-more-specifics = yes eid-prefix = 192.168.129.0/24 } } This is logs from lisp-ms.log 01/24/23 11:56:20.401: ms: lispers.net LISP Map-Server starting up 2023-01-24 11:56:20.401255, version 0.590, hostname ^[[1mAlexeyBs-VB^[[0m 01/24/23 11:56:20.401: ms: Local addresses are IPv4: ^[[1m^[[91m10.0.2.15^[[0m^[[0m, IPv6: ^[[1m^[[91mnone^[[0m^[[0m from device ^[[1menp0s3^[[0m, iid 0 01/24/23 11:56:21.286: ms: ^[[1mReceive^[[0m 36 bytes ^[[1mfrom lisp-core^[[0m no-port, command: 'lisp debug' 01/24/23 11:56:21.286: ms: ^[[1mEnable^[[0m process debug logging 01/24/23 11:56:21.286: ms: ^[[1mReceive^[[0m 230 bytes ^[[1mfrom lisp-core^[[0m no-port, command: 'lisp site' 01/24/23 11:56:21.287: ms: Send IPC 251-out-of-251 byte to lisp-core succeeded 01/24/23 11:56:21.291: ms: ^[[1mReceive^[[0m 36 bytes ^[[1mfrom lisp-core^[[0m no-port, command: 'lisp debug' 01/24/23 11:56:21.291: ms: ^[[1mEnable^[[0m process debug logging 01/24/23 11:56:21.291: ms: ^[[1mReceive^[[0m 162 bytes ^[[1mfrom lisp-core^[[0m no-port, command: 'lisp site' 01/24/23 11:56:21.291: ms: Send IPC 183-out-of-183 byte to lisp-core succeeded 01/24/23 11:56:48.671: ms: ^[[1mReceive^[[0m 9 bytes ^[[1mfrom lisp-core^[[0m no-port, command: 'show site' 01/24/23 11:56:48.671: ms: Send IPC 1500-out-of-2209 byte to lisp-core succeeded 01/24/23 11:56:48.671: ms: Send IPC 709-out-of-2209 byte to lisp-core succeeded This is logs from lisp-mr.log 01/24/23 11:56:19.368: mr: lispers.net LISP Map-Resolver starting up 2023-01-24 11:56:19.367997, version 0.590, hostname ^[[1mAlexeyBs-VB^[[0m 01/24/23 11:56:19.368: mr: Local addresses are IPv4: ^[[1m^[[91m10.0.2.15^[[0m^[[0m, IPv6: ^[[1m^[[91mnone^[[0m^[[0m from device ^[[1menp0s3^[[0m, iid 0 01/24/23 11:56:21.286: mr: ^[[1mReceive^[[0m 38 bytes ^[[1mfrom lisp-core^[[0m no-port, command: 'lisp debug' 01/24/23 11:56:21.286: mr: ^[[1mEnable^[[0m process debug logging 01/24/23 11:56:21.291: mr: ^[[1mReceive^[[0m 38 bytes ^[[1mfrom lisp-core^[[0m no-port, command: 'lisp debug' 01/24/23 11:56:21.291: mr: ^[[1mEnable^[[0m process debug logging This is logs from lisp-core.log /home/alexeybs/gitClone/lispers.net/build/releases/release-0.590/poly1305.py:40: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in the next release. 01/24/23 11:56:19.237: core: lispers.net LISP core-process starting up 2023-01-24 11:56:19.237722, version 0.590, hostname ^[[1mAlexeyBs-VB^[[0m 01/24/23 11:56:19.240: core: Local addresses are IPv4: ^[[1m^[[91m10.0.2.15^[[0m^[[0m, IPv6: ^[[1m^[[91mnone^[[0m^[[0m from device ^[[1menp0s3^[[0m, iid 0 01/24/23 11:56:19.275: core: Listen on 0::0, port 4342 01/24/23 11:56:19.276: core: Listen on 0::0, port 4341 01/24/23 11:56:19.277: core: Processing configuration file ./lisp.config Bottle v0.12.23 server starting up (using iiIiiII1II1ii(fast=True))... Listening on http://0.0.0.0:8080/ Hit Ctrl-C to quit. 01/24/23 11:56:19.279: core: Process the 'lisp enable' command 01/24/23 11:56:19.280: core: Start process 'lisp-mr' on Вт 24 янв 2023 11:56:19 +07 Exception in thread Thread-7: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner self.run() File "/usr/lib/python2.7/threading.py", line 754, in run self.__target(*self.__args, **self.__kwargs) File "/usr/local/lib/python2.7/dist-packages/cheroot/ssl/builtin.py", line 63, in _loopback_for_cert_thread server, do_handshake_on_connect=True, server_side=True, File "/usr/lib/python2.7/ssl.py", line 369, in wrap_socket _context=self) File "/usr/lib/python2.7/ssl.py", line 557, in init socket.init(self, _sock=sock._sock) AttributeError: '_socket.socket' object has no attribute '_sock' /home/alexeybs/gitClone/lispers.net/build/releases/release-0.590/poly1305.py:40: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in the next release. 01/24/23 11:56:20.278: core: *** Process 'lisp-mr' has come up *** 01/24/23 11:56:20.283: core: Start process 'lisp-ms' on Вт 24 янв 2023 11:56:20 +07 /home/alexeybs/gitClone/lispers.net/build/releases/release-0.590/poly1305.py:40: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in the next release. 01/24/23 11:56:21.285: core: Process the 'lisp debug' command 01/24/23 11:56:21.286: core: Suppress sending IPC to lisp-etr 01/24/23 11:56:21.286: core: ^[[1mDisable^[[0m process debug logging Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/bottle.py", line 876, in _handle return route.call(**args) File "/usr/local/lib/python2.7/dist-packages/bottle.py", line 1756, in wrapper rv = callback(*a, **ka) File "lisp-core.py", line 1425, in O0o0oo0oOO0oO File "lispconfig.py", line 1589, in lisp_process_show_command File "lispconfig.py", line 196, in lisp_show_wrapper UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 4310: ordinal not in range(128) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.

Answer 6 · 2023-01-25T07:51:00.000Z

(1) I can't use flag -R (more: unknown parameter -R), but using "more" it seems:
lisp-core.log:

alexeybs@AlexeyBs-VB:~/gitClone/lispers.net/build/releases/release-0.590/logs$ more lisp-core.log
/home/alexeybs/gitClone/lispers.net/build/releases/release-0.590/poly1305.py:40: CryptographyDeprecat
ionWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated
in cryptography, and will be removed in the next release.
01/25/23 14:34:35.292: core: lispers.net LISP core-process starting up 2023-01-25 14:34:35.292611, ve
rsion 0.590, hostname AlexeyBs-VB
01/25/23 14:34:35.294: core: Local addresses are IPv4: 10.0.2.15, IPv6: none
from device enp0s3, iid 0
01/25/23 14:34:35.331: core: Listen on 0::0, port 4342
01/25/23 14:34:35.332: core: Listen on 0::0, port 4341
01/25/23 14:34:35.333: core: Processing configuration file ./lisp.config
Bottle v0.12.23 server starting up (using iiIiiII1II1ii(fast=True))...
Listening on http://0.0.0.0:8080/
Hit Ctrl-C to quit.

01/25/23 14:34:35.335: core: Process the 'lisp enable' command
01/25/23 14:34:35.336: core: Start process 'lisp-mr' on Ср 25 янв 2023 14:34:35 +07
Exception in thread Thread-7:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 754, in run
self.__target(*self.__args, **self.__kwargs)
File "/usr/local/lib/python2.7/dist-packages/cheroot/ssl/builtin.py", line 63, in _loopback_for_cer
t_thread
server, do_handshake_on_connect=True, server_side=True,
File "/usr/lib/python2.7/ssl.py", line 369, in wrap_socket
_context=self)
File "/usr/lib/python2.7/ssl.py", line 557, in init
socket.init(self, _sock=sock._sock)
AttributeError: '_socket.socket' object has no attribute '_sock'

/home/alexeybs/gitClone/lispers.net/build/releases/release-0.590/poly1305.py:40: CryptographyDeprecat
ionWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated
in cryptography, and will be removed in the next release.
01/25/23 14:34:36.334: core: *** Process 'lisp-mr' has come up ***
01/25/23 14:34:36.348: core: Start process 'lisp-ms' on Ср 25 янв 2023 14:34:36 +07
/home/alexeybs/gitClone/lispers.net/build/releases/release-0.590/poly1305.py:40: CryptographyDeprecat
ionWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated
in cryptography, and will be removed in the next release.
01/25/23 14:34:37.349: core: Process the 'lisp debug' command
01/25/23 14:34:37.349: core: Suppress sending IPC to lisp-etr
01/25/23 14:34:37.349: core: Enable process debug logging
01/25/23 14:34:37.349: core: Send IPC 60-out-of-60 byte to lisp-mr succeeded
01/25/23 14:34:37.349: core: Suppress sending IPC to lisp-ddt
01/25/23 14:34:37.349: core: Suppress sending IPC to lisp-rtr
01/25/23 14:34:37.349: core: Send IPC 58-out-of-58 byte to lisp-ms succeeded
01/25/23 14:34:37.349: core: Suppress sending IPC to lisp-itr
01/25/23 14:34:37.349: core: Process the 'lisp user-account' command
01/25/23 14:34:37.349: core: Process the 'lisp site' command
01/25/23 14:34:37.349: core: Send IPC 253-out-of-253 byte to lisp-ms succeeded
01/25/23 14:34:37.349: core: Waiting for response to config command 'lisp site'
01/25/23 14:34:37.350: core: Receive 230 bytes from lisp-ms no-port, command
01/25/23 14:34:37.352: core: Send command 'lisp debug' to restarting process 'lisp-mr'
01/25/23 14:34:37.352: core: Send IPC 60-out-of-60 byte to lisp-mr succeeded
01/25/23 14:34:37.352: core: *** Process 'lisp-ms' has come up ***
01/25/23 14:34:37.352: core: Send command 'lisp debug' to restarting process 'lisp-ms'
01/25/23 14:34:37.352: core: Send IPC 58-out-of-58 byte to lisp-ms succeeded
01/25/23 14:34:37.352: core: Send command 'lisp site' to restarting process 'lisp-ms'
01/25/23 14:34:37.352: core: Send IPC 185-out-of-185 byte to lisp-ms succeeded
01/25/23 14:34:37.352: core: Waiting for response to config command 'lisp site'
01/25/23 14:34:37.353: core: Receive 162 bytes from lisp-ms no-port, command
01/25/23 14:34:42.348: core: Send IPC 30-out-of-30 byte to lisp-ms succeeded
01/25/23 14:34:42.348: core: Waiting for response to show command 'show site'
01/25/23 14:34:42.349: core: Received 1478-out-of-2187 byte segment from lisp-ms
01/25/23 14:34:42.349: core: Received 709-out-of-2187 byte segment from lisp-ms
01/25/23 14:34:42.349: core: Receive 2187 bytes from lisp-ms no-port, command
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/bottle.py", line 876, in _handle
return route.call(**args)
File "/usr/local/lib/python2.7/dist-packages/bottle.py", line 1756, in wrapper
rv = callback(*a, **ka)
File "lisp-core.py", line 1425, in O0o0oo0oOO0oO
File "lispconfig.py", line 1589, in lisp_process_show_command
File "lispconfig.py", line 196, in lisp_show_wrapper
UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 4304: ordinal not in range(128)

lisp-ms.log:

alexeybs@AlexeyBs-VB:~/gitClone/lispers.net/build/releases/release-0.590/logs$ more lisp-ms.log
01/25/23 14:34:36.518: ms: lispers.net LISP Map-Server starting up 2023-01-25 14:34:36.518470, versio
n 0.590, hostname AlexeyBs-VB
01/25/23 14:34:36.519: ms: Local addresses are IPv4: 10.0.2.15, IPv6: none
from device enp0s3, iid 0
01/25/23 14:34:37.349: ms: Receive 36 bytes from lisp-core no-port, command: 'lisp debug'

01/25/23 14:34:37.349: ms: Enable process debug logging
01/25/23 14:34:37.349: ms: Receive 230 bytes from lisp-core no-port, command: 'lisp site'

01/25/23 14:34:37.350: ms: Send IPC 251-out-of-251 byte to lisp-core succeeded
01/25/23 14:34:37.352: ms: Receive 36 bytes from lisp-core no-port, command: 'lisp debug'

01/25/23 14:34:37.352: ms: Enable process debug logging
01/25/23 14:34:37.352: ms: Receive 162 bytes from lisp-core no-port, command: 'lisp site'

01/25/23 14:34:37.353: ms: Send IPC 183-out-of-183 byte to lisp-core succeeded
01/25/23 14:34:42.348: ms: Receive 9 bytes from lisp-core no-port, command: 'show site'
01/25/23 14:34:42.349: ms: Send IPC 1500-out-of-2209 byte to lisp-core succeeded
01/25/23 14:34:42.349: ms: Send IPC 709-out-of-2209 byte to lisp-core succeeded

lisp-mr.log

01/25/23 14:34:35.424: mr: lispers.net LISP Map-Resolver starting up 2023-01-25 14:34:35.424910, vers
ion 0.590, hostname AlexeyBs-VB
01/25/23 14:34:35.425: mr: Local addresses are IPv4: 10.0.2.15, IPv6: none
from device enp0s3, iid 0
01/25/23 14:34:37.349: mr: Receive 38 bytes from lisp-core no-port, command: 'lisp debug'

01/25/23 14:34:37.349: mr: Enable process debug logging
01/25/23 14:34:37.352: mr: Receive 38 bytes from lisp-core no-port, command: 'lisp debug'

01/25/23 14:34:37.352: mr: Enable process debug logging

(2) Yes
(3) log file:

Answer 7 · 2023-01-25T12:09:57.000Z

I also have a question about the code: I can't understand what is db. Is it storage of xTR or MSMR?
(scrin from lisp.py)

Answer 8 · 2023-01-25T22:11:45.000Z

So the ssl.py is a known problem but the API gets around the failure and the code still operates. I will have a look to see if the owners have fixed it.

This is going to be a problem. You need a value for an instance-ID. If you don't care about it, it will default to 0, if you don't supply the command. That is probably the reason for the crash.

On Jan 25, 2023, at 4:10 AM, Bystrykh Alexey ***@***.***> wrote: I also have a question about the code: I can't understand what is db. Is it storage of xTR or MSMR? (scrin from lisp.py)

A "db" throughout the code means it a lisp_mapping() class, created from a "lisp database-mapping" command clause. Dino

…

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.

Answer 9 · 2023-01-26T05:42:08.000Z

I fix the iid parameter, but it don't help...
config file:

Answer 10 · 2023-01-26T12:34:46.000Z

I have another question about the code:
at the moment I'm research the interaction of EID and xTR, I settled on function "lisp_process_punt" (line 19620 in lisp.py). As far as I understand, the package received from EID is processed in it and a decision is made on further actions with it. I can't understand the following piece of code:

on line 19711 it is checked if there is a record on the xTR for the source EID, then on line 19717 it is checked whether this EID is dynamic, and on line 19720 the "lisp_itr_discover_eid" function can be called, in which there is a comment "# Tell ETR process so it can register dynamic-EID.", on the basis of which, I assume that registration of a dynamic EID on ETR will follow.
The main question is: why is "lisp_itr_discover_eid" called exactly there and only after a few checks?

Answer 11 · 2023-01-26T21:35:45.000Z

Okay, good to rule out a bad configuration syntax. Your new lisp.config looks like it should be acceptable. Can you try this in one of my docker images. I need to know your environment to debug it more. But try your lisp.config in a docker container using the following docker image: https://www.dropbox.com/s/s0pu4r7lm595woy/lispers.net-0.592-ubuntu-docker-image Once you download it then use: sudo docker load -i lispers.net-0.592-ubuntu-docker-image And start the docker container like this: export HN=<you-fill-in> sudo docker run -p 8080 --privileged --name $HN -h $HN -v /:/hostOS -ti lispers.net/ubuntu Thanks, Dino

…

On Jan 25, 2023, at 9:42 PM, Bystrykh Alexey ***@***.***> wrote: I fix the iid parametr, but it don't help... config file: — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.

Answer 12 · 2023-01-26T21:50:05.000Z

I have another question about the code:

lisp_process_punt() is used by a data-plane to punt packets to the control-plane because the data-plane did not find a map-cache entry for the packet's destination.

at the moment I'm research the interaction of EID and xTR, I settled on function "lisp_process_punt" (line 19620 in lisp.py). As far as I understand, the package received from EID is processed in it and a decision is made on further actions with it. I can't understand the following piece of code:

That code is doing dynamic EID discovery. So if the ITR sees a packet for an EID in a "lisp database-mapping" command with a a dynamic-eid=yes configured, it will cache the discovery an start registering the EID to the mapping system with its own RLOC. Look at docs/lisp-config-commands.txt for descriptions on the functionality configuration commands give you.

on line 19711 it is checked if there is a record on the xTR for the source EID, then on line 19717 it is checked whether this EID is dynamic, and on line 19720 the "lisp_itr_discover_eid" function can be called, in which there is a comment "# Tell ETR process so it can register dynamic-EID.", on the basis of which, I assume that registration of a dynamic EID on ETR will follow. The main question is: why is "lisp_itr_discover_eid" called exactly there and only after a few checks?

Right, because if an ITR gets a packet for an EID-prefix it is not registering, it will not process the packet. When dynamic-EID=yes is configured, the EID-prefix is ONLY registered when a more specific EID is discovered. Dino

Answer 13 · 2023-01-27T08:03:37.000Z

I tried running LISPERS using the current config file in docker container, everything went successfully
core log:

MR log:

MS log:

Does this mean that the problem is in the my operating system (ubuntu 20.04)?

Answer 14 · 2023-01-27T19:38:58.000Z

In the lispers.net directory on your system, try this: python2 lipsers.net-test-install.pyo And see if all the lispers.net libraries dependencies have been installed. Yes, its something with your OS. Dino

…

On Jan 27, 2023, at 12:03 AM, Bystrykh Alexey ***@***.***> wrote: I tried running LISPERS using the current config file in docker container, everything went successfully core log: MR log: MS log: Does this mean that the problem is in the my operating system (ubuntu 20.04)? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.

Answer 15 · 2023-01-30T07:15:10.000Z

The output of "python2 lipsers.net-test-install.pyo" seems correct:

I don't know, how I can see dependencies...

Another question about code: values of feeld "type", like "statistics", "discovery" and others, aren't familiar to me. At first I thought these were LISP protocol fields, but I only found 4 valid values there: "Map-Request", "Map-Notify", "Map-Register", "Map-Reply".

Answer 16 · 2023-01-30T07:33:18.000Z

Maybe it's worth changing the operating system, for example, arch, fedora, or one of the previous versions of ubuntu?

Answer 17 · 2023-01-30T20:08:17.000Z

Another question about code: values of feeld "type", like "statistics", "discovery" and others, aren't familiar to me. At first I thought these were LISP protocol fields, but I only found 4 valid values there: "Map-Request", "Map-Notify", "Map-Register", "Map-Reply".

This is the data-plane API to get information to the lispers.net control-plane. See https://github.com/farinacci/lispers.net/blob/master/docs/lisp-ipc-data-plane.txt for details. Dino

Answer 18 · 2023-01-31T11:28:39.000Z

I tried to run the project on Ubuntu 18.04 and Debian 11.5.0, the result is the same as on ubuntu 20.04... apparently, in the future I will work with containers.
Thanks for the help with the installation and the hints related to the code)

Answer 19 · 2023-01-31T18:05:41.000Z

Turn on core=yes under “lisp debug” and send me the lisp-core.log Kang with the other log files. Maybe I can figure it out. If you want to debug it further, I can provide a debug image with more logging so we can find root cause. DinoOn Jan 31, 2023, at 3:28 AM, Bystrykh Alexey ***@***.***> wrote: I tried to run the project on Ubuntu 18.04 and Debian 11.5.0, the result is the same as on ubuntu 20.04... apparently, in the future I will work with containers. Thanks for the help with the installation and the hints related to the code) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>