• Fur Affinity Forums are governed by Fur Affinity's Rules and Policies. Links and additional information can be accessed in the Site Information Forum.

FULL SYSTEM UPGRADE!

yak

Site Developer
Staff member
Administrator
OS - FreeBSD
HTTP - Apache 1.3.34
PHP - 4.4.2 i believe
Well, these were the specs of the old server.

Don't know anyhing about the new one, except it is FreeBSD as well. It finally has /server-status disabled.
 

yak

Site Developer
Staff member
Administrator
Uhmm, Suule - i think you are in a wrong thread :p
 

Dragoneer

Site Developer
Staff member
Site Director
Administrator
yak said:
OS - FreeBSD
HTTP - Apache 1.3.34
PHP - 4.4.2 i believe
Well, these were the specs of the old server.

Don't know anyhing about the new one, except it is FreeBSD as well. It finally has /server-status disabled.
FreeBSD is being upgraded to 6.1 tonight. We found an issue which is causing some... problems. I don't know the exact nature of the problem, but the server is apparently "reverting" itself to older copies of FA. We're not sure why.

I dunno. If this were a IIS server I'd probably know what to do, but... LOL. I wouldn't run FA on a IIS. I have too much respect. =P
 

Vgm22

Furry/Scalie Of Mystery
RE:   FULL SYSTEM UPGRADE!

Dragoneer said:
yak said:
OS - FreeBSD
HTTP - Apache 1.3.34
PHP - 4.4.2 i believe
Well, these were the specs of the old server.

Don't know anyhing about the new one, except it is FreeBSD as well. It finally has /server-status disabled.
FreeBSD is being upgraded to 6.1 tonight. We found an issue which is causing some... problems. I don't know the exact nature of the problem, but the server is apparently "reverting" itself to older copies of FA. We're not sure why.

I dunno. If this were a IIS server I'd probably know what to do, but... LOL. I wouldn't run FA on a IIS. I have too much respect. =P

Could you give us a run through of what's been done and what's going on? I know a lot of peeps would like to know, including me.
 

Suule

Member
yak said:
Uhmm, Suule - i think you are in a wrong thread :p

Not really. I'm summing up all what's been said on the issue so far :3

Dragoneer said:
FreeBSD is being upgraded to 6.1 tonight. We found an issue which is causing some... problems. I don't know the exact nature of the problem, but the server is apparently "reverting" itself to older copies of FA. We're not sure why.

You mean to older backups?
 
Can someone please put up a damned error message on the front page or something? With a link to this thread?

:? I feel like a broken record saying this over and over again.
 

benanderson

Banned
Banned
This explains why I can't get on FA... >.=.>

A new server(s) will be good, especially if your using a Xeon over a P4!

I predict uber speed-ness in the future! ^.=.^
 

dragonfan

Member
i've been wondering why i couldn't get on either so now i know i hope the
upgrades will be better than the old ones
 

Firon

New Member
Nooooooo. Don't use Apache, for the love of god. :p Switch to Lighttpd and run PHP in FastCGI mode, and watch the loadavg drop...
 

Dragoneer

Site Developer
Staff member
Site Director
Administrator
dragonfan said:
i've been wondering why i couldn't get on either so now i know i hope the
upgrades will be better than the old ones
If you wanna browse head over to 8.7.49.240
 

dragonfan

Member
RE:   FULL SYSTEM UPGRADE!

Dragoneer said:
dragonfan said:
i've been wondering why i couldn't get on either so now i know i hope the
upgrades will be better than the old ones
If you wanna browse head over to 8.7.49.240

i've already headed over there now and it is quite fast compared to the old stuff and i like it
 

Dragoneer

Site Developer
Staff member
Site Director
Administrator
cesarin said:
I still say opterons would have done a better job, and they wouldnt have spitted heat enought to make your cofee :p

anyway theserver as it is, its loading preety fast I supose, even if its in maintenance mode, the first page usually took quite a bit to show, now is instantly.
Well, give me $900 and I'll get us dual 265 opterons. But, being as it is... I don't have that money, so... =P
 

Myr

Big Dragon
Great work on the system upgrade! :D It's working really well now. Checking thousands of submissions will be a breeze now that browsing loads so fast.

And if anyone complains about the site being too fast, I'm going to eat them...this dragon needs a good meal...mmm...*rubs belly* >^.=.^<
 
Uh, sorry to be a pest, but I just got the following errors while trying to login on the new server:

Warning: file(./templates/default_old/sidebar.htm): failed to open stream: No such file or directory in /usr/data/furaffinity/public_html/system/functions.sys on line 14

Warning: implode(): Bad arguments. in /usr/data/furaffinity/public_html/system/functions.sys on line 14

Warning: Cannot modify header information - headers already sent by (output started at /usr/data/furaffinity/public_html/system/functions.sys:14) in /usr/data/furaffinity/public_html/system/session.sys on line 17

Warning: Cannot modify header information - headers already sent by (output started at /usr/data/furaffinity/public_html/system/functions.sys:14) in /usr/data/furaffinity/public_html/login.asp on line 23
 

gushi

New Member
Firon said:
Are you guys using Apache or Lighttpd? (lighttpd ftw, 'n such, death to apache and it's 10x higher loads). I do hope you're running PHP5 in FastCGI mode (which works better on Lighttpd as well), at the very least...
What OS you using?

The OS is FreeBSD 6.1-amd64.

We're presently using php4. The codebase hasn't been tested on php5, although it may be in the future -- php has never been very good about not breaking things on upgrades.

Lighttpd could possibly be a consideration for the future as well. Right now, my experience is with running and tuning apache.

However, at the moment, changes need to be controlled, as any slowdown is another cause to start examining EVERYTHING that had been changed and start pointing fingers. Besides which, we've learned in the past that something that seems to work on a testbed server may simply not SCALE when it's being hit with the concurrent hits that the fandom delivers.

Without revealing too much, I can honestly say that we're about to embark on a few steps that won't as much add features as add stability, both to the codebase, as well as to the coders and admins :)

When dealing with a site that gets millions of hits a day, something as trivial as a symlink in a single directory can cause excessive load.
 

Firon

New Member
gushi: yeah, we had some migration issues when moving over to lighttpd and PHP5. A lot of things just... didn't work anymore. :p Half of it was the fact that everything used to be running as iso-8859-1 and we migrated to UTF-8, and the other half was that some of the stuff used apache-specific commands. If you do decide to migrate, you'll definitely need a testbed to work out all those kinks... But it's really worth it in the end, the load decrease is just incredible.
And if you do decide to run/test lighttpd, I highly recommend to build the latest version from source, and run PHP4/5 in CGI mode externally (using spawn-fcgi), instead of using the server's adaptive process spawning. And have at least two PHP parent processes as well, in case one decides to segfault (not that it should, but you never know) the site won't die. Though, if you use eAccelerator or any other cache system, you'll want to keep the parent PHP processes to a minimum, since each parent has its own SHM segment.
fyi, though eAccelerator says it doesn't work with PHP in CGI mode, or with lighttpd, it does, and does just fine. Our site gets a few million hits a day and it's working A-OK.
 

Dragoneer

Site Developer
Staff member
Site Director
Administrator
Torin_Darkflight said:
Uh, sorry to be a pest, but I just got the following errors while trying to login on the new server...
Try it again. I believe I fixed it.
 
Top