Re: [Slashcode-general] Install Question

[Shane Z. <sh...@lo...>]

On Apr 15, 2008, at 9:49 PM, Ken Tiller wrote:
> Thanks Shane. I applied your patch and followed your instructions, but
> install-plugin hung on execution for a couple of hours, so I killed  
> it, and
> then followed the uninstall instructions linked from my first  
> message, and
> then rebuilt.
>
> This time all the steps followed through smoothly, and I installed  
> Tags
> along with the rest of the plugins at the install slashsite stage.
>
> I have now been able to start Apache, and start slash. When I visit  
> the URL
> of the slashsite (same as the one from the install-slashsite  
> questions),
> nothing displays. It's behaving just like a normal Apache.
>
> I have looked through the troubleshooting tips and can confirm:
>
> - Apache error log is clean (excepting File does not exist messages)
> - mod_perl was built with PERL_MARK_WHERE=1 EVERYTHING=1
> - httpd.conf does indeed include the slash conf file, which does  
> indeed
> include the site specific conf file
>
> The slash daemon has been running for 48 hours now.
>
> I feel like I'm missing something fundamental.

Well this sounds like an apache problem. The general troubleshooting  
rule is to remove any other includes, such that the only "thing"  
running under your apache 1.3 is slash.

Make sure the hostname you made up for the thing, that you told  
install-slashsite, is in your /etc/hosts or your internal DNS for the  
IP httpd's using.

Then start with the apachectl configtest, apachectl start.

You can save yourself some time, if, after doing an install-slashsite  
(and before you fire up apache) you do the equivalent to the following:

/usr/local/slash/bin/symlink-tool -u slash -U
/usr/local/slash/bin/runtask -u slash new_headfoot
/usr/local/slash/bin/runtask -u slash freshenup
/etc/rc.d/init.d/slash start
/usr/local/apache/bin/apachectl start

the new_headfoot && freshenup, by running those tasks by hand, ensure  
that the .shtml's are written to disk. So even if you have something  
wrong with your Perl/Apache setup, you can hit mysite.tld.com/ 
index.shtml and see a normally-rendered page. Which once you hit that  
then you'd know Apache and your machine are OK and start looking at  
other areas of your Apache configuration.

  Shane

PS you can also try the IRC channel for "insta-help" :)