Initial Feeback

Toddimus · October 30, 2019

18 minutes ago, larryllix said:

Thanks Michel!

It appears that all went OK (have to spell 'cryptography' correctly )
However, I seem to have lost my PolyGlot auto-launch. I can get no response from the https://192.168.0.165:3000 now. Rebooted from PuTTY a few times.
Can't seem to navigate around the polisys without some standard linux basics, to investigate further.

Just received my Polisy as well. Seems like fires and power outages delayed its journey a bit.

FWIW, my box had a rattle as well. It was the WiFi card. I opened it up and re-installed the card easily. No big deal there.

I'm having the same issue. Before I did the updates, I could reach the Polisy at https://<ipaddress>:3000 (where <ipaddress> is a reserved address set up in my router's DHCP). Now, after the update and a few reboots from PuTTY, I don't get any response at https://<ipaddress> or https://<ipaddress>:3000 or anything else I can think of. I can ping the Polisy though from a windows CMD prompt.

Michel Kohanim · October 30, 2019

@Toddimus,

What do you get from
ps -aux | grep poly

With kind regards,
Michel

Toddimus · October 30, 2019

6 minutes ago, Michel Kohanim said:

@Toddimus,

What do you get from
ps -aux | grep poly

With kind regards,
Michel

[admin@polisy ~]$ ps -aux | grep poly
polyglot 1507  54.7  2.1 656816 87268  -  R    12:21    0:01.96 /usr/local/bin/
polyglot 1091   0.0  0.1  10768  2188  -  Ss   11:56    0:00.36 daemon: /usr/lo
admin    1509   0.0  0.1  11248  2696  0  S+   12:21    0:00.01 grep poly

EDIT:

I had also tried the killall and stop/start polyglot you mentioned a few posts above. It did seem to make the second polyglot instance go away but still wasn't able to access the web page. Here's what I get after running those commands:

[admin@polisy ~]$ sudo killall daemon
Password:
[admin@polisy ~]$ sudo service polyglot stop
polyglot not running? (check /var/polyglot/polyglot_daemon.pid).
[admin@polisy ~]$ sudo service polyglot start
Starting polyglot.
[admin@polisy ~]$ ps -aux | grep poly
polyglot 1559   0.0  0.1  10768  2336  -  Ss   12:23    0:00.02 daemon: /usr/lo
admin    1572   0.0  0.1  11248  2696  0  S+   12:24    0:00.01 grep poly
[admin@polisy ~]$

Edited October 30, 2019 by Toddimus

Michel Kohanim · October 30, 2019

@Toddimus,

It's definitely running. Are you certain the IP address has not changed (ipconfig igb0) for whatever reason?

With kind regards,
Michel

Toddimus · October 30, 2019

1 minute ago, Michel Kohanim said:

@Toddimus,

It's definitely running. Are you certain the IP address has not changed (ipconfig igb0) for whatever reason?

With kind regards,
Michel

you mean ifconfig?

Yes, it does show the same address as I had reserved on the DHCP server.

Bumbershoot · October 30, 2019

After installing the py37-cryptography package and rebooting, Polyglot has entered an unproductive state.

Polyglot itself is running, but none of the individual nodeservers are.

[admin@polisy /var/polyglot/log]$ ps aux | grep poly
polyglot 1216  66.9  2.6 684776 108124  -  R    12:29    0:03.44 /usr/local/bin/polyglot-v2-freebsd-x64 -w /var/polyglot
polyglot 1023   0.0  0.1  10768   2188  -  Ss   12:24    0:00.07 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[1216] (daemon)
admin    1218   0.0  0.1  11248   2696  0  S+   12:29    0:00.01 grep poly

From the logs:

2019-10-30 10:42:33 [polyglot] error: MQTTS: clientError: DARKSKY read ECONNRESET
2019-10-30 10:42:33 [polyglot] error: unhandledRejection REPORT THIS!: MongoError: interrupted at shutdown
    at Connection.Pool.socketCount (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/pool.js:466:61)
    at Connection.emit (events.js:159:13)
    at processMessage (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:364:10)
    at Socket.module.exports (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:533:15)
    at Socket.emit (events.js:159:13)
    at addChunk (_stream_readable.js:265:12)
    at readableAddChunk (_stream_readable.js:252:11)
    at Socket.Readable.push (_stream_readable.js:209:10)
    at TCP.onread (net.js:598:20)
