[WebDNA] Solution to PrivateTmp setting and "Sorry WebDNA server not

This WebDNA talk-list message is from

2019


It keeps the original formatting.
numero = 114789
interpreted = N
texte = 2415 FOR FUTURE REFERENCE: Here are my corrected instructions for eliminating the "Sorry WebDNA server not running" error message when caused by a bad "PrivateTmp" setting in an Apache 2.4 server config file on an Ubuntu 18.04 server: 1- Run this command on the server which will (a) open a blank "override" file if this has never been done before, or (b) open the previously created "override" file: sudo systemctl edit apache2.serviceService 2a- If you see a blank override file in your editor, type these two lines exactly as shown here: [Service] PrivateTmp=false 2b- If your override file contains existing content, make sure the same two lines appear in this file ... and confirm that there is only one [Service] line and one PrivateTmp line in this file. 4- Save the override file, close the editor, reboot the server, and check to make sure WebDNA is running. That's it for the instructions. This worked for me so hopefully it will work for you, too. And Stuart, thanks for finding the missing piece of this puzzle! Apparently my override file was ignored when I tested my previous instructions because of the missing [Service] line ... but I didn't know it because earlier I had set "PrivateTmp=false" manually in my apache2.service file. So this time, to confirm that this solution actually works, I manually re-edited my apache2.service file by setting PrivateTmp back to its original/default "true" value, then I added the [Service] line to my override file and rebooted ... The result was YES, WebDNA is running -- which means my override file is working! :) Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Urgent/Emergency Phone: (228) 222-2917 Website, Database, Network, and Communication Systems > Hi Ken > > I found the answer to my previous question to you. > > The override.conf file needs an inclusion of [Service], ie: > > [Service] > PrivateTmp=false > > > 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 . Associated Messages, from the most recent to the oldest:

    
  1. [WebDNA] Solution to PrivateTmp setting and "Sorry WebDNA server not (WebDNA Solutions 2019)
2415 FOR FUTURE REFERENCE: Here are my corrected instructions for eliminating the "Sorry WebDNA server not running" error message when caused by a bad "PrivateTmp" setting in an Apache 2.4 server config file on an Ubuntu 18.04 server: 1- Run this command on the server which will (a) open a blank "override" file if this has never been done before, or (b) open the previously created "override" file: sudo systemctl edit apache2.serviceService 2a- If you see a blank override file in your editor, type these two lines exactly as shown here: [Service] PrivateTmp=false 2b- If your override file contains existing content, make sure the same two lines appear in this file ... and confirm that there is only one [Service] line and one PrivateTmp line in this file. 4- Save the override file, close the editor, reboot the server, and check to make sure WebDNA is running. That's it for the instructions. This worked for me so hopefully it will work for you, too. And Stuart, thanks for finding the missing piece of this puzzle! Apparently my override file was ignored when I tested my previous instructions because of the missing [Service] line ... but I didn't know it because earlier I had set "PrivateTmp=false" manually in my apache2.service file. So this time, to confirm that this solution actually works, I manually re-edited my apache2.service file by setting PrivateTmp back to its original/default "true" value, then I added the [Service] line to my override file and rebooted ... The result was YES, WebDNA is running -- which means my override file is working! :) Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Urgent/Emergency Phone: (228) 222-2917 Website, Database, Network, and Communication Systems > Hi Ken > > I found the answer to my previous question to you. > > The override.conf file needs an inclusion of [Service], ie: > > [Service] > PrivateTmp=false > > > 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 . 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:

taxRate and grandTotal calculation is not showing up on myThankYou.tpl (2000) 5.0 upgrade - config docs? (2003) Web Catalog vs. ICAT (1997) Is this possible, WebCat2.0 and checkboxes (1997) Emailer error codes (1999) WebCat2b15MacPlugin - showing [math] (1997) Multiple 'Users.db' files not possible (1997) Multiple Newcarts (1996) Encrypting userid for email (2000) Summing fields (1997) WebCat editing, SiteGuard & SiteEdit (1997) WebCat2 - Getting to the browser's username/password data (1997) Moment of Thanks (1997) WebCatalog 4.0.2b5 available (2000) Roundup function? (1997) Running 2 two WebCatalog.acgi's (1996) Problem with empty form-variables in [search] (1998) Using WC for Bulk Emailings (1997) Multiple transactions per cart (2000) Latin Characters (1998)