was there cover art on that site? We could link some into musicbrainz ;)
ruaok groans
nikki
why is it painful?
ruaok
the entire concept of the cd index was painful.
I'm giving a talk about OSS/MB at Cal Poly on thu.
from my notes:
" When Slashdot asked what the replacement for CDDB was, I finished a rough version of the index and it was slashdotted. It tipped over and failed."
"- A craptastic community evolved from the screaming bitches that streamed in from Slashdot."
a slashdot borne community is *not* what you want. :)
nikki can imagine
dinog1 joined the channel
djce joined the channel
nikki prods ocharles_
nikki
ruaok: problem on test is back
ruaok
which one. :)
warp
postgresql is eating 100% cpu
nikki
Caught exception in MusicBrainz::Server::Controller::Root->begin "DBD::Pg::st fetchrow_array failed: no statement executing at /home/musicbrainz/perl5/lib/perl5/Catalyst/Plugin/Session/Store/DBI.pm line 32."
it's the one ollie wanted to look at, wasn't it?
but I bet he's not here now :P
ruaok
this is a new one. postgres has not previously taken 100%.
nikki
oh
it's the same error message at least
ruaok
yeah.
that we should leave to ocharles.
let me see what pg is doing though.
thats the newfangled empty artists query running.
uhm. ya. that query needs to be split up into something more sane.
its only been going a measley 15 hours. should finish any moment now.
nikki
whoa
ruaok
processor hours. probably has been running longer in wallclock time
ocharles: I wasn't trying to bust your chops on MBS-1557. I was just trying to figure out why hobbes was running old code.
sorry about, that. :(
ocharles_
no problem :)
ruaok waves to nikki
where were you running it from?
~musicbrainz/musicbrainz-server should have next on
ruaok
it was running on hobbes. from cron
thats why I was confused.
but the only thing that could've happened is that the cron job ran, then the code was updated and some hours later I came and killed it
ocharles_
yea, that's a possibility
i cat'ed it earlier though and it looks right now
re db backed sessions, I'm not having much luck
ruaok
have you run that script by hand on hobbes?
ocharles_
nope, only locally
ruaok
not much luck in which way?
ocharles_
i couldn't work out what was happening. looking at the logs the fastcgi processes were dying and restarting
ruaok
I saw that it died again last night. in a very particular and worrysome way,
ocharles_
and when I checked ps only 1 session db connection was open, 2 raw data, and 5 readwrite were open it
should be 5 of each
ruaok
do you know which module might be at fault?
ocharles_
Well, I can only imagine it's Session::Store::DBI, but when I asked in #catalyst I didn't get much of a response
I may try the ML
ruaok
please do.
ocharles_
I tried Memcached sessions in the meantime, and that also seems to be useless
ruaok
this would be an excellent thing to have working.
nikki
ocharles_: hm... I don't understand the change you made for the youtube urls, it doesn't seem to do anything different
ocharles_
after a few hours sessions immediately expired
ruaok
lame.
ocharles_
nikki: yea, I've just noticed I forgot the ?
bah.
nikki
what's the point of having it there if it's optional?
and you didn't update the other youtube regex
ocharles_
eww, duplication
time to fix that so I don't make that mistake again
ruaok: so options are to keep trying to figure out why dbi backed sessions aren't working, look into writing our own session store driver, or look at using memcached/redis/something else
memcached is nice but the moment it runs out of space it starts expiring sessions
redis could be a good middleground
but it's more server software to run
ruaok
my order of preferences:
1. debug the DBI session store.
2. tinker with memcached.
3. seek something else.
for #2, we could run a separate instance in memcached that did nothing but sessions and was tuned for that.
that would be easy to try too.
ocharles_
that could work
ruaok
just run another copy on another port and turn it to what you need.
thats easy to try.
ocharles_
yea
ruaok
s/turn/tune
ocharles_
hrm, I think I know why memcached was failing... turns out the default expiry time is 0
no, no it isn't, it's 86400. hrm.
ruaok
it could be full.
how much ram is allocated to it?
ocharles_
i think it may well be that problem
no idea, I haven't configured it at all
ruaok
memcached will give you all sorts of stats.
restart memcached and what what it does over time.