2019-10-30 10:42:33 [polyglot] info: Caught SIGTERM/SIGINT Shutting down.
2019-10-30 10:42:33 [polyglot] info: MQTTS: Client Disconnected:
2019-10-30 10:42:33 [polyglot] error: unhandledRejection REPORT THIS!: MongoError: interrupted at shutdown
    at Connection.Pool.socketCount (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/pool.js:466:61)
    at Connection.emit (events.js:159:13)
    at processMessage (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:364:10)
    at Socket.module.exports (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:533:15)
    at Socket.emit (events.js:159:13)
    at addChunk (_stream_readable.js:265:12)
    at readableAddChunk (_stream_readable.js:252:11)
    at Socket.Readable.push (_stream_readable.js:209:10)
    at TCP.onread (net.js:598:20)
2019-10-30 10:42:33 [polyglot] error: unhandledRejection REPORT THIS!: MongoError: interrupted at shutdown
    at Connection.Pool.socketCount (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/pool.js:466:61)
    at Connection.emit (events.js:159:13)
    at processMessage (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:364:10)
    at Socket.module.exports (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:533:15)
    at Socket.emit (events.js:159:13)
    at addChunk (_stream_readable.js:265:12)
    at readableAddChunk (_stream_readable.js:252:11)
    at Socket.Readable.push (_stream_readable.js:209:10)
    at TCP.onread (net.js:598:20)
2019-10-30 10:42:33 [polyglot] error: unhandledRejection REPORT THIS!: MongoError: interrupted at shutdown
    at Connection.Pool.socketCount (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/pool.js:466:61)
    at Connection.emit (events.js:159:13)
    at processMessage (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:364:10)
    at Socket.module.exports (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:533:15)
    at Socket.emit (events.js:159:13)
    at addChunk (_stream_readable.js:265:12)
    at readableAddChunk (_stream_readable.js:252:11)
    at Socket.Readable.push (_stream_readable.js:209:10)
    at TCP.onread (net.js:598:20)
2019-10-30 10:42:33 [polyglot] error: unhandledRejection REPORT THIS!: MongoError: interrupted at shutdown
    at Connection.Pool.socketCount (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/pool.js:466:61)
    at Connection.emit (events.js:159:13)
    at processMessage (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:364:10)
    at Socket.module.exports (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:533:15)
    at Socket.emit (events.js:159:13)
    at addChunk (_stream_readable.js:265:12)
    at readableAddChunk (_stream_readable.js:252:11)
    at Socket.Readable.push (_stream_readable.js:209:10)
    at TCP.onread (net.js:598:20)
2019-10-30 10:42:33 [polyglot] error: unhandledRejection REPORT THIS!: MongoError: interrupted at shutdown
    at Connection.Pool.socketCount (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/pool.js:466:61)
    at Connection.emit (events.js:159:13)
    at processMessage (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:364:10)
    at Socket.module.exports (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:533:15)
    at Socket.emit (events.js:159:13)
    at addChunk (_stream_readable.js:265:12)
    at readableAddChunk (_stream_readable.js:252:11)
    at Socket.Readable.push (_stream_readable.js:209:10)
    at TCP.onread (net.js:598:20)
2019-10-30 10:42:34 [polyglot] error: unhandledRejection REPORT THIS!: MongoError: interrupted at shutdown
    at Connection.Pool.socketCount (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/pool.js:466:61)
    at Connection.emit (events.js:159:13)
    at processMessage (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:364:10)
    at Socket.module.exports (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:533:15)
    at Socket.emit (events.js:159:13)
    at addChunk (_stream_readable.js:265:12)
    at readableAddChunk (_stream_readable.js:252:11)
    at Socket.Readable.push (_stream_readable.js:209:10)
    at TCP.onread (net.js:598:20)
