[ic] undefined carts on upgrade
David_e at charter.net
Mon Dec 30 17:48:27 UTC 2013
----- Original Message -----
From: "David Etheredge" <David_e at charter.net>
To: <interchange-users at icdevgroup.org>
Sent: Monday, December 30, 2013 12:17 AM
Subject: Re: [ic] undefined carts on upgrade
> ----- Original Message -----
> From: "Josh Lavin" <josh at perusion.com>
> To: <interchange-users at icdevgroup.org>
> Sent: Friday, December 27, 2013 12:52 PM
> Subject: Re: [ic] undefined carts on upgrade
>> Quoting Gert van der Spoel (gert at 3edge.com):
>>> >> When putting back the old files, did you also replace cart.cgi with
>>> >> the old version? Or are you using the latest compiled version that
>>> >> came with your new install?
>>> >> Is this a staging/testing environment? If so it might help to comment
>>> >> out all but 1 catalog and see to get one of them working. There have
>>> >> been situations where issues sometimes happen in 1 catalog and
>>> >> cascade
>>> >> to the next, making it harder to debug.
>>> >> CU,
>>> >> Gert
>>> > You may have hit the nail on the head. It does appear that the
>>> > technician
>>> did copy the old cart.cgi as the files carry a 2007 date.
>>> > I will have to see if I can fine the right version and correct this.
>>> > Any suggestions as to the best way to replace the old files without
>>> > doing
>>> a complete re-install?
>>> Have a look in your interchange install dir, there should be a src
>>> and likely a vlink.something file (I assume you need vlink and not
>>> but my knowledge in this area is very rusty).
>>> With a bit of luck you can copy that one in place of your cart.cgi (make
>>> backup ;)).
>>> Keep in mind to do the chmod +s on the cart.cgi if I remember correctly.
>>> Else I think running ./configure in that src directory will create you a
>>> vlink/tlink file.
>> You don't need to switch to the src directory; just cd to
>> /usr/local/interchange or wherever your IC install is located, then do
>> That will compile the 'tlink' and 'vlink' programs in the src directory;
>> you can then copy the appropriate one (typically vlink) to your cgi-bin
>> as Gert described above, rename to your cgi script name (cart.cgi), and
>> then `chmod +s cart.cgi`.
>> Josh Lavin
>> Perusion -- Expert Interchange Consulting http://www.perusion.com/
>> ... ask me about job opportunities ...
> After a long struggle with the db files and a few other glitches,
> interchange is finally coming up but when I call the cart.cgi, I get a 500
> 500 Internal Server Error
> The request was not completed. The server met an unexpected condition.
> 22.214.171.124/~ezclang/cgi-bin/cart.cgi (port 80)
> Please forward this error screen to 126.96.36.199's WebMaster.
> Apache/2.2.26 (Unix) mod_ssl/2.2.26 OpenSSL/1.0.1e-fips
> mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/188.8.131.5235 Server at
> 184.108.40.206 Port 80
>>From the apache error.log I get
> [Mon Dec 30 00:52:17 2013] [error] [client 220.127.116.11] Premature end of
> script headers: cart.cgi
> [Mon Dec 30 00:52:17 2013] [error] [client 18.104.22.168] File does not
> exist: /home/ezclang/public_html/cgi-bin/sys_cpanel, referer:
> I do not understand where the sys_cpanel comes from?
> Did you recompile the vlink program as I described previously?
> How did you install Interchange?
> Are you running on a host with the cPanel control panel?
Yes, I actually did that twice.Interchange was installed manually from the
package as a shell operation.Cpanel is present but does not support or
include interchange. It was not used for any of the installation.
More information about the interchange-users