Does this still happen with 3.0.6 ?
Thread Starter
Nick
(@ncrawford)
Yes – so I just tried updating the default WP themes, and got the same error. Problem must be on my end, although I’m not sure what.
Thread Starter
Nick
(@ncrawford)
Read that. Not a space issue. I’m self-hosted with 900+ GB of space free. Also looked for the mbstring.func_overload = 7 and it was already commented out (albeit it was = 0). Fresh installation of apache/php/WP, so I’m wondering if there’s a permissions issue somewhere…I have no problems auto-downloading/installing new themes/plugins, though.
Reports are:
http://wordpress.org/support/topic/incompatible-archive-pclzip_err_bad_format-10?replies=36
That your hosting server needs to increase the available space you have.
Sometimes this can occur with your hosts temp directory / inode being full.
Either or, it’s a situation where you need to contact your hosting.
Thread Starter
Nick
(@ncrawford)
Just double checked and no longer can install new themes. I could before, though…going to have to track down what system changes I made in the past little bit.
Nick:
Is this a VPS that you have root on, by any chance?
Try bumping your PHP mem limits. Also, check for SELinux.
Thread Starter
Nick
(@ncrawford)
increased php mem from 128 to 256. Not sure about SELinux other than a quick description of what I googled. (Yes, I have root access). Running Open Suse 12.1
What’s in /etc/selinux/config?
Thread Starter
Nick
(@ncrawford)
linux-nick:/etc/selinux # ls
semanage.conf
In that file, only uncommented lines are
module-store = direct
expand-check=0
Thread Starter
Nick
(@ncrawford)
I’m thinking it’s a file permissions issue – but the apache user (wwwrun) has full permissions for the entire WP directory.
I’m still betting on the temp directory ;/ the partition could be full – of course I know diddly squat on the subject 😉
Thread Starter
Nick
(@ncrawford)
My install is not standard in that everything is one partition (no separate tmp partitions). This is because of the way I set-up software raid mirroring.
Thread Starter
Nick
(@ncrawford)
Sigh. What a noob move. It was giving this error because the Zips WERE invalid – they were HTML files due to the Firewall blocking the download. =\ Realized this when I manually tried to run a wget on the zip file, then “zip xxxx.zip”
