Conveyor 2.2.2 going wild with MakerWare 2.2.2.89 ?

[D Woale]

Conveyord seems to recycle every second (or so), each time listening to port++

Anyone else experiencing this ?

Log shows ;

2013-08-23 14:28:49,993 - INFO - conveyord 2.2.2 started

2013-08-23 14:28:49,993 - INFO - process id: 3056

2013-08-23 14:28:49,993 - INFO - python version: '2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)]'

2013-08-23 14:28:50,025 - INFO - python platform: 'Windows-7-6.1.7601-SP1'

2013-08-23 14:28:50,025 - INFO - python pointer size: 32

2013-08-23 14:30:50,704 - INFO - accepted TCP connection: 127.0.0.1:49229

2013-08-23 14:30:53,543 - INFO - accepted TCP connection: 127.0.0.1:49245

...

2013-08-23 14:31:01,562 - INFO - accepted TCP connection: 127.0.0.1:49300

2013-08-23 14:31:01,562 - CRITICAL - internal error

Traceback (most recent call last):

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\error.py", line 271, in guard

    code = func()

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\server\__init__.py", line 579, in func

    self._jsonrpc.run()

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\jsonrpc.py", line 201, in run

    self._jsonreader.feed(data)

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\json.py", line 320, in feed

    self._consume(ch)

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\json.py", line 191, in _consume

    self._send()

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\json.py", line 314, in _send

    self._callback(data)

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\jsonrpc.py", line 103, in _jsonreadercallback

    self._send(outdata)

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\jsonrpc.py", line 186, in _send

    self._outfp_writer.write(data)

  File "C:\MakerBot\MakerWare\virtualenv\lib\codecs.py", line 352, in write

    self.stream.write(data)

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\connection.py", line 89, in write

    sent = self._socket.send(data[i:])

error: [Errno 10054] An existing connection was forcibly closed by the remote host

2013-08-23 14:31:02,576 - INFO - accepted TCP connection: 127.0.0.1:49303

2013-08-23 14:31:02,576 - CRITICAL - internal error

Traceback (most recent call last):

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\error.py", line 271, in guard

    code = func()

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\server\__init__.py", line 579, in func

    self._jsonrpc.run()

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\jsonrpc.py", line 201, in run

    self._jsonreader.feed(data)

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\json.py", line 320, in feed

    self._consume(ch)

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\json.py", line 191, in _consume

    self._send()

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\json.py", line 314, in _send

    self._callback(data)

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\jsonrpc.py", line 103, in _jsonreadercallback

    self._send(outdata)

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\jsonrpc.py", line 186, in _send

    self._outfp_writer.write(data)

  File "C:\MakerBot\MakerWare\virtualenv\lib\codecs.py", line 352, in write

    self.stream.write(data)

  File "C:\MakerBot\MakerWare\virtualenv\lib\site-packages\conveyor-2.0.0-py2.7.egg\conveyor\connection.py", line 89, in write

    sent = self._socket.send(data[i:])

error: [Errno 10053] An established connection was aborted by the software in your host machine

2013-08-23 14:31:03,591 - INFO - accepted TCP connection: 127.0.0.1:49304

2013-08-23 14:31:03,591 - CRITICAL - internal error

Traceback (most recent call last):

...

[Jetguy]

Most people don't try to talk to a loopback IP address (TCP connection: 127.0.0.1:49304)?

Something is screwy with your python in what it though was a valid com port.

I'd say no, nobody else on the planet has this problem.

 

Reboot and see what it does or remove whatever python you had going before you tried to install Makerware.

[Dan Newman]

On 23 Aug 2013 , at 10:50 AM, Jetguy wrote:

> Most people don't try to talk to a loopback IP address (TCP connection: *
> 127.0.0.1* <http://127.0.0.1/>:*49304)*?

