#metabrainz

heh

"NO HUMANS PAST THIS POINT"

Getting this error while accessing any DB-dependant page: Internal server error

(psycopg2.OperationalError) FATAL: remaining connection slots are reserved for non-replication superuser connections (Background on this error at: https://sqlalche.me/e/14/e3q8). Anyone else facing this issue?

HI plibither8, what are you using?

Accessing the website from Chrome on a Mac. Example: https://listenbrainz.org/current-status/

lucifer, mayhem, monkey ^

The main LB site? That works for me here, interesting

Hopefully the pinged LB team members can help figure it out

Yep, the main one. I was logged in first and accessing my profile and got the error, so I thought to try to clear the website storage and retry. That didn't work.

Thanks for the quick response guys!

Seems to be working now!

Thanks for reporting the issue in any case, worth investigating for the team to try to avoid it happening again!

( ☞˙ᵕ˙)☞

yvanzo: ok, installed prereqs for mb-docker - how do I set it to run and create containers in a different SSD than the default?

Is this something to set up before I run all the commands?

Yes

Do you have any docker stuff atm?

As in, running containers?

No, or at least nothing I want to keep

`docker ps --all` and `docker system df`

Apparently, a bunch of stuff :D

metabrainz_web related stuff is the only bit that might be of use but I can just set that up again when needed on the other disc

Probably a dev setup of MeB.O website?

Yes, I knew about that one, I didn't remember I still had the MBS containers around tho

Those are probably MeB.o containers too.

MeB.o uses both Redis and PG.

Yeah, but I assume musicbrainz-docker_indexer_1 and whatnot are MBS :)

Anyway, I'd be happy to just clear all this and start from scratch - so stop all, remove all, remove all images?

reosarevok: It’s probably fine to wipe everything out: `docker system prune --all --volumes

Oops, `docker system prune --all --volumes`

Everything is stopped already (status = exited)

Is it? some said Up 10 minutes

Anyway, running that for now, let it purge as much as it will

oh sorry

Had to scroll down.

So you actually have had some containers part of MB-docker running for about 15 months.

Seems so :D

`prune` won’t remove the running containers and the images they use.

Any reason not to just stop them and then pruning again?

You can just use them.

So I can move them to a different partition?

You probably have enough disk space on this partition anyway.

I probably do, but it's HDD not SSD :)

Will that difference make, well, a difference?

(I *think* those are running on my secondary HDD, anyway)

(not sure how to tell exactly)

Dunno what is faster for you: internal HDD or external SSD, it depends on buses.

Well, we can just put them in the HDD I guess for now, less thinking

You can use either `dd` or `hdparm` to find it out.

To find out where my docker containers are, or what is faster? :)

(reading on those, what is faster I guess)

I can probably live with slower, let's just get it set up in the HDD

what is faster ^

Since there already are performance issues, it's probably safer not to pile up hardware issues.

To find out where your current compose project files are: `docker container inspect --format '{{.Config.Labels}}' musicbrainz-docker-db-1`

See `com.docker.compose.project.working_dir`

com.docker.compose.project.working_dir:/media/data/musicbrainz-docker - ok, that's the HDD

That's only for the config files, not for the containers.

What about for the containers themselves?

`docker system info -f '{{.DockerRootDir}}'`

That's /media/data/docker so also the HDD. Guess we moved that there last time we tried - but then we tried to reuse the existing MB local install for dev and it was messy

IIRC that's why I gave up eventually

So let's just make this a fully separate install this time

Then stop everything and prune.

Perfect

Ok, done

I guess now I just follow the dev install instructions?

👍

A red line says "dpkg-preconfigure: unable to re-open stdin:"

should I worry?

Seems to be happily continuing so I guess not?

heh

DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/relea... pip 21.0 will remove support for this functionality.

January 2021, huh

That's soon!

You’re not thinking fourth dimensionally!

yvanzo:

reosarevok: for which command?

sudo docker-compose run --rm musicbrainz createdb.sh -sample -fetch

yvanzo: ^

(sorry, got sidetracked for a moment)

Did you check that there was no image left after pruning your system?

(and no volume)

Try `sudo docker-compose run --rm musicbrainz recreatedb.sh -sample`

I did not :)

Checking

Ok, recreate worked

yvanzo: ok, finished running the steps, but http://localhost:5000/ is not working yet

Maybe it is setting up

It take a while to run for the first time because it is installing dependencies.

Ok :)

You can follow progress through container's logs: `sudo docker-compose logs --follow --tail 1 --timestamps musicbrainz`

So that's basically just it doing compile_resources

Also, you don't have a MBS instance running outside of docker?

Not at the moment

(I haven't put plackup up)

The musicbrainz-server path is a different clone than the one you use outside of docker?

Yes

👍

In a different partition, should hopefully not affect each other at all

It would have overwritten your `lib/DBDefs.pm` otherwise.

You can change ports later on so that they can run at the same time.

aerozol: MBS-13326 could use a check

MBS-13326: UI/UX problem: People misread sort name as short name or use it for legal name, disambiguation, etc. https://tickets.metabrainz.org/browse/MBS-13326

Is "short name" a common thing in India, lucifer / akshaaatt / Pratha-Fish? Most of our "short name" misreads seem to be Indian editors

yvanzo: hmm...

Seems like the server should be up but 500s

It is! Golu, chintu, monu, etc, reosarevok 😂 But I would like to see an example pf it being used incorrectly somewhere to understand the context better

See the link from the ticket:

Seems to be a bunch of Indians entering a nickname under "sort name" and complaining that it's their "short name" when someone downvotes :)

reosarevok: check the resources compilation log file: `sudo docker-compose exec musicbrainz tail -f /compile_resources.log`

akshaaatt: but most people just call it nicknames, don't they? 😂

The shared link doesn’t open for me, reosarevok

I am on mobile though

akshaaatt: hmm. Are you logged in?

Oh, yeah, so it dropped the log-in only parts of the search, but that made it too wide so it failed :D

Help me understand this reosarevok , so for an artist named Machine Gun Kelly, people usually refer to him as mgk. So would mgk be his sort name?

https://musicbrainz.org/edit/104773929 / https://musicbrainz.org/edit/104484207

I am assuming sort name is for the search