yeah...he's all over the events page in the rttp attendance and still has the annoying profile


check it out

At least someone is at least claiming to go to see my band.

I know, it's depressing how much of a liar "deleted" is though...when no one shows up...I'll be like, "what the fuck, deleted?" you lying son of a bitch


and frankly I'm just not ready for that kind of inner turmoil

deleted never went away
dunno why he can't fix that

cause I'm not sure where its coming from.
I will look into it again

ok, I think I figured out what was happening (not sure)...
I put something in place so deleted cause be added to the events list.
this morning, I got that deleted person trying to add themselves every 30 seconds from 8:30 to 8:50.

Is anyone having problems added themselves to the events page?

i'm on text...
but this is what i was trying to remind you about last night

65.19.150.222
http://www.omni-explorer.com

I believe that is who deleted is

actually: "e-SocietyRobot"
http://www.yama.info.waseda.ac.jp/~yamana/es/

would this "deleted" be the reason that RTTP is running kind of sluggish today?

no.. there is something up with the sql server lately.
I need to optimize it... but I'm not sure how.

I've tried all the tweaks for my.cnf I could find, but it still runs so much slower than 3.28

my.cnf
---------------------------
[rttp@returntothepit ~]$ more my.cnf
[mysqld]
basedir = /usr
datadir = /var/lib/mysql
socket=/var/lib/mysql/mysql.sock

skip-innodb
max_connections = 650
key_buffer = 64M
myisam_sort_buffer_size = 64M
join_buffer_size = 1M
read_buffer_size = 2M
sort_buffer_size = 2M
table_cache = 1500
thread_cache_size = 128
wait_timeout = 900
connect_timeout = 10
tmp_table_size = 128M
max_allowed_packet = 16M
max_connect_errors = 99999
read_rnd_buffer_size = 524288
bulk_insert_buffer_size = 8M
query_cache_limit = 2M
query_cache_size = 128M
query_cache_type = 1
query_prealloc_size = 16384
query_alloc_block_size = 16384

[mysqld_safe]
open_files_limit = 8192
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

[mysqldump]
quick
max_allowed_packet = 16M

[myisamchk]
key_buffer = 64M
sort_buffer = 64M
read_buffer = 16M
write_buffer = 16M
--------------------------------------------------

if you can think of anything else to add...
for some reason I can't get slow query logging to work on it either

ARG! the spammers that are spamming the board/cd reviews/band comments just started adding members to bands.

[mysqld]
skip-innodb
skip-locking
key_buffer = 16K
max_allowed_packet = 1M
thread_stack = 64K
table_cache = 4
sort_buffer = 64K
net_buffer_length = 2K

look into adding the 'net_buffer_length = ???' line to your .cnf file. the one I have set up here on my test box it only 2K, because it's only accessable my myself. I wonder if you bumped it up to 1 or 2M if it would help. and I think your query cache set to 128M might be a bit large, but I understand the need for it. both the db and apache are running on the same machine, I'm assuming... it may be time to start looking into having a seperate DB server... but that's even more money, and RTTP is already expensive enough for you to run... hmmm

I'm not getting another box.

I found that some of the spam bots are coming from
http://ev1servers.net/
I'm reporting it.

the_reverend said:

didn't think you were. it was merely a suggestion though.

what version of mysql are you running?

4.1.14

hmm... why not upgrade to 4.1.16?

more importantly, tell me why would I need to?
so far, 3.28 worked better for RttP's db's than 4.1.14

the only reason I upgraded was to be able to use "multi-groups" and "update or insert"
neither of which either work or I have used.

the only version that interests me right now is 5.x with fast spc and plc. though I don't really have the time to convert things to spc

hmmm... if I'm not mistaken, 4.1.16 was basically a bugfix for 4.1.14. I'll look more into it in a moment when I've got a free second.

otherwise, maybe you may want to consider migrating back to 3.28 (which would probably be a huge headache).

found a list of bug fixes in 4.1.16 (you may want to look at the list of fixes in 4.1.15 as well to see if it was cleared up in that release)

http://dev.mysql.com/doc/refman/4.1/en/news-4-1-16.html

back-reving would be impossibly hard as I upgraded php too

the_reverend said:

I figured as much...

I'll probably just yum the new one

4.1.16-1.FC4 installed

gd 4.1.16-1 kind of sucks.

ok, I rebooted

zzz

actually it's better than zzz
it's faster now

this thread should be about strongbad