2019-10-30 10:42:34 [polyglot] error: unhandledRejection REPORT THIS!: MongoError: interrupted at shutdown
    at Connection.Pool.socketCount (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/pool.js:466:61)
    at Connection.emit (events.js:159:13)
    at processMessage (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:364:10)
    at Socket.module.exports (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:533:15)
    at Socket.emit (events.js:159:13)
    at addChunk (_stream_readable.js:265:12)
    at readableAddChunk (_stream_readable.js:252:11)
    at Socket.Readable.push (_stream_readable.js:209:10)
    at TCP.onread (net.js:598:20)
2019-10-30 10:42:34 [polyglot] error: unhandledRejection REPORT THIS!: MongoError: interrupted at shutdown
    at Connection.Pool.socketCount (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/pool.js:466:61)
    at Connection.emit (events.js:159:13)
    at processMessage (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:364:10)
    at Socket.module.exports (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:533:15)
    at Socket.emit (events.js:159:13)
    at addChunk (_stream_readable.js:265:12)
    at readableAddChunk (_stream_readable.js:252:11)
    at Socket.Readable.push (_stream_readable.js:209:10)
    at TCP.onread (net.js:598:20)
2019-10-30 10:42:34 [polyglot] error: unhandledRejection REPORT THIS!: MongoError: interrupted at shutdown
    at Connection.Pool.socketCount (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/pool.js:466:61)
    at Connection.emit (events.js:159:13)
    at processMessage (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:364:10)
    at Socket.module.exports (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:533:15)
    at Socket.emit (events.js:159:13)
    at addChunk (_stream_readable.js:265:12)
    at readableAddChunk (_stream_readable.js:252:11)
    at Socket.Readable.push (_stream_readable.js:209:10)
    at TCP.onread (net.js:598:20)
2019-10-30 10:42:34 [polyglot] error: unhandledRejection REPORT THIS!: MongoError: interrupted at shutdown
    at Connection.Pool.socketCount (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/pool.js:466:61)
    at Connection.emit (events.js:159:13)
    at processMessage (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:364:10)
    at Socket.module.exports (/snapshot/polyglot-v2/node_modules/mongodb/lib/core/connection/connection.js:533:15)
    at Socket.emit (events.js:159:13)
    at addChunk (_stream_readable.js:265:12)
    at readableAddChunk (_stream_readable.js:252:11)
    at Socket.Readable.push (_stream_readable.js:209:10)
    at TCP.onread (net.js:598:20)
2019-10-30 10:42:34 [polyglot] info: MQTTS: Client Disconnected:
2019-10-30 10:42:34 [polyglot] info: MQTTS: Client Disconnected:
2019-10-30 10:42:34 [polyglot] info: MQTTS: Client Disconnected:
2019-10-30 10:42:34 [polyglot] info: MQTTS: Client Disconnected:
2019-10-30 10:42:35 [polyglot] info: LiFX(4):: Not running. Ignoring stop command.
2019-10-30 10:43:33 [polyglot] info: Starting Polyglot....
2019-10-30 10:43:33 [polyglot] info: Settings: Polyglot Version 2.2.5
2019-10-30 10:43:33 [polyglot] info: Settings: Retrieved config from database
2019-10-30 10:43:33 [polyglot] info: Running in Polisy mode
2019-10-30 10:43:33 [polyglot] info: Settings: Retrieved config overrides from .env and updated database
2019-10-30 10:43:33 [polyglot] info: Aedes MQTT Broker Service: Started on port 1883
2019-10-30 10:43:38 [polyglot] info: Starting Polyglot....
2019-10-30 10:43:39 [polyglot] info: Settings: Polyglot Version 2.2.5
2019-10-30 10:43:39 [polyglot] info: Settings: Retrieved config from database
2019-10-30 10:43:39 [polyglot] info: Running in Polisy mode
2019-10-30 10:43:39 [polyglot] info: Settings: Retrieved config overrides from .env and updated database
2019-10-30 10:43:44 [polyglot] info: Starting Polyglot....
2019-10-30 10:43:44 [polyglot] info: Settings: Polyglot Version 2.2.5

larryllix · October 30, 2019

17 minutes ago, Michel Kohanim said:

@Toddimus,

What do you get from
ps -aux | grep poly

With kind regards,
Michel

@Michel Kohanim

No such port 443 luck. IP address has not changed in router. Here is what I get.