I agree it's odd for conveyord to be reaching out over IP as it's
basically a server of sorts. My guess is that it was checking for
software updates but how it ended up using the IPv4 loopback is
odd. (Bug? Maybe conveyor tries to connect back to MW for some
reason? Who knows.)

However, note that TCP/IP is commonly used as an interprocess comms
path when writing cross platform code. It's pretty common denominator
these days unlike other IPC mechanisms (e.g., unix domain sockets,
doorbells, shared memory, etc.). So, I wouldn't be surprised if
MW connects over TCP/IP to Conveyord using the loopback address.
Fairly common actually. (And, odds are, MBI usurped a TCP port
number and hasn't bothered to register the use with IANA.)

Dan

[S Scherrer]

 

 

Conveyor does open a local port and listens. You can see it during installation or in the log. You can even connect to it locally with C:\Program Files (x86)\MakerBot\MakerWare\conveyor-ui.exe

 

Its configuration is conveyor.conf and starts with...

{ // Basic configuration parameters used by both the conveyor client and
  // service.
  "common":
    { // The address of the conveyor service.
      "address": "tcp:127.0.0.1:9999"
    , // The location of the conveyor service PID file.
      "pid_file": "conveyord.pid"
    }

 

With tcpview from sysinternals you do see python.exe listening on that socket.

 

>> Providing it was working before and you did not install a new software (that could conflict on that port listened) or firewall blocking this communication, I would uninstall and resintall. Takes 3mn and would make sure any file is cleaned if any got corrupted.,

Now if you want to xshoot... enable DEBUG in the conf, stop and restart conveyor and get all the details as to why it is failing...

 

Good luck

[Joseph Chiu]

could you have Windows firewall or any security software misconfigured?  (Although I would expect that loopback interfaces would not normally be affected by this, it's still possible to put a blocking rule.)

--
You received this message because you are subscribed to the Google Groups "MakerBot Operators" group.
To unsubscribe from this group and stop receiving emails from it, send an email to makerbot+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Dan Newman]

On 23 Aug 2013 , at 11:49 AM, S Scherrer wrote:

>
>
> Conveyor does open a local port and listens. You can see it during
> installation or in the log.

Yup, it's binding and listening with accept. And they also
did the unprofessional naughty act of usurping a TCP port, 9999. Amateur hour.
That port is registered for use by distinct.com and used by their
software products. It's one thing to in-house use a convenient
port number. However, it's an entirely different -- and unprofessional --
to then release said code to customers. You want to cause support
headache for your own company, that's your business. But don't
cause support problems for your customers and another company
which played by the rules and obtained a port assignment from
IANA.

Dan

>> 2013-08-23 14:31:01,562 - INFO - accepted TCP connection: 127.0.0.1:*49300
>> *

>> 2013-08-23 14:31:02,576 - INFO - accepted TCP connection: 127.0.0.1:*49303
>> *

>> 2013-08-23 14:31:03,591 - INFO - accepted TCP connection: 127.0.0.1:*49304
>> *

>> 2013-08-23 14:31:03,591 - CRITICAL - internal error
>> Traceback (most recent call last):
>> ...
>>
>>
>

[Dan Newman]

On 23 Aug 2013 , at 12:34 PM, Joseph Chiu wrote:

> could you have Windows firewall or any security software misconfigured?
> (Although I would expect that loopback interfaces would not normally be
> affected by this, it's still possible to put a blocking rule.)

It's perfectly fine and VERY common to use 127.0.0.1 or ::1 for interprocess
communication. And that's likely what is going on here: conveyord likely binds
to INADDR_ANY (all available IP interfaces) using TCP port 9999. Then MakerWare
just connects to the loopback addr, 127.0.0.1, on the same port. That's then
how the two processes chit-chat. Completely normal. And completely unprofessional
to release commercial code usurping another product's rightfully registered
TCP port, 9999.

Dan

[D Woale]

Ok, just reinstalled python 2.7.3 and MakerWare 2.2.2.89 to fix this.
Thanks all to have checked this out.