#musicbrainz-devel

some memory profiling, mostly, though it may be within postgres that the problem lies

in fact, the weekly ones might be faster if the bottleneck is the download :)

ianmcorvidae: I think it might be doing too many transactions.

one for each XID might be the "correct" thing to do, but also slows things down.

I wonder if we can safely batch more changes.

I'm not sure

ruaok : something like, "I see you are running a replication from more than a week back, would you like to apply the full dump? (This is much faster!!!)"

and script it :)

Lonewlf: its not quite that easy.

for people who are running in mission critical environments, the replication is easier than swapping in a new DB.

ruaok : no, it never is, but that's what you'd like it work like :P

ruaok : indeed

oh, hey, I have access to the musicbrainz-server repo, didn't know that

(well, more than read-only I mean :P)

ruaok : ok, I'm like... stupid here... I'm getting a syntax error

ruaok: Can't locate Statistics/Basic.pm?

did cd musicbrainz-server then cd admin then ./psql READWRITE

mapti89: carton install Statistics::Basic

mapti89: you may be seeing a pattern here :)

and now I'm stumped on the syntax fro dropping the db

Lonewlf: you need to drop the DB as user postgres, outside of psql

Lonewlf: sudo -u postgres dropdb musicbrainz_db

I think that ruaok missed the '-u'

oh, I normally do sudo su postgres

I didn't even know about the -u flag. :)

oh right ok

ah :)

ruaok: how kosher is it for me to poke at the frontend stuff for test? our deployment seems to have made some strange choices re: protocol support and ciphers and things

ianmcorvidae: poke away!

you've got the keys to the kingdom and you have sense in your head. poke it!

k

just still wary about touching frontend stuff, given the potential to accidentally burn the world :)

you mean nginx on carl/lenny?

nginx -t

is your friend. ;)

well, yes

even so :)

do you need some guideance on what to change?

nah, I think for test I'm set

k.

we really need ingestr. like yesterday.

disabling insecure SSL versions, improving the lists of ciphers, etc.

more people want to send us data. and we have no place to put it. :(

hopefully we can make some progress on this on Oct 22nd.

ahhh. 22nf

that's so close

thats our day at the archive.

not the MB summit, alastairp

oh. so it is

sigh. so much on

ruaok: actually, I do have one question: how do I make nginx reload its config? :)

cd /usr/local/nginx

I realize we're not using plain sysvinit for that, so

we're using daemontools

yeah, I've never used it before, hence the question :)

thanks

hmph

so, another question... having blown away my database so that I can run the import, did I shoot myself in the foot in some regard by only getting the 3 files suggested? should I have gotten all of them?

plaintext: hi the inc analyis looks good but Im surprised there doesn't seem to be a section for releases

I only goet mdump, the derived and the editor

those are the only ones you need

i think this is the entity I use most, and I suspect others do as well

although the others are pretty small, so I normally import those anyway

ijabz: the 'Summary' section is actually releases, I think we determined

ijabz: with the wrong label obviously, but

ijabz: I found the bug that causes this, and I'm working on it :)

btw, I think Summary is just Summary

Is summary just the top ones over any entities, now I look at it some clearly seem to be for release and others clearly not

yes it's the top for every entity

just releases are the most common, I see

bah c'mon nginx why won't you notice my config changes

theeeere we go

hey thanks guys, I'll pop in again if I blow myself up again

other than our cert being self-signed we're doing pretty well on ssllabs' test now

ianmcorvidae: why not use the new wildcard cert.

the deets on are carl.

ruaok: was working on other things first is all, that's next :)

k

Compilation failed in require at app.psgi line 21.

BEGIN failed--compilation aborted at app.psgi line 21.

carton install Catalyst::Utils

catalyst::utils looks like it's already there

it's failing in that file after all

not sure what's going on there

You have Catalyst::Utils (undef)

whoo, test now using the real cert

huh, apparently the wildcard has plain musicbrainz.org as a SAN

someone got an idea?

yay, bug fixed

it feels nice when fixing a bug results in much cleaner code

haha, yeah

I love when I can delete huge swaths of code as part of a patch :D

ok, I'm off to have lunch with my stalker.

heheh

ocharles, warp: could one of you pull in mbs-5301-ssl-gravatars and deploy it to test for me?

hm

why is my firefox still telling me the cert is insecure

answer seems to be "my firefox is poorly configured"

mapti89: I'd try running plain 'carton install' and seeing if it pulls anything in

mapti89: looking a bit deeper that error is being thrown when it can't load *something*, but unfortunately it's not printing what it's failing to load that I can see

ianmcorvidae: after running carton install, did i have to run: "carton install --deployment"?

they do largely the same thing; --deployment looks for specific versions while without it doesn't

so no, you should just need one or the other

see if there were any errors, though, of course :)

yes ;-)

the command install a lot of things that are missing!

do we not have a datepicker plugin for jquery ui?

or am I missing something?

plaintext: no idea, heh

https://www.ssllabs.com/ssltest/analyze.html?d=... btw, test is looking pretty nice SSL-wise :)

hm, I wonder if we'll need SSL for coverartarchive.org

to silence insecure-resources errors

(obviously only once *.s3dns.us.archive.org works properly, but)

YES IT S RUNNING

whoo! :)

not responding but running lol

if you're running it with RT_SLAVE, make sure you have something configured for READONLY

in DBDefs

there's a patch that'll hopefully mean we don't have to tell anyone to do that after next monday, but for now :)

i gona look again for thaht!

# READONLY => undef,

yeah, that'll not work

copy the block for READWRITE and change READWRITE to READONLY

(you need to have both, but they can have the same configuration)

how to shutdown MB properly? ctrl + C???

ctrl-c will do it, yes

for the dev server, which is what you're running

if you start it with -r you don't need to explicitly stop and restart it though

It's up and running

on the webpage i have a stack trace is it normal?

probably not

djce: ruaok headed out so now I'll pester you -- when I commit to the nginx git repo, how do I then deploy it on the frontends?

k :)

it's in syswiki but under GatewayPair