Also grateful for the info belo=w, thank you Ken, appreciated
From: Stuart Tremain
Sent: 21 September 2019 23:28
To: WebDNA Talk List
Subject: Re: [WebDNA] CRITICAL ISSUE: PrivateTmp and "Sorry Web=DNA server not running" ...
On 22 Sep 2019, at 00:05, WebDNA Solutions <ken@webdnasolutions.com> w=rote:Two months ago I ran into the dreaded "Sorry WebDNA se=rver
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.webdnasolu=tions.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
|
Also grateful for the info belo=w, thank you Ken, appreciated
From: Stuart Tremain
Sent: 21 September 2019 23:28
To: WebDNA Talk List
Subject: Re: [WebDNA] CRITICAL ISSUE: PrivateTmp and "Sorry Web=DNA server not running" ...
On 22 Sep 2019, at 00:05, WebDNA Solutions <ken@webdnasolutions.com> w=rote:Two months ago I ran into the dreaded "Sorry WebDNA se=rver
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.webdnasolu=tions.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
DOWNLOAD WEBDNA NOW!
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...