You are not logged in.

#226 2019-02-24 15:42:59

eduardo.eae
Member
From: Reconquista - Argentina
Registered: 2010-01-24
Posts: 66

Re: pacserve - easily share Pacman packages between computers

I followed the wiki, opened ports manually (others servers are being added correctly), added the "Include" line to each Repo of my pacman.conf, but pacman seems to enter an ethernal loop. Looking at the logs I get this:

redirecting to http://localhost:15678/pacman/core/x86_64/core.db
tell the Pacman devs to url-decode their redirects
"GET /pacman/core/x86_64/core.db HTTP/1.1" 303 -

Repeated forever

* Fixed. Turns out I had no "127.0.0.1 localhost" in my /etc/hosts file, oops.

Last edited by eduardo.eae (2019-02-27 00:59:34)

Offline

#227 2019-02-27 20:41:15

Xyne
Moderator/TU
Registered: 2008-08-03
Posts: 6,412
Website

Re: pacserve - easily share Pacman packages between computers

@connection_reset
Thanks for reporting the error and posting patches and links. I've integrated both in today's release of python3-threaded_servers.

I was about to write "welcome to the forum" after seeing your post count, but then I saw the registration date and wondered if I should apologize for breaking your silence with my bug. Reminds me of this scene tongue

@eduardo.eae
Glad you got it working smile


My Arch Linux StuffForum EtiquetteCommunity Ethos - Arch is not for everyone

Offline

#228 2019-03-02 15:20:50

eduardo.eae
Member
From: Reconquista - Argentina
Registered: 2010-01-24
Posts: 66

Re: pacserve - easily share Pacman packages between computers

Now I have another problem in another network:

WARNING: unrecognized multicast message from 192.168.1.100

I see this message in both PCs in this network.
Maybe my router is doing something funny with multicast?
Multicast was set to disabled in the router. I set it to IGMP v3 and it didn't change anything.

Offline

#229 2019-03-03 03:56:40

Xyne
Moderator/TU
Registered: 2008-08-03
Posts: 6,412
Website

Re: pacserve - easily share Pacman packages between computers

Did the warnings appear after Wednesday's upgrade? Do the the servers detect each other?
If you provide some details about your network setup, it will help me to try to reproduce the warning and fix it.


My Arch Linux StuffForum EtiquetteCommunity Ethos - Arch is not for everyone

Offline

#230 2019-03-04 22:49:11

eduardo.eae
Member
From: Reconquista - Argentina
Registered: 2010-01-24
Posts: 66

Re: pacserve - easily share Pacman packages between computers

Now it is working as intended, and I have changed nothing neutral

Offline

#231 2019-03-06 21:32:41

Xyne
Moderator/TU
Registered: 2008-08-03
Posts: 6,412
Website

Re: pacserve - easily share Pacman packages between computers

eduardo.eae wrote:

Now it is working as intended, and I have changed nothing neutral

Strange. If it happens again, post the setup and full console output.


My Arch Linux StuffForum EtiquetteCommunity Ethos - Arch is not for everyone

Offline

#232 2019-03-17 10:00:19

connection_reset
Member
Registered: 2017-04-25
Posts: 2

Re: pacserve - easily share Pacman packages between computers

eduardo.eae wrote:
WARNING: unrecognized multicast message from 192.168.1.100

This happened to me too just now.
I updated one installation (out of multiple) from python3-threaded_servers version 2019.2.3 (with my patches) to Xyne's latest 2019.2.27 and got that warning and no peers.
The multicast message contains an identifier with the version and is discarded (with that warning) if it doesn't match, so apparently different versions don't work together.

Offline

#233 2019-06-06 04:49:08

alex.forencich
Member
Registered: 2011-05-29
Posts: 91

Re: pacserve - easily share Pacman packages between computers

Xyne wrote:

@alex.forencich
The underlying HTTP server is the one provided by the Python standard library and it is limited to listening to either all or a single interface at a time (unless that's changed since I last checked). If you bind it to a non-local interface, update /etc/pacman.d/pacserve, /etc/powerpill/powerpill.json or whatever else uses pacserve to point to the bound interface instead of localhost.

The configuration files are located in /etc/pacserve. I have updated the project page.

How do I do that when the interface address comes from DHCP?

Edit: I also tried playing around with some of the command line parameters.  Adding ---multicast-interface eno1 seems to do nothing.  Adding --multicast-server-address eno1 causes pacserve to fail with:

pacserve[11855]: Traceback (most recent call last):
pacserve[11855]:   File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
pacserve[11855]:     "__main__", mod_spec)
pacserve[11855]:   File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
pacserve[11855]:     exec(code, run_globals)
pacserve[11855]:   File "/usr/lib/python3.7/site-packages/ThreadedServers/Pacserve.py", line 325, in <module>
pacserve[11855]:     run(main)
pacserve[11855]:   File "/usr/lib/python3.7/site-packages/ThreadedServers/common.py", line 413, in run
pacserve[11855]:     main()
pacserve[11855]:   File "/usr/lib/python3.7/site-packages/ThreadedServers/Pacserve.py", line 314, in main
pacserve[11855]:     page_generators,
pacserve[11855]:   File "/usr/lib/python3.7/site-packages/ThreadedServers/Pacserve.py", line 108, in __init__
pacserve[11855]:     super().__init__(*args, **kwargs)
pacserve[11855]:   File "/usr/lib/python3.7/site-packages/ThreadedServers/PeeredQuickserve.py", line 207, in __init__
pacserve[11855]:     self.start_multicast_threads()
pacserve[11855]:   File "/usr/lib/python3.7/site-packages/ThreadedServers/Multicast.py", line 324, in start_multicast_threads
pacserve[11855]:     self.options.multicast_group
pacserve[11855]:   File "/usr/lib/python3.7/site-packages/ThreadedServers/Multicast.py", line 214, in __init__
pacserve[11855]:     super().__init__(*args, **kwargs)
pacserve[11855]:   File "/usr/lib/python3.7/site-packages/ThreadedServers/Multicast.py", line 176, in __init__
pacserve[11855]:     socketserver.UDPServer.__init__(self, server_address, handler, *args, **kwargs)
pacserve[11855]:   File "/usr/lib/python3.7/socketserver.py", line 452, in __init__
pacserve[11855]:     self.server_bind()
pacserve[11855]:   File "/usr/lib/python3.7/site-packages/ThreadedServers/Multicast.py", line 195, in server_bind
pacserve[11855]:     self.socket.bind(self.server_address)
pacserve[11855]: TypeError: str, bytes or bytearray expected, not IPv4Address

Last edited by alex.forencich (2019-06-06 04:53:19)

Offline

#234 Yesterday 03:06:12

Xyne
Moderator/TU
Registered: 2008-08-03
Posts: 6,412
Website

Re: pacserve - easily share Pacman packages between computers

Passing the interface name is the right way to handle dhcp. The bug in --multicast-server-address should be fixed with today's release.

The --multicast-interface selects the interface to which multicast announcements are sent, not received.


My Arch Linux StuffForum EtiquetteCommunity Ethos - Arch is not for everyone

Offline

Board footer

Powered by FluxBB