Re: [WebDNA] 6.2 Monitor
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108168
interpreted = N
texte = Do these problems occur on Linux or Windows servers or only on OSX? How long does the process remain so high? Was there visitor activity that could have caused it? Any templates requested upon restart? Sincerely, Kenneth Grome > Ok, this acted up again, and am not getting errors in the > debug, or any error logs, which is strange. The > processor just climbed to 180% on the WebCatalog > process. I am getting a few lines in the signal > termination log, but that's it, and a couple of them > were probably generated by me trying to get it to start. > > ---Mon Jan 23 06:03:56 2012 MST Processid 66785 receive > SIGTERM: ---Mon Jan 23 07:56:02 2012 MST Processid 66958 > receive SIGTERM: ---Mon Jan 23 07:59:02 2012 > MST Processid 69107 receive SIGTERM: > > However, I am getting a weird error when I trigger > /Library/WebServer/CGI-Executables/WebCatalogEngine/WebC > atalogCtl restart in terminal. I get about ten or twelve > lines of: > > "sem_open failed: returned ENOSPC: No space left on device" > > and can't exit terminal without quitting it. > > Not sure at all what that error is, any ideas? The server > has 450 gigs of free space(Mac os x 10.6.8, WebDNA 6.2). > I did do an uninstall, and complete reinstall of WebDNA, > but it still comes up with this same error on restart. > WebDNA does start and run normally though. > > We will eventually move over to version 7, but can't get > at it for a few months, so need to get this stable for > now, or at least to the point where we don't have to > babysit it. > > Rob > > On Jan 19, 2012, at 5:55 AM, Rob wrote: > > Hi Robert > > > > On Jan 18, 2012, at 8:27 PM, Robert Minor wrote: > >> Maybe the thought he was funny. > >> > >> Was your old server intel based? > > > > No, it was PPC... 10.4.11 > > > >> did you turn on the troubleshooting tools? > > > > Yes, they are on now... Hoping to catch it the next > > time it happens. > > > > > > Rob > > > >> On Jan 18, 2012, at 6:37 PM, Rob wrote: > >>> Uuuuh...the server is only six months old.... how new > >>> do you want me to try?... All that's happened is we > >>> retired an old server, that wasn't having any > >>> problems, but it was over 5 years old, and we just > >>> didn't trust it any more, and to replace internal > >>> hardware would cost more then purchasing a new one. > >>> > >>> > >>> Rob > >>> > >>> On Jan 18, 2012, at 4:35 PM, William DeVaul wrote: > >>>> Try a new server. Worked wonders for me. > >>>> > >>>> Bill > >>>> > >>>> On Wed, Jan 18, 2012 at 11:18 AM, Rob
wrote: > >>>>> On Jan 18, 2012, at 10:00 AM, Donovan Brooke wrote: > >>>>>> Rob wrote: > >>>>>>> Hi All, > >>>>>>> > >>>>>>> Very rarely(once every couple months) I have > >>>>>>> WebDNA 6.2 stop, and drive > >>>>> > >>>>> the CPU nuts on Snow Leopard Server, and am looking > >>>>> at adding a script to keep an eye on it while I go > >>>>> on vacation. I found an old script... not sure > >>>>> where it come from or where I got it, but I had it > >>>>> on one of the old servers, and would like to get > >>>>> it working using launchd to start it, which isn't > >>>>> the problem. When I trigger the script, it comes > >>>>> up with "ps: No user named 'x'". Which is fairly > >>>>> obvious to those who no about these scripts, which > >>>>> I don't. > >>>>> > >>>>>>> So my question is, does anyone know how to get > >>>>>>> this working, or is > >>>>> > >>>>> there a better way? ... Script below. > >>>>> > >>>>>>> Rob > >>>>>> > >>>>>> I wouldn't use that script for a couple reasons. > >>>>>> > >>>>>> First, It's not bad if your server shoots up to a > >>>>>> 145% usage (2 CPU's) > >>>>> > >>>>> for short instances now and then.. > >>>>> > >>>>>> Second, kill -9 is *not* a good way of stopping > >>>>>> WebDNA... at least not > >>>>> > >>>>> for 6.2 which still uses WebDNAMonitor. > >>>>> > >>>>>> Anyway, the script seems to contain logical > >>>>>> problems in my opinion. > >>>>>> > >>>>>> If you were to use it, I'd change it to 199%... > >>>>>> and change the 'kill -9' > >>>>> > >>>>> to > >>>>> '/Library/WebServer/WebCatalogEngine/WebCatalogCtl > >>>>> restart'. > >>>>> > >>>>>> To fix the script, there is a change to how 'ps' > >>>>>> functions in Snow > >>>>> > >>>>> Leopard.. > >>>>> > >>>>>> basically change the instances of "ps -aux" in > >>>>>> your script to "ps aux". > >>>>>> > >>>>>> To fix your CPU issue, I'd start looking into > >>>>>> standard troubleshooting > >>>>> > >>>>> techniques.. looking at logs, looking for overgrown > >>>>> log files etc.. > >>>>> > >>>>>> Donovan > >>>>> > >>>>> Thanks for the input Donovan. > >>>>> > >>>>> I'm not sure if I'm going to use it or not, at this > >>>>> point. Its just an avenue I'm looking at, unless > >>>>> there is a better solution. I did notice, however, > >>>>> that when WebDNA dies, the CPU hoovers around 60%, > >>>>> so I'm not sure this will even work when it acts > >>>>> up. > >>>>> > >>>>> I've been looking at the logs trying to pin out > >>>>> down, but it happens so rarely that its hard to > >>>>> get a handle on it... :-( .. I think all turn on > >>>>> everything in the Prefs Technical section for a > >>>>> while to see if I can catch it. > >>>>> > >>>>> Rob > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
Do these problems occur on Linux or Windows servers or only on OSX? How long does the process remain so high? Was there visitor activity that could have caused it? Any templates requested upon restart? Sincerely, Kenneth Grome > Ok, this acted up again, and am not getting errors in the > debug, or any error logs, which is strange. The > processor just climbed to 180% on the WebCatalog > process. I am getting a few lines in the signal > termination log, but that's it, and a couple of them > were probably generated by me trying to get it to start. > > ---Mon Jan 23 06:03:56 2012 MST Processid 66785 receive > SIGTERM: ---Mon Jan 23 07:56:02 2012 MST Processid 66958 > receive SIGTERM: ---Mon Jan 23 07:59:02 2012 > MST Processid 69107 receive SIGTERM: > > However, I am getting a weird error when I trigger > /Library/WebServer/CGI-Executables/WebCatalogEngine/WebC > atalogCtl restart in terminal. I get about ten or twelve > lines of: > > "sem_open failed: returned ENOSPC: No space left on device" > > and can't exit terminal without quitting it. > > Not sure at all what that error is, any ideas? The server > has 450 gigs of free space(Mac os x 10.6.8, WebDNA 6.2). > I did do an uninstall, and complete reinstall of WebDNA, > but it still comes up with this same error on restart. > WebDNA does start and run normally though. > > We will eventually move over to version 7, but can't get > at it for a few months, so need to get this stable for > now, or at least to the point where we don't have to > babysit it. > > Rob > > On Jan 19, 2012, at 5:55 AM, Rob wrote: > > Hi Robert > > > > On Jan 18, 2012, at 8:27 PM, Robert Minor wrote: > >> Maybe the thought he was funny. > >> > >> Was your old server intel based? > > > > No, it was PPC... 10.4.11 > > > >> did you turn on the troubleshooting tools? > > > > Yes, they are on now... Hoping to catch it the next > > time it happens. > > > > > > Rob > > > >> On Jan 18, 2012, at 6:37 PM, Rob wrote: > >>> Uuuuh...the server is only six months old.... how new > >>> do you want me to try?... All that's happened is we > >>> retired an old server, that wasn't having any > >>> problems, but it was over 5 years old, and we just > >>> didn't trust it any more, and to replace internal > >>> hardware would cost more then purchasing a new one. > >>> > >>> > >>> Rob > >>> > >>> On Jan 18, 2012, at 4:35 PM, William DeVaul wrote: > >>>> Try a new server. Worked wonders for me. > >>>> > >>>> Bill > >>>> > >>>> On Wed, Jan 18, 2012 at 11:18 AM, Rob wrote: > >>>>> On Jan 18, 2012, at 10:00 AM, Donovan Brooke wrote: > >>>>>> Rob wrote: > >>>>>>> Hi All, > >>>>>>> > >>>>>>> Very rarely(once every couple months) I have > >>>>>>> WebDNA 6.2 stop, and drive > >>>>> > >>>>> the CPU nuts on Snow Leopard Server, and am looking > >>>>> at adding a script to keep an eye on it while I go > >>>>> on vacation. I found an old script... not sure > >>>>> where it come from or where I got it, but I had it > >>>>> on one of the old servers, and would like to get > >>>>> it working using launchd to start it, which isn't > >>>>> the problem. When I trigger the script, it comes > >>>>> up with "ps: No user named 'x'". Which is fairly > >>>>> obvious to those who no about these scripts, which > >>>>> I don't. > >>>>> > >>>>>>> So my question is, does anyone know how to get > >>>>>>> this working, or is > >>>>> > >>>>> there a better way? ... Script below. > >>>>> > >>>>>>> Rob > >>>>>> > >>>>>> I wouldn't use that script for a couple reasons. > >>>>>> > >>>>>> First, It's not bad if your server shoots up to a > >>>>>> 145% usage (2 CPU's) > >>>>> > >>>>> for short instances now and then.. > >>>>> > >>>>>> Second, kill -9 is *not* a good way of stopping > >>>>>> WebDNA... at least not > >>>>> > >>>>> for 6.2 which still uses WebDNAMonitor. > >>>>> > >>>>>> Anyway, the script seems to contain logical > >>>>>> problems in my opinion. > >>>>>> > >>>>>> If you were to use it, I'd change it to 199%... > >>>>>> and change the 'kill -9' > >>>>> > >>>>> to > >>>>> '/Library/WebServer/WebCatalogEngine/WebCatalogCtl > >>>>> restart'. > >>>>> > >>>>>> To fix the script, there is a change to how 'ps' > >>>>>> functions in Snow > >>>>> > >>>>> Leopard.. > >>>>> > >>>>>> basically change the instances of "ps -aux" in > >>>>>> your script to "ps aux". > >>>>>> > >>>>>> To fix your CPU issue, I'd start looking into > >>>>>> standard troubleshooting > >>>>> > >>>>> techniques.. looking at logs, looking for overgrown > >>>>> log files etc.. > >>>>> > >>>>>> Donovan > >>>>> > >>>>> Thanks for the input Donovan. > >>>>> > >>>>> I'm not sure if I'm going to use it or not, at this > >>>>> point. Its just an avenue I'm looking at, unless > >>>>> there is a better solution. I did notice, however, > >>>>> that when WebDNA dies, the CPU hoovers around 60%, > >>>>> so I'm not sure this will even work when it acts > >>>>> up. > >>>>> > >>>>> I've been looking at the logs trying to pin out > >>>>> down, but it happens so rarely that its hard to > >>>>> get a handle on it... :-( .. I think all turn on > >>>>> everything in the Prefs Technical section for a > >>>>> while to see if I can catch it. > >>>>> > >>>>> Rob > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Kenneth Grome
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:
Getting Started (2003)
New iMac, now ... how do I make webdna serve .html files? (2005)
Stumped by [thisUrl] (2006)
Setting up shop (1997)
Faxing orders in place of email (1997)
Storebuilder (2000)
Upgrade to wsV (2004)
format problem on NT? (1997)
Maybe off topic but how to charge (1997)
Mime Headers for Mail (1998)
Configuring E-mail (1997)
RE: Signal Raised (1997)
WebCatalog for guestbook ? (1997)
Simple way to create unique SKU (1997)
Emailer port change (1997)
[WebDNA] TCPConnect Problem (2010)
URGENT: Can't email orders - HELP #2 (1998)
searches with dash, period etc. (back form politeness) (2000)
Limiting user access to .tmpl files (1997)
HELP WITH DATES (1997)