Run Your Own - User contributions [en]

Mailman 3 Service and Troubleshooting

2024-12-02T12:59:33Z

LeWikiAdmin: /* Something is stuck in the Hyperkitty spool */

== Service Configuration and Installation ==

There are two services needed:
systemctl status mailman3 # AKA mailman-core you only need this for lists to work
systemctl status mailmanweb # AKA hyperkitty, postorius, uwsgi, django hell, needed for the web interface

== Troubleshooting ==
=== Where is everything logged? ===

Don't think you can start understand anything without at least doing the following:
* mailman core
tail -f /home/mailman/we.lurk.org/mm/var/logs/*
tail -f /var/log/mail.err /var/log/mail.log /var/log/mail.warn
journalctl --follow _SYSTEMD_UNIT=mailman3.service + _SYSTEMD_UNIT=mariadb.service
* web stuff
tail -f /home/mailman/we.lurk.org/web/logs/*
tail -f /var/log/nginx/*log

=== Mailman3 service does not (re)start ===
Quite often when mm3 crashes or when the server crashes and reboots, or if there has been a power shortage, mm3 leaves a stale lock which prevents the service to start again. This can be confirmed with:
systemctl status mailman3

Check for this line:
Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try using --force

If you see it, congrats, you have a stale lock, you can remove it like this:
rm /home/mailman/we.lurk.org/mm/var/locks/master.lck

You can now restart mailman3 and mailmanweb
systemctl start mailman3
systemctl restart mailmanweb

=== Something is stuck in the Hyperkitty spool ===
Sometimes Hyperkitty does not like an email and won't be able to store it in its database. If that's the case there will be errors showing up both on the mailman3 and mailmanweb sides, notably about the relevant table/column in the mailman_web mariadb database that's struggling. Until this is solved the email will keep on being re-queued at <code>/home/mailman/we.lurk.org/mm/var/archives/hyperkitty/spool</code> and and new attempts to store the problematic email will happen ''every time'' the archiver is called, for instance when a new email is received on a list that has to be archived. This will not block the queue, just that the problem email will keep being tried over and over again until the problem is solved which can become quite expensive from a computational POV.

To inspect an item stuck in the queue you can do this:
su mailman # ALWAYS
cd /home/mailman/we.lurk.org/mm/var/archives/hyperkitty/spool
mailman qfile 1234567890.1234567890.pck | less

=== Running mailman standalone ===
'''Only do this when manually troubleshooting otherwise this will conflict with <code>systemctl</code> initiated services.'''
* Mailman 3 relies on its own mailman user to handle the processing of the emails.
su mailman # switch to the mailman user
cd # make sure you cd to mailman's home !IMPORTANT
* You're now ready to control mailman
* Everything is handled with the mailman command line tool. Do not run these commands with another user!
mailman status # report on the service
mailman start # start mailman
mailman stop # stop mailman
mailman restart # stop and start mailman shorcut

[[Category: Email]]

Wildcard Certificates with acme.sh

2019-10-03T14:58:58Z

LeWikiAdmin: /* Renewal */

== Base installation ==

apt install python-pip
pip install wheel
pip install certbot

== DNS plugins ==
=== Gandi ===
'''NOTE: At time of writing, only an API key from the domain owner will work. So another account, even if listed technical contact, will not able to use the live DNS API, just the live DNS web interface. Since the writing of this HOWTO, there is now this as well https://github.com/obynio/certbot-plugin-gandi TODO'''

