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

This WebDNA talk-list message is from

2019

It keeps the original formatting. numero = 114782
interpreted = N
texte = 2408Two months ago I ran into the dreaded "Sorry WebDNA servernot running" error message on my local development serverafter an OS upgrade to Ubuntu 18.04 and the follow-upinstallation of the then-latest version of Apache. Stuart saved me by pointing out that this WebDNA error wascaused by the Apache "PrivateTmp=true" setting in this file:/lib/systemd/system/apache2.serviceSo 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 thisfile, and surprisingly it was set back to its original"true" value!This file was apparently overwritten during last week's Apacheupgrade, but the problem never appeared until yesterday whenI rebooted the server -- likely because last week's upgradedid not restart Apache or reboot the server, so the new filewas never read into RAM until yesterday's reboot.It bothered me that an Apache upgrade would overwrite mymanual configuration change, so I did some more researchinto this issue. Apparenly we're not supposed to manuallyedit 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, wemust enter "PrivateTmp=false" on a single line (without thequotes) and save it with its default name and in its defaultlocation, then close/exit the editor and restart Apache.This override file will not be changed during an Apacheupgrade, which means any overrides we create in this filewill 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. Thenrestart Apache and check to make sure WebDNA is running.Regards,Kenneth GromeWebDNA Solutionshttp://www.webdnasolutions.comUrgent/Emergency Phone: (228) 222-2917Website, Database, Network, and Communication Systems---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=55Bug Reporting: support@webdna.us. Associated Messages, from the most recent to the oldest:

[WebDNA] CRITICAL ISSUE: PrivateTmp and "Sorry WebDNA server not running" (WebDNA Solutions 2019)

2408Two months ago I ran into the dreaded "Sorry WebDNA servernot running" error message on my local development serverafter an OS upgrade to Ubuntu 18.04 and the follow-upinstallation of the then-latest version of Apache. Stuart saved me by pointing out that this WebDNA error wascaused by the Apache "PrivateTmp=true" setting in this file:/lib/systemd/system/apache2.serviceSo 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 thisfile, and surprisingly it was set back to its original"true" value!This file was apparently overwritten during last week's Apacheupgrade, but the problem never appeared until yesterday whenI rebooted the server -- likely because last week's upgradedid not restart Apache or reboot the server, so the new filewas never read into RAM until yesterday's reboot.It bothered me that an Apache upgrade would overwrite mymanual configuration change, so I did some more researchinto this issue. Apparenly we're not supposed to manuallyedit 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, wemust enter "PrivateTmp=false" on a single line (without thequotes) and save it with its default name and in its defaultlocation, then close/exit the editor and restart Apache.This override file will not be changed during an Apacheupgrade, which means any overrides we create in this filewill 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. Thenrestart Apache and check to make sure WebDNA is running.Regards,Kenneth GromeWebDNA Solutionshttp://www.webdnasolutions.comUrgent/Emergency Phone: (228) 222-2917Website, Database, Network, and Communication Systems---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=55Bug Reporting: support@webdna.us. WebDNA Solutions

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:

Emailer file formats (1998) [WebDNA] max number of searches and lookups on a page (2016) Frames and WebCat (1997) Help! Strange happenings... (1997) 2.0Beta Command Ref (can't find this instruction) (1997) (ot) sitemap generator (1998) Problem 2: Prefs file... (1997) Robots fill event log (1997) emailer w/F2 (1997) [WebDNA] sudo and shell (2010) Encrypt Users.db problem (1998) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997) docs for WebCatalog2 (1997) Re:WebCat Contest (1998) OK, here goes... (1997) Classified (1999) Just a thought (1998) Location of Browser Info.txt file (1997) Forms Search Questions (1997) RE: Error: template (1997)