[WebDNA] =?windows-1252?Q?Re=3A_=5BWebDNA=5D_Re=3A_=5BWebDNA=5D_Re=3A_=5BWebDNA=5D_=5BWebDNA=5D_Re=3A_?=

This WebDNA talk-list message is from

2012


It keeps the original formatting.
numero = 108060
interpreted = N
texte = --20cf303ea7a8346c1904b632e63d Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jan 10, 2012 at 3:20 PM, wrote: > It looks there is something wrong with your httpd.conf. SIGTERM is the > signal sent to a process to request its termination. In this case, it shuts > apache down because it "Could not reliably determine the server's fully > qualified domain name", and if it can't, it is most probably because apache > is not properly configured. > > - chris Sorry to contradict you, but apache handled the domain name for the server and started up anyway. I've seen this as a start up message when servers are just getting configured but no DNS is ready. I'm guessing Apache is running and then crashes, even if for a short time. The SIGTERM is something else and happens before apache restarts. I doubt the httpd.conf is causing the error alone because apache won't startup in many cases if the conf has an error. I would still check the error logs for webDNA and apache just before the time of the SIGTERM entry. Bill --20cf303ea7a8346c1904b632e63d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Jan 10, 2012 at 3:20 PM, <christophe.billiottet@webdna.us> wrote:
It looks there is something wrong with your httpd.conf. SIGTERM is the sign= al sent to a process to request its termination. In this case, it shuts apa= che down because it "Could not reliably determine the server's ful= ly qualified domain name", and if it can't, it is most probably be= cause apache is not properly configured.

- chris

Sorry to contradict you, but apache= handled the domain name for the server and started up anyway. =A0I've = seen this as a start up message when servers are just getting configured bu= t no DNS is ready. =A0I'm guessing Apache is running and then crashes, = even if for a short time. =A0

The SIGTERM is something else and happens before apache= restarts. =A0I doubt the httpd.conf is causing the error alone because apa= che won't startup in many cases if the conf has an error. =A0

I would still check the error logs for webDNA and apache jus= t before the time of the SIGTERM entry. =A0

Bill
--20cf303ea7a8346c1904b632e63d-- Associated Messages, from the most recent to the oldest:

    
  1. [WebDNA] =?windows-1252?Q?Re=3A_=5BWebDNA=5D_Re=3A_=5BWebDNA=5D_Re=3A_=5BWebDNA=5D_=5BWebDNA=5D_Re=3A_?= (William DeVaul 2012)
--20cf303ea7a8346c1904b632e63d Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jan 10, 2012 at 3:20 PM, wrote: > It looks there is something wrong with your httpd.conf. SIGTERM is the > signal sent to a process to request its termination. In this case, it shuts > apache down because it "Could not reliably determine the server's fully > qualified domain name", and if it can't, it is most probably because apache > is not properly configured. > > - chris Sorry to contradict you, but apache handled the domain name for the server and started up anyway. I've seen this as a start up message when servers are just getting configured but no DNS is ready. I'm guessing Apache is running and then crashes, even if for a short time. The SIGTERM is something else and happens before apache restarts. I doubt the httpd.conf is causing the error alone because apache won't startup in many cases if the conf has an error. I would still check the error logs for webDNA and apache just before the time of the SIGTERM entry. Bill --20cf303ea7a8346c1904b632e63d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Jan 10, 2012 at 3:20 PM, <christophe.billiottet@webdna.us> wrote:
It looks there is something wrong with your httpd.conf. SIGTERM is the sign= al sent to a process to request its termination. In this case, it shuts apa= che down because it "Could not reliably determine the server's ful= ly qualified domain name", and if it can't, it is most probably be= cause apache is not properly configured.

- chris

Sorry to contradict you, but apache= handled the domain name for the server and started up anyway. =A0I've = seen this as a start up message when servers are just getting configured bu= t no DNS is ready. =A0I'm guessing Apache is running and then crashes, = even if for a short time. =A0

The SIGTERM is something else and happens before apache= restarts. =A0I doubt the httpd.conf is causing the error alone because apa= che won't startup in many cases if the conf has an error. =A0

I would still check the error logs for webDNA and apache jus= t before the time of the SIGTERM entry. =A0

Bill
--20cf303ea7a8346c1904b632e63d-- William DeVaul

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Cart # Starting at 1000 (2000) WebCat b15 Mac plug-in (1997) Solve the Problem, get the code! (2001) Search all Fields in a db (1997) Link with [cart] in db field (1999) Hiding HTML and page breaks (1997) Search in 2 or more catalogs (1997) problems with 2 tags (1997) Duplicates (1998) RE: Formulas.db + Users.db (1997) Re:Emailer and encryption (1997) Sending E-mail (1997) RE:DatabaseHelper (1997) Shell traceroute (2001) SERIAL NUMBER PROBLEM *AGAIN*!!! (1998) Webcat listserver - WAS - webcat method for waitingspecific amount of time? (2000) Max Record length restated as maybe bug (1997) Using Eudora instead of Emailer, and cron facility (1998) bug in [SendMail] (1997) price on detail, but not shoppingcart (1997)