Tony

The process of verifying the integrity of the raid array is still ongoing. Unfortunately it is causing some slowness on the server which we unfortunately cannot correct. This is a necessary step in maintaining the integrity of the data on the server.

Should be back online now and hopefully stay that way.

The /home partition just went to phase 2 of the fsck and is now checking the directory structure. Hopefully should be done soon.

Still running the fsck at this time.

We're going to play it safe and run a fsck on all the other partitions as well as they're quite small in comparison to /home . It will still take some time we'll update once we have more information.

We're going to be running a fsck on the /home partition as we are unable to get the partition to not go read only. This unfortunately means the machine may be down for up to an hour. Nothing we can do to solve this unfortunately as we assume something with one of the drives caused the issue but it's not something we can correct without running a fsck. This is one of the cases where the down time is necessary for the health of the system and the data the machine has. We are also continuing to investigate the raid itself.

We're still working on it. For the time being the server can serve requests but you'll be unable to add new data until we resolve the underlying cause of the file system issues.

Read only once again. We're investigating some weird errors coming from the raid card.

The machine is back online and serving requests once again. It may be slightly slower than usual for the next 10 minutes while it rebuilds caches in memory for various applications.

The saturn server has gone off line as of 8:36 PM CDT we are currently investigating the problem. We believe it may be related to the file system of the home directory going read only. We will update this once we have more information.

On Thursday July 16th we will be upgrading the MySQL version of the Jupiter server to 5.0.81 from 5.0.77 between 1:00 and 1:30AM EDT. We do not estimate that it'll take 30 minutes to do we will just be doing it during this window. We estimate there will be 1 minute of MySQL down time in order to restart the service to complete the upgrade. There may be none at all we're just giving an estimate that it could be 1 minute. The reason for this upgrade is to stay on top of the latest versions available to us through cPanel. Date: 07/15/2009 Start time (EDT): 1:00am End time (EDT): 1:30am Duration: 30 Minutes Estimated Down Time: 1 Minute

On Wednesday July 15th we will be upgrading the MySQL version of the Titan server to 5.0.81 from 5.0.77 between 9:30 and 10:00PM PDT. We do not estimate that it'll take 30 minutes to do we will just be doing it during this window. We estimate there will be 1 minute of MySQL down time in order to restart the service to complete the upgrade. There may be none at all we're just giving an estimate that it could be 1 minute. The reason for this upgrade is to stay on top of the latest versions available to us through cPanel. Date: 07/15/2009 Start time (PDT): 9:30pm End time (PDT): 10:00pm Duration: 30 Minutes Estimated Down Time: 1 Minute

intangible goods are not covered under buyer protection. You should win 99.9% of all disputes unless their bank reverses it or they do a credit card charge back. If they do win nothing you can really do but if you find them running your software on their site send a DMCA to their host and keep doing it until they stop running the software.

It was probably a combination of cPanel and the 64bit system. Basically we could install it but never integrate it properly it just would not work. Unable to setup configurations properly and such. Just not something interested in exploring at this point. Last time I did one there were issues with the triggers and stored procedures. Was an old old version though Except all the cPanel integration breaks. So we're sticking with what we have not going to go outside of it at this point.