* Get API key from Gandi (somewhere in account settings)
* install certbot-plugin-gandi
pip install 'git+https://gitlab.com/cspublic/certbot-plugin-gandi.git'
mkdir /etc/certbot-plugin-gandi
* create /etc/certbot-plugin-gandi/gandi.ini with the following:
certbot_plugin_gandi:dns_api_key=APIKEY
* a bit of paranoia
chmod 600 /etc/certbot-plugin-gandi/gandi.ini
* request certificate for both mydomain.blabla '''and''' *.mydomain.blabla
'''NOTE: At time of writing, the default sever end point used by cerbot (0.22) is not compatible with ACME v2, as a workaround --server must be passed manually. Next version of certbot should point to the right server'''
/usr/local/bin/certbot certonly -a certbot-plugin-gandi:dns --certbot-plugin-gandi:dns-credentials /etc/certbot-plugin-gandi/gandi.ini -d mydomain.blabla -d *.mydomain.blabla --server https://acme-v02.api.letsencrypt.org/directory
* If all goes well certs will be there:
'''NOTE: At time of writing, certbot-plugin-gandi seems to behave a bit funnily when asked to request a challenge for a wildcard cert (it works flawslessly for regular domains). It might be needed to run the command several times to get the infamous CONGRATULATION message from certbot.'''
/etc/letsencrypt/live/mydomain.blabla/fullchain.pem
/etc/letsencrypt/live/mydomain.blabla/privkey.pem

== Renewal ==
To non-interactively renew *all* of your certificates:
/usr/local/bin/certbot renew

=== douglas ===
=== agnes ===
'''TODO: hooks!'''
<pre>
service nginx restart
prosodyctl reload
</pre>

[[Category:Certificates]]

Talk:Homebrew Server Club

2019-01-17T13:44:30Z

LeWikiAdmin:

==Todo==
What do we need on this page?

:Actually maybe we need much more pages? The HBS page could be used to describe the HBSC community and relevant links? But this could grow as the documentation improves of course. The thread on the list was started in relation to collect links about making website not ridiculously heavy, so we could start with that? [[User:LeWikiAdmin|LeWikiAdmin]] ([[User talk:LeWikiAdmin|talk]]) 13:44, 17 January 2019 (UTC)

Main Page

2018-04-13T12:08:07Z

LeWikiAdmin:

[[File:Computer Lib cover by Ted Nelson 1974.png|right]]
'''Welcome to RUN YOUR OWN, the wiki documentation of LURK's servers.'''

One of LURK's mission is to make sure we're not creating yet another silo for online discussions and publishing, but also give enough inspiration for others to do the same and start provide their own centralised, decentralised, federated, and whatnot services.

Running your own server, and its services, is not always straightforward, so this is why we are using this space to document and make public how we maintain and configure LURK servers.

== Request for Feedback ==

This documentation effort is an ongoing process, we add stuff as we develop the environment, and learn more about it ourselves. We gladly welcome your feedback and comments:
* Mailing list about LURK: https://we.lurk.org/postorius/lists/metalurk.we.lurk.org
* Chat about LURK: https://talk.lurk.org/channel/_meta

== Support! ==

'''LURK is a volunteer run project.'''

