[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-apl] [bug-apl] SVN 346 APserver error on startup
From: |
Juergen Sauermann |
Subject: |
Re: [Bug-apl] [bug-apl] SVN 346 APserver error on startup |
Date: |
Sun, 29 Jun 2014 11:16:23 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130330 Thunderbird/17.0.5 |
Hi apm,
looks like APserver is not running.
Normally APserver is forked automatically by the apl interpreter,
but that can fail for numerous reasons. For the automatic
start of APserver it must be:
- executable, and
- located in the same directory as the apl interpreter.
You can also start APserver manually before the apl interpreter.
Other reasons can be security related, such as a firewall preventing
TCP connections from the apl interpreter to APserver on 127.0.0.1.
/// Jürgen
On 06/28/2014 05:47 PM, apm wrote:
I upgraded to SVN 346 and get the following on startup:
$ apl
execve() failed
::connect() to existing APserver failed: Connection refused
*** using local Svar_DB cache
after which the apl workspace is unresponsive unless I press ctrl-C,
then I get the message:
*** Failed to start APnnn: processor 1001 will not accept incoming
shared variable offers. Expect surprises.
Using Linux Mint Debian 64-bit; did the following:
svn update
./configure
make
sudo make install
make clean
APserver is in /usr/local/bin along with the other apl executables.
When I revert to SVN 344 everything works normally.