Not receiving packets from GEM

[imperial]

I changed the server destination on my GEM to a new box after upgrading firmware to 3.18/1.49. On the new box I moved btmon.py and the old configuration file over, however I'm not receiving any data on the new box. When I run btmon from the command line with debug on, this is what the output looks like-

2015/01/19 18:30:39 %d format: a number is required, not str
Traceback (most recent call last):
File "./btmon.py", line 2070, in _blockingread
self._read(packet_format)
File "./btmon.py", line 2057, in _read
packets.extend(packet_format.read(self))
File "./btmon.py", line 1450, in read
return self._read1(collector, self.DATA_BYTES_LENGTH, self.PACKET_ID)
File "./btmon.py", line 1337, in _read1
data = collector.readbytes(1)
File "./btmon.py", line 2299, in readbytes
dbgmsg('SOCKET: read %d bytes from socket' % nbytes)
TypeError: %d format: a number is required, not str
2015/01/19 18:30:39 waiting 60 seconds before retry
2015/01/19 18:31:39 reading 1 of 1 packets
2015/01/19 18:31:39 failed read 2 of 0
2015/01/19 18:31:39 %d format: a number is required, not str
Traceback (most recent call last):
File "./btmon.py", line 2070, in _blockingread
self._read(packet_format)
File "./btmon.py", line 2057, in _read
packets.extend(packet_format.read(self))
File "./btmon.py", line 1450, in read
return self._read1(collector, self.DATA_BYTES_LENGTH, self.PACKET_ID)
File "./btmon.py", line 1337, in _read1
data = collector.readbytes(1)
File "./btmon.py", line 2299, in readbytes
dbgmsg('SOCKET: read %d bytes from socket' % nbytes)
TypeError: %d format: a number is required, not str
2015/01/19 18:31:39 waiting 60 seconds before retry
2015/01/19 18:32:39 reading 1 of 1 packets
2015/01/19 18:32:39 failed read 3 of 0
2015/01/19 18:32:39 %d format: a number is required, not str
Traceback (most recent call last):
File "./btmon.py", line 2070, in _blockingread
self._read(packet_format)
File "./btmon.py", line 2057, in _read
packets.extend(packet_format.read(self))
File "./btmon.py", line 1450, in read
return self._read1(collector, self.DATA_BYTES_LENGTH, self.PACKET_ID)
File "./btmon.py", line 1337, in _read1
data = collector.readbytes(1)
File "./btmon.py", line 2299, in readbytes
dbgmsg('SOCKET: read %d bytes from socket' % nbytes)
TypeError: %d format: a number is required, not str
2015/01/19 18:32:39 waiting 60 seconds before retry

Any ideas?

[ben]

How are you communicating with the new box?

If via TCP, did you change over the GEMs configuration parameters to point at the new box?

[imperial]

How are you communicating with the new box?

If via TCP, did you change over the GEMs configuration parameters to point at the new box?

I did. I have attached a screen shot of the network utility. 10.115.1.10 is the new box running btmon.

3Kp8PxqVMe.png (123.48 KiB) Viewed 3618 times

[ben]

Can you also copy/paste your btmon config file?

Says Not Connected, is it possible that the ports are mismatched?

[imperial]

Can you also copy/paste your btmon config file?

Says Not Connected, is it possible that the ports are mismatched?

Sorry, I hadn't clicked connect. Here is a screen shot of it connected.

And the config file-

Code: Select all

[source]
device_type = gem
ip_read = true
ip_port = 5000
ip_mode = server
reverse_polarity = 1
[seg]
smartenergygroups_out = true
seg_token = <token>
seg_upload_period = 30

[ben]

Got me a little stumped, everything looks good.

You can try forcing a Ethernet client connection by reducing Idle Time to 0 and setting the Ethernet module to Client mode.

[imperial]

No luck with that either. I'm seeing some malformed packets come across via wireshark but that is about it.

[ben]

What version of Python are you running?

[imperial]

What version of Python are you running?

Python 2.7.9 (default, Jan 7 2015, 11:49:12)
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

[imperial]

Just a note I switched the configuration back to point at the old box I had btmon running on. That box is also not receiving any packets.

I also factory reset the GEM and set it back up last night to no avail as well.