Hmmm something weird just happened. I restarted Komanche, then when I saved
the image and the CPU rushed to 100%!


2013/9/25 Janko Mivšek <janko.miv...@eranova.si>

> Hi Bernat,
>
> I remember once having similar problems on Swazoo. But on image restart.
> If Swazoo was not stopped before image shutdown, image went into 100%
> CPU after restart. Something like that. It seems therefore that this is
> sockets related problem
>
> What if you stop your web server and start again?
>
> Best regards
> Janko
>
> Dne 25. 09. 2013 10:03, piše Bernat Romagosa:
> > Forgot to answer that I'm not using RFB. I had sooo many problems with
> > it that since last year I've been using xpra <http://xpra.org/> instead,
> > which lets you capture running X windows remotely over SSH. It's kind of
> > like screen (not even remotely so powerful) but for GUIs.
> >
> > Cheers,
> > Bernat.
> >
> >
> > 2013/9/25 Bernat Romagosa <tibabenfortlapala...@gmail.com
> > <mailto:tibabenfortlapala...@gmail.com>>
> >
> >     Not really, the image is not being saved regularly... all data is
> >     stored in a neo4j database, so there's no need to save the image.
> >
> >     It seems like it may have something to do with users uploading files
> >     in some particular moments, but I'm using Göran's file upload
> >     mechanism, in which files are streamed straight to disk, so there
> >     shouldn't be any image clogging problems even for huge files...
> >
> >     2013/9/24 Mariano Martinez Peck <marianop...@gmail.com
> >     <mailto:marianop...@gmail.com>>
> >
> >         Bernat, could this be triggered when you SAVE the image? If
> >         true, do you happen to have RFB running?
> >
> >
> >         On Tue, Sep 24, 2013 at 4:45 AM, Bernat Romagosa
> >         <tibabenfortlapala...@gmail.com
> >         <mailto:tibabenfortlapala...@gmail.com>> wrote:
> >
> >             Hi list,
> >
> >             A couple months ago I deployed an Iliad application in a
> >             Debian VPS, which has been working great except for the fact
> >             that about every two weeks the image takes up 100% of the
> >             CPU and, of course, the app becomes unusable.
> >
> >             Does anyone have a method for finding out what's going on?
> >             I've been trying to debug the problem, but as I don't know
> >             what triggers it, it's pretty impossible to detect...
> >
> >             I've checked the running threads and nothing seems unusual.
> >             I've also profiled the app for a whole day of real usage
> >             with end users and not a single method took more time than
> >             what I expected, so I'm completely lost here.
> >
> >             Any help will be appreciated! :)
>
>
> --
> Janko Mivšek
> Aida/Web
> Smalltalk Web Application Server
> http://www.aidaweb.si
>
>


-- 
Bernat Romagosa.

Reply via email to