Read-only historical archive Reconstructed community archive · captured 17 November 2010

Forum index / News / HGF News

HGF News

15 posts · page 1 of 1

WEAK
post #1
17 July 2006, 08:56 UTC#1
It's possible that HGF may be causing problems with the server. Tech support feels that it is, and I'm not surprised considering all the problems HGF has caused servers in the past.

The server tech recommended I purchase a seperate server specifically for HGF. That would cost several hundred dollars. I can't afford that, and considering HGF makes zero money, it's not worth it.

I'm going to look into the matter more deeply. If I find that HGF is in fact responsible for the current server problems, I will be making some big changes to this place that some of you may see as negative.

One thing I would consider doing is closing the forum off to public viewing - meaning visitors cant see anything but a registration page. This is sort of what we're doing already, only they wouldn't even be able to see thread titles.

Also, the search function has been disabled. The search functions are CPU intensive and if anything on this forum is responsible for overloading the server...it would be the Search function.

Overall, I doubt many of you'll care much about the possible changes as they will affect visitors only, with the acception of the Search function.

I'll keep you updated.

- - - - - - - - - - - -

Also, please post in here when HGF lags for you. Hopefully turning off the Search function has helped a bit.
Dan Avery
post #2
17 July 2006, 09:11 UTC#2
Do it if it saves you lots of money man.
WEAK
post #3
17 July 2006, 09:14 UTC#3
Nah it doesnt save me any money...it just keeps me from having to put $400 a month into HGF to keep it running..which I could never afford even if I wanted to.

Eh I guess that is saving money haha.

Anyway, Im hoping that disabling the Search form has helped. Things seem to be running better now than it has been for the past 5 hours.
Adem
post #4
17 July 2006, 10:48 UTC#4
do it dude, I never even touch the search area anyway.
gman
post #5
17 July 2006, 10:56 UTC#5
What are OF talking about? Seriously, I've grepped the ouput of MySQL and it barely causes any load.

To prove OF wrong, I'm gonna migrate the HGF database to our second server. Granted the second server won't have much of a load. I'm getting pretty sick of OF's resolutions now. They're trying to cover up that they don't know the problem.

It aint HGF, if it was the loads would be high right now. It's IMPOSSIBLE.
made
post #6
17 July 2006, 10:56 UTC#6
As long as the board stays online and functional I aint botherd dude, you pay alot for the server anyway. And for that I thank you! X
WEAK
post #7
17 July 2006, 10:59 UTC#7
QUOTE(gman @ Jul 17 2006, 10:56 AM) [snapback]362010[/snapback]

What are OF talking about? Seriously, I've grepped the ouput of MySQL and it barely causes any load.

To prove OF wrong, I'm gonna migrate the HGF database to our second server. Granted the second server won't have much of a load. I'm getting pretty sick of OF's resolutions now. They're trying to cover up that they don't know the problem.

It aint HGF, if it was the loads would be high right now. It's IMPOSSIBLE.


Well man...I understand what you mean...and it is odd that now...out of the 3 months we've been on OF...that HGF would be causing problems. Its not like the traffic has increased or anything.

Reguardless, we need to resolve this matter ASAP.
gman
post #8
17 July 2006, 11:05 UTC#8
QUOTE(WEAK @ Jul 17 2006, 12:59 PM) [snapback]362012[/snapback]

QUOTE(gman @ Jul 17 2006, 10:56 AM) [snapback]362010[/snapback]

What are OF talking about? Seriously, I've grepped the ouput of MySQL and it barely causes any load.

To prove OF wrong, I'm gonna migrate the HGF database to our second server. Granted the second server won't have much of a load. I'm getting pretty sick of OF's resolutions now. They're trying to cover up that they don't know the problem.

It aint HGF, if it was the loads would be high right now. It's IMPOSSIBLE.


Well man...I understand what you mean...and it is odd that now...out of the 3 months we've been on OF...that HGF would be causing problems. Its not like the traffic has increased or anything.

Reguardless, we need to resolve this matter ASAP.



I'm getting the impression that everytime you want a problem resolved, we're getting a dumbass level1 tech. I'm pretty pissed now. Look at this:

QUOTE
[root@server1674 ~]# ps waux | grep mysql
root 4014 0.0 0.0 6240 1016 ? S Jul13 0:00 /bin/sh /usr/bin/ mysqld_safe --old-passwords --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/s erver1674.alphared.com.pid
mysql 4044 0.0 1.1 53324 23032 ? S Jul13 2:39 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4045 0.0 1.1 53324 23032 ? S Jul13 3:24 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4046 0.0 1.1 53324 23032 ? S Jul13 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4047 0.0 1.1 53324 23032 ? S Jul13 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4048 0.0 1.1 53324 23032 ? S Jul13 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4049 0.0 1.1 53324 23032 ? S Jul13 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4053 0.0 1.1 53324 23032 ? S Jul13 0:01 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4054 0.0 1.1 53324 23032 ? S Jul13 0:01 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4055 0.0 1.1 53324 23032 ? S Jul13 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4056 0.0 1.1 53324 23032 ? S Jul13 0:09 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
root 30629 0.0 0.0 5132 688 pts/0 S+ 05:59 0:00 grep mysql
mysql 30630 0.0 1.1 53452 23036 ? R 05:59 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
[root@server1674 ~]#


