RE: Problems on Setup

["Thompson-Jordan" <Thompson-Jordan@mindspring.com>]

1. You can ignore the warnings about 'index'. If you want to get rid of
them, edit those lines in minivend.

2. The files vlink and tlink are compiled C programs. Make sure that the
permissions are correct and that you have configured properly for cgiwrap.

3. You don't need access to httpd.conf and many hosting companies don't
give access. Minivend can be set up fine without it.

Christopher Thompson


> -----Original Message-----
> From: owner-minivend-users@minivend.com
> [mailto:owner-minivend-users@minivend.com]On Behalf Of Glenn A. Polsey
> Sent: Saturday, July 31, 1999 7:12 PM
> To: minivend-users
> Subject: Problems on Setup
>
>
> ******    message to minivend-users from "Glenn A. Polsey"
> <gpmain@laspantry.com>     ******
>
> Hi the name is Glenn.  I have got through the setup of Minivend about 5
> times, hoping something will work.  I am installing as a virtual hosting
> user on an Apache system with Linux. I have access through telnet (if
> this means anything).
>
> Now the problems:  (This is long)
>
> The setup runs into problems at the end of the setup when it asks to
> start minivend. This is what is from the log I created.
>     Start the MiniVend server? [yes]
> Apparently no MiniVend daemons were up -- no PID files.
> Ambiguous use of index => resolved to "index" => at
> /home/laspantry/mvend/lib/Vend/Parse.pm line 145.
> Ambiguous use of index => resolved to "index" => at
> /home/laspantry/mvend/lib/Vend/Parse.pm line 325.
> Ambiguous use of index => resolved to "index" => at
> /home/laspantry/mvend/lib/Vend/Parse.pm line 397.
> CyberCash module found (CyberCash 2).
> MiniVend V3.14
> Configuring catalog simple...done.
> MiniVend server started in INET and UNIX mode(s) (process id 11933)
>
> The front page to the simple demo comes up in a browser. From there to
> access the noframes start of the store I get:
>
> Internal Server Error  (500)
>     The server encountered an internal error or misconfiguration and was
> unable to complete your request.
>
> I had run across some info from my virtual hosting about how to check a
> cgi script. I checked the simple.cgi. It was in binary form. If I
> understand correctly, a cgi file has to be run as ASCII.
>
> 1.    So why did Minivend change the vlink file (simple.cgi) to a binary
> file or should it have?
>
> I copied the vlink.pl from the Mvend/src directory and copied it to the
> cgi-bin directory and renamed it as simple.cgi. Ran the html from
> browser and still got the same message.
> I also ran a test from the telnet side using the args: "perl
> simple.cgi"  I got the message: (after I'd changed files)
>          "Too late "-T" option at simple.cgi line 1"
> 2. What is the "-wT" for in the file? I deleted this from the simple.cgi
> and got after the test that Minivend was very busy and try again. Any
> thoughts here.
>
> 3. In a vritual hosting side, how does one set up the httpd.con?  The
> best I could figure from someone else on this list is:
>         for my setup----  /home/laspantry
>
> Any thoughts and solutions to these points?
>
> And lastly just a few lines snipped out of the local error file:
>
>         'Server.pm:3',
> "Error reconfiguring catalog %s from running server (%s)\n%s",
>
> 'Server.pm:4',
> "INET mode error port %s: %s\n\nContinuing in UNIX MODE ONLY\n",
>
> 'Server.pm:5',
> "INET mode server failed to start on port %s: %s",
>
> 'Server.pm:6',
> "SERVER TERMINATING",
>
> 'Server.pm:7',
> "error '%s' from select.",
>
> 'Server.pm:8',
> "Died in select, retrying: %s",
>
> 'Server.pm:9',
> "Can't fork: %s",
>
> 'Server.pm:10',
> "Runtime error: %s",
>
> 'Server.pm:11',
> "Runtime error: %s",
>
> 'Server.pm:12',
> "Died in server spawn: %s",
>
> 'Server.pm:13',
> "Died in housekeeping, retry.",
>
> 'Server.pm:14',
> "STOP server (%s) on signal TERM",
>
> 'Server.pm:15',
> "START server (%s) (%s)",
>
> This was not all but a snippet of the problems listed.  Well any
> thoughts on how to get past the first page?
>
> Thank You,
> Glenn Polsey
> Laspantry.com
>
> -
> To unsubscribe from the list, DO NOT REPLY to this message.
> Instead, send
> email with 'UNSUBSCRIBE minivend-users' in the body to
> Majordomo@minivend.com.
> Archive of past messages: http://www.minivend.com/minivend/minivend-list
>