RE: Upgrading from FreeBSD 6.1-Stable to Latest
Taking this thread a little further since it is right in line with my todo list for tonight. I currently have 6.1 installed on a Supermicro machine with two ata drives. There has been a major bug that causes frequent kernel panics which started at 6.0. The following build options seemed to help with quick rebooting and recovery. But of course this week the reboots aren't going to well and it is definately time to upgrade to 6.2-RELEASE (RELENG_6_2) in hopes that whatever is causing the kernel panics is software related and has been fixed. makeoptions DEBUG=-g options DDB, KDB, GDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS_KDB options WITNESS_SKIPSPIN options BREAK_TO_DEBUGGER,ALT_BREAK_TO_DEBUGGER options KDB_UNATTENDED options QUOTA options PMAP_SHPGPERPROC=601 options TCP_DROP_SYNFIN options SMP options IPFILTER options IPFILTER_LOG options IPFILTER_DEFAULT_BLOCK options IPFIREWALL options IPFIREWALL_VERBOSE options DUMMYNET options IPSTEALTH options HZ=2000 #optionsRESTARTABLE_PANICS options PANIC_REBOOT_WAIT_TIME=5 Will some of these options still work with 6.2-RELEASE or should I omit something here in order to use the 6.2 release properly? I am sure there are some since I am going from a 6.1 prerelease to a release. I am just not sure which ones should be omitted. I still want the capability of the machine rebooting unattended if a panic should occur. Here is some more info in case anybody sees anything that I don't regarding those panics. Never a single vmcore so I have found debugging quite useless. But of course I do understand that I have alot to learn about debugging. Not my forte. ### uname -a ### 123.domain.net 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Thu Apr 20 16:01:16 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM-KERNEL i386 ### dmesg.today ### Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-PRERELEASE #0: Thu Apr 20 16:01:16 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM-KERNEL Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3206.53-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf43 Stepping = 3 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,M CA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,P BE Features2=0x641dSSE3,RSVD2,MON,DS_CPL,CNTX-ID,CX16,b14 AMD Features=0x2010NX,LM Hyperthreading: 2 logical CPUs real memory = 2146893824 (2047 MB) avail memory = 2094931968 (1997 MB) MPTable: INTELLindenhurst FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0: Assuming intbase of 0 ioapic1: Assuming intbase of 24 ioapic2: Assuming intbase of 48 ioapic3: Assuming intbase of 72 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard ioapic3 Version 2.0 irqs 72-95 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface cpu0 on motherboard cpu1 on motherboard cpu2 on motherboard cpu3 on motherboard pcib0: MPTable Host-PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pci0: base peripheral at device 1.0 (no driver attached) pcib1: PCI-PCI bridge irq 16 at device 2.0 on pci0 pci1: PCI bus on pcib1 pcib2: PCI-PCI bridge at device 0.0 on pci1 pci2: PCI bus on pcib2 pci1: base peripheral, interrupt controller at device 0.1 (no driver attached) pcib3: PCI-PCI bridge at device 0.2 on pci1 pci3: PCI bus on pcib3 pci1: base peripheral, interrupt controller at device 0.3 (no driver attached) pcib4: PCI-PCI bridge irq 16 at device 4.0 on pci0 pci4: PCI bus on pcib4 pcib5: PCI-PCI bridge irq 16 at device 6.0 on pci0 pci5: PCI bus on pcib5 pcib6: MPTable PCI-PCI bridge at device 28.0 on pci0 pci6: PCI bus on pcib6 em0: Intel(R) PRO/1000 Network Connection Version - 3.2.18 port 0x2000-0x203f mem 0xdd20-0xdd21 irq 24 at device 1.0 on pci6 em0: Ethernet address: 00:30:48:84:f0:04 em1: Intel(R) PRO/1000 Network Connection Version - 3.2.18 port 0x2040-0x207f mem 0xdd22-0xdd23 irq 25 at device 2.0 on pci6 em1: Ethernet address: 00:30:48:84:f0:05 uhci0: UHCI (generic) USB controller port 0x1400-0x141f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: UHCI (generic) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: UHCI (generic) USB controller port 0x1420-0x143f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: UHCI (generic) USB
Upgrading from FreeBSD 6.1-Stable to Latest
What is the _easiest_ way to upgrade from a FreeBSD 6.1-stable install to a 6.2-stable install? I can't run freebsd-update because it doesn't know about -stable, and I'd prefer to avoid doing a buildworld because of the time. Any suggestions? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading from FreeBSD 6.1-Stable to Latest
On Tue, 13 Mar 2007 20:24:50 -0700 Don O'Neil wrote: What is the _easiest_ way to upgrade from a FreeBSD 6.1-stable install to a 6.2-stable install? I can't run freebsd-update because it doesn't know about -stable, and I'd prefer to avoid doing a buildworld because of the time. Any suggestions? Get the apropriate CD iso image and do a binary upgrade: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200703/ PS. I didn't do it myself, it's only an assumption. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6
Hello,
I'm having trouble building tcl84. These issues did
not seem to exist until I updated the ports tree and
world the other day
Heres the basic stuff:
FreeBSD 6.1-STABLE #6 Sun Sept 17 22:03:38
is what uname -a spits out ports were updated right
before the system source update.
make.conf has
CFLAGS=-pipe -O2 -fno-strict-aliasing
CXXFLAGS+=-O3 -fno-strict-aliasing
COPTS=-pipe -O2 -fno-strict-aliasing
CPUTYPE=pentium4m
MAKEOPTS=-j5
my ports.conf has:
.if ${.CURDIR:M*/lang/tcl84}
WITH_THREADS=YES
BLACKHOLE=YES
.endif
ports.conf is loaded into make.conf with this
.if ${.CURDIR:M/usr/ports*}
include /foo/bar/ports.conf
.endif
I use it to make configuring ports easier and more
standard then the portupgrades configuration method.
I initially attempted to rebuild the system with
portupgrade -afR
but found tcl84-threads hanging on socket test 7.4
although it says every single test fails. So because
my system was a little messed up due to having half of
gnome-2.12.x and gnome-2.14.x because of updating the
ports tree halfway through the build to start because
of a then broken port... and now because of a hlf
rebuilt system. I decided to do a pkg_delete -a and
start over from scratch to see if my configs would
work right. The port still halts on socket 7.4 test,
and halted at one point for 8+ hours when I was off at
work.
on a tangent Xorg seemed to be busted after being
rebuilt and configured (X -configure) I did notice
something about drm in the kernel now is I915 support
in there now???
I've read socket test hangs could be because the
tunable net.inet.tcp.blackhole is enabled but it is
not on my system. That is why I added BLACKHOLE=YES to
my config to try to disable the tests as the Makefile
suggests but the build seemed to ignore me.
then I starting getting these kernel panics. Once
while it was testing and the next time right after I
rebooted in to single user mode to assess filesystem
damage.
Fatal double fault:
eip=0xc0729c9c
esp=0xdc4fe00c
ebp=0xdc4feb78
panic: double fault
I suspect that my 2nd dimm banks memory controller has
finally shit the bed in my laptop, but post cause
maybe it is related. I'm not certain what a double
fault is exactly; not off a tennis court anyway...
I will see if I can find the reason for the double
faults by removing the likely unreadable memory stick
and attempt to update the source and ports trees and
see if that helps, but not before dumping my system to
tape.
any help would be appreciated.
-brian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6
On Thu, Sep 21, 2006 at 06:11:52PM -0700, backyard wrote: Hello, I'm having trouble building tcl84. These issues did not seem to exist until I updated the ports tree and world the other day Heres the basic stuff: FreeBSD 6.1-STABLE #6 Sun Sept 17 22:03:38 is what uname -a spits out ports were updated right before the system source update. make.conf has CXXFLAGS+=-O3 -fno-strict-aliasing Don't do that, it can cause problems MAKEOPTS=-j5 Don't do that, it can cause problems kris pgpYJ9lxjmgGW.pgp Description: PGP signature
Re: TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6
--- Kris Kennaway [EMAIL PROTECTED] wrote: On Thu, Sep 21, 2006 at 06:11:52PM -0700, backyard wrote: Hello, I'm having trouble building tcl84. These issues did not seem to exist until I updated the ports tree and world the other day Heres the basic stuff: FreeBSD 6.1-STABLE #6 Sun Sept 17 22:03:38 is what uname -a spits out ports were updated right before the system source update. make.conf has CXXFLAGS+=-O3 -fno-strict-aliasing Don't do that, it can cause problems can you be a little more specific? I was just using CXXFLAGS+=-O3 before I thought the aliasing issues because of type casting could cause issues and so -fno-strict-aliasing was what you had to do to make optimization above level 1 work rigt. At least thats what reading about -fno-strict-aliasing seemed to get at with FreeBSD specifically. should it be CXXFLAGS+= dafaulting to O2 with no strict aliasing? given my CFLAGS=-pipe -O2 -fno-strict-aliasing MAKEOPTS=-j5 Don't do that, it can cause problems I know doing make -j5 buildworld or buildkernel or just about anything else would/used to puke things. But I haven't seen any issues with MAKEOPTS doing that. Perhaps until now? I know specifically make -j5 on the shell would cause the build to skip the build and fail on the install or skip the build of the objects and fail on linking the uncompiled library. kris dazed confused and ignorant... -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6
On Thu, Sep 21, 2006 at 06:29:52PM -0700, backyard wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: On Thu, Sep 21, 2006 at 06:11:52PM -0700, backyard wrote: Hello, I'm having trouble building tcl84. These issues did not seem to exist until I updated the ports tree and world the other day Heres the basic stuff: FreeBSD 6.1-STABLE #6 Sun Sept 17 22:03:38 is what uname -a spits out ports were updated right before the system source update. make.conf has CXXFLAGS+=-O3 -fno-strict-aliasing Don't do that, it can cause problems can you be a little more specific? I was just using CXXFLAGS+=-O3 before I thought the aliasing issues because of type casting could cause issues and so -fno-strict-aliasing was what you had to do to make optimization above level 1 work rigt. At least thats what reading about -fno-strict-aliasing seemed to get at with FreeBSD specifically. should it be CXXFLAGS+= dafaulting to O2 with no strict aliasing? given my CFLAGS=-pipe -O2 -fno-strict-aliasing Just use the defaults (which is currently the same as your CFLAGS). MAKEOPTS=-j5 Don't do that, it can cause problems I know doing make -j5 buildworld or buildkernel or just about anything else would/used to puke things. But I haven't seen any issues with MAKEOPTS doing that. Perhaps until now? I know specifically make -j5 on the shell would cause the build to skip the build and fail on the install or skip the build of the objects and fail on linking the uncompiled library. The base system is fine, but many ports of third party software fail to build (or the build misbehaves) with make -j. Kris pgpZjkWgO0Qov.pgp Description: PGP signature
Re: TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6
--- Kris Kennaway [EMAIL PROTECTED] wrote: On Thu, Sep 21, 2006 at 06:29:52PM -0700, backyard wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: On Thu, Sep 21, 2006 at 06:11:52PM -0700, backyard wrote: Hello, I'm having trouble building tcl84. These issues did not seem to exist until I updated the ports tree and world the other day Heres the basic stuff: FreeBSD 6.1-STABLE #6 Sun Sept 17 22:03:38 is what uname -a spits out ports were updated right before the system source update. make.conf has CXXFLAGS+=-O3 -fno-strict-aliasing Don't do that, it can cause problems can you be a little more specific? I was just using CXXFLAGS+=-O3 before I thought the aliasing issues because of type casting could cause issues and so -fno-strict-aliasing was what you had to do to make optimization above level 1 work rigt. At least thats what reading about -fno-strict-aliasing seemed to get at with FreeBSD specifically. should it be CXXFLAGS+= dafaulting to O2 with no strict aliasing? given my CFLAGS=-pipe -O2 -fno-strict-aliasing Just use the defaults (which is currently the same as your CFLAGS). MAKEOPTS=-j5 Don't do that, it can cause problems I know doing make -j5 buildworld or buildkernel or just about anything else would/used to puke things. But I haven't seen any issues with MAKEOPTS doing that. Perhaps until now? I know specifically make -j5 on the shell would cause the build to skip the build and fail on the install or skip the build of the objects and fail on linking the uncompiled library. The base system is fine, but many ports of third party software fail to build (or the build misbehaves) with make -j. Kris well I'll see if I have any better luck with the more conservative CXXFLAGS and the removal of -j5 from MAKEOPTS. I have a conditional build directive for the system build so I can update ports and sys separately as having SUPFILE and PORTSUPFILE set seems to update both whether I'm in /usr/ports or /usr/sys with a make update. If -j5 is safe for the FreeBSD build I'll cut Makeopts into that knob, I hope thats the right way to use that term... thanks -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Virtual hosts and PHP downloads: php5 and apache22 on FreeBSD 6.1-STABLE
-Original Message- From: John DeStefano [mailto:[EMAIL PROTECTED] Sent: 07 June 2006 01:19 To: [EMAIL PROTECTED] Subject: Re: Virtual hosts and PHP downloads: php5 and apache22 on FreeBSD 6.1-STABLE John, I have the same problem with a new install and asked the same question re php not working. One of the replys that I received was that the latest php port was broken and try the previous version. I haven't had chance to try that yet though. Rob Hi Rob, I'm hearing that too now as well... wish I'd realized it sooner. I wonder whether just reverting to an earlier version of PHP5 will be enough though, or if it will also require an earlier apache version... I guess we'll find out! Thanks, ~John John, PHP4 works fine with Apache22, as I understand it; it is just the latest port of PHP5 that the problem is with. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Virtual hosts and PHP downloads: php5 and apache22 on FreeBSD 6.1-STABLE
I upgraded my system from 5.4-RELEASE to 6.1-STABLE last week, and my web server immediately stopped serving PHP pages, where I had no problem doing so before. Instead of processing the PHP code on the server and displaying the result in a browser, browsing to any page containing PHP code resulted in a prompt to download the PHP page as a file. /usr/ports/UPGRADING mentions that PHP has been streamlined and must be recompiled to work with Apache and other packages. After deinstalling, configuring (where applicable), and reinstalling PHP5, php5-extensions, and apache2 to the latest versions, not only were PHP files not being served, but my web server was toast: Forbidden You don't have permission to access / on this server. I edited the new apache config file (now located in /usr/local/etc/apache22/httpd.conf) with my system information, including a DocumentRoot path. But when I started apache, I got some very peculiar errors: Warning: DocumentRoot [/www/docs/dummy-host.example.com] does not exist Warning: DocumentRoot [/www/docs/dummy-host2.example.com] does not exist Not only did I confirm beforehand that I had set the DocumentRoot path, and that apache was using the correct config file... but these dummy paths didn't exist in the config file! I learned eventually that a new apache directive splits out virtual host directives to a new include file (/usr/local/etc/apache22/extra/httpd-vhosts.conf). Then I learned after getting a server warning (NameVirtualHost *:80 has no VirtualHosts) that the syntax has been slightly modified, so that the IP/port value of each VirtualHost specification must match that of the NameVirtualHost directive (i.e., NameVirtualHost *:80 and VirtualHost *:80). Still having trouble though: my main site loads properly, but the other virtual hosts aren't. Browsing to any virtual host address other than the default results in either the wrong content or an error. Here's what my httpd-vhosts.conf looks like: NameVirtualHost *:80 VirtualHost *:80 ServerName www.SiteA.com ServerAlias SiteA.com *.SiteA.com DocumentRoot /usr/www ErrorLog /var/log/httpd-SiteA-error.log CustomLog /var/log/httpd-SiteA-access.log combined /VirtualHost VirtualHost *:80 ServerName www.SiteB.com ServerAlias SiteB.com *.SiteB.com DocumentRoot /usr/www2 ErrorLog /var/log/httpd-SiteB-error.log CustomLog /var/log/httpd-SiteB-access.log combined /VirtualHost So, what's happening is that SiteA works as expected, but browsing to SiteB brings you to SiteA, or doesn't load at all (403 error). In addition, I'm back to my original problem, where PHP files are not loading, and browsing to a PHP page prompts the user to download the page as a file. Any help on either the virtual hosts or the PHP download issue would be greatly appreciated. Thanks, ~John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Virtual hosts and PHP downloads: php5 and apache22 on FreeBSD 6.1-STABLE
John DeStefano wrote: I upgraded my system from 5.4-RELEASE to 6.1-STABLE last week, and my web server immediately stopped serving PHP pages, where I had no problem doing so before. Instead of processing the PHP code on the server and displaying the result in a browser, browsing to any page containing PHP code resulted in a prompt to download the PHP page as a file. As you are probably already painfully aware, this is *usually* due to the absence of the necessary lines in the httpd.conf file; specifically, AddModule and LoadModule (pointing to the PHP shared object) and AddType (referring to the MIME type for PHP files). /usr/ports/UPGRADING mentions that PHP has been streamlined and must be recompiled to work with Apache and other packages. After deinstalling, configuring (where applicable), and reinstalling PHP5, php5-extensions, and apache2 to the latest versions, not only were PHP files not being served, but my web server was toast: Forbidden You don't have permission to access / on this server. Not toast, exactly. Another configuration error, most likely. httpd.conf tells the server which file(s) is/are acceptable as INDEX files. If all your index files were index.php, for example, and the httpd.conf file (which is new, apparently?) says that only index.html files are allowed as INDEX files, you'll get this error every time. I edited the new apache config file (now located in /usr/local/etc/apache22/httpd.conf) with my system information, including a DocumentRoot path. But when I started apache, I got some very peculiar errors: Warning: DocumentRoot [/www/docs/dummy-host.example.com] does not exist Warning: DocumentRoot [/www/docs/dummy-host2.example.com] does not exist Not only did I confirm beforehand that I had set the DocumentRoot path, and that apache was using the correct config file... but these dummy paths didn't exist in the config file! I learned eventually that a new apache directive splits out virtual host directives to a new include file (/usr/local/etc/apache22/extra/httpd-vhosts.conf). Then I learned after getting a server warning (NameVirtualHost *:80 has no VirtualHosts) that the syntax has been slightly modified, so that the IP/port value of each VirtualHost specification must match that of the NameVirtualHost directive (i.e., NameVirtualHost *:80 and VirtualHost *:80). Still having trouble though: my main site loads properly, but the other virtual hosts aren't. Browsing to any virtual host address other than the default results in either the wrong content or an error. Here's what my httpd-vhosts.conf looks like: NameVirtualHost *:80 VirtualHost *:80 ServerName www.SiteA.com ServerAlias SiteA.com *.SiteA.com DocumentRoot /usr/www ErrorLog /var/log/httpd-SiteA-error.log CustomLog /var/log/httpd-SiteA-access.log combined /VirtualHost VirtualHost *:80 ServerName www.SiteB.com ServerAlias SiteB.com *.SiteB.com DocumentRoot /usr/www2 ErrorLog /var/log/httpd-SiteB-error.log CustomLog /var/log/httpd-SiteB-access.log combined /VirtualHost IANAE here, but that's not like my httpd.conf, in which the ports aren't specified. I also don't use ServerAlias directives. Like I said, no expert. So, what's happening is that SiteA works as expected, but browsing to SiteB brings you to SiteA, or doesn't load at all (403 error). In addition, I'm back to my original problem, where PHP files are not loading, and browsing to a PHP page prompts the user to download the page as a file. Any help on either the virtual hosts or the PHP download issue would be greatly appreciated. You said you did this already, but I'd again make **sure** I was editing the correct httpd.conf. Get the right syntax, and it'll be there. Watch out for IF syntax, also. Can you post the relevant lines (AddModule, LoadModule, AddType) and whether or not they are contained in an IF ?? Kevin Kinsey -- How do you explain school to a higher intelligence? -- Elliot, E.T. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Virtual hosts and PHP downloads: php5 and apache22 on FreeBSD 6.1-STABLE
On 6/6/06, Kevin Kinsey [EMAIL PROTECTED] wrote: John DeStefano wrote: I upgraded my system from 5.4-RELEASE to 6.1-STABLE last week, and my web server immediately stopped serving PHP pages, where I had no problem doing so before. Instead of processing the PHP code on the server and displaying the result in a browser, browsing to any page containing PHP code resulted in a prompt to download the PHP page as a file. As you are probably already painfully aware, this is *usually* due to the absence of the necessary lines in the httpd.conf file; specifically, AddModule and LoadModule (pointing to the PHP shared object) and AddType (referring to the MIME type for PHP files). Hi Kevin. Yes: painfully aware at this point. /usr/ports/UPGRADING mentions that PHP has been streamlined and must be recompiled to work with Apache and other packages. After deinstalling, configuring (where applicable), and reinstalling PHP5, php5-extensions, and apache2 to the latest versions, not only were PHP files not being served, but my web server was toast: Forbidden You don't have permission to access / on this server. Not toast, exactly. Another configuration error, most likely. httpd.conf tells the server which file(s) is/are acceptable as INDEX files. If all your index files were index.php, for example, and the httpd.conf file (which is new, apparently?) says that only index.html files are allowed as INDEX files, you'll get this error every time. Yup... and with apache22, one of the benefits is that the PHP file handler lines are automatically filled in when compiling PHP (although I assume that would be the case with any version of apache as well). I edited the new apache config file (now located in /usr/local/etc/apache22/httpd.conf) with my system information, including a DocumentRoot path. But when I started apache, I got some very peculiar errors: Warning: DocumentRoot [/www/docs/dummy-host.example.com] does not exist Warning: DocumentRoot [/www/docs/dummy-host2.example.com] does not exist Not only did I confirm beforehand that I had set the DocumentRoot path, and that apache was using the correct config file... but these dummy paths didn't exist in the config file! I learned eventually that a new apache directive splits out virtual host directives to a new include file (/usr/local/etc/apache22/extra/httpd-vhosts.conf). Then I learned after getting a server warning (NameVirtualHost *:80 has no VirtualHosts) that the syntax has been slightly modified, so that the IP/port value of each VirtualHost specification must match that of the NameVirtualHost directive (i.e., NameVirtualHost *:80 and VirtualHost *:80). Still having trouble though: my main site loads properly, but the other virtual hosts aren't. Browsing to any virtual host address other than the default results in either the wrong content or an error. Here's what my httpd-vhosts.conf looks like: NameVirtualHost *:80 VirtualHost *:80 ServerName www.SiteA.com ServerAlias SiteA.com *.SiteA.com DocumentRoot /usr/www ErrorLog /var/log/httpd-SiteA-error.log CustomLog /var/log/httpd-SiteA-access.log combined /VirtualHost VirtualHost *:80 ServerName www.SiteB.com ServerAlias SiteB.com *.SiteB.com DocumentRoot /usr/www2 ErrorLog /var/log/httpd-SiteB-error.log CustomLog /var/log/httpd-SiteB-access.log combined /VirtualHost IANAE here, but that's not like my httpd.conf, in which the ports aren't specified. I also don't use ServerAlias directives. Like I said, no expert. Right: that's not from the httpd.conf file itself any longer; it's the httpd-vhosts.conf file, which is called on as an include in the 2.2 version of httpd.conf. In earlier versions, the VirtualHost directives have been moved from the main config file to that include file. And the IP/port specification for each VirtualHost entry must now match that of the NameVirtualHost entry (as shown above). So, what's happening is that SiteA works as expected, but browsing to SiteB brings you to SiteA, or doesn't load at all (403 error). In addition, I'm back to my original problem, where PHP files are not loading, and browsing to a PHP page prompts the user to download the page as a file. Any help on either the virtual hosts or the PHP download issue would be greatly appreciated. You said you did this already, but I'd again make **sure** I was editing the correct httpd.conf. Get the right syntax, and it'll be there. Watch out for IF syntax, also. I triple-checked the config to make sure apache is loading the correct config file. In fact, I've finally gotten the config to the point where none of the apache self-tests report any syntax or configuration errors at all. Unfortunately, that doesn't mean it works as I'd expected; just means there are no syntax errors. Can you post the relevant lines (AddModule, LoadModule, AddType) and whether or not they are contained in an IF ?? Please find my httpd.conf and httpd-vhosts.conf
Re: Virtual hosts and PHP downloads: php5 and apache22 on FreeBSD 6.1-STABLE
John DeStefano wrote: This body part will be downloaded on demand. Remove unnecessary spaces from your httpd.conf: AddType application/x- httpd-php .php ^ AddType application/x- httpd-php-source .phps ^ Make sure you clear cache on your browser before you test. Cheers, Mikhail. -- Mikhail Goriachev Webanoide Telephone: +61 (0)3 62252501 Mobile Phone: +61 (0)4 38255158 E-Mail: [EMAIL PROTECTED] Web: http://www.webanoide.org PGP Key ID: 0x4E148A3B PGP Key Fingerprint: D96B 7C14 79A5 8824 B99D 9562 F50E 2F5D 4E14 8A3B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.1-STABLE !!
on a dev box, did a cvsup and buildworld yesterday... and now my kernel says 6.1 stable! fbsd60-2# uname -a FreeBSD fbsd60-2.dev.dfwlp.com 6.1-STABLE FreeBSD 6.1-STABLE #0: Sun May 7 18:33:48 CDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FBSD60-2 i386 *shrug* i look on freebsd.org, but i didnt see an announcement about it yet. how close to release does this put us? cheers, jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1-STABLE !!
Jonathan Horne wrote: on a dev box, did a cvsup and buildworld yesterday... and now my kernel says 6.1 stable! fbsd60-2# uname -a FreeBSD fbsd60-2.dev.dfwlp.com 6.1-STABLE FreeBSD 6.1-STABLE #0: Sun May 7 18:33:48 CDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FBSD60-2 i386 *shrug* i look on freebsd.org, but i didnt see an announcement about it yet. how close to release does this put us? *Very* close but not there yet. Only after an official announcement is it released. cheers, jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Regards, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1-STABLE !!
On 8/5/06 15:39, Jonathan Horne [EMAIL PROTECTED] wrote: on a dev box, did a cvsup and buildworld yesterday... and now my kernel says 6.1 stable! fbsd60-2# uname -a FreeBSD fbsd60-2.dev.dfwlp.com 6.1-STABLE FreeBSD 6.1-STABLE #0: Sun May 7 18:33:48 CDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FBSD60-2 i386 *shrug* i look on freebsd.org, but i didnt see an announcement about it yet. how close to release does this put us? It essentially means that the release has been finished, and is being built/uploaded. Ceri -- That must be wonderful! I don't understand it at all. -- Moliere ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1-STABLE !!
On Monday 08 May 2006 10:55, Ceri Davies wrote: On 8/5/06 15:39, Jonathan Horne [EMAIL PROTECTED] wrote: on a dev box, did a cvsup and buildworld yesterday... and now my kernel says 6.1 stable! fbsd60-2# uname -a FreeBSD fbsd60-2.dev.dfwlp.com 6.1-STABLE FreeBSD 6.1-STABLE #0: Sun May 7 18:33:48 CDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FBSD60-2 i386 *shrug* i look on freebsd.org, but i didnt see an announcement about it yet. how close to release does this put us? It essentially means that the release has been finished, and is being built/uploaded. Ceri It's sitting on the mirror sites, if you look. I downloaded one this morning. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1-STABLE !!
On Mon, May 08, 2006 at 11:44:15AM -0500, Donald J. O'Neill wrote: On Monday 08 May 2006 10:55, Ceri Davies wrote: On 8/5/06 15:39, Jonathan Horne [EMAIL PROTECTED] wrote: on a dev box, did a cvsup and buildworld yesterday... and now my kernel says 6.1 stable! fbsd60-2# uname -a FreeBSD fbsd60-2.dev.dfwlp.com 6.1-STABLE FreeBSD 6.1-STABLE #0: Sun May 7 18:33:48 CDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FBSD60-2 i386 *shrug* i look on freebsd.org, but i didnt see an announcement about it yet. how close to release does this put us? It essentially means that the release has been finished, and is being built/uploaded. It's sitting on the mirror sites, if you look. I downloaded one this morning. Yes, I know, but until it is announced, you can't be guaranteed that those bits are the right ones. The delay allows us to make sure that all mirrors have it before they start getting hammered. Ceri -- That must be wonderful! I don't understand it at all. -- Moliere pgphgz2L7dzaR.pgp Description: PGP signature