If you found something useful here, please [https://liberapay.com/LURK consider supporting us] (if you can afford it!)

== Server Documents ==

{{Special:AllPages|namespace=14}}

Main Page

2018-04-13T12:06:00Z

LeWikiAdmin: /* Support! */

[[File:Computer Lib cover by Ted Nelson 1974.png|right]]
'''Welcome to RUN YOUR OWN, the wiki documentation of LURK's servers.'''

One of LURK's mission is to make sure we're not creating yet another silo for online discussions and publishing, but also give enough inspiration for others to do the same and start provide their own centralised, decentralised, federated, and whatnot services.

Running your own server, and its services, is not always straightforward, so this is why we are using this space to document and make public how we maintain and configure LURK servers. This is an ongoing process, we add stuff as we develop the environment, and learn more about it ourselves.

== Request for Feedback ==

This documentation effort is an ongoing process, we add stuff as we develop the environment, and learn more about it ourselves. We gladly welcome your feedback and comments:
* Mailing list about LURK: https://we.lurk.org/postorius/lists/metalurk.we.lurk.org
* Chat about LURK: https://talk.lurk.org/channel/_meta

== Support! ==

'''LURK is a volunteer run project.'''

If you found something useful here, please [https://liberapay.com/LURK consider supporting us] (if you can afford it!)

== Server Documents ==

{{Special:AllPages|namespace=14}}

File:Runyourown.png

2018-04-13T12:04:17Z

LeWikiAdmin:

Main Page

2018-04-13T11:56:31Z

LeWikiAdmin:

[[File:Computer Lib cover by Ted Nelson 1974.png|right]]
'''Welcome to RUN YOUR OWN, the wiki documentation of LURK's servers.'''

One of LURK's mission is to make sure we're not creating yet another silo for online discussions and publishing, but also give enough inspiration for others to do the same and start provide their own centralised, decentralised, federated, and whatnot services.

Running your own server, and its services, is not always straightforward, so this is why we are using this space to document and make public how we maintain and configure LURK servers. This is an ongoing process, we add stuff as we develop the environment, and learn more about it ourselves.

== Request for Feedback ==

This documentation effort is an ongoing process, we add stuff as we develop the environment, and learn more about it ourselves. We gladly welcome your feedback and comments:
* Mailing list about LURK: https://we.lurk.org/postorius/lists/metalurk.we.lurk.org
* Chat about LURK: https://talk.lurk.org/channel/_meta

== Support! ==

'''LURK is a volunteer run project.'''

If you found something useful here, please [https://liberapay.com/LURK consider supporting us] (if you can afford it!)

== Server Documents ==

{{Special:AllPages|namespace=14}}

File:Computer Lib cover by Ted Nelson 1974.png

2018-04-13T11:55:33Z

LeWikiAdmin:

Main Page

2018-04-13T11:50:18Z

LeWikiAdmin: /* Support! */

'''Welcome to RUN YOUR OWN, the wiki documentation of LURK's servers.'''

One of LURK's mission is to make sure we're not creating yet another silo for online discussions and publishing, but also give enough inspiration for others to do the same and start provide their own centralised, decentralised, federated, and whatnot services.

Running your own server, and its services, is not always straightforward, so this is why we are using this space to document and make public how we maintain and configure LURK servers. This is an ongoing process, we add stuff as we develop the environment, and learn more about it ourselves.

== Request for Feedback ==

This documentation effort is an ongoing process, we add stuff as we develop the environment, and learn more about it ourselves. We gladly welcome your feedback and comments:
* Mailing list about LURK: https://we.lurk.org/postorius/lists/metalurk.we.lurk.org
* Chat about LURK: https://talk.lurk.org/channel/_meta

== Support! ==

'''LURK is a volunteer run project.'''

If you found something useful here, please [https://liberapay.com/LURK consider supporting us] (if you can afford it!)

== Server Documents ==

{{Special:AllPages|namespace=14}}

Main Page

2018-04-13T11:48:05Z

LeWikiAdmin:

'''Welcome to RUN YOUR OWN, the wiki documentation of LURK's servers.'''

One of LURK's mission is to make sure we're not creating yet another silo for online discussions and publishing, but also give enough inspiration for others to do the same and start provide their own centralised, decentralised, federated, and whatnot services.

Running your own server, and its services, is not always straightforward, so this is why we are using this space to document and make public how we maintain and configure LURK servers. This is an ongoing process, we add stuff as we develop the environment, and learn more about it ourselves.

== Request for Feedback ==

This documentation effort is an ongoing process, we add stuff as we develop the environment, and learn more about it ourselves. We gladly welcome your feedback and comments:
* Mailing list about LURK: https://we.lurk.org/postorius/lists/metalurk.we.lurk.org
* Chat about LURK: https://talk.lurk.org/channel/_meta

== Support! ==

LURK is a volunteer run project, if you found something useful here, consider supporting us (if you can afford it!)

https://liberapay.com/LURK

== Server Documents ==

{{Special:AllPages|namespace=14}}

Main Page

2018-04-13T11:16:10Z

LeWikiAdmin:

MediaWiki has been installed.

test

Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [//www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]