Welcome to Polisy!
[admin@polisy ~]$ ps -aux | grep poly
polyglot 1748 62.4 3.1 697284 128824 - R 12:32 0:04.25 /usr/local/bin/polyglot-v2-fr
polyglot 1009 0.0 0.1 10768 2188 - Ss 11:39 0:00.70 daemon: /usr/local/bin/polygl
admin 1750 0.0 0.1 11248 2696 0 S+ 12:32 0:00.01 grep poly
[admin@polisy ~]$

Edited October 30, 2019 by larryllix

Toddimus · October 30, 2019

More info...

FWIW, I did the crypto updates you mentioned a few posts back. Don't know if that's part of the problem. I also for grins, ran the grep line a few times and found that the PID seems to be changing. Doesn't that mean the process is continually restarting??


[admin@polisy ~]$ ps -aux | grep poly
polyglot 1559   0.0  0.1  10768  2336  -  Ss   12:23     0:00.21 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[1734] (daemon)
admin    1736   0.0  0.1  11248  2696  0  S+   12:38     0:00.01 grep poly
[admin@polisy ~]$ ps -aux | grep poly
polyglot 1737  68.4  3.3 706424 135960  -  R    12:38     0:05.20 /usr/local/bin/polyglot-v2-freebsd-x64 -w /var/polyglot
polyglot 1559   0.0  0.1  10768   2336  -  Ss   12:23     0:00.21 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[1737] (daemon)
admin    1739   0.0  0.1  11248   2696  0  S+   12:38     0:00.01 grep poly
[admin@polisy ~]$ ps -aux | grep poly
polyglot 1740  53.1  2.3 679328 95832  -  R    12:38     0:02.44 /usr/local/bin/polyglot-v2-freebsd-x64 -w /var/polyglot
polyglot 1559   0.0  0.1  10768  2336  -  Ss   12:23     0:00.21 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[1740] (daemon)
admin    1742   0.0  0.1  11248  2696  0  S+   12:38     0:00.01 grep poly
[admin@polisy ~]$ ps -aux | grep poly
polyglot 1559   0.0  0.1  10768  2336  -  Ss   12:23     0:00.21 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[1743] (daemon)
polyglot 1743   0.0  1.4 604688 56488  -  R    12:38     0:00.66 /usr/local/bin/polyglot-v2-freebsd-x64 -w /var/polyglot
admin    1745   0.0  0.1  11248  2696  0  S+   12:38     0:00.01 grep poly
[admin@polisy ~]$ ps -aux | grep poly
polyglot 1559   0.0  0.1  10768  2336  -  Ss   12:23     0:00.21 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[1746] (daemon)
polyglot 1746   0.0  1.3 602092 53956  -  R    12:38     0:00.60 /usr/local/bin/polyglot-v2-freebsd-x64 -w /var/polyglot
admin    1748   0.0  0.1  11248  2696  0  S+   12:38     0:00.01 grep poly
[admin@polisy ~]$

Bumbershoot · October 30, 2019

6 minutes ago, Toddimus said:
Doesn't that mean the process is continually restarting??
 

I'm seeing the same thing after the crypto updates.

Bumbershoot · October 30, 2019

Starting Polyglot at the command line after the crypto updates:

[admin@polisy /usr/local/bin]$ ./polyglot-v2-freebsd-x64 
WARNING: The `useMongoClient` option is no longer necessary in mongoose 5.x, please remove it.
    at handleUseMongoClient (/snapshot/polyglot-v2/node_modules/mongoose/lib/connection.js:738:17)
    at NativeConnection.Connection.openUri (/snapshot/polyglot-v2/node_modules/mongoose/lib/connection.js:572:7)
    at Mongoose.connect (/snapshot/polyglot-v2/node_modules/mongoose/lib/index.js:327:15)
    at Object.start (/snapshot/polyglot-v2/lib/services/db.js:40:40)
    at start (/snapshot/polyglot-v2/bin/polyglot-v2.js:101:14)
    at Object.<anonymous> (/snapshot/polyglot-v2/bin/polyglot-v2.js:215:1)
    at Module._compile (pkg/prelude/bootstrap.js:1243:22)
    at Object.Module._extensions..js (module.js:650:10)
    at Module.load (module.js:558:32)
    at tryModuleLoad (module.js:501:12)
    at Function.Module._load (module.js:493:3)
    at Function.Module.runMain (pkg/prelude/bootstrap.js:1298:12)
    at startup (bootstrap_node.js:227:16)
    at bootstrap_node.js:649:3
