portland independent media center  
images audio video
newswire article portland metro

pdx indy hiccups - some posts lost

technical update
the pdx indy server suffered some technical difficulties last evening and overnight. some posts were lost in that process. a volunteer found and reposted a couple of them, but a few are just gone at this point, mostly comments added to other stories.

pdx indy technical volunteers will be doing some upgrading soon to handle this and other problems (such as the infamous "no story to tell" error). plans are still coming together. some support from the community might be helpful when those upgrades are ready to be implemented.

more updates will follow. please keep postin' and bein' patient!
Am I invited? 20.Oct.2002 13:30

Trilox

"some support from the community might be helpful when those upgrades are ready to be implemented."

Am I invited or are you only asking for help from people who are in opposition to my viewpoints?

invitations 20.Oct.2002 13:52

pdx indy volunteer

hey trilox -- that phrase about "support from the community" was a soft-pedal suggestion that support of a financial or otherwise nature might be necessary to help upgrade. if that turns out to be the case (we'll see), help from people who support the website and its mission would be free to contribute.

CNN.com may need help 20.Oct.2002 14:12

i only care to disrupt

maybe cnn.com could use some help "Trilox"

Ok, here contribution for consciences raising 20.Oct.2002 16:07

FWR

Ok, here contribution for consciences raising for bewildered Sys Admins...

First, get rid of ProgreSQL and replace it with MySQL. It works much better with PHP, and its free, there is more third party support, and its Open Source, so you can still claim you are defeating Microsoft (as if bill gates cares).

You need a better error trapping routine on the backend, I shouldn't see "Unable to allocate space, disk full" errors spew all over the screen. Even if I was the one who accidentally caused it..

Write it so it traps the error, and throws an exception so you can catch it and deal with it.

Move the database off of the webserver and put it on its own dedicated box. This will speed up things greatly.

Add some memory to both the webserver and the database server, and defrag your database disk.

Upgrade to PHP 4, it supports session variables and some other features you may find useful.

I know all of this takes time , and a little cash, but this is a practical matter. Holding hands in a circle or climbing a tree won't impress the computer setup you have.

And one more thing, if you are going to constantly expect people to post items in this Compost Bin Laden of yours, you should at least put a link on the front page so people could find it...

FYI 20.Oct.2002 16:42

FWR

Number of files uploaded: 1
Warning: Unable to connect to PostgreSQL server: FATAL 1: The database system is shutting down in /www/active-cvs/portland/shared/db_class.php3 on line 58

Cannot get a connection to postgreSQL database!
Warning: Supplied argument is not a valid PostgreSQL link resource in /www/active-cvs/portland/shared/db_class.php3 on line 1113

Warning: Supplied argument is not a valid PostgreSQL link resource in /www/active-cvs/portland/shared/db_class.php3 on line 1118

Warning: Unable to connect to PostgreSQL server: FATAL 1: The database system is shutting down in /www/active-cvs/portland/shared/db_class.php3 on line 58

Warning: Supplied argument is not a valid PostgreSQL link resource in /www/active-cvs/portland/shared/db_class.php3 on line 1113

Warning: Supplied argument is not a valid PostgreSQL link resource in /www/active-cvs/portland/shared/db_class.php3 on line 1118

Warning: Unable to connect to PostgreSQL server: FATAL 1: The database system is shutting down in /www/active-cvs/portland/shared/db_class.php3 on line 58

Warning: Supplied argument is not a valid PostgreSQL link resource in /www/active-cvs/portland/shared/db_class.php3 on line 1113

Warning: Supplied argument is not a valid PostgreSQL link resource in /www/active-cvs/portland/shared/db_class.php3 on line 1118

Warning: Unable to connect to PostgreSQL server: FATAL 1: The database system is shutting down in /www/active-cvs/portland/shared/db_class.php3 on line 58


Your article has been published - Please be patient while the front page refreshes.