Hi all: This is not strictly SuSE related but..I have a number of web sites running on a managed server (FC1) using Mambo. It has been working fine for a long time but a few weeks back I suddenly got plagued with upload errors relating to pclzip. The support of the site is less than forthcoming as it is a root server and they are not experts on individual packages. Having trawled through various forums I suspect that it relates to the version of Apache and PHP that are out of synch? It is running 2.0.50 and 4.3.8 respectively. I suspect that the provider updated one or other of these for me but I'm not sure. I installed Mambo on my home machine running 2.0.53 and 4.3.10 and have none of these upload problems. In order to move forward on these packages I assume I would probably need to upgrade the OS to FC2 or 3. This would entail yum as it is a remote device and I'm not sure this would work without bringing down the whole thing. They will do this for me but from scratch so I need good backups and to get all the sites back the way they were. probably easy but.. Any thoughts? -- De omnibus dubitandum
--- Paul Taylor <ptaylor@uklinux.net> wrote:
This is not strictly SuSE related but..I have a number of web sites
This has never stopped anyone in the past... :)
through various forums I suspect that it relates to the version of Apache and PHP that are out of synch? It is running 2.0.50 and 4.3.8
Maybe. But if the error is specific to pclzip, it is probably that alone causing the issues rather than, say, missing files from a bad upgrade of packages.
have none of these upload problems. In order to move forward on these packages I assume I would probably need to upgrade the OS to FC2 or 3. This
You could upgrade the OS, or you could try to find suitable versions of packages for the current OS version. Mind you, being FC, that might be quite a headache...
would entail yum as it is a remote device and I'm not sure this would work without bringing down the whole thing.
It's certainly possible, but you'd have to make sure of a few things, such as making sure the version of glibc was consistent for the packaged versions.
They will do this for me but from scratch so I need good backups and to get all the sites back the way they were. probably easy but.. Any thoughts?
So we're back to the backup scenario, Paul? Perhaps the "easiest" way is to rename your .php files to .txt, and wget the whole lot somewhere safe, allow your provider to fix their mistake, transfer your files back, and rename the .txt to .php. -- Thomas Adam ___________________________________________________________ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
participants (2)
-
Paul Taylor -
Thomas Adam