Basically giving you links to phpinfo files there are reasons a lot of people disable the ability to generate them at all (we don't do that). As for PostgreSQL the problem with them as I stated is they provide no way to even upgrade. You get a version you're stuck with it. You want to upgrade then you dump all your data and import it again. Not exactly ideal for a shared hosting environment. Data has to be inserted in a certain order there is no guarantee that happens again when going back. Also the fact that you'd have down time associated with it. This explains why very few have latest versions ever. Right now the latest version is actually 8.4 but I doubt anyone is running it. We'd have numerous issues getting 8.3 to run in our 64bit systems (ran fine in 32bit). So we choose to use the CentOS distribution version which is 8.1 with all fixes backported to it. We choose to use a version that works over nothing at all. So we can maintain most things MySQL, PHP ect. but PostgreSQL is a nightmare to do unfortunately. Someone wants 8.4 we'd have to say to an entire server we're going to dump all data currently then import again and hopefully it goes back in order! Everything else you upgrade and you might worry about incompatibilties only not the fact that you may have broke everything switching versions. For reference their guide to upgrading between versions: http://www.postgresql.org/docs/8.4/static/install-upgrading.html MySQL for example says you may have issues make a backup. Not you cannot even attempt to upgrade without re-importing data.

You can compile any PDO module through PECL which makes a .so which is then just added to the php.ini file. We run the latest available in our distribution as there have been issues with 8.3, our cPanel setup and our 64bit systems. So we're running the CentOS distribution back ported version as it actually works properly. We will not be upgrading any machines to 8.3. The fact is PostgreSQL has a very poor upgrade system last time I checked. The solution is to just dump all DB's then import them in again which is just insane to do in a hosting environment. So that's why cPanel support is poor at best (you install it then it maybe works unlike MySQL which they maintain the versions). So we stick with CentOS version which will work as far as upgrades for security issues only. So Cody is mistaken we no longer run 8.3 after all our systems became 64bit. It's not information we want to give to someone who is not a customer of ours. If anyone trying to sell you on our hosting they should not have done that. You asked if it was there I provided an image of it. Our PHP is compiled with everything that is compatible out of the box including PDO, MySQLi ect. ect. Past that we load the odd PECL module when users request them and there is no risk of causing issues. Compile line: './configure' '--enable-bcmath' '--enable-calendar' '--enable-dbase' '--enable-exif' '--enable-ftp' '--enable-gd-native-ttf' '--enable-libxml' '--enable-magic-quotes' '--enable-mbstring' '--enable-pdo=shared' '--enable-soap' '--enable-sockets' '--enable-wddx' '--enable-zip' '--prefix=/usr/local' '--with-bz2' '--with-curl=/opt/curlssl/' '--with-curlwrappers' '--with-freetype-dir=/usr' '--with-gd' '--with-gettext' '--with-imap=/opt/php_with_imap_client/' '--with-imap-ssl=/usr' '--with-jpeg-dir=/usr' '--with-kerberos' '--with-libdir=lib64' '--with-libexpat-dir=/usr' '--with-libxml-dir=/opt/xml2' '--with-libxml-dir=/opt/xml2/' '--with-mcrypt=/opt/libmcrypt/' '--with-mhash=/opt/mhash/' '--with-mime-magic' '--with-mysql=/usr' '--with-mysql-sock=/var/lib/mysql/mysql.sock' '--with-mysqli=/usr/bin/mysql_config' '--with-openssl=/usr' '--with-openssl-dir=/usr' '--with-pdo-mysql=shared' '--with-pdo-sqlite=shared' '--with-pgsql=/usr' '--with-pic' '--with-png-dir=/usr' '--with-pspell' '--with-sqlite=shared' '--with-tidy=/opt/tidy/' '--with-ttf' '--with-xmlrpc' '--with-xpm-dir=/usr' '--with-xsl=/opt/xslt/' '--with-zlib' '--with-zlib-dir=/usr' '--with-litespeed' [/CODE]

Screen shot: [ATTACH]32[/ATTACH] Click on it for a larger version (silly vbulletin)

Not a single server has pdo_pgsql installed on it currently. I know it'll install fine since we have pdo_mysql and pdo_sqlite are already loaded on them and both are PECL modules which makes them easy to install.

We run PDO on all our servers by default and as far as the pdo_pgsql it's not installed by default but we could easily install it as the PDO support is already there and pdo_pgsql is just a PECL extension. As for phpinfo outputs we do not provide them as there is no guarantee that every server is identical due to some PDO extensions being different. So in your case once you signed up and were assigned a server you could check the server you're on and if it's not there make a ticket and we can add it.

The system we use is a paid solution so a lot of things are just not possible. 1) Not an option within the system 2) May be possible by modifying templates it may not be as the data may not be there. Either way we stay clear of modifying it besides the header and footer as things could break otherwise on each update.

Well virtual goods are not covered by buyer protection. If you tell Paypal that in a dispute you should win it almost every time. We still lose some or have a charge back but it's just something we deal with. It's not like every user who signs up goes and disputes the payment.

I'm on my second logitech access keyboard. I have a whole box of them so I'm never running out. I'm resistant to new keyboards I like the noise the keyboard makes.

The chattr is used to protect it from changes happening such as a cPanel update or whatever. You're right about it being on a cron though once a day stats run for each user on each server.

You could install http://piwik.org/ which is an alternative to analytics. The one negative is you're now doing the processing of the stats which obviously adds load to the server. There might be places which offer free piwik hosting but if you're scared of google probably be the same about any of them.

Google analytics is better than webalizer or you could ask for us to do it but please explain the situation entirely it's highly unlikely I'd handle it so explain the reasoning and all of that.