DuckCorp Projects: Issueshttps://projects.duckcorp.org/https://projects.duckcorp.org/favicon.ico?16699090422024-02-04T14:36:07ZDuckCorp Projects
Redmine Bip - Enhancement #807 (New): Add IRCv3 capabilitieshttps://projects.duckcorp.org/issues/8072024-02-04T14:36:07ZLoïc Gomez
<p><a class="external" href="https://ircv3.net/specs/extensions/capability-negotiation.html">https://ircv3.net/specs/extensions/capability-negotiation.html</a></p> DuckCorp Infrastructure - Bug #788 (New): needrestart should not restart ppp serviceshttps://projects.duckcorp.org/issues/7882024-01-08T12:29:54ZMarc Dequènesduck@duckcorp.org
<p>It causes the Internet connection to restart but that is not needed. Affects Elwing.</p> DuckCorp Infrastructure - Enhancement #786 (New): Check services still missing systemd confighttps://projects.duckcorp.org/issues/7862023-07-09T14:14:10ZMarc Dequènesduck@duckcorp.org
<p>This is not cosmetic, this usually causes bugs, like bad tracking fo the service state, no support for the READY notification etc.</p>
<p>We might also be able to remove some workarounds in Ansible.</p> DuckCorp Infrastructure - Enhancement #785 (New): Upgrade and cleanup custom logcheck filtershttps://projects.duckcorp.org/issues/7852023-07-09T14:11:45ZMarc Dequènesduck@duckcorp.org
<p>rsyslog now defaults to “high precision timestamps” and we need to update regexs in our custom filters. Many must be obsolete so let's reintroduce them wehn needed.</p>
<p>Currently the old filters are still installed but let's move them aside and readd rules with updated regex when needed.</p> DuckCorp Infrastructure - Enhancement #784 (New): Do we still need rsyslog?https://projects.duckcorp.org/issues/7842023-07-09T14:08:59ZMarc Dequènesduck@duckcorp.org
<p>Debian is moving towards systemd journals and removing rsyslogd is now possible. I don't think we need special features besides what journald provides so let's check if we can simplify things.</p>
<p>logcheck now supports using systemd but I think not all logs are read from there and I suspect some other services are not ready yet.</p> DuckCorp Infrastructure - Enhancement #773 (New): Investigate Kea usagehttps://projects.duckcorp.org/issues/7732022-06-26T11:59:48ZPierre-Louis Bonicolipierre-louis.bonicoli@ir5.eu
<p>ISC doesn't recommend <a href="https://www.isc.org/dhcp/" class="external">ISC DHCP</a> (for new project):</p>
<blockquote>
<p>We recommend that new implementers use Kea and implement ISC DHCP only if Kea does not meet their needs. The Kea distribution does not currently include either a client or a relay.</p>
</blockquote>
<p>The next Debian release provides a <a href="https://packages.debian.org/bookworm/kea" class="external">Kea package</a>.</p> DuckCorp Infrastructure - Bug #767 (New): mailman3-web internal errorhttps://projects.duckcorp.org/issues/7672022-03-27T19:49:44ZPierre-Louis Bonicolipierre-louis.bonicoli@ir5.eu
<p>I just tried to use mailmain3-web to remove my old email address from the the dc-admins list. I encountered an HTTP 500 (twice).<br /><pre>
ERROR 2022-03-27 21:43:42,082 1507813 postorius Mailman REST API not available
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 445, in _make_request
six.raise_from(e, None)
File "<string>", line 3, in raise_from
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 440, in _make_request
httplib_response = conn.getresponse()
File "/usr/lib/python3.9/http/client.py", line 1347, in getresponse
response.begin()
File "/usr/lib/python3.9/http/client.py", line 307, in begin
version, status, reason = self._read_status()
File "/usr/lib/python3.9/http/client.py", line 276, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755, in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 532, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/usr/lib/python3/dist-packages/six.py", line 718, in reraise
raise value.with_traceback(tb)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 445, in _make_request
six.raise_from(e, None)
File "<string>", line 3, in raise_from
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 440, in _make_request
httplib_response = conn.getresponse()
File "/usr/lib/python3.9/http/client.py", line 1347, in getresponse
response.begin()
File "/usr/lib/python3.9/http/client.py", line 307, in begin
version, status, reason = self._read_status()
File "/usr/lib/python3.9/http/client.py", line 276, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 107, in call
response = request(
File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 71, in view
return self.dispatch(request, *args, **kwargs)
File "/usr/lib/python3/dist-packages/django/contrib/auth/mixins.py", line 52, in dispatch
return super().dispatch(request, *args, **kwargs)
File "/usr/lib/python3/dist-packages/django/contrib/auth/mixins.py", line 109, in dispatch
return super().dispatch(request, *args, **kwargs)
File "/usr/lib/python3/dist-packages/postorius/views/generic.py", line 74, in dispatch
return super(MailingListView, self).dispatch(request, *args, **kwargs)
File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 97, in dispatch
return handler(request, *args, **kwargs)
File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 183, in post
return self._member_post(request, role)
File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 135, in _member_post
self.mailing_list.unsubscribe(member)
File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/mailinglist.py", line 414, in unsubscribe
self._connection.call(path, method='DELETE')
File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 135, in call
raise MailmanConnectionError(
mailmanclient.restbase.connection.MailmanConnectionError: ('Could not connect to Mailman API: ', "ConnectionError(ProtocolError('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')))")
ERROR 2022-03-27 21:43:42,091 1507813 django.request Service Unavailable: /postorius/lists/dc-admins.lists.duckcorp.org/members/member/
</pre></p> Bip - Bug #763 (New): Backlog is being lost on unstable connectionshttps://projects.duckcorp.org/issues/7632022-03-16T19:03:53ZLoïc Gomez
<p><a class="external" href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595408">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595408</a></p>
<p>Per Arnaud's comment there:</p>
<blockquote>
<p>Tcp will detect such connection breakage only when bip sends data to<br />your ADSL ip and times out waiting for ACKs. So bip indeed<br />approximates when the connection is lost. The blreset_on_talk should<br />be useful to you as bip will replay logs as long as you did not reply<br />anything.</p>
<p>I don't see any trivial way to implement a better connection loss<br />detection for backlog reset. It should be feasible to delay backlog<br />resetting to only when we receive any data from client, which would<br />prevent some errors of the type you described (but not all).<br />Another way would be to poll the tcp buffer size and to reset logs<br />only when it's down to 0. It's probably the best solution.</p>
</blockquote> Bip - Bug #762 (New): Systemctl integration does not actually stop biphttps://projects.duckcorp.org/issues/7622022-03-16T18:55:17ZLoïc Gomez
<p><a class="external" href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963907">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963907</a></p>
<p>Checked up on this but could not reproduce on Ubuntu/hirsute with a fresh start. Although, on Debian stable, it indeed shows up as dead even though restart had occurred less than 2d ago, and I remember having such issue stopping bip:<br /><pre><code>
● bip.service - Bip IRC Proxy
Loaded: loaded (/lib/systemd/system/bip.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/bip.service.d
└─custom.conf, override.conf
Active: inactive (dead) since Thu 2022-03-10 21:29:43 CET; 5 days ago
Main PID: 5508 (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 4668)
Memory: 11.4M
CPU: 1d 4h 57min 33.009s
CGroup: /system.slice/bip.service
└─5509 /usr/bin/bip -f /etc/bip/bip.conf -s /var/lib/bip
Warning: journal has been rotated since unit was started, output may be incomplete.
</code></pre></p>
<p>Couldn't find any difference in systemctl unit</p> Bip - Bug #749 (New): bip doesn't create ~/.bip/ directory when using default PID filehttps://projects.duckcorp.org/issues/7492022-01-03T11:29:06ZLoïc Gomez
<p>30-12-2021 14:34:11 Default pid file: /home/kyoshiro/.bip/bip.pid<br />30-12-2021 14:34:11 FATAL: Cannot write to PID file (/home/kyoshiro/.bip/bip.pid.redacted.3764810) No such file or directory</p> DuckCorp Infrastructure - Enhancement #736 (New): Dovecot: adapt for upcoming deprecated featureshttps://projects.duckcorp.org/issues/7362021-10-22T08:03:46ZMarc Dequènesduck@duckcorp.org
<p><a class="external" href="https://dovecot.org/pipermail/dovecot-news/2020-March/000436.html">https://dovecot.org/pipermail/dovecot-news/2020-March/000436.html</a><br /><a class="external" href="https://dovecot.org/pipermail/dovecot/2020-March/118483.html">https://dovecot.org/pipermail/dovecot/2020-March/118483.html</a></p>
<p>We use the expire plugin but I don't think the rest impacts us, need to proofread though.</p> DuckCorp Infrastructure - Bug #735 (New): Configure mail properly on Nicecity and Orthoshttps://projects.duckcorp.org/issues/7352021-10-21T05:42:49ZMarc Dequènesduck@duckcorp.org
<p>Currently the default Debian mailer (exim) is installed but not configured.</p> Bip - Enhancement #733 (New): Error message is unclear when SSL server is unresponsivehttps://projects.duckcorp.org/issues/7332021-09-16T13:55:42ZLoïc Gomez
<p>It seems we get these when bip is unable to connect at all to a server using SSL:</p>
<blockquote>
<p>WARNING: mySSL_get_cert() SSL server supplied no certificate !<br />ERROR: No certificate in SSL write_socket</p>
</blockquote>
<p>We need to find a way to make it clear there is a connect() issue and not an SSL related problem.</p> Bip - Enhancement #730 (New): Update /bip backlog [n] to make it backlog private messages toohttps://projects.duckcorp.org/issues/7302021-09-03T12:36:27ZLoïc Gomez
<p>Current /bip backlog command does not backlog private messages.<br />I think it is related to bip not being aware of which private messages to look for, as they're scattered in multiple files.</p>
<p>Maybe it does work with an in-memory backlog setup though (to be tested).</p>
<p>We could probably list changed files in the logdir and backlog the ones matching the [n] parameter.</p> DuckCorp Infrastructure - Enhancement #725 (New): Mailing-lists: automate filling the dc-users li...https://projects.duckcorp.org/issues/7252021-05-29T09:01:55ZMarc Dequènesduck@duckcorp.org
<p>We need to check there is no disparity between the contact field in the LDAP and the registered addresses.</p>
<p>We also need to add a field (which does not need to be propagated in the LDAP) to opt-out users who do not care about our news.</p>