Thanks for the suggestions. Last time i had an issue that i couldn't resolve remotely i drove down and power cycled everything including the display and that eventually fixed the problem.
I got someone on site to power cycle the display and it didn't fix it. So I was brainstorming this for a few hours and i was surprised to see that *sudo apt-get update* wasn't working. So i vnc'd into the pi and tried to browse a website and that didn't work either. Strange that even tho i was connected to it remotely via ssh, it was having DNS issues. I edited *sudo nano /etc/resolv.conf* and added *nameserver 8.8.8.8* and viola it worked! Not sure how that setting got lost because i am the only one with access. Thanks for all the support. On Wed, Jan 8, 2020 at 11:08 AM mwall <goo...@lancet.mit.edu> wrote: > > > On Sunday, November 24, 2019 at 1:29:24 AM UTC-5, Sean Jahnig wrote: >> >> Thanks for the suggestion, does this mean anything to anyone? >>> >> >> [ 2.770063] usb 1-1.2.4.4: New USB device found, idVendor=24c0, >> idProduct=0003, bcdDevice= 0.20 >> >> [ 2.770081] usb 1-1.2.4.4: New USB device strings: Mfr=0, Product=2, >> SerialNumber=0 >> >> [ 2.770094] usb 1-1.2.4.4: Product: Chaney Instrument >> >> [ 2.780625] input: Chaney Instrument as >> /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.4/1-1.2.4.4:1.0/0003:24C0:0003.0001/input/input0 >> [ 2.780828] hid-generic 0003:24C0:0003.0001: input,hidraw0: USB HID >> v1.11 Device [Chaney Instrument] on usb-0000:01:00.0-1.2.4.4/input0 >> >> to me it looks like the device is connected - yet it is still giving a >> pipe error? >> > > i used to see this behavior from time to time when i was developing the > acurite driver. sometimes the usb would get into a state where the station > showed up on the usb, but no communication was possible. i had to power > cycle the acurite console to recover. sometimes that was not enough - i'd > have to turn of power to the console, unplug the usb, then replug and power > on. > > i found that i could often induce the state by messing with the usb > voltage or by messing with the console power supply > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "weewx-user" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/weewx-user/o1UrJlt2-nQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > weewx-user+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/08ab4d1c-c9a6-4aa5-9445-734fe7b0b024%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/08ab4d1c-c9a6-4aa5-9445-734fe7b0b024%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CALeSoZn_3PDpe-9K2XXaTG%2B_sTdbNsKNim8%3D6GRaJmMC6FNwgg%40mail.gmail.com.
