Comment 32 for bug 43150

Revision history for this message
Ariel Faigon (ariel.faigon) wrote : Re: wxmaxima fails with error, can't connect to maxima

Really sorry! plain-text attachments seem to have their newlines eaten on upload, sigh. What I uploaded is completely unreadable.

Reading more on this bug in the dups, it becomes obvious that the problem is in maxima (when called as a 'server' with -s <portnumber>) rather than in wxmaxima.

Running this simpler example, results in this failure:

    $ maxima -s 7776
    jfa: starting server on port 7776
    couldn't open socket:$

Note that there's not even a newline at the end of the error message.

The strace shows:

21650 socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3
21650 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
21650 connect(3, {sa_family=AF_INET, sin_port=htons(7776), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 ECONNREFUSED (Connection refused)
21650 write(2, "couldn\'t open socket:", 21) = 21
21650 exit_group(1) = ?

So it looks like a bug in maxima. Clearing all the iptables restrictions doesn't change anything. I have no restrictions on localhost connections and I still get 'connection refused'.