| Time |
Nick |
Message |
| 07:36 |
|
kworstell-isl joined #evergreen |
| 07:43 |
|
JBoyer_ joined #evergreen |
| 07:57 |
|
BDorsey joined #evergreen |
| 08:35 |
|
collum joined #evergreen |
| 08:42 |
|
jvwoolf joined #evergreen |
| 08:46 |
|
mmorgan joined #evergreen |
| 08:50 |
|
rfrasur joined #evergreen |
| 09:02 |
|
dguarrac joined #evergreen |
| 09:10 |
|
Dyrcona joined #evergreen |
| 10:00 |
|
sleary joined #evergreen |
| 10:13 |
jvwoolf |
Anybody else having problems with Launchpad? |
| 10:18 |
Bmagic |
always |
| 10:18 |
jvwoolf |
Bmagic++ |
| 10:18 |
jvwoolf |
It's not loading for me at all right now |
| 10:20 |
Bmagic |
just checked. Confirmed, no worky |
| 10:21 |
Dyrcona |
@blame Launchpad |
| 10:21 |
pinesol |
Dyrcona: Launchpad must eat cottage cheese! |
| 10:33 |
|
Christineb joined #evergreen |
| 11:38 |
|
jihpringle joined #evergreen |
| 12:16 |
|
stompro__ joined #evergreen |
| 12:19 |
|
stompro_home joined #evergreen |
| 12:26 |
csharp_ |
for the jacket uploader, are people using a shared directory across bricks similar to reports/offline/vandelay? |
| 12:27 |
csharp_ |
seems like we'd have to, right? |
| 12:28 |
Dyrcona |
Yeah, I think you'd have to. |
| 12:31 |
jeff |
it's either that or a lot of scheduled rsync jobs with --update in the mix. :-) |
| 12:32 |
jeff |
(that's mostly a joke, but a surprising amount of jokes end up in production -- especially in a pinch) |
| 12:36 |
stompro_home |
inotifywait + rsync for those instant updates. |
| 12:37 |
|
collum joined #evergreen |
| 12:54 |
Dyrcona |
Heh. |
| 12:57 |
Dyrcona |
You could just hack the cover upload process to do the rsync --update. |
| 12:58 |
Dyrcona |
Another joke, in case it isn't obvious. |
| 13:08 |
* csharp_ |
realizes all his configurations are based on #evergreen jokes :-( |
| 13:08 |
csharp_ |
really chasing my tail on upgraded ejabberd on 20.04 |
| 13:08 |
csharp_ |
in-place upgrade from 18.04 |
| 13:09 |
csharp_ |
I believe it's TLS-related |
| 13:17 |
|
collum joined #evergreen |
| 13:24 |
Dyrcona |
csharp_: What are the symptoms? |
| 13:25 |
Dyrcona |
Also, I think we've got new performance issues on Pg 15. Either that or my DB server has gone totally pathological. |
| 13:26 |
Dyrcona |
Oh, look! It finally finished. |
| 13:39 |
jeffdavis |
We're using an NFS share for uploaded cover images, FWIW. |
| 13:48 |
jeffdavis |
We also had trouble using the stock Ubuntu 20.04 ejabberd.yml, I believe I ended up copying whatever's used by the ansible installer. |
| 13:52 |
Dyrcona |
I've not had any real trouble with it after disabling apparmor and following the directions in the README. |
| 13:52 |
Dyrcona |
Upgrades can be finicky. |
| 14:18 |
JBoyer_ |
It may also be necessary post-upgrade to totally wipe the mnesia db directory. (basically everything under /var/lib/ejabberd/*) |
| 14:25 |
stompro_home |
Here is a diff of my ejabberd 21.01-2 (Debian 11.5) for comparison - https://gist.github.com/stompro/2553aa6edbf0fac06d893d836c9e3c75 |
| 14:26 |
stompro_home |
I was trying to figure out a timeout issues, so there may be a few lines in there having to do with timeouts that are not needed. |
| 14:32 |
|
mmorgan joined #evergreen |
| 15:11 |
|
sleary joined #evergreen |
| 16:32 |
|
sleary joined #evergreen |
| 16:41 |
|
stompro__ joined #evergreen |
| 16:46 |
|
mmorgan left #evergreen |
| 16:57 |
|
JBoyer joined #evergreen |
| 17:51 |
|
jvwoolf joined #evergreen |
| 19:34 |
|
jvwoolf left #evergreen |