(node:1307) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.
(node:1307) DeprecationWarning: current Server Discovery and Monitoring engine is deprecated, and will be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUnifiedTopology: true } to the MongoClient constructor.
[winston] Attempt to write logs with no transports {"message":"Polyglot shutdown complete with code: 1","level":"info"}

larryllix · October 30, 2019

My RPi Polyglot would never load v2.2.5, in case that is related. Now the offer of v2.2.5 is gone from the PolyGlot everywhere.

Bumbershoot · October 30, 2019

2 minutes ago, larryllix said:

My RPi Polyglot would never load v2.2.5, in case that is related. Now the offer of v2.2.5 is gone from the PolyGlot everywhere.

Well, 2.2.5_4 was running fine prior to the last command in this sequence (reboot):

[admin@polisy ~]$ ps aux | grep poly
polyglot 4043  31.0  3.9 735316 160240  -  S    09:49      5:08.74 /usr/local/bin/polyglot-v2-freebsd-x64 -w /var/polyglot
polyglot 4047   9.3  0.7  47568  29524  -  Is   09:49      1:53.53 python3 ./sonos-poly.py (python3.7)
polyglot 3619   1.6  0.7  46872  29536  -  Is   05:59      2:26.99 python3 ./darksky.py (python3.7)
polyglot 4046   1.6  0.8  51424  31424  -  Is   09:49      0:07.92 python3 ./wirelesstags-poly.py (python3.7)
polyglot 4049   1.4  0.7  48100  30500  -  Is   09:49      0:24.07 python3 ./darksky.py (python3.7)
polyglot 3966   1.1  0.7  47604  30152  -  Is   09:00      1:18.68 python3 ./darksky.py (python3.7)
polyglot 1011   0.0  0.1  10768   2192  -  Is   10:33      0:00.02 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[4043] (daemon)
polyglot 1840   0.0  0.7  48264  29940  -  Is   16:01     92:56.74 python3 ./sonos-poly.py (python3.7)
polyglot 1866   0.0  0.7  47792  30164  -  Is   16:13      2:36.27 python3 ./darksky.py (python3.7)
polyglot 3618   0.0  0.7  47776  29712  -  Is   05:59     20:08.85 python3 ./sonos-poly.py (python3.7)
polyglot 3964   0.0  0.7  48108  30048  -  Is   09:00      5:29.02 python3 ./sonos-poly.py (python3.7)
polyglot 4044   0.0  0.7  45124  27492  -  Is   09:49      0:02.74 python3 ./push-poly.py (python3.7)
polyglot 4070   0.0  0.6  44380  24528  -  Is   09:56      0:33.76 python3 ./lifx-poly.py (python3.7)
admin    4091   0.0  0.1  11248   2696  0  S+   10:06      0:00.01 grep poly
[admin@polisy ~]$ sudo pkg install py37-netifaces
Password:
Updating udi repository catalogue...
udi repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent versions of packages are already installed
[admin@polisy ~]$ sudo pkg update && sudo pkg upgrade
Updating udi repository catalogue...
udi repository is up to date.
All repositories are up to date.
Updating udi repository catalogue...
udi repository is up to date.
All repositories are up to date.
Checking for upgrades (0 candidates): 100%
Processing candidates (0 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.
[admin@polisy ~]$ sudo pkg install py37-cryptography
Updating udi repository catalogue...
udi repository is up to date.
All repositories are up to date.
The following 5 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	py37-cryptography: 2.6.1
	py37-six: 1.12.0
	py37-cffi: 1.13.1
	py37-pycparser: 2.19
	py37-asn1crypto: 0.24.0

Number of packages to be installed: 5

The process will require 6 MiB more space.
867 KiB to be downloaded.

Proceed with this action? [y/N]: y
[1/5] Fetching py37-cryptography-2.6.1.txz: 100%  327 KiB 334.8kB/s    00:01    
[2/5] Fetching py37-six-1.12.0.txz: 100%   19 KiB  19.0kB/s    00:01    
[3/5] Fetching py37-cffi-1.13.1.txz: 100%  202 KiB 207.3kB/s    00:01    
[4/5] Fetching py37-pycparser-2.19.txz: 100%  163 KiB 167.2kB/s    00:01    
[5/5] Fetching py37-asn1crypto-0.24.0.txz: 100%  156 KiB 159.3kB/s    00:01    
Checking integrity... done (0 conflicting)
[1/5] Installing py37-pycparser-2.19...
[1/5] Extracting py37-pycparser-2.19: 100%
[2/5] Installing py37-six-1.12.0...
[2/5] Extracting py37-six-1.12.0: 100%
[3/5] Installing py37-cffi-1.13.1...
[3/5] Extracting py37-cffi-1.13.1: 100%
[4/5] Installing py37-asn1crypto-0.24.0...
[4/5] Extracting py37-asn1crypto-0.24.0: 100%
[5/5] Installing py37-cryptography-2.6.1...
[5/5] Extracting py37-cryptography-2.6.1: 100%
[admin@polisy ~]$ sudo reboot

This might be helpful to UDI. No joy for Polyglot after the reboot...

larryllix · October 30, 2019

6 minutes ago, Bumbershoot said:

Well, 2.2.5_4 was running fine prior to the last command in this sequence (reboot):

<snipped>

No sign of v2.4.5 anymore here, despite reboots, and refreshes.

Bumbershoot · October 30, 2019

7 minutes ago, larryllix said:

No sign of v2.4.5 anymore here, despite reboots, and refreshes.

I've got my trusty 2.2.4 running on my RPi for fallback. ?

gviliunas · October 30, 2019

I initially had the Polyglot web page open. Then I did:

1. ssh to polisy
2. sudo pkg update && sudo pkg upgrade
3. sudo pkg install py37-netifaces
4. sudo pkg install py37-cryptography
5. sudo reboot

Now, I can ssh into Policy and I can see the tasks running:

[admin@polisy ~]$ ps -aux | grep poly
polyglot 1183 1.4 6.3 833984 260524 - S 13:28 0:05.31 /usr/local/bin/polyglot-v2-freebsd-x64 -w /var/polyglot
polyglot 1009 0.0 0.1 10768 2188 - Ss 13:24 0:00.05 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[1183] (daemon)
admin 1185 0.0 0.1 11248 2696 0 S+ 13:29 0:00.01 grep poly

But, I get a connection refused if I try to access the web UI. I have tried

https://polisy

https://polisy:3000

https://192.168.1.77

https://192.168.1.77:3000

Bumbershoot · October 30, 2019

2 minutes ago, gviliunas said:

I initially had the Polyglot web page open. Then I did:

1. ssh to polisy
2. sudo pkg update && sudo pkg upgrade
3. sudo pkg install py37-netifaces
4. sudo pkg install py37-cryptography
5. sudo reboot

Now, I can ssh into Policy and I can see the tasks running:

[admin@polisy ~]$ ps -aux | grep poly
polyglot 1183 1.4 6.3 833984 260524 - S 13:28 0:05.31 /usr/local/bin/polyglot-v2-freebsd-x64 -w /var/polyglot
polyglot 1009 0.0 0.1 10768 2188 - Ss 13:24 0:00.05 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[1183] (daemon)
admin 1185 0.0 0.1 11248 2696 0 S+ 13:29 0:00.01 grep poly

But, I get a connection refused if I try to access the web UI. I have tried

https://polisy

https://polisy:3000

https://192.168.1.77

https://192.168.1.77:3000

Same symptoms here, exactly. I believe it's the package 'py37-cryptography' that causes the problems. Here's the output of 'ps aux | grep poly' prior to that installation"

[admin@polisy ~]$ ps aux | grep poly
polyglot 4043  31.0  3.9 735316 160240  -  S    09:49      5:08.74 /usr/local/bin/polyglot-v2-freebsd-x64 -w /var/polyglot
polyglot 4047   9.3  0.7  47568  29524  -  Is   09:49      1:53.53 python3 ./sonos-poly.py (python3.7)
polyglot 3619   1.6  0.7  46872  29536  -  Is   05:59      2:26.99 python3 ./darksky.py (python3.7)
polyglot 4046   1.6  0.8  51424  31424  -  Is   09:49      0:07.92 python3 ./wirelesstags-poly.py (python3.7)
polyglot 4049   1.4  0.7  48100  30500  -  Is   09:49      0:24.07 python3 ./darksky.py (python3.7)
polyglot 3966   1.1  0.7  47604  30152  -  Is   09:00      1:18.68 python3 ./darksky.py (python3.7)
polyglot 1011   0.0  0.1  10768   2192  -  Is   10:33      0:00.02 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[4043] (daemon)
polyglot 1840   0.0  0.7  48264  29940  -  Is   16:01     92:56.74 python3 ./sonos-poly.py (python3.7)
polyglot 1866   0.0  0.7  47792  30164  -  Is   16:13      2:36.27 python3 ./darksky.py (python3.7)
polyglot 3618   0.0  0.7  47776  29712  -  Is   05:59     20:08.85 python3 ./sonos-poly.py (python3.7)
polyglot 3964   0.0  0.7  48108  30048  -  Is   09:00      5:29.02 python3 ./sonos-poly.py (python3.7)
polyglot 4044   0.0  0.7  45124  27492  -  Is   09:49      0:02.74 python3 ./push-poly.py (python3.7)
polyglot 4070   0.0  0.6  44380  24528  -  Is   09:56      0:33.76 python3 ./lifx-poly.py (python3.7)
admin    4091   0.0  0.1  11248   2696  0  S+   10:06      0:00.01 grep poly

and after the package was installed and a reboot:

[admin@polisy ~]$ ps aux | grep poly
polyglot 1319   0.0  0.1  10768  2336  -  Ss   12:48     0:00.69 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[1920] (daemon)
polyglot 1920   0.0  1.2 596420 50940  -  R    13:37     0:00.57 /usr/local/bin/polyglot-v2-freebsd-x64 -w /var/polyglot
admin    1922   0.0  0.1  11248  2696  0  S+   13:37     0:00.01 grep poly
[admin@polisy ~]$

You'll also may notice that the process ID of the running binary changes every second or so, meaning that it's constantly stopping | restarting.

gviliunas · October 30, 2019

I checked the Polglot debug log and can confirm restarting per this repeating pattern:

2019-10-30 13:55:11 [polyglot] info: Starting Polyglot....
2019-10-30 13:55:11 [polyglot] info: Settings: Polyglot Version 2.2.5
2019-10-30 13:55:11 [polyglot] info: Settings: Retrieved config from database
2019-10-30 13:55:11 [polyglot] info: Running in Polisy mode
2019-10-30 13:55:11 [polyglot] info: Settings: Retrieved config overrides from .env and updated database
2019-10-30 13:55:17 [polyglot] info: Starting Polyglot....
2019-10-30 13:55:17 [polyglot] info: Settings: Polyglot Version 2.2.5
2019-10-30 13:55:17 [polyglot] info: Settings: Retrieved config from database
2019-10-30 13:55:17 [polyglot] info: Running in Polisy mode
2019-10-30 13:55:17 [polyglot] info: Settings: Retrieved config overrides from .env and updated database
2019-10-30 13:55:22 [polyglot] info: Starting Polyglot....

garybixler · October 30, 2019

I just received my first WEMO device and thought I would give it a try on Polisy. The WEMO node server loaded fine with no errors but it can't find the device when I do Re-Discover.

I did find that WEMO node server running in Pi required the python module Pywemo to discover the devices. Not sure if that means anything or not. Anyway not critical for now just thought I would pass it along. Love the Polisy.

Thanks

Gary

Michel Kohanim · October 30, 2019

Hello everyone,

Sincere apologies for the radio silence. The crashing issue is definitely related to multiple instances of Polyglot running. We are working on a fix.

@Bumbershoot, in the meantime, please do this:

sudo killall daemon
sudo service polyglot stop
sudo service polyglot start

Please let me know what you get.

@Toddimus,

Please the same as above BUT do not do sudo polyglot start. Please let me know what ps shows.

With kind regards,
Michel

Toddimus · October 30, 2019

5 minutes ago, Michel Kohanim said:

Hello everyone,

Sincere apologies for the radio silence. The crashing issue is definitely related to multiple instances of Polyglot running. We are working on a fix.

@Bumbershoot, in the meantime, please do this:

sudo killall daemon
sudo polyglot stop
sudo polyglot start

Please let me know what you get.

@Toddimus,

Please the same as above BUT do not do sudo polyglot start. Please let me know what ps shows.

With kind regards,
Michel

I think you meant sudo service polyglot stop. Here's what I get. Looks like it's stopped.

[admin@polisy ~]$ sudo killall daemon
Password:
[admin@polisy ~]$ sudo polyglot stop
sudo: polyglot: command not found
[admin@polisy ~]$ sudo service polyglot stop
polyglot not running? (check /var/polyglot/polyglot_daemon.pid).
[admin@polisy ~]$ ps -aux | grep poly
admin   1252   0.0  0.1  11248  2696  0  S+   14:33   0:00.00 grep poly
[admin@polisy ~]$ ps -aux | grep poly
admin   1254   0.0  0.1  11248  2696  0  S+   14:33   0:00.01 grep poly
[admin@polisy ~]$ ps -aux | grep poly
admin   1256   0.0  0.1  11248  2696  0  S+   14:33   0:00.00 grep poly
[admin@polisy ~]$

Michel Kohanim · October 30, 2019

@Toddimus,

Correct. Apologies.

Ok, now, please do
sudo service polyglot start

And, repeat your experiment with ps and grep.

With kind regards,
Michel

Toddimus · October 30, 2019

1 minute ago, Michel Kohanim said:

@Toddimus,

Correct. Apologies.

Ok, now, please do
sudo service polyglot start

And, repeat your experiment with ps and grep.

With kind regards,
Michel

I thought you might want that. I had just done it anyways. Still restarting and increasing the PID value


[admin@polisy ~]$ sudo service polyglot start
Starting polyglot.
[admin@polisy ~]$ ps -aux | grep poly
polyglot 1271  68.1  2.9 690060 118932  -  R    14:36    0:03.92 /usr/local/bin/polyglot-v2-freebsd-x64 -w /var/polyglot
polyglot 1270   0.5  0.1  10768   2332  -  Ss   14:36    0:00.00 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[1271] (daemon)
admin    1273   0.0  0.1  11248   2696  0  S+   14:36    0:00.01 grep poly
[admin@polisy ~]$ ps -aux | grep poly
polyglot 1270   0.4  0.1  10768  2336  -  Ss   14:36    0:00.00 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[1271] (daemon)
admin    1275   0.0  0.1  11248  2696  0  S+   14:36    0:00.00 grep poly
[admin@polisy ~]$ ps -aux | grep poly
polyglot 1276  60.2  2.0 650544 81504  -  R    14:36    0:01.78 /usr/local/bin/polyglot-v2-freebsd-x64 -w /var/polyglot
polyglot 1270   0.2  0.1  10768  2336  -  Ss   14:36    0:00.00 daemon: /usr/local/bin/polyglot-v2-freebsd-x64[1276] (daemon)
admin    1278   0.0  0.1  11248  2696  0  S+   14:36    0:00.01 grep poly
[admin@polisy ~]$ sudo killall daemon
[admin@polisy ~]$ sudo service polyglot stop
polyglot not running? (check /var/polyglot/polyglot_daemon.pid).
[admin@polisy ~]$ ps -aux | grep poly
admin   1292   0.0  0.1  11248  2696  0  S+   14:37    0:00.00 grep poly
[admin@polisy ~]$

Michel Kohanim · October 30, 2019

@Toddimus,

Ok, let's try this:

1. killall and stop
2. mongo polyglot --eval "db.dropDatabase()"
3. reboot

Thank you!

With kind regards,
Michel

io_guy · October 30, 2019

Well I just plugged in my box and updated it. The interface on 3000 doesn't work after the update, oh well. I did get something else running:

image.png.fe2cd492b08b09fa5cd4e5aeb07ee59a.png

Michel Kohanim · October 30, 2019

@io_guy, perfect!!!

Please try https:// without the port.

With kind regards,
Michel

Sign In

Initial Feeback

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Recently Browsing

Who's Online (See full list)

Forum Statistics