Re: [WebDNA] CRITICAL ISSUE: PrivateTmp and "Sorry WebDNA server not

This WebDNA talk-list message is from

2019


It keeps the original formatting.
numero = 114783
interpreted = N
texte = 2409 --Apple-Mail=_F9CFD0E4-FBB9-4828-BE2A-2C3DB1875901 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Hey Ken That is a really great tip, thanks very much !! Kind regards Stuart Tremain Pharoah Lane Software AUSTRALIA webdna@plsoftware.com.au > On 22 Sep 2019, at 00:05, WebDNA Solutions wrote: > > Two months ago I ran into the dreaded "Sorry WebDNA server > not running" error message on my local development server > after an OS upgrade to Ubuntu 18.04 and the follow-up > installation of the then-latest version of Apache. > > Stuart saved me by pointing out that this WebDNA error was > caused by the Apache "PrivateTmp=true" setting in this file: > > /lib/systemd/system/apache2.service > > So I manually changed it to "PrivateTmp=false" and rebooted. > Then WebDNA ran fine until yesterday when I was hit by the > "Sorry WebDNA server not running" error again ... > > :( > > The first thing I checked was my PrivateTmp setting in this > file, and surprisingly it was set back to its original > "true" value! > > This file was apparently overwritten during last week's Apache > upgrade, but the problem never appeared until yesterday when > I rebooted the server -- likely because last week's upgrade > did not restart Apache or reboot the server, so the new file > was never read into RAM until yesterday's reboot. > > It bothered me that an Apache upgrade would overwrite my > manual configuration change, so I did some more research > into this issue. Apparenly we're not supposed to manually > edit this file. Instead we're supposed to run the command: > > sudo systemctl edit apache2.service > > ... which creates a uniquely named OVERRIDE FILE in: > > /etc/systemd/system/apache2.service.d/ > > And then since this new override file starts out blank, we > must enter "PrivateTmp=false" on a single line (without the > quotes) and save it with its default name and in its default > location, then close/exit the editor and restart Apache. > > This override file will not be changed during an Apache > upgrade, which means any overrides we create in this file > will persist after upgrading Apache in the future. > > BOTTOM LINE: > > Never edit "/lib/systemd/system/apache2.service" manually. > Just edit it via the above command and instructions. Then > restart Apache and check to make sure WebDNA is running. > > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Urgent/Emergency Phone: (228) 222-2917 > Website, Database, Network, and Communication Systems > > > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list talk@webdna.us > To unsubscribe, E-mail to: talk-leave@webdna.us > archives: http://www.webdna.us/page.dna?numero=55 > Bug Reporting: support@webdna.us --Apple-Mail=_F9CFD0E4-FBB9-4828-BE2A-2C3DB1875901 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hey = Ken

That is a really = great tip, thanks very much !!


Kind regards

Stuart Tremain
Pharoah Lane Software
AUSTRALIA







On 22 Sep 2019, at 00:05, WebDNA Solutions <ken@webdnasolutions.com> wrote:

Two = months ago I ran into the dreaded "Sorry WebDNA server
not = running" error message on my local development server
after = an OS upgrade to Ubuntu 18.04 and the follow-up
installation= of the then-latest version of Apache.

Stuart saved me by pointing out that this WebDNA error was
caused by the Apache "PrivateTmp=3Dtrue" setting in this = file:

/lib/systemd/system/apache2.service

So I manually changed it to "PrivateTmp=3Dfalse"= and rebooted.
Then WebDNA ran fine until yesterday when I = was hit by the
"Sorry WebDNA server not running" error = again ...

:(

The= first thing I checked was my PrivateTmp setting in this
file, and surprisingly it was set back to its original
"true" value!

This file was = apparently overwritten during last week's Apache
upgrade, = but the problem never appeared until yesterday when
I = rebooted the server -- likely because last week's upgrade
did not restart Apache or reboot the server, so the new = file
was never read into RAM until yesterday's reboot.

It bothered me that an Apache upgrade would = overwrite my
manual configuration change, so I did some = more research
into this issue. Apparenly we're not = supposed to manually
edit this file. Instead we're = supposed to run the command:

sudo systemctl = edit apache2.service

... which creates a = uniquely named OVERRIDE FILE in:

/etc/systemd/system/apache2.service.d/

And then since this new override file starts out blank, we
must enter "PrivateTmp=3Dfalse" on a single line (without = the
quotes) and save it with its default name and in its = default
location, then close/exit the editor and restart = Apache.

This override file will not be = changed during an Apache
upgrade, which means any = overrides we create in this file
will persist after = upgrading Apache in the future.

BOTTOM = LINE:

Never edit = "/lib/systemd/system/apache2.service" manually.
Just edit = it via the above command and instructions. Then
restart = Apache and check to make sure WebDNA is running.

Regards,
Kenneth Grome
WebDNA = Solutions
http://www.webdnasolutions.com
Urgent/Emergency Phone: (228) 222-2917
Website, = Database, Network, and Communication Systems



---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list talk@webdna.us
To unsubscribe, = E-mail to: talk-leave@webdna.us
archives: = http://www.webdna.us/page.dna?numero=3D55
Bug Reporting: = support@webdna.us

= --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --Apple-Mail=_F9CFD0E4-FBB9-4828-BE2A-2C3DB1875901-- . Associated Messages, from the most recent to the oldest:

    
  1. RE: [WebDNA] CRITICAL ISSUE: PrivateTmp and "Sorry WebDNA server not ("Scott @ Itsula" 2019)
  2. Re: [WebDNA] CRITICAL ISSUE: PrivateTmp and "Sorry WebDNA server not (Stuart Tremain 2019)
  3. Re: [WebDNA] CRITICAL ISSUE: PrivateTmp and "Sorry WebDNA server not (Stuart Tremain 2019)
  4. Re: [WebDNA] CRITICAL ISSUE: PrivateTmp and "Sorry WebDNA server not (Stuart Tremain 2019)
  5. [WebDNA] CRITICAL ISSUE: PrivateTmp and "Sorry WebDNA server not running" (WebDNA Solutions 2019)
2409 --Apple-Mail=_F9CFD0E4-FBB9-4828-BE2A-2C3DB1875901 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Hey Ken That is a really great tip, thanks very much !! Kind regards Stuart Tremain Pharoah Lane Software AUSTRALIA webdna@plsoftware.com.au > On 22 Sep 2019, at 00:05, WebDNA Solutions wrote: > > Two months ago I ran into the dreaded "Sorry WebDNA server > not running" error message on my local development server > after an OS upgrade to Ubuntu 18.04 and the follow-up > installation of the then-latest version of Apache. > > Stuart saved me by pointing out that this WebDNA error was > caused by the Apache "PrivateTmp=true" setting in this file: > > /lib/systemd/system/apache2.service > > So I manually changed it to "PrivateTmp=false" and rebooted. > Then WebDNA ran fine until yesterday when I was hit by the > "Sorry WebDNA server not running" error again ... > > :( > > The first thing I checked was my PrivateTmp setting in this > file, and surprisingly it was set back to its original > "true" value! > > This file was apparently overwritten during last week's Apache > upgrade, but the problem never appeared until yesterday when > I rebooted the server -- likely because last week's upgrade > did not restart Apache or reboot the server, so the new file > was never read into RAM until yesterday's reboot. > > It bothered me that an Apache upgrade would overwrite my > manual configuration change, so I did some more research > into this issue. Apparenly we're not supposed to manually > edit this file. Instead we're supposed to run the command: > > sudo systemctl edit apache2.service > > ... which creates a uniquely named OVERRIDE FILE in: > > /etc/systemd/system/apache2.service.d/ > > And then since this new override file starts out blank, we > must enter "PrivateTmp=false" on a single line (without the > quotes) and save it with its default name and in its default > location, then close/exit the editor and restart Apache. > > This override file will not be changed during an Apache > upgrade, which means any overrides we create in this file > will persist after upgrading Apache in the future. > > BOTTOM LINE: > > Never edit "/lib/systemd/system/apache2.service" manually. > Just edit it via the above command and instructions. Then > restart Apache and check to make sure WebDNA is running. > > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Urgent/Emergency Phone: (228) 222-2917 > Website, Database, Network, and Communication Systems > > > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list talk@webdna.us > To unsubscribe, E-mail to: talk-leave@webdna.us > archives: http://www.webdna.us/page.dna?numero=55 > Bug Reporting: support@webdna.us --Apple-Mail=_F9CFD0E4-FBB9-4828-BE2A-2C3DB1875901 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hey = Ken

That is a really = great tip, thanks very much !!


Kind regards

Stuart Tremain
Pharoah Lane Software
AUSTRALIA







On 22 Sep 2019, at 00:05, WebDNA Solutions <ken@webdnasolutions.com> wrote:

Two = months ago I ran into the dreaded "Sorry WebDNA server
not = running" error message on my local development server
after = an OS upgrade to Ubuntu 18.04 and the follow-up
installation= of the then-latest version of Apache.

Stuart saved me by pointing out that this WebDNA error was
caused by the Apache "PrivateTmp=3Dtrue" setting in this = file:

/lib/systemd/system/apache2.service

So I manually changed it to "PrivateTmp=3Dfalse"= and rebooted.
Then WebDNA ran fine until yesterday when I = was hit by the
"Sorry WebDNA server not running" error = again ...

:(

The= first thing I checked was my PrivateTmp setting in this
file, and surprisingly it was set back to its original
"true" value!

This file was = apparently overwritten during last week's Apache
upgrade, = but the problem never appeared until yesterday when
I = rebooted the server -- likely because last week's upgrade
did not restart Apache or reboot the server, so the new = file
was never read into RAM until yesterday's reboot.

It bothered me that an Apache upgrade would = overwrite my
manual configuration change, so I did some = more research
into this issue. Apparenly we're not = supposed to manually
edit this file. Instead we're = supposed to run the command:

sudo systemctl = edit apache2.service

... which creates a = uniquely named OVERRIDE FILE in:

/etc/systemd/system/apache2.service.d/

And then since this new override file starts out blank, we
must enter "PrivateTmp=3Dfalse" on a single line (without = the
quotes) and save it with its default name and in its = default
location, then close/exit the editor and restart = Apache.

This override file will not be = changed during an Apache
upgrade, which means any = overrides we create in this file
will persist after = upgrading Apache in the future.

BOTTOM = LINE:

Never edit = "/lib/systemd/system/apache2.service" manually.
Just edit = it via the above command and instructions. Then
restart = Apache and check to make sure WebDNA is running.

Regards,
Kenneth Grome
WebDNA = Solutions
http://www.webdnasolutions.com
Urgent/Emergency Phone: (228) 222-2917
Website, = Database, Network, and Communication Systems



---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list talk@webdna.us
To unsubscribe, = E-mail to: talk-leave@webdna.us
archives: = http://www.webdna.us/page.dna?numero=3D55
Bug Reporting: = support@webdna.us

= --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --Apple-Mail=_F9CFD0E4-FBB9-4828-BE2A-2C3DB1875901-- . Stuart Tremain

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:

Multiple download orders of the same product? (1997) + character mystery (2003) Dealer Locator (2008) Remove from list server (1997) Re:HELP - NONE STOP DIGESTS. Digest for 4/24/97) (1997) Multiple shipping databases (1997) xmlparse and utf-8 encoding (2006) Moment of Thanks (1997) Re:Emailer (1998) Limitations on fields? Server is crashing (1997) Three new problems, maybe a fourth (1997) Dumb Question about Docs (1997) PIXO with cometsite ... and/or other plugins (1998) [WriteFile] problems (1997) [WebDNA] [WSC] WebDNA Development Summit (2014) How far do [showif]s go? (1997) [WebDNA] Internal [ipaddress] ? (2009) Examples of cross-selling with WebCatalog? (1998) shipcost (1997) [WebDNA] naming math vars in v.7 (2010)