@Lazar-Demin it gives the following error in a red popup bottom right corner
ERROR
You are only allowed to edit posts for 3600 second(s) after posting
J
Posts made by josh hightower
-
RE: 2+ boots from usb, but goes into read only modeposted in Omega Talk
-
RE: 2+ boots from usb, but goes into read only modeposted in Omega Talk
wanted to change post title to "[solved...kinda by using a different 2+/new USB] 2+ boots from usb, but goes into read only mode", but it says that posts can only be edited for 3600 after being posted...is there not a way to mark as "solved"?
-
RE: 2+ boots from usb, but goes into read only modeposted in Omega Talk
@tjoseph1 long story short, that flash drive was failing...well more like failed. Forensic images have been taken merged with /overlay and just mounted and other and is a future project to test recovery or repair (have not looked at drive's board yet). Brand new flash drive (usb 3.0 even tho im pretty sure 2+ only supports usb 2) different 2+ and it is running fine. Also forced me to finish the update to my thermostat code to be able to push it to the different 2+. Even with this new drive that is working with 3199, could not get 1AB5 (one referenced to begin with) or my pro to correctly boot off it. Came across this, https://github.com/Pi4IoT/Omega2_External_Storage, which changes 2 flags...have not dug into it but it is mostly the same as the onion docs and it is working. Maybe that has to do with why the other 2 would not boot off it, they just booted and then mounted it. Never saw mtdblock6/7 before, wondering if the new firmware means that page (https://docs.onion.io/omega2-docs/boot-from-external-storage.html) is a little out of date?
Ω-ware: 0.3.2 b233 ----------------------------------------------------- root@Omega-3199:~# df -hT Filesystem Type Size Used Available Use% Mounted on /dev/root squashfs 7.8M 7.8M 0 100% /rom tmpfs tmpfs 60.9M 4.7M 56.3M 8% /tmp /dev/sda1 ext4 28.3G 85.4M 26.8G 0% /overlay overlayfs:/overlay overlay 28.3G 85.4M 26.8G 0% / tmpfs tmpfs 512.0K 0 512.0K 0% /dev /dev/sda1 ext4 28.3G 85.4M 26.8G 0% /mnt/sda1 /dev/mtdblock6 jffs2 22.1M 7.1M 15.0M 32% /mnt/mtdblock6 /dev/mtdblock7 jffs2 512.0K 196.0K 316.0K 38% /mnt/mtdblock7 root@Omega-3199:~# -
RE: 2+ boots from usb, but goes into read only modeposted in Omega Talk
@tjoseph1 it uses oled, relay, 1 wire sensor, and then everything else if python libs so shouldn't be an issue there. I would assume that the functionality of some of the add ons (like relay) are not being removed even tho the hardware is being stopped? I have not verified it since code changes have been made since the last hardware swap, but the following is in my install script. I know python 2 is at EOL, but i have not migrated the project to python 3 yet.
opkg update opkg install python pyOledExp pyRelayExp python-pip pip insstall pyowm -
RE: 2+ boots from usb, but goes into read only modeposted in Omega Talk
@tjoseph1 everything uses paths relative to home. The second mount (/tmp/run/mountd/sda1) is just the automatic one, not manual. But if that were a problem, why would it be in the onion docs?
-
RE: 2+ boots from usb, but goes into read only modeposted in Omega Talk
@tjoseph1 the example output at bottom of the linked booting from external storage page does as well
Filesystem Size Used Available Use% Mounted on /dev/root 5.5M 5.5M 0 100% /rom tmpfs 29.7M 196.0K 29.5M 1% /tmp /dev/sda1 14.1G 46.7M 13.4G 0% /overlay overlayfs:/overlay 14.1G 46.7M 13.4G 0% / tmpfs 512.0K 0 512.0K 0% /dev /dev/sda1 14.1G 46.7M 13.4G 0% /tmp/run/mountd/sda1 -
RE: 2+ boots from usb, but goes into read only modeposted in Omega Talk
@crispyoz booted with usb unplugged, then plugged in for second call
Ω-ware: 0.2.2 b200 ----------------------------------------------------- root@Omega-1AB5:~# df -hT Filesystem Type Size Used Available Use% Mounted on /dev/root squashfs 6.0M 6.0M 0 100% /rom tmpfs tmpfs 61.4M 212.0K 61.1M 0% /tmp /dev/mtdblock6 jffs2 24.4M 1.2M 23.2M 5% /overlay overlayfs:/overlay overlay 24.4M 1.2M 23.2M 5% / tmpfs tmpfs 512.0K 0 512.0K 0% /dev root@Omega-1AB5:~# root@Omega-1AB5:~# root@Omega-1AB5:~# df -hT Filesystem Type Size Used Available Use% Mounted on /dev/root squashfs 6.0M 6.0M 0 100% /rom tmpfs tmpfs 61.4M 220.0K 61.1M 0% /tmp /dev/mtdblock6 jffs2 24.4M 1.2M 23.2M 5% /overlay overlayfs:/overlay overlay 24.4M 1.2M 23.2M 5% / tmpfs tmpfs 512.0K 0 512.0K 0% /dev /dev/sda1 ext4 14.6G 875.2M 13.0G 6% /tmp/run/mountd/sda1 root@Omega-1AB5:~#booted with usb plugged in
Ω-ware: 0.2.2 b200 ----------------------------------------------------- Your JFFS2-partition seems full and overlayfs is mounted read-only. Please try to remove files from /overlay/upper/... and reboot! root@(none):~# df -hT Filesystem Type Size Used Available Use% Mounted on /dev/root squashfs 6.0M 6.0M 0 100% /rom tmpfs tmpfs 61.4M 204.0K 61.2M 0% /tmp /dev/sda1 ext4 14.6G 939.1M 12.9G 7% /overlay overlayfs:/overlay overlay 14.6G 939.1M 12.9G 7% / tmpfs tmpfs 512.0K 0 512.0K 0% /dev /dev/sda1 ext4 14.6G 939.1M 12.9G 7% /tmp/run/mountd/sda1 root@(none):~#both of these were done over wifi connection
-
2+ boots from usb, but goes into read only modeposted in Omega Talk
All the files show up under /root as they normally would, and df -h shows sda1 mounted as overlay, but it boots into "Your JFFS2-partition seems full and overlayfs is mounted read-only". The 16gb usb only has has ~1gb on it. If i boot with the usb not plugged in, and then plug it in i can access and edit content, but some reads/writes are REALLY slow...like one time a directory with like 5 files in it took almost 30 seconds to ls -lah. Adding correct fstab to /etc/config or /tmp/mountd/.../upper/etc/config and rebooting did not change anything.
Suspecting that the issue is the usb is about to die, and the inconsistent read/write performance being the cause (also slow when using an ubuntu box to make a backup). Either
-
A) what else do i need to try/outputs you want (and boot method no usb, with usb, firmware recovery mode over usb serial)
-
B) would the correct method to switch usb sticks be to follow https://docs.onion.io/omega2-docs/boot-from-external-storage.html on new usb, copy fstab off new usb, restore image of current usb to new usb, move fstab into new usb
-
-
RE: Pro keeps rebotting, some files gone, and filesystem in read onlyposted in Omega Talk
Can probably skip this at the top as the problem seems to be with a command filling and growing swap.page with null.
@crispyoz
factory reset 2+root@Omega-3183:~# df -hT Filesystem Type Size Used Available Use% Mounted on /dev/root squashfs 6.0M 6.0M 0 100% /rom tmpfs tmpfs 61.4M 92.0K 61.3M 0% /tmp /dev/mtdblock6 jffs2 24.4M 768.0K 23.6M 3% /overlay overlayfs:/overlay overlay 24.4M 768.0K 23.6M 3% / tmpfs tmpfs 512.0K 0 512.0K 0% /devhttps://docs.onion.io/omega2-docs/boot-from-external-storage.html completed on 2+
root@Omega-3183:~# df -hT Filesystem Type Size Used Available Use% Mounted on /dev/root squashfs 6.0M 6.0M 0 100% /rom tmpfs tmpfs 61.4M 216.0K 61.1M 0% /tmp /dev/sda1 ext4 14.6G 47.1M 13.8G 0% /overlay overlayfs:/overlay overlay 14.6G 47.1M 13.8G 0% / tmpfs tmpfs 512.0K 0 512.0K 0% /dev /dev/sda1 ext4 14.6G 47.1M 13.8G 0% /tmp/run/mountd/sda1pro no USB (not in read only mode, but not 8 gigs either)
root@Omega-58B6:~# df -hT Filesystem Type Size Used Available Use% Mounted on /dev/root squashfs 7.8M 7.8M 0 100% /rom tmpfs tmpfs 29.3M 208.0K 29.1M 1% /tmp /dev/mtdblock6 jffs2 6.6M 1.1M 5.4M 17% /overlay overlayfs:/overlay overlay 6.6M 1.1M 5.4M 17% / tmpfs tmpfs 512.0K 0 512.0K 0% /devUSB plugged in
root@Omega-58B6:~# df -hT Filesystem Type Size Used Available Use% Mounted on /dev/root squashfs 7.8M 7.8M 0 100% /rom tmpfs tmpfs 29.3M 208.0K 29.1M 1% /tmp /dev/mtdblock6 jffs2 6.6M 1.8M 4.8M 27% /overlay overlayfs:/overlay overlay 6.6M 1.8M 4.8M 27% / tmpfs tmpfs 512.0K 0 512.0K 0% /devmkdir /mnt/<device name>
mount /dev/<device name> /mnt/root@Omega-58B6:~# df -hT Filesystem Type Size Used Available Use% Mounted on /dev/root squashfs 7.8M 7.8M 0 100% /rom tmpfs tmpfs 29.3M 208.0K 29.1M 1% /tmp /dev/mtdblock6 jffs2 6.6M 2.3M 4.3M 35% /overlay overlayfs:/overlay overlay 6.6M 2.3M 4.3M 35% / tmpfs tmpfs 512.0K 0 512.0K 0% /dev /dev/sda1 ext4 14.6G 47.1M 13.8G 0% /mntDid not duplicate /overlay as the stuff that would be moved to the flash drive is not showing up, so no reason to duplicate it
===================================================================================
/overlay/upper/mnt/swap.page is continuously growing, which reached ~200 meg again causing reboot loop and read-only file system.
root@Omega-58B6:~# ls -lah /overlay/upper/mnt/ drwxr-xr-x 4 root root 0 May 16 11:20 . drwxr-xr-x 7 root root 0 May 16 11:14 .. lrwxrwxrwx 1 root root 1 May 16 11:14 .fs_state -> 2 -rw-r--r-- 1 root root 35.3M May 16 11:23 swap.page drwxr-xr-x 6 root root 0 May 16 11:14 upper drwxr-xr-x 3 root root 0 Jan 1 1970 work root@Omega-58B6:~# ls -lah /overlay/upper/mnt/ drwxr-xr-x 4 root root 0 May 16 11:20 . drwxr-xr-x 7 root root 0 May 16 11:14 .. lrwxrwxrwx 1 root root 1 May 16 11:14 .fs_state -> 2 -rw-r--r-- 1 root root 38.3M May 16 11:24 swap.page drwxr-xr-x 6 root root 0 May 16 11:14 upper drwxr-xr-x 3 root root 0 Jan 1 1970 work root@Omega-58B6:~# ls -lah /overlay/upper/mnt/ drwxr-xr-x 4 root root 0 May 16 11:20 . drwxr-xr-x 7 root root 0 May 16 11:14 .. lrwxrwxrwx 1 root root 1 May 16 11:14 .fs_state -> 2 -rw-r--r-- 1 root root 40.3M May 16 11:24 swap.page drwxr-xr-x 6 root root 0 May 16 11:14 upper drwxr-xr-x 3 root root 0 Jan 1 1970 work root@Omega-58B6:~# ls -lah /overlay/upper/mnt/ drwxr-xr-x 4 root root 0 May 16 11:20 . drwxr-xr-x 7 root root 0 May 16 11:14 .. lrwxrwxrwx 1 root root 1 May 16 11:14 .fs_state -> 2 -rw-r--r-- 1 root root 42.0M May 16 11:24 swap.page drwxr-xr-x 6 root root 0 May 16 11:14 upper drwxr-xr-x 3 root root 0 Jan 1 1970 work root@Omega-58B6:~# ls -lah /overlay/upper/mnt/ drwxr-xr-x 4 root root 0 May 16 11:20 . drwxr-xr-x 7 root root 0 May 16 11:14 .. lrwxrwxrwx 1 root root 1 May 16 11:14 .fs_state -> 2 -rw-r--r-- 1 root root 42.7M May 16 11:24 swap.page drwxr-xr-x 6 root root 0 May 16 11:14 upper drwxr-xr-x 3 root root 0 Jan 1 1970 work root@Omega-58B6:~# ls -lah /overlay/upper/mnt/ drwxr-xr-x 4 root root 0 May 16 11:20 . drwxr-xr-x 7 root root 0 May 16 11:14 .. lrwxrwxrwx 1 root root 1 May 16 11:14 .fs_state -> 2 -rw-r--r-- 1 root root 43.4M May 16 11:24 swap.page drwxr-xr-x 6 root root 0 May 16 11:14 upper drwxr-xr-x 3 root root 0 Jan 1 1970 work root@Omega-58B6:~# ls -lah /overlay/upper/mnt/ drwxr-xr-x 4 root root 0 May 16 11:20 . drwxr-xr-x 7 root root 0 May 16 11:14 .. lrwxrwxrwx 1 root root 1 May 16 11:14 .fs_state -> 2 -rw-r--r-- 1 root root 43.9M May 16 11:24 swap.page drwxr-xr-x 6 root root 0 May 16 11:14 upper drwxr-xr-x 3 root root 0 Jan 1 1970 work root@Omega-58B6:~# ls -lah /overlay/upper/mnt/ drwxr-xr-x 4 root root 0 May 16 11:20 . drwxr-xr-x 7 root root 0 May 16 11:14 .. lrwxrwxrwx 1 root root 1 May 16 11:14 .fs_state -> 2 -rw-r--r-- 1 root root 44.6M May 16 11:24 swap.page drwxr-xr-x 6 root root 0 May 16 11:14 upper drwxr-xr-x 3 root root 0 Jan 1 1970 work root@Omega-58B6:~# ls -lah /overlay/upper/mnt/ drwxr-xr-x 4 root root 0 May 16 11:20 . drwxr-xr-x 7 root root 0 May 16 11:14 .. lrwxrwxrwx 1 root root 1 May 16 11:14 .fs_state -> 2 -rw-r--r-- 1 root root 45.1M May 16 11:24 swap.page drwxr-xr-x 6 root root 0 May 16 11:14 upper drwxr-xr-x 3 root root 0 Jan 1 1970 work root@Omega-58B6:~# ls -lah /overlay/upper/mnt/ drwxr-xr-x 4 root root 0 May 16 11:20 . drwxr-xr-x 7 root root 0 May 16 11:14 .. lrwxrwxrwx 1 root root 1 May 16 11:14 .fs_state -> 2 -rw-r--r-- 1 root root 45.9M May 16 11:24 swap.page drwxr-xr-x 6 root root 0 May 16 11:14 upper drwxr-xr-x 3 root root 0 Jan 1 1970 work root@Omega-58B6:~# ls -lah /overlay/upper/mnt/ drwxr-xr-x 4 root root 0 May 16 11:20 . drwxr-xr-x 7 root root 0 May 16 11:14 .. lrwxrwxrwx 1 root root 1 May 16 11:14 .fs_state -> 2 -rw-r--r-- 1 root root 46.6M May 16 11:24 swap.page drwxr-xr-x 6 root root 0 May 16 11:14 upper drwxr-xr-x 3 root root 0 Jan 1 1970 work root@Omega-58B6:~# ls -lah /overlay/upper/mnt/ drwxr-xr-x 4 root root 0 May 16 11:20 . drwxr-xr-x 7 root root 0 May 16 11:14 .. lrwxrwxrwx 1 root root 1 May 16 11:14 .fs_state -> 2 -rw-r--r-- 1 root root 47.2M May 16 11:24 swap.page drwxr-xr-x 6 root root 0 May 16 11:14 upper drwxr-xr-x 3 root root 0 Jan 1 1970 work root@Omega-58B6:~# ls -lah /overlay/upper/mnt/ drwxr-xr-x 4 root root 0 May 16 11:20 . drwxr-xr-x 7 root root 0 May 16 11:14 .. lrwxrwxrwx 1 root root 1 May 16 11:14 .fs_state -> 2 -rw-r--r-- 1 root root 47.6M May 16 11:25 swap.page drwxr-xr-x 6 root root 0 May 16 11:14 upper drwxr-xr-x 3 root root 0 Jan 1 1970 workAssumed this was swap for ram, but apparently not.
root@Omega-58B6:~# cat /proc/meminfo | grep Swap SwapCached: 0 kB SwapTotal: 0 kB SwapFree: 0 kBFound the source of the growth, but do not understand why it is doing it. The 2+ is not running that command and cant find that file on 2+ at all.
Mem: 48172K used, 11776K free, 208K shrd, 752K buff, 21984K cached CPU: 0% usr 99% sys 0% nic 0% idle 0% io 0% irq 0% sirq Load average: 2.08 1.92 1.33 2/57 1977 PID PPID USER STAT VSZ %VSZ %CPU COMMAND 1907 1863 root R 2240 4% 98% dd if /dev/zero of /mnt/swap.page bs 1M count 384 1977 1691 root R 1212 2% 1% top 204 2 root RW 0 0% 1% [spi0] 1669 1176 root S 1132 2% 0% /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -K 300 -T 3 7 2 root SW 0 0% 0% [ksoftirqd/0] 1272 2 root SW 0 0% 0% [RtmpCmdQTask] 1831 1 mosquitt S 3320 6% 0% mosquitto -c /etc/mosquitto/mosquitto.conf 1421 1 root S 1968 3% 0% /usr/sbin/onion-helper 1771 1 root S 1796 3% 0% /sbin/rpcd 1052 1 root S 1724 3% 0% /sbin/netifd 1351 1 nobody S 1568 3% 0% avahi-daemon: running [Omega-58B6.local] 1 0 root S 1556 3% 0% /sbin/procd===================================================================================
Was going to copy the old swap.page back on and see how it behaves. Did not try that as the problem seems to be a growing zeroed out swap.page file
-
RE: Pro keeps rebotting, some files gone, and filesystem in read onlyposted in Omega Talk
@crispyoz Used a new 2+ to do this https://docs.onion.io/omega2-docs/boot-from-external-storage.html and then plugged the usb into the pro and it behaved the same way (on the 2+ it showed full ~16 gigs).
The only file that I could find that was large (217.7 MB) was swap.page, which by pasting the following in was fast enough to copy it off before reboot (like seconds to spare). Last line to confirm it had finished.
mkdir /tmp/mounts mount /dev/sda1 /tmp/mounts/ cd /overlay/upper/mnt cp swap.page /tmp/mounts/swap.page ls -lah /tmp/mounts/After that reboot deleted swap.page which allowed it to boot normally and stop the loop. With and without the USB, it behaved the same way-like a normal 2/2+ with no additional storage added. The 8 GB eMMC worth of storage is not showing up tho. Wondering if the eMMC burned out causing all the issues, but if that were the case, why has my little shell script been there the whole time?
If able, adding eMMC to the tags since it might be related. In the mean time, I'll run my stuff off the 2+ with a flash drive, which is kinda ironic because the whole reason this was switched to pro was to not need to have a USB off the side.
-
Pro keeps rebotting, some files gone, and filesystem in read onlyposted in Omega Talk
My 2 pro has been working great since I got it a while back (had preordered it). Yesterday it crashed. Now it is in a boot loop where it will boot and be fine for a minute or 2 and then restart again. Was running my thermostat, so I can live with loosing the data that was on it if I need to. When I get into it it says
BusyBox v1.28.3 () built-in shell (ash) ____ _ ____ / __ \___ (_)__ ___ / __ \__ _ ___ ___ ____ _ / /_/ / _ \/ / _ \/ _ \ / /_/ / ' \/ -_) _ `/ _ `/ \____/_//_/_/\___/_//_/ \____/_/_/_/\__/\_, /\_,_/ W H A T W I L L Y O U I N V E N T ? /___/ ----------------------------------------------------- Ω-ware: 0.3.1 b211 ----------------------------------------------------- Your JFFS2-partition seems full and overlayfs is mounted read-only. Please try to remove files from /overlay/upper/... and reboot! root@Omega-58B6:~#My script to kill the LED is there, but the rest of my stuff is not and my cronjob is gone. All my stuff was stored in /root/.
Every time before it does a restart it has
Removing MTD device #6 (rootfs_data) with use count 1
and then
reboot: Restarting systemfollowed by restarting (see serial output from COM3 below).COM3
https://pastebin.com/1NTK4jmJHow do I access the files to back them up. And how to stop the reboot. Or is doing an update my only option and my stuff is just gone? It is not the power supply-has been running off a samsung fast charger since got it, and tried a couple other supplies just to check and they all behave the same way.
-
RE: Spectre / Speculative CPU Issueposted in Omega Talk
@Stephen-Tunney My understanding is that all cpus are in danger, but non-intel ones only have to be concerned when someone gets physical access to the device.
-
1 wire sensors keep going awayposted in Omega Talk
I have 4 of this sensor https://www.amazon.com/gp/product/B00CHEZ250/ref=oh_aui_detailpage_o06_s00?ie=UTF8&psc=1 wired in parallel using pwm cables. At the omega It is connected with pin 19, 3.3v, and a 4.7k like said to do here https://wiki.onion.io/Tutorials/Reading-1Wire-Sensor-Data
This is part of my ac thermostat that I've been working on, so there is a relay shield and an oled also connected to omega 2+. It was working fine for quite a while, then the sensors were no longer listed in w1_bus_master. The only thing that I found to make them show back up is to run the code on the 1 wire sensor tutorial and reboot. Sometimes they show back up and sometimes they do not. When they do show back up, they might stay for a few hours but sometimes only a couple minutes.
I'm out of ideas as to cause and solution.
-
RE: Aws IoT seems to require python3, but 2.7 won't leaveposted in Omega Talk
Starting to think it might be an aws iot code issue. This is trying to set up a new device, and using their setup script. It at least starts to work, because on the aws monitor dashboard I see connections. This is the output it gives. I am posting this on their sdk issues too https://github.com/aws/aws-iot-device-sdk-python/issues/85
root@Omega-3199:~# ./start.sh
Running pub/sub sample application...
2017-11-01 05:13:53,808 - AWSIoTPythonSDK.core.protocol.internal.clients - DEBUG - Initializing MQTT layer...
2017-11-01 05:13:53,817 - AWSIoTPythonSDK.core.protocol.internal.clients - DEBUG - Registering internal event callbacks to MQTT layer...
2017-11-01 05:13:53,822 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Event consuming thread started
2017-11-01 05:13:53,825 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - MqttCore initialized
2017-11-01 05:13:53,828 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Client id: basicPubSub
2017-11-01 05:13:53,832 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Protocol version: MQTTv3.1.1
2017-11-01 05:13:53,834 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Authentication type: TLSv1.2 certificate based Mutual Auth.
2017-11-01 05:13:53,838 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Configuring endpoint...
2017-11-01 05:13:53,842 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Configuring certificates...
2017-11-01 05:13:53,845 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Configuring reconnect back off timing...
2017-11-01 05:13:53,848 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Base quiet time: 1.000000 sec
2017-11-01 05:13:53,852 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Max quiet time: 32.000000 sec
2017-11-01 05:13:53,855 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Stable connection time: 20.000000 sec
2017-11-01 05:13:53,859 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Configuring offline requests queueing: max queue size: -1
2017-11-01 05:13:53,864 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Configuring offline requests queue draining interval: 0.500000 sec
2017-11-01 05:13:53,869 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Configuring connect/disconnect time out: 10.000000 sec
2017-11-01 05:13:53,873 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Configuring MQTT operation time out: 5.000000 sec
2017-11-01 05:13:53,876 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Performing sync connect...
2017-11-01 05:13:53,879 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Performing async connect...
2017-11-01 05:13:53,883 - AWSIoTPythonSDK.core.protocol.mqtt_core - INFO - Keep-alive: 30.000000 sec
2017-11-01 05:13:53,886 - AWSIoTPythonSDK.core.protocol.mqtt_core - DEBUG - Passing in general notification callbacks to internal client...
2017-11-01 05:13:53,890 - AWSIoTPythonSDK.core.protocol.internal.clients - DEBUG - Filling in fixed event callbacks: CONNACK, DISCONNECT, MESSAGE
Traceback (most recent call last):
File "aws-iot-device-sdk-python/samples/basicPubSub/basicPubSub.py", line 89, in <module>
myAWSIoTMQTTClient.connect()
File "/usr/lib/python2.7/site-packages/AWSIoTPythonSDK/MQTTLib.py", line 408, in connect
return self._mqtt_core.connect(keepAliveIntervalSecond)
File "/usr/lib/python2.7/site-packages/AWSIoTPythonSDK/core/protocol/mqtt_core.py", line 168, in connect
self.connect_async(keep_alive_sec, self._create_blocking_ack_callback(event))
File "/usr/lib/python2.7/site-packages/AWSIoTPythonSDK/core/protocol/mqtt_core.py", line 179, in connect_async
rc = self._internal_async_client.connect(keep_alive_sec, ack_callback)
File "/usr/lib/python2.7/site-packages/AWSIoTPythonSDK/core/protocol/internal/clients.py", line 113, in connect
rc = self._paho_client.connect(host, port, keep_alive_sec)
File "/usr/lib/python2.7/site-packages/AWSIoTPythonSDK/core/protocol/paho/client.py", line 654, in connect
return self.reconnect()
File "/usr/lib/python2.7/site-packages/AWSIoTPythonSDK/core/protocol/paho/client.py", line 797, in reconnect
ciphers=self._tls_ciphers)
File "/usr/lib/python2.7/ssl.py", line 943, in wrap_socket
ciphers=ciphers)
File "/usr/lib/python2.7/ssl.py", line 552, in init
self._context.load_verify_locations(ca_certs)
ssl.SSLError: unknown error (_ssl.c:2947)
Exception in thread Thread-1 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
File "/usr/lib/python2.7/threading.py", line 754, in run
File "/usr/lib/python2.7/site-packages/AWSIoTPythonSDK/core/protocol/internal/workers.py", line 137, in _dispatch
File "/usr/lib/python2.7/threading.py", line 289, in exit
File "/usr/lib/python2.7/threading.py", line 216, in exit
File "/usr/lib/python2.7/threading.py", line 203, in release
<type 'exceptions.TypeError'>: 'NoneType' object is not callable -
Aws IoT seems to require python3, but 2.7 won't leaveposted in Omega Talk
I am having connection issues trying to get aws iot started on my 2+. From what I am finding on the errors, it seems to be an issue with python 2.7. How do I get just python3 installed? I thought I had uninstalled 2.7, but it is still here/back. Unless ignoring the installation of 2.7, and just doing an alias python=python3 is the right call (but where since we don't have bash.rc)?