I have been running this fine on outside servers via ftp upload. I decided to bring it in house and host using my iMac and OS 10.2/Apache. I have my site set up OK, and I also have a very complicated perl script installed and running - a News Updater. So, I know my stuff is set up correctly. I installed the UBB601 per instructions- just dragging the files into the correct places, then chmod-ing them all to the correct permisions. Once I was done, I tried to call the cp.cgi script and got the 500 Internal Server Error. I know this usually means the path to perl is wrong (it's not), or the permissions are set wrong. I then decided to run that ubb6_test.cgi script comes with the program. I get the same exact error when I try to run that. I even set it's permisions to 777, still get the 500 error... Does anyone have any idea why this would be? Has anyone set this up locally on an OSX machine? Like I said, I have other scripts running- with the same path to Perl, etc. Is there a section for OS X instructions? Any help would be greatly appreciated!
Check the Apache error log (/private/var/log/httpd/error_log by default), as it often provides useful errors.
If you're installing in a user directory, make sure that ExecCGI is enabled. There are a few hidden .htaccess files that can be a pain.
Do the hello.cgi and hello.pl files work?
For the record - we only know that versions 6.3.1 and higher can be safely installed on OS X, and the first version with "official" support will be 6.6, to be released later this summer. Prior versions are either untested or contain problems that may prevent them from working properly.
-- Charles Capps UBB.classic™ Developer Having problems? Open up a support ticket!
OK, I will look in the error logs when I get home tonight and post the results here. Thw page is running from the root, not a user directory- plus I have other scripts running just fine from the same place. As far as what versions will run on OS X, the script really has nothing to do with OS X. It is running on Unix- and Apache, just like any other server. I dont have the hello.cgi script, but again- my other scripts run fine, so it's a little wierd. I am running the site on port 8000...maybe that has something to do with it??
I have definitely sucessfully installed UBB.classic (post-6.3) on Mac OS X 10.2.x client. Unfortunately, I don't believe I have a UBB 6.0.x archive anywhere that I can try. Sorry!
(2)No such file or directory almost always means that either the path to Perl is incorrect, or the script wasn't uploaded in ASCII. But you didn't upload the script, you copied it right onto the machine.
When unzipping the archive (assuming you used a .zip), did you use the -a switch? Otherwise, did you ensure that the file line endings are correct?
-- Charles Capps UBB.classic™ Developer Having problems? Open up a support ticket!
That explains that then. They surely have the wrong line endings. You can either use the unzip utility at the command line via the terminal, or use another utility to convert the line endings from DOS to Unix format.
If you don't have any such utilities, I'd look at enabling the FTP service on the server (if disabled), then performing a traditional install via FTP (even though it's a local machine)
-- Charles Capps UBB.classic™ Developer Having problems? Open up a support ticket!
Well, It doesnt seem to have anything to do with the unzipping. I unzipped on another machine- one I used before to upload to a server from. I guess it has to do with uploading. Maybe by dragging the files locally, they don't "upload" as ASCI.
I am not sure what I need to do to ftp in. I activated ftp in the system prefs, but cant log in. I am on port 8000, so when I try to ftp in, I use my address, the correct log/pass, and non-standard port 8000...any ideas?
OK...I ftp'd in, was able to upload everything correctly. I was very excited to see the UBB set-up pop up.
Now, here is another problem...
THe cgi-bin in OS X Apache is called CGI-Executables. Most scripts recognize this as "cgi-bin" when the scripts are run. UBB does not. When you set up the variable (paths) in the initial set-up, UBB detects the CGI paths as CGI-Executables. SO, when you then start to make accounts, etc- the URL is www.xxx.com/CGI-Executables/xx.cgi. This does not work- because it needs to be cgi-bin/xx.cgi.
I tried to go back to the initial set-up and changed all the CGI paths from CGI_Executabes to cgi-bin, but UBB wont let that happen- it says the path is wrong.
Now, what I am thinking (hoping), is that these paths are written to one of the cgi files, and I could go in manually and change them to the correct, workable cgi-bin.
Yep. That, in my experience, is a problem with the way Apache is configured in Mac OS X client.
There may be an easier way... But, what I've done in the past is modify the httpd.conf file (/etc/httpd/httpd.conf) to change the CGI-Executables to a new cgi-bin directory. You may have to edit it as "sudo" and then you will have to restart Apache to see the changes take effect (most easily done in X by just unchecking the web sharing box and re-checking it in the System Preferences' Sharing pane).
Possibly not the most elegant thing to do (especially if you have a complex httpd configuration), but it seems to get the job done. <img src="https://www.ubbcentral.com/boards/images/graemlins/wink.gif" alt="" />
Yea, I suppose I could do that. but I am afraid it would screw up my other script. I am also running Article Manager on the site, and it is already all set up. I am hoping that I could modify the vars_config.cgi file, but whenever I do, it brings me back to the initial set-up page again. I realize OS X is new and all, but maybe someone here from tech support could at least let me know if there is a way around this...???
Replace the vars_config file with a stock copy from the zip, and be sure to put members_test.cgi back in the Members directory... that will allow you to make a "clean" new installation with the right paths/URLs. (No members, topics, forums, etc, will be lost.)
-- Charles Capps UBB.classic™ Developer Having problems? Open up a support ticket!
Right, I know that. Like I said, when I replace that file, it does send me back to the first set-up screen. Then when I put in "cgi-bin" instead of "CGI-Executables" for the cgi paths, it says the path is wrong. UBB wants to see the exact path- which is "CGI-Executables", but THEN when you start configure the UBB more, the path is wrong- because it is "CGI_Executables", and not cgi-bin!!
Have you changed your Apache configuration? By default, /cgi-bin is a ScriptAlias for the CGI-Executables directory, so there shouldn't be any problems whatsoever with getting to the scripts using it...
-- Charles Capps UBB.classic™ Developer Having problems? Open up a support ticket!
terrapinstation said that he/she is running "Article Manager" and doesn't want to screw up the existing scripts by changing the apache conf file. <img src="https://www.ubbcentral.com/boards/images/graemlins/frown.gif" alt="" />
However, I don't see a way around it... except possibly by using a symlink to the CGI-Executables directory. But I don't know how Apache would handle that.
However, I don't see a way around it... except possibly by using a symlink to the CGI-Executables directory. But I don't know how Apache would handle that.
Yea, this is starting to get aggravating. The problem here is with the name CGI-Executables. Again, when UBB sets up- it uses this path:
/Library/WebServer/CGI-Executables
and wont accept a path with cgi-bin in the name. When I go to register- the URL is:
See, that doesnt work. But since the UBB had to be set up with that path, I am stuck.
I tries to modify the vars_config.cgi file manualy, after I made it through the initial set-up, but then every time the UBB calls the cp.cgi file, it reverts back to the initial login.
So, I hope this explains things better. All I want to know if there is something I can do within the realms of UBB set-up or modification od files that will fix this.
If not, I guess I will try to rename the CGI-Executables directory. I am hesitant because I dont want to screw anything up...
<img src="https://www.ubbcentral.com/boards/images/graemlins/smile.gif" alt="" /> Aha! Now that is the answer I was looking for! Works fine now. Thanks so much.
Now, does anyone know what I need to do within my httpd config so I can connect to my site without inputing the :8000 (I had to change the port due to port 80 being blocked)??
