Re: [WebDNA] Sorry WebDNA server not running - September 2019 Edition
This WebDNA talk-list message is from 2019
It keeps the original formatting.
numero = 114744
interpreted = N
texte = 2370 When WebDNA is shutdown the WebCatalog.pid file is automatically = deleted, so I can=E2=80=99t delete it. But followed your instructions 1) WebDNA turned off 2) WebCatalog.pid removed itself 3) Searched for any rogue instances off WebCatalog and WebDNA, none = found 4) Started WebDNA Did a ... sudo lsof -n > myoutput.txt Only to see a lot of =E2=80=A6 WebDNAMon 82 root 190u unix 0x7513d6b8c5c9a0af = 0t0 /tmp/.WebDNAMonitor =E2=80=A6once again and =E2=80=9CSorry WebDNA server not running=E2=80=9D = continues to occur. /Palle > On 15 Sep 2019, at 16.09, Donovan Brooke
wrote: >=20 > No time right now.. but; > - turn off WebDNA (asadmin) > WebCatalogCtl shutdown >=20 > - delete the WebCatalog.pid file (in that same directory) >=20 > - search for any rogue instances of webcatalog or WebDNA monitor > ps aux | Web >=20 > If there are any, kill those processes: > kill -9 >=20 > Start WebDNA >=20 >=20 >=20 >=20 > D. Brooke Mobile >=20 >> On Sep 15, 2019, at 7:31 AM, H - Powerpalle = wrote: >>=20 >> Hi Chris et al >>=20 >> I have just restarted the server and have run the command. Only a few = moments later I have noticed that is growing = rapidly and after roughly an hour (maybe less) there were at least a = couple of hundred of the following instances. I logically this could be = the issue as to why the server is puking after while, but not = necessarily why it also does the =E2=80=9CSorry WebDNA server not = running=E2=80=9D. >>=20 >> Anf then again, then =E2=80=9CSorry WebDNA server not running=E2=80=9D = occurs the WebDNAMonitor seems absent for a short while only to initiate = itself again. This could (maybe) add to the proces. >>=20 >> Anyhow, what could be the cause of the WebDNAMonitor starting som = many instances of itself? I did not (as far as I know) tell it to do = that=E2=80=A6 >>=20 >> =E2=80=94> Just a few of them (used: sudo lsof -n > myoutput.txt) >> WebDNAMon 82 root 190u unix 0x7513d6b8c5c9a0af = 0t0 /tmp/.WebDNAMonitor >> WebDNAMon 82 root 191u unix 0x7513d6b8c5c99047 = 0t0 /tmp/.WebDNAMonitor >> WebDNAMon 82 root 192u unix 0x7513d6b8c5c98eb7 = 0t0 /tmp/.WebDNAMonitor >> WebDNAMon 82 root 193u unix 0x7513d6b8c5c9a23f = 0t0 /tmp/.WebDNAMonitor >> WebDNAMon 82 root 194u unix 0x7513d6b8c5c98d27 = 0t0 /tmp/.WebDNAMonitor >> WebDNAMon 82 root 195u unix 0x7513d6b8c5c98b97 = 0t0 /tmp/.WebDNAMonitor >> WebDNAMon 82 root 196u unix 0x7513d6b8c5c9a3cf = 0t0 /tmp/.WebDNAMonitor >> WebDNAMon 82 root 197u unix 0x7513d6b8c5c9a55f = 0t0 /tmp/.WebDNAMonitor >>=20 >> /Palle >>=20 >>=20 >>=20 >>> On 13 Sep 2019, at 22.20, christophe.billiottet@webdna.us wrote: >>>=20 >>> Seems like there are too many open files, and it is causing = problems. If it happens after an hour, I'd probably run "sudo lsof -n > = myoutput.txt" 30 minutes after restarting to see if there is anything = interesting going on. >>>=20 >>>=20 >>> You could run it again too after the problem occurs: sudo lsof -n > = myoutput2.txt >>>=20 >>> If you send us both .txt files we could look at them for hints. >>>=20 >>> My guess is you have a script that never finishes and so there are = tons of open WebDNA threads and file descriptors. >>>=20 >>> - chris >>>=20 >>>=20 >>> --------------------------------------------------------- >>> 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 >>=20 >> --------------------------------------------------------- >> 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 >=20 > --------------------------------------------------------- > 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 .
Associated Messages, from the most recent to the oldest:
2370 When WebDNA is shutdown the WebCatalog.pid file is automatically = deleted, so I can=E2=80=99t delete it. But followed your instructions 1) WebDNA turned off 2) WebCatalog.pid removed itself 3) Searched for any rogue instances off WebCatalog and WebDNA, none = found 4) Started WebDNA Did a ... sudo lsof -n > myoutput.txt Only to see a lot of =E2=80=A6 WebDNAMon 82 root 190u unix 0x7513d6b8c5c9a0af = 0t0 /tmp/.WebDNAMonitor =E2=80=A6once again and =E2=80=9CSorry WebDNA server not running=E2=80=9D = continues to occur. /Palle > On 15 Sep 2019, at 16.09, Donovan Brooke wrote: >=20 > No time right now.. but; > - turn off WebDNA (asadmin) > WebCatalogCtl shutdown >=20 > - delete the WebCatalog.pid file (in that same directory) >=20 > - search for any rogue instances of webcatalog or WebDNA monitor > ps aux | Web >=20 > If there are any, kill those processes: > kill -9 >=20 > Start WebDNA >=20 >=20 >=20 >=20 > D. Brooke Mobile >=20 >> On Sep 15, 2019, at 7:31 AM, H - Powerpalle = wrote: >>=20 >> Hi Chris et al >>=20 >> I have just restarted the server and have run the command. Only a few = moments later I have noticed that is growing = rapidly and after roughly an hour (maybe less) there were at least a = couple of hundred of the following instances. I logically this could be = the issue as to why the server is puking after while, but not = necessarily why it also does the =E2=80=9CSorry WebDNA server not = running=E2=80=9D. >>=20 >> Anf then again, then =E2=80=9CSorry WebDNA server not running=E2=80=9D = occurs the WebDNAMonitor seems absent for a short while only to initiate = itself again. This could (maybe) add to the proces. >>=20 >> Anyhow, what could be the cause of the WebDNAMonitor starting som = many instances of itself? I did not (as far as I know) tell it to do = that=E2=80=A6 >>=20 >> =E2=80=94> Just a few of them (used: sudo lsof -n > myoutput.txt) >> WebDNAMon 82 root 190u unix 0x7513d6b8c5c9a0af = 0t0 /tmp/.WebDNAMonitor >> WebDNAMon 82 root 191u unix 0x7513d6b8c5c99047 = 0t0 /tmp/.WebDNAMonitor >> WebDNAMon 82 root 192u unix 0x7513d6b8c5c98eb7 = 0t0 /tmp/.WebDNAMonitor >> WebDNAMon 82 root 193u unix 0x7513d6b8c5c9a23f = 0t0 /tmp/.WebDNAMonitor >> WebDNAMon 82 root 194u unix 0x7513d6b8c5c98d27 = 0t0 /tmp/.WebDNAMonitor >> WebDNAMon 82 root 195u unix 0x7513d6b8c5c98b97 = 0t0 /tmp/.WebDNAMonitor >> WebDNAMon 82 root 196u unix 0x7513d6b8c5c9a3cf = 0t0 /tmp/.WebDNAMonitor >> WebDNAMon 82 root 197u unix 0x7513d6b8c5c9a55f = 0t0 /tmp/.WebDNAMonitor >>=20 >> /Palle >>=20 >>=20 >>=20 >>> On 13 Sep 2019, at 22.20, christophe.billiottet@webdna.us wrote: >>>=20 >>> Seems like there are too many open files, and it is causing = problems. If it happens after an hour, I'd probably run "sudo lsof -n > = myoutput.txt" 30 minutes after restarting to see if there is anything = interesting going on. >>>=20 >>>=20 >>> You could run it again too after the problem occurs: sudo lsof -n > = myoutput2.txt >>>=20 >>> If you send us both .txt files we could look at them for hints. >>>=20 >>> My guess is you have a script that never finishes and so there are = tons of open WebDNA threads and file descriptors. >>>=20 >>> - chris >>>=20 >>>=20 >>> --------------------------------------------------------- >>> 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 >>=20 >> --------------------------------------------------------- >> 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 >=20 > --------------------------------------------------------- > 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 .
H - Powerpalle
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:
WebTen and WebCat (1997)
Retrieve deleted files (2001)
expire headers in mac305b11 (1999)
Simple way to create unique SKU (1997)
Pass Thru Page? (1998)
Nesting [RAW] (1998)
security problem (1997)
Add - optional parameters textA=.... (1997)
can WC render sites out? (1997)
Search Engine questions ... (2002)
Shopping Carts (2000)
lineitems context in sendmail context (1998)
RE: what characters are replaced for tab and CR? (1998)
RE: Signal Raised (1997)
Emailer choke (1997)
Many $WebCat.exe processes (1998)
WebCat Error Log problem (2.0.1, acgi, Mac) (1997)
CopyFile not working? (2000)
Re:Signal Raised (1997)
Re:E-mailer application times out (1998)