UBB.threads PHP Forum Software Community Forums UBB.classic UBB.classic 6 Support cp.cgi can't find vars_config.cgi

Hi all,

New to UBB and trying to get it to work on IIS. My site is setup under IIS version 5 as a virtual directory to another server (the whole site is a virtual directory). I installed Perl and it works great. When running the cp.cgi file it tells me it cannot find the vars_config.cgi file. It complains about the path. If I enter the path as just /cgi-bin/ it doesn't work even though that is where the vars files are. I ran ubbclass_test.cgi and it shows that the vars files exist under the cgi-bin folder. Is there a problem using a virtual directory with the cp.cgi setup file? Is there a way around this?

Thanks for you help!

Hi Havoc -

You should probably contact your host and ask about the absolute path to your cgi-bin - then try using that, and let me know how it goes. <img src="https://www.ubbcentral.com/boards/images/graemlins/smile.gif" alt="" />

I am the host :-)

The reason the whole virtual directory exists as a site is because we are using a product called Macromedia Contribute to have users update the site. Here is some more generic information if it helps

site files exist on \server1contributeoverdrive

the vars files are on \server1contributeoverdrivecgi-bin

the actual web site (remember it is a virtual) is on one of our IIS servers. There are no actual web files there, they are all on server.

Thanks for any help that you can give me.

Did you map that drive so it can be found across the network?

yes, but it doesn't seem to have any effect. I still get the same error that it doesn't appear to be the right folder. Could there be a problem using a virtual directory?

For your path to work across servers you'll need to map the folder to the server running IIS. This will mean your path will be something like:

p:contributeoverdrivecgi-bin

(with "p" the drive letter you used when mapping the folder, use whatever letter you like <img src="https://www.ubbcentral.com/boards/images/graemlins/smile.gif" alt="" /> ) and the url would then be http://www.yoursite.com/cgi-bin/


Be sure the shared folder has the correct permissions as set out in the install instructions, as well. <img src="https://www.ubbcentral.com/boards/images/graemlins/smile.gif" alt="" />

Allen uses "p:" the rest of us use "drive:" or "x:" <img src="https://www.ubbcentral.com/boards/images/graemlins/wink.gif" alt="" /> ...

With the UBB it doesn't like using "\computernamepathtofiles" it prefers to use a map like "x:pathtofiles" as mapped.

Please be aware that running UBB over network mounts is not a supported configuration.

Please use only physical drives in the physical server.

Oh, and always use forward slashes, i.e. x:/path/to/files/

<img src="https://www.ubbcentral.com/boards/images/graemlins/smile.gif" alt="" />

Oh yeh, it's forward slashes it didn't like :slaps head: it's like Adobe products on a mac, it woudln't know what to do with a backslash if it came up and decked the crap out of it...

Then what do you do when you have a web server farm handling all the traffic to the site?

You should arrange for only one machine to handle all traffic to the board. Setting up a subdomain and pointing it at one particular machine would probably be the easiest approach.

If you are using Apache, you could probably use mod_proxy (or something like it) to pass connections through from a mount point to a specific machine internally.

(The main reason we do not support this configuration is due to the generally poor file locking (and poor file performance) that comes with most network mounts. UBB.classic is tied directly to the filesystem. If a lock failure were to occur, data could easily become corrupted. In addition, the latency introduced by the network would only decrease performance, which is pretty much the exact opposite of what load balancing is trying to achieve, after all. <img src="https://www.ubbcentral.com/boards/images/graemlins/smile.gif" alt="" /> UBB.threads is much better suited to running in a load balanced environment, as it only has to speak to a single instance of MySQL over the network.)