::background music = theme from The Twilight Zone
What a strange evening I've had.
Been playing around with my brandy new vps. Fun
learn
ing
experience. It's the
Ubuntu
7.10 server based on
Debian
, so it's very much like my dev virtual here on the home pc.
Got things going my way with the email, ftp server, mysql, all the goodies I need/want.
Put up a nifty little intro page as the index.
php
. Things looking good.
This afternoon I decided to install a SMF forum. So, I did so. Went pretty well I thought. The docs at SMF gave a good list of the changes needed for
php
.ini. Went to the admin page and set things up, you know, setting permissions and adding sections. Pretty nifty.
I thought.
I tried to access the forum without my cookie. Just to see what the default login page looked like. Guess what? 403 forbidden. WTF?
So off I go to the SMF forum to get the low down on the fix. Shittah. The gurus over there say that there is a problem with a module called mod_security.c. So, I opens up a blank .htaccess and paste in their remedy. All fixed up, right? Not on your sweet ass!
Now I've got a 500 internal server error. WTF? X 2 = wtf wtf?
Back to the SMF forum. Not much in the way of help there. So, I go back to my box and remove the fix in .htaccess. Back to a 403 again. Well, says I, that's a permission prob. I hack around with chown for a while. Back to the index page. Still 403. Just on the off chance, I changed the url from www.mysite.com to mysite.com. Up pops the
Apache
default page. WTF?
Open up .htaccess again and post the old remedy in there.
Options +FollowSymlinks
RewriteEngine on
rewritecond %{http_host} ^example.com [nc]
rewriterule ^(.*)$ http://www.example.com/$1 [r=301,nc]
Ha, says I, gotcha now big boy. El wrongo. Now I'm back to the 500 error again.
::increase the volume of background music::
I decide to let the server tell me what's going on so I go read the
apache
log. Guess what? Found a whole bunch of this: "caught SIGWINCH, shutting down gracefully". Gooogled around a while for what that means (still don't know) and how to fix it.
One site had a reasonable sounding solution:
sudo apt-get remove --purge
php
5 lib
apache
2-mod-
php
5
then reinstall with
sudo apt-get install lib
apache
2-mod-
php
5
His comment was "Bingo. Works fine now". I cry Bull Shit. It don't work for this old man. Upon trying the reinstall I got a message from hell. "Your
apache
configuration is like a pool of putrid snot lying on a dung heap and we ain't re starting it. So there."
Just exactly what I wanted to hear. I tried another removal and re install of the
php
5 package. Seemed like it went thru fine, but didn't change the results at all.
In desperation (it's been like six hours now) I tried my old Windoxe trick. Re boot the whole shebang. Dint worky.
So where are things now? Dabbed if I know. I came over here to cry on your shoulders. Guess I'll delete the whole mess and start over again. Sigh....
I don't <>know> if it is a problem with the SMF 2.0 beta thingie, but I believe it is.
If I decide to go back with SMF, I think I'll try to find one of the earlier versions.
I bare my backsides and smile. Once again.
Ratz. Big farking ratz with tails this...............farking long.