They talk bullshit, how is HGF causing any load problems? That's eFUKT and HGF combined, HGF's database is optimised and repaired. When HGF caused problems was when the database was corrupted, so a server had to work 20 times as hard to lookup a single query, I fixed that shit ages ago.

You're too quick to believe OF, I work off facts and experience directly from the shell. Viewing the processes in the terminal always shows dozens of HTTP connections and little MySQL connections. HGF is pretty much all MySQL and the PHP documents cause fuck all load.

Secondly, HGF is set so it returns a "Server busy" message when the load reaches a certain point. Now before the kernel was upgraded, the load would go to 12 and remain there for some time, thus disabling HGF a few times. This proved in no way did HGF cause any load problems.

It's bullshit, they're completely bullshitting you.
WEAK
post #9
17 July 2006, 11:08 UTC#9
QUOTE(gman @ Jul 17 2006, 11:05 AM) [snapback]362015[/snapback]

QUOTE(WEAK @ Jul 17 2006, 12:59 PM) [snapback]362012[/snapback]

QUOTE(gman @ Jul 17 2006, 10:56 AM) [snapback]362010[/snapback]

What are OF talking about? Seriously, I've grepped the ouput of MySQL and it barely causes any load.

To prove OF wrong, I'm gonna migrate the HGF database to our second server. Granted the second server won't have much of a load. I'm getting pretty sick of OF's resolutions now. They're trying to cover up that they don't know the problem.

It aint HGF, if it was the loads would be high right now. It's IMPOSSIBLE.


Well man...I understand what you mean...and it is odd that now...out of the 3 months we've been on OF...that HGF would be causing problems. Its not like the traffic has increased or anything.

Reguardless, we need to resolve this matter ASAP.



I'm getting the impression that everytime you want a problem resolved, we're getting a dumbass level1 tech. I'm pretty pissed now. Look al this:

QUOTE
[root@server1674 ~]# ps waux | grep mysql
root 4014 0.0 0.0 6240 1016 ? S Jul13 0:00 /bin/sh /usr/bin/ mysqld_safe --old-passwords --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/s erver1674.alphared.com.pid
mysql 4044 0.0 1.1 53324 23032 ? S Jul13 2:39 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4045 0.0 1.1 53324 23032 ? S Jul13 3:24 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4046 0.0 1.1 53324 23032 ? S Jul13 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4047 0.0 1.1 53324 23032 ? S Jul13 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4048 0.0 1.1 53324 23032 ? S Jul13 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4049 0.0 1.1 53324 23032 ? S Jul13 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4053 0.0 1.1 53324 23032 ? S Jul13 0:01 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4054 0.0 1.1 53324 23032 ? S Jul13 0:01 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4055 0.0 1.1 53324 23032 ? S Jul13 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
mysql 4056 0.0 1.1 53324 23032 ? S Jul13 0:09 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
root 30629 0.0 0.0 5132 688 pts/0 S+ 05:59 0:00 grep mysql
mysql 30630 0.0 1.1 53452 23036 ? R 05:59 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/serv er1674.alphared.com.pid --skip-locking --port=3306 --socket=/var/lib/mysql/mysql .sock --old-passwords
[root@server1674 ~]#


They talk bullshit, how is HGF causing any load problems? That's eFUKT and HGF combined, HGF's database is optimised and repaired. When HGF caused problems was when the database was corrupted, so a server had to work 20 times as hard to lookup a single query, I fixed that shit ages ago.

You're too quick to believe OF, I work off facts and experience directly from the shell. Viewing the processes in the terminal always shows dozens of HTTP connections and little MySQL connections. HGF is pretty much all MySQL and the PHP documents cause fuck all load.

Secondly, HGF is set so it returns a "Server busy" message when the load reaches a certain point. Now before the kernel was upgraded, the load would go to 12 and remain there at sometime, thus disabling HGF a few times. This proved in no way did HGF cause any load problems.

It's bullshit, they're completely bullshitting you.


HGF gets disabled at 10. You said you notice latency anywhere from when the load hits beyond something like 4..
Funk Master Steven
post #10
17 July 2006, 13:59 UTC#10
I use the search alot.

And once I finish paying off this camera and this brand new fucking ticket, I'll throw in some cash for a new server.
gman
post #11
17 July 2006, 14:04 UTC#11
Those techs were proved wrong :happy:
Funk Master Steven
post #12
17 July 2006, 14:07 UTC#12
QUOTE(gman @ Jul 17 2006, 02:04 PM) [snapback]362056[/snapback]

Those techs were proved wrong :happy:


Did Gman pwn some pimply nerd ass?
WEAK
post #13
17 July 2006, 14:10 UTC#13
Problem solved. Had nothing to do with HGF.
gman
post #14
17 July 2006, 14:11 UTC#14
QUOTE(Funk Master Steven @ Jul 17 2006, 04:07 PM) [snapback]362060[/snapback]

QUOTE(gman @ Jul 17 2006, 02:04 PM) [snapback]362056[/snapback]

Those techs were proved wrong :happy:


Did Gman pwn some pimply nerd ass?



Something like that :happy:
WEAK
post #15
17 July 2006, 14:12 UTC#15
Get on MSN or AIM you cunt, tech support contacted me about the mime shit.