Installation problems

[ryan]

Hello

I'm new to APE, so please forgive me if any of this is really newbie
stuff - I've gone through the docs and made sense of what I can, and
I'm still at a loss.

I've installed APE (v 1.00) on my Media Temple (dv) server, so its
running Cent OS, and I used the RPM package to install. I've set
everything up in the ape.conf and demos/config.js file as instructed,
however when I run the APE_JSF/Tools/Check/ script, I get the
following:

...
Running test : Contacting APE Server
Connection etablished but something went wrong. Server response is
[{"time":"1260705364","raw":"ERR","data":
{"code":"003","value":"BAD_CMD"}}]
...

And when I run the any of the demos (eg the chat room), it just loads
something like 2.ape.rtnetworks.net/?[json] until it times out - the
server never responds to the request...

Help?!

Thanks,
Ryan

[Nicolas Trani]

Hi,

the error you have with the check tool mean that the checkTool module is
not loaded.

Edit your ape.conf and set "daemon = no" then start your APE server :

/usr/bin/ape-server --cfg /etc/ape/ape.conf

The serveur should output something like that :

[.......]
[Module] [spidermonkey] Loading module : Javascript embeded (0.01) -
Anthony Catel
[JS] Loading script /var/ape/framework/mootools.js
[JS] Loading script /var/ape/framework/Http.js
[JS] Loading script /var/ape/framework/userslist.js
[JS] Loading script /var/ape/utils/utils.js
[JS] Loading script /var/ape/commands/proxy.js
[.......]

If it's not the case it should outpout some error, post it here.

Regards.

--
Nicolas Trani - D�veloppeur web
Weelya - Improve the web
32 rue du faubourg boutonnet
34090 Montpellier
Tel : 04 67 169 778
http://www.weelya.com

[ryan]

Hello

Yeah I have daemon = no in the ape.conf...
When I start the server i get the spidermonkey line, and then no
others after that, so I guess the scripts aren't loading. Any reason
why that would be? They are in the same folder as the modules
folder...

Thanks for your help,
Ryan

[Nicolas Trani]

Hi,

if you installed the APE Server with deb or RPM scripts are in /var/ape/
if it's precompiled or git, scripts are in scripts directory. Check the
js file is readable, also check the conf file javascript.conf it
contain the path to scripts directory. Depend on your setup it can be in
/etc/ape/javascript.conf (package), or conf/ (precompiled) or
modules/conf/ (git or src).

Cheers.

ryan a �crit :

[ryan]

Ok, thats great - the scripts are now loading and i've got a bit
further now.
On the tools/check script, I now get the error:

...
Running test : Initializing APE Client
Can't load APE JSF
...

I really really appreciate your help! Can't wait to get going with
APE.

Thanks,
Ryan

[Nicolas Trani]

Humm, Can you check with firebug you have no error? Do you see some file that fail to load in firebug (net tab)? Please note if you are using FF 3.5 some JS error are not showed (FF bug), use FF 3.0 or 3.7 do to those test.

[ryan]

Yeah there is no error, just a page that keeps on loading:
http://1.ape.rtnetworks.net:6969/?[{%22cmd%22:%22script%22,%22params%22:{%22domain%22:%22ape.rtnetworks.net%22,%22scripts%22:[%22/APE_JSF/Source/mootools-core.js%22,%22/APE_JSF/Source/Core/APE.js%22,%22/APE_JSF/Source/Core/Events.js%22,%22/APE_JSF/Source/Core/Core.js%22,%22/APE_JSF/Source/Pipe/Pipe.js%22,%22/APE_JSF/Source/Pipe/PipeProxy.js%22,%22/APE_JSF/Source/Pipe/PipeMulti.js%22,%22/APE_JSF/Source/Pipe/PipeSingle.js%22,%22/APE_JSF/Source/Request/Request.js%22,%22/APE_JSF/Source/Request/Request.Stack.js%22,%22/APE_JSF/Source/Request/Request.CycledStack.js%22,%22/APE_JSF/Source/Transport/Transport.longPolling.js%22,%22/APE_JSF/Source/Transport/Transport.SSE.js%22,%22/APE_JSF/Source/Transport/Transport.XHRStreaming.js%22,%22/APE_JSF/Source/Transport/Transport.JSONP.js%22,%22/APE_JSF/Source/Core/Utility.js%22,%22/APE_JSF/Source/Core/JSON.js%22]}}]

[ryan]

PS - the server is running, so if it helps to do any testing direct,
just go to http://ape.rtnetworks.net ... everything should be at the
expected paths after that.

[Anthony Catel]

Hi,

You have very strange things here. I did some test on your server.
It looks like there is something like a filter that hook the connection.

Any idea?

Le 13/12/09 20:50, ryan a écrit :

[ryan]

Its a brand new server, and all I've done so far is install the RPM
from your website.
So there should be nothing else interfering with APE server.

[ryan]

Hmm, I've downloaded the src and run "make" on it - building a system
specific version, but still no luck. I get the same problem - it gets
no return from the server and I get "Can't load APE JSF" on the tools/
check script.

I'm off to bed - but I'm about tomorrow and would love to get to the
bottom of this!

[Anthony Catel]

Did you run build.sh ?

Anthony

Le 13/12/09 23:36, ryan a �crit :

[ryan]

Yep, ran it and all seemed well. A few warnings about null being
replaced, but nothing else.
Then i ran the generated aped, but still no luck.

[ryan]

Hello

I got a bit more time to look into this, and found a work around. It
might be useful for the devs to look at this too, as its probably
worth implementing across the board?

The problem seemed to be with { and }, but nothing on the server
seemed to be causing it. So I changed one of the lines in the Client/
Mootools.js file:

line #98
iframe.set('src', 'http://' + config.frequency + '.' +
config.server + '/?' + escape('[{"cmd":"script","params":{"domain":"'
+ document.domain + '","scripts":["' + config.scripts.join('","') +
'"]}}]'));

notice I added an escape() around the parameters being passed.

Now everything seems to work without a problem...

Thanks,
Ryan

[Nicolas Trani]

Hi ryan,

Some other people had the same issue with {} (but i don't know why).
I'll do some check and update the JSF. Thanks :)

Cheers.