Support

Hi guys. I thought I was finally all "in the pink," since I've decided to move half my sites back to my more robust host, but just now backing one of them up (on that more robust host), I keep getting a server error 500, even with it set on "conservative" mode. I suspect I know why -- this site contains a fair number of largish JPGs, in the Joomla extension "JoomlaGallery" -- but I wanted to touch base with you guys, with the log an all, see if you agree or if it might be something entirely other than that, before I go off half-cocked and start fixing things that may or may not be broken -- I keep proving that I am certainly no expert. :D

So, here's the log file. Oh, and this site does have the "plus" version installed, so if it's a matter of needing to exclude those JPGs, I think the "plus" version provides for exclusions? Haven't really fiddled with a lot of the enhancements in the plus version, since the basic stuff in the "core" version had been working pretty well for me, even with having to have multiple back-up files (a bunch of those 1mb files) -- this particular site generated 49 of those before succumbing to the error 500 -- and yeah, the files are present when I view the dir in FTP, but the interface just says "failed", so I don't know how reliable the 49 files really are. But at 49+ mb, you can see it's a fairly big site, so maybe it's failing for the same reason the 25 mb site did, on the less robust host. I dunno, all this server-tech is kinda greek to me -- definitely not a programmer here! :D

Hope you can help me figure out why this keeps going bust, and how I can run it successfully (even if I have to make exclusions of the JPGs).

Thx!!
Andria JoomlaPack_Debug_Log-20100210.zip

It was chugging along, but it stopped in /galleries/vintage/60s70s. Let's exclude the gallery and see if that lets it complete. If it does, Nicholas may be able to tweak the magic numbers to get everything to back up.

Well, it turned out that several directories outside my Joomla installation (but in the same directory which houses that domain, because they're subdomains) were included. Once I excluded them, and all the JoomGallery pics, I was able to do a backup (actually in balanced mode, once all the big files and extraneous stuff was excluded).

Which turned out to be a very excellent thing for me, since I was this afternoon cleaning out the "Fantastico" area of this host, since there was a TON of stuff in there I had once installed, played with,but never really had a use for -- and when I deleted a Joomla installation that I thought was an old, outdated Joomla 1.0 installation (in this same dir/domain), it took out my NEW Joomla install. You see how my best intentions get me into all kinds of hot water. :x

So anyway, after smacking myself in the head 8 or 10 times and smoking a cigarette or 5, I finally got my host to clue me in to why I kept getting a server 500 error when I tried to run Kickstart and restore the site (something about public writes, I dunno, all that *nix stuff is SOOO greek to me!) -- so I was able to run Kickstart and get the site back, but of course then I had to go and manually remove all references to JoomGallery, just to get the darn thing reinstalled. So I got it back, got it reconfigured, and now, before uploading any pics, I'm doing a complete backup again, since I FINALLY have a workable site.

And I think after this, and getting the pics re-added, I will quit "fiddling about" with it before I manage to kill it again. :D

A really tired...
Andria

PS... the new backup just completed, 10 MB in 12 minutes, in balanced mode. I can live with it! :)

I missed that you had other sites included. :oops: I was scanning for the big file/big folder warnings.

The "public writes" means that you have permissions set higher than 755. If you have a file with 775 or 777 permissions, that will trigger a 500 error. This is a pain, but servers set up that way normally don't give you a lot of ownership and permission problems because the server is keeping it straight.

I'm not familiar with JoomGallery, but you shouldn't have to reinstall it after a restore. Does it keep a fixed path in the component's configuration file? Usually when an uninstall/reinstall makes it work, the real reason is the configuration is being updated by the process.

I'm going to PM you on something off topic.

Dale

I had to do all that manual stuff and reinstalling because I should have excluded the component, not just the dir. -- so when I restored the site, JoomGallery was like, half-installed, half not, and all f'ed up. :)

The way I *finally* did it, I got the whole component backed up, I just hadn't inserted any pics yet -- so, if I manage to kill the site again, I can Kickstart the whole site properly, and just re-add the pics -- the categories and settings will be in place, so re-adding the pics won't be a huge deal, if I need to do that.

I'm in the process of re-creating another site in Joomla/JoomGallery, originally created in plain HTML but I'm so tired of, everytime I take a notion to change the way a site looks, I have to totally re-create the site -- a *huge* pain. I'm hoping that putting the site into a Joomla interface will solve that problem, and I can update the look of the sites so converted without necessarily needing to update the actual content -- you know, the "new & improved" kind of marketing. ;) I'm thinking that I'll do the backup for it in a similar way -- get the whole site completed except for adding the pics, do the backup, THEN add the pics. Seems to be the best alternative until such time as I win the lottery and can have my own dedicated server with its own dedicated bandwidth. :o

The off-topic PM answered. ;)

Andria

The site template idea was one of the things that Nicholas had in mind when he started working on JoomlaPack. :D