Gossamer Forum
Home : Products : Gossamer Links : Discussions :

2.0.2 under speedy problem

Quote Reply
2.0.2 under speedy problem
Alex,

I tried to upgrade the FAQ site, just updating the cgi/perl scripts by running the install program, saying N to templates and config, and Y to scripts.

It all went to poop.

ConfigData.pm was deleted, and not rewritten, on a second try, install.cgi went into an endless loop (because of that) and I ended up having to install the whole site again from scratch.

I don't know if this was a random thing, or if it was a problem under Speedy, but it was a problem.

A non-speedy install went without a hitch.

I have one other speedy install to try, but I'll wait til much later to try it, when I can afford reinstall the site.



PUGDOGŪ Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
Quote Reply
Re: 2.0.2 under speedy problem In reply to
Hi Pugdog,

Ack. The install.cgi wasn't under speedy though? It was using regular perl?

Cheers,

Alex

--
Gossamer Threads Inc.
Quote Reply
Re: 2.0.2 under speedy problem In reply to
Yes, the install script was running under perl.

I've been too busy to try the speedycgi install again, on a different site, but maybe tonight or tomorrow I'll see if it's repeatable, or if it was a one-time glitch.

It was the ConfigData.pm causing the problem, it was '0' bytes after the install, and that was what was doing it. This happened 2x, until I did a completely new install.

More later.

PUGDOGŪ Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
Quote Reply
Re: 2.0.2 under speedy problem In reply to
Alex,

I just upgraded another site, one on a hostpro virtual server (their paths create a real problem since the user and server see the server differently!!), and I just hit the '0' byte config problem again.

Everything was working ok, I ran the upgrade program -- update config N, update template N, update perl/cgi Y.

And ended up with a zero byte config. I had (fortunately) made a copy of the 2.0.1 ConfigData.pm and just copied it over changing the 2.0.1 to 2.0.2, and it worked. I didn't try to get into the whole re-install thing.

But, this is now _NOT_ on my servers, and with virtually unmodified (only plug-ins) installed setup, so it has to be something not of my doing (although I did install both copies... )



PUGDOGŪ Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum