World: r3wp

static pages ( index.html ) work .. but cgi and rsp don't.

Security Error: Content at http://compkarori.no-ip.biz:8001/ may 
not load or link to chrome://firebug/content/highlighter.css.

In other words, I can't see it in Firebug

Just a crash involving cgi and rsp.  Static pages are still okay.

I've seen that happen here too in rare cases (cause undetermined). 
If you can run the %UniServe/clients/rconsole.r script on your server, 
you should check for this :

probe uniserve/services/task-master/shared/pool-count

I'lll have to wait to I get to work .. unfortunately I don't have 
vnc access to this box

In some cases, this value can be messed up and Cheyenne doesn't seem 
able to start a new process anymore. I've made a small improvement 
in v0.9.19, but I'm unsure how if it will be really efficient.

I'd better upgrade to 9.19

Right, but test well your RSP webapps first with this new version 
before upgrading in production.

Odd .. crashed on me again.  the above probe said 8

This is with 9.19

Have you identified the pattern of actions causing that ?

I was just calling imagemagick ...

but now it's running okay again.  Very odd.

Sounds like the erratic crashes I've been getting. I thought I had 
found a pattern, but no.

It's clearly divide by zero.

Henrik, are your crashes also with the rsp engine?

Graham, I'm not sure. I have to restart Cheyenne to get it going 
again.

are static pages still working when it crashes?

I honestly haven't checked.

please check next time ... well, if you have some static pages!

I will.

It seems that the issue is caused by helper processes being stuck 
in "busy" mode and 'pool-count reaching the max value (8 in v0.9.18), 
so that any new CGI or RSP request coming won't find a free helper 
process. I still don't see why helper processes would remain stuck 
in "busy" mode. I'll run a few tests tomorrow to investigate that 
more deeply.

can we change the max value?

sure

it's not yet exported in config file, but you can change the default 
value in %Cheyenne.r source code.

ok

Hi Henrick, I store my site at %/c/www/

sorry for the delayed response

Crashed again ... static pages still serving, just rsp down and this 
is with 9.19

All I'm doing is editing RSP pages, and running them.

running source code cheyenne.r on OpenSuse  ( I think )

Nicolas, sorry, the question has scrolled out of view here. Would 
you mind posting it again?

Nicholas "Hi, I'm new to cheyenne. I've tried http://localhost/
and I get the message It works!. But I can't view my site.  How can 
I ? Any tips?"

odd ..

should be Cheyenne/www/site here ....

I can't view my site
 <- what exactly happens?

Nicolas.. your site needs to be in Cheyenne's www folder -> %/c/Cheyenne/www 
(or

Doc, is it this line here to increase the nymber of helper processes?

			shared/pool-max: any [all [flag? 'debug 0] 8]

yes, just change the 8 value.

thanks for the help guys

Are there any issues with an rsp script executing scripts in the 
Cheyenne directory?  As opposed to www and below?  I get these odd 
error messages where the script can't access them due to protected-exec

If I can't store scripts above the web root for security purposes 
.. how does one store user lists etc without using a db?

An update on my web fax portal.  http://screencast.com/t/1n1HgxKH8

When I click on a fax, it gets converted to PNG and then the Rebol 
plugin in invoked.  I bring up a new window outside of the browser 
window and display the fax.

Haven't figured out how to invert or rotate the image in place yet, 
so just bring up a new window with the rotated image.

BTW, as soon as Cheyenne starts, it uses 4 in the pool-count.. ?

You can change it in settings and or code. I think.

Would bad RSP code cause the processes to hang increasing the pool-count?

Perhaps that's why you rarely see them ... ??

In theory, if you code bad RSP that, e.g., loops forever without 
crashing, that may cause such situation (helper processes starvation).