Modemmanager is still trying to grab the port. I had the name wrong: it's actually modemmanager, not modem-manager, but it looks like you already discovered that. Just to double check, try killing it and uninstalling it:
sudo kill -9 529 sudo apt-get remove modemmanager Then try again. Please note, while the logs may not be technically empty, they do not have any information about weewx. There should be many entries that mention weewx. If not, you still haven't captured the startup. Your technique of using tail -f /var/log/syslog>log.txt is fine. -tk On Mon, Nov 14, 2016 at 4:54 PM, <[email protected]> wrote: > I do look at them to be sure they are not empty. The last one was 2979 > bytes. If they are empty when they get there, I guess I have a problem > with firefox and the drag and drop attach on this website. I tried to > remove the modem-manager and it said it wasn't installed. I got into > synaptic and searched for modem-manager and it found two file > (modem-manager-gui and another one) but it said they were not installed. I > then searched for ModemManager and it found it. It is gone now. I am > resending the last log, but not attaching it. I will just cut and paste it > in. Is there supposed to be something other than what is below in there? > I did click on the attachment above and it agreed that these lines were in > it. > In order to start the log I am using sudo tail -f /var/log/syslog > > log.txt Is there something wrong there? Before I try to do another log > run, let me know if that is correct.. > > John > > > Nov 14 11:54:57 raspberrypi weewx[663]: engine: Unable to load driver: While > getting EEPROM data value at address 0x29 > Nov 14 11:54:57 raspberrypi weewx[663]: **** Exiting... > Nov 14 11:54:58 raspberrypi ModemManager[529]: <info> Creating modem with > plugin 'Generic' and '1' ports > Nov 14 11:54:58 raspberrypi ModemManager[529]: <warn> Could not grab port > (tty/ttyUSB0): 'Cannot add port 'tty/ttyUSB0', unhandled serial type' > Nov 14 11:54:58 raspberrypi ModemManager[529]: <warn> Couldn't create modem > for device at > '/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.4': Failed to > find primary AT port > Nov 14 11:55:24 raspberrypi kernel: [ 56.585720] w1_master_driver > w1_bus_master1: Family 0 for 00.800000000000.8c is not registered. > Nov 14 11:55:24 raspberrypi rsyslogd-2007: action 'action 17' suspended, next > retry is Mon Nov 14 11:55:54 2016 [try http://www.rsyslog.com/e/2007 ] > Nov 14 11:55:55 raspberrypi rsyslogd-2007: action 'action 17' suspended, next > retry is Mon Nov 14 11:56:25 2016 [try http://www.rsyslog.com/e/2007 ] > Nov 14 11:56:24 raspberrypi kernel: [ 115.968862] w1_master_driver > w1_bus_master1: Family 0 for 00.400000000000.46 is not registered. > Nov 14 11:56:43 raspberrypi rsyslogd-2007: action 'action 17' suspended, next > retry is Mon Nov 14 11:57:13 2016 [try http://www.rsyslog.com/e/2007 ] > Nov 14 11:57:11 raspberrypi kernel: [ 163.326415] w1_master_driver > w1_bus_master1: Family 0 for 00.c00000000000.ca is not registered. > Nov 14 11:57:47 raspberrypi rsyslogd-2007: action 'action 17' suspended, next > retry is Mon Nov 14 11:58:17 2016 [try http://www.rsyslog.com/e/2007 ] > Nov 14 11:57:52 raspberrypi wee_device[1131]: vantage: Archive memory cleared. > Nov 14 11:58:11 raspberrypi systemd[1]: Started LSB: weewx weather system. > Nov 14 11:58:22 raspberrypi kernel: [ 234.636942] w1_master_driver > w1_bus_master1: Family 0 for 00.200000000000.23 is not registered. > Nov 14 11:58:22 raspberrypi rsyslogd-2007: action 'action 17' suspended, next > retry is Mon Nov 14 11:58:52 2016 [try http://www.rsyslog.com/e/2007 ] > Nov 14 11:59:22 raspberrypi kernel: [ 293.947423] w1_master_driver > w1_bus_master1: Family 0 for 00.a00000000000.af is not registered. > Nov 14 11:59:22 raspberrypi rsyslogd-2007: action 'action 17' suspended, next > retry is Mon Nov 14 11:59:52 2016 [try http://www.rsyslog.com/e/2007 ] > Nov 14 11:59:57 raspberrypi kernel: [ 329.359905] w1_master_driver > w1_bus_master1: Family 0 for 00.600000000000.65 is not registered. > Nov 14 11:59:57 raspberrypi rsyslogd-2007: action 'action 17' suspended, next > retry is Mon Nov 14 12:00:27 2016 [try http://www.rsyslog.com/e/2007 ] > Nov 14 12:00:34 raspberrypi kernel: [ 366.687849] w1_master_driver > w1_bus_master1: Family 0 for 00.e00000000000.e9 is not registered. > Nov 14 12:00:34 raspberrypi rsyslogd-2007: action 'action 17' suspended, next > retry is Mon Nov 14 12:01:04 2016 [try http://www.rsyslog.com/e/2007 ] > Nov 14 12:01:33 raspberrypi kernel: [ 425.578107] w1_master_driver > w1_bus_master1: Family 0 for 00.100000000000.9d is not registered. > Nov 14 12:01:33 raspberrypi rsyslogd-2007: action 'action 17' suspended, next > retry is Mon Nov 14 12:02:03 2016 [try http://www.rsyslog.com/e/2007 ] > Nov 14 12:02:09 raspberrypi kernel: [ 461.918464] w1_master_driver > w1_bus_master1: Family 0 for 00.900000000000.11 is not registered. > Nov 14 12:02:09 raspberrypi rsyslogd-2007: action 'action 17' suspended, next > retry is Mon Nov 14 12:03:09 2016 [try http://www.rsyslog.com/e/2007 ] > Nov 14 12:03:20 raspberrypi kernel: [ 532.308999] w1_master_driver > w1_bus_master1: Family 0 for 00.500000000000.db is not registered. > Nov 14 12:03:20 raspberrypi rsyslogd-2007: action 'action 17' suspended, next > retry is Mon Nov 14 12:04:20 2016 [try http://www.rsyslog.com/e/2007 ] > Nov 14 12:04:08 raspberrypi kernel: [ 580.589167] w1_master_driver > w1_bus_master1: Family 0 for 00.d00000000000.57 is not registered. > Nov 14 12:04:33 raspberrypi kernel: [ 605.079407] w1_master_driver > w1_bus_master1: Family 0 for 00.300000000000.be is not registered. > Nov 14 12:04:33 raspberrypi rsyslogd-2007: action 'action 17' suspended, next > retry is Mon Nov 14 12:05:33 2016 [try http://www.rsyslog.com/e/2007 ] > Nov 14 12:05:19 raspberrypi kernel: [ 651.442253] w1_master_driver > w1_bus_master1: Family 0 for 00.b00000000000.32 is not registered. > Nov 14 12:05:55 raspberrypi kernel: [ 687.879963] w1_master_driver > w1_bus_master1: Family 0 for 00.700000000000.f8 is not registered. > Nov 14 12:05:55 raspberrypi rsyslogd-2007: action 'action 17' suspended, next > retry is Mon Nov 14 12:06:55 2016 [try http://www.rsyslog.com/e/2007 ] > Nov 14 12:06:44 raspberrypi kernel: [ 736.170391] w1_master_driver > w1_bus_master1: Family 0 for 00.f00000000000.74 is not registered. > Nov 14 12:07:42 raspberrypi kernel: [ 794.650827] w1_master_driver > w1_bus_master1: Family 0 for 00.080000000000.c2 is not registered. > Nov 14 12:07:42 raspberrypi rsyslogd-2007: action 'action 17' suspended, next > retry is Mon Nov 14 12:08:42 2016 [try http://www.rsyslog.com/e/2007 ] > Nov 14 12:07:57 raspberrypi systemd[1]: Stopping LSB: weewx weather system... > Nov 14 12:07:57 raspberrypi weewx[1217]: Stopping weewx weather system: weewx > not running.... > Nov 14 12:07:57 raspberrypi systemd[1]: Stopped LSB: weewx weather system. > > > > > > > On Monday, November 14, 2016 at 1:03:37 PM UTC-6, Tom Keffer wrote: >> >> Not so fast. >> >> The module modem-manager is competing with weewx for port /dev/ttyUSB0. >> Eventually, it will give up and release the port, but until it does, weewx >> cannot start. So, there is nothing in the log >> >> The easiest thing to do is remove modem-manager and try again: >> >> sudo apt-get remove modem-manager >> >> >> Restart weewx, then send the log. I'd suggest taking a look at it before >> posting it to make sure there's actually something in there. >> >> -tk >> >> >> >> >> >> On Mon, Nov 14, 2016 at 10:34 AM, <[email protected]> wrote: >> >>> Well, now it is no longer working when I changed back to software. So >>> is the faulty memory in the usb connector or the logger itself. The site >>> you sent me to was some guy who had come up with a usb connector, but his >>> had no archive. It sounds like the archive memory is in the official >>> connector. This would mean I have to get a new usb connector, or a whole >>> new logger unit? >>> john >>> >>> >>> On Monday, November 14, 2016 at 12:13:15 PM UTC-6, >>> [email protected] wrote: >>>> >>>> The system has been sending data for 3 hours now. I think this also >>>> explains why it worked for 10 minutes earlier. I had unplugged and removed >>>> the batteries to the logger which is one way of resetting it. It then >>>> worked for 10 minutes and stopped. >>>> Things are going out to the weather underground but it is using the >>>> software archive. BTW, I am doing everything from the command line >>>> already. >>>> So >>>> Bring up the pi. >>>> Go back to hardware >>>> start the log. >>>> clear the memory >>>> start the service. >>>> Wait 10 minutes. The weather underground is reporting it is getting >>>> something, but no values are changing. >>>> https://www.wunderground.com/personal-weather-station/dashb >>>> oard?ID=KMOSAINT27#history >>>> they were changing when it was set for software >>>> >>>> end service >>>> close log >>>> >>>> attach log. >>>> There you go. Now I will try the same thing with the software archive. >>>> On Monday, November 14, 2016 at 9:19:22 AM UTC-6, Tom Keffer wrote: >>>>> >>>>> Yes, weewx will get data from the console, but at the end of every >>>>> archive interval if record generation is set to hardware, it will attempt >>>>> to retrieve any old archive records from the logger. Because of the bad >>>>> logger memory, it fails, and so nothing gets retrieved, nothing gets put >>>>> in >>>>> the database, and nothing goes out to the Weather Underground. >>>>> >>>>> The log you attached has only one entry from weewx and it was a notice >>>>> that weewx was not running. >>>>> >>>>> Please try again. If it is easier, run weewx from the command line. >>>>> First clear the memory, then run it for 10 minutes or so, then post the >>>>> log. >>>>> >>>>> -tk >>>>> >>>>> >>>>> >>>>> On Mon, Nov 14, 2016 at 7:04 AM, <[email protected]> wrote: >>>>> >>>>>> While my memory may be bad, that is not the problem I need to fix. >>>>>> This setup is not uploading any data, current or archived to the weather >>>>>> underground. I don't really care whether or not the logger maintains its >>>>>> own data if it is also stored on the internet at wunderground. The Usb >>>>>> connection with the datalogger is way overpriced for what it is as is the >>>>>> console, so if the archiving doesn't work I likely won't bother to get it >>>>>> fixed as long as the data is being uploaded. The Rpi is clearly getting >>>>>> the data from the console (I am seeing it in the terminal). The console >>>>>> is >>>>>> clearly getting the data from the instrument. The weather underground >>>>>> only >>>>>> got data for 10minutes before data stopped being transferred. If I can >>>>>> get >>>>>> the data transferred to my wunderground site, I am done. A bandaid will >>>>>> be fine. I will try to change the record_generation and do the log >>>>>> again. >>>>>> Thanks for your help, >>>>>> john >>>>>> >>>>>> Ok. so this morning I booted the computer. I recleared the memory. >>>>>> Started the log. started the weewx. waited 5 minutes. stopped the >>>>>> weewx. stopped the log. Uploaded the text file as an attachment. Next I >>>>>> will try changing the record_generation to software. Anyway, this log is >>>>>> attached. >>>>>> >>>>>> On Sunday, November 13, 2016 at 11:37:11 PM UTC-6, Tom Keffer wrote: >>>>>>> >>>>>>> You did not post a new log, so I can't tell if you're still getting >>>>>>> the same error. Are you? If you've cleared the logger and you're still >>>>>>> getting a bad archive type, then the logger is bad. >>>>>>> >>>>>>> You may not have noticed it before because your prior system may not >>>>>>> have taken advantage of the onboard memory of the logger. You can do the >>>>>>> same thing with weewx by changing the option record_generation >>>>>>> <http://www.google.com/url?q=http%3A%2F%2Fweewx.com%2Fdocs%2Fusersguide.htm%23StdArchive&sa=D&sntz=1&usg=AFQjCNGmMe-mtiQ61M_DHjpTv7o6ZmVLzw> >>>>>>> from 'hardware' to 'software,' but that's putting a bandaid on the >>>>>>> problem. >>>>>>> >>>>>>> -tk >>>>>>> >>>>>>> On Sun, Nov 13, 2016 at 9:26 PM, <[email protected]> wrote: >>>>>>> >>>>>>>> >>>>>>>> I tried clearing the memory and it makes no difference. I don't >>>>>>>> think it is hardware as it has been working for years on a windows >>>>>>>> system, >>>>>>>> and was just taken off 2 days ago to try this. I used wee_device and >>>>>>>> changed the interval to 10 and that seemed successful. It is still not >>>>>>>> uploading to the weather underground. >>>>>>>> >>>>>>>> Jon >>>>>>>> >>>>>>>> >>>>>>>> On Sunday, November 13, 2016 at 10:43:34 PM UTC-6, gjr80 wrote: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> This post >>>>>>>>> <https://groups.google.com/d/msg/weewx-user/9BeGjBZj5zE/0ZiqSZJsMIMJ>might >>>>>>>>> give you a way ahead. Note though that wee_config_device is now >>>>>>>>> wee_device >>>>>>>>> <http://weewx.com/docs/utilities.htm#wee_device_utility> (since >>>>>>>>> weewx v3.2.0), the equivalent command is: >>>>>>>>> >>>>>>>>> wee_device --clear-memory >>>>>>>>> >>>>>>>>> Also, not a big deal but your weewx.conf is telling your device >>>>>>>>> to use an archive interval of 5 minutes but your device is set to use >>>>>>>>> 10 >>>>>>>>> minutes. In such cases the device archive period is used, if you >>>>>>>>> really do >>>>>>>>> want 5 minutes then you will need to set your device to use 5 minutes >>>>>>>>> (again use wee_device but this time with the --set-interval >>>>>>>>> option). Note that you need to stop weewx to use wee_device. >>>>>>>>> >>>>>>>>> Gary >>>>>>>>> >>>>>>>>> On Monday, 14 November 2016 14:30:39 UTC+10, >>>>>>>>> [email protected] wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I started the log; ran start; allowed it to send the log to a >>>>>>>>>> text file; stopped it after 10 minutes. The log file is attached. >>>>>>>>>> Thanks for any help. >>>>>>>>>> John >>>>>>>>>> >>>>>>>>>> On Sunday, November 13, 2016 at 10:20:05 PM UTC-6, >>>>>>>>>> [email protected] wrote: >>>>>>>>>>> >>>>>>>>>>> I am working on it now. Will post in a few minutes. I think >>>>>>>>>>> the archive was reset as I disconnected the power and battery and >>>>>>>>>>> usb to >>>>>>>>>>> the weather station after reading a post about resetting it. I >>>>>>>>>>> think that >>>>>>>>>>> got the archive, though I could be wrong. I am giving it about 10 >>>>>>>>>>> minutes >>>>>>>>>>> to finish the archiving and will post the text file then. >>>>>>>>>>> Thanks, >>>>>>>>>>> John >>>>>>>>>>> >>>>>>>>>>> On Sunday, November 13, 2016 at 8:04:34 PM UTC-6, Tom Keffer >>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> Please restart weewx and post the log from startup. Also, I >>>>>>>>>>>> don't know how long your archive interval is, but let it run at >>>>>>>>>>>> least that >>>>>>>>>>>> long. >>>>>>>>>>>> >>>>>>>>>>>> -tk >>>>>>>>>>>> >>>>>>>>>>>> On Sun, Nov 13, 2016 at 6:00 PM, <[email protected]> >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi all, >>>>>>>>>>>>> I am new to this so I could use some help. I am connecting a >>>>>>>>>>>>> vantage vue weather station through a Raspberry pi 2 to the >>>>>>>>>>>>> weather >>>>>>>>>>>>> underground. I installed the debian install of weewx on the pi a >>>>>>>>>>>>> day ago. >>>>>>>>>>>>> (current version). The pi can see the weatherstation, and came >>>>>>>>>>>>> up and sent >>>>>>>>>>>>> data to the weather underground for about 10 minutes last night. >>>>>>>>>>>>> >>>>>>>>>>>>> Debug=1 is on. >>>>>>>>>>>>> here is the syslog >>>>>>>>>>>>> >>>>>>>>>>>>> pi@raspberrypi ~/Scripts $ ./wx-syslog.sh >>>>>>>>>>>>> Nov 13 19:42:24 raspberrypi weewx[2424]: vantage: gentle wake >>>>>>>>>>>>> up of console successful >>>>>>>>>>>>> Nov 13 19:42:24 raspberrypi weewx[2424]: vantage: Requesting >>>>>>>>>>>>> 200 LOOP packets. >>>>>>>>>>>>> Nov 13 19:42:24 raspberrypi weewx[2424]: vantage: gentle wake >>>>>>>>>>>>> up of console successful >>>>>>>>>>>>> Nov 13 19:43:07 raspberrypi kernel: [18416.464275] >>>>>>>>>>>>> w1_master_driver w1_bus_master1: Family 0 for 00.de8000000000.67 >>>>>>>>>>>>> is not >>>>>>>>>>>>> registered. >>>>>>>>>>>>> Nov 13 19:43:31 raspberrypi kernel: [18440.725167] >>>>>>>>>>>>> w1_master_driver w1_bus_master1: Family 0 for 00.3e8000000000.8e >>>>>>>>>>>>> is not >>>>>>>>>>>>> registered. >>>>>>>>>>>>> Nov 13 19:44:17 raspberrypi kernel: [18487.177578] >>>>>>>>>>>>> w1_master_driver w1_bus_master1: Family 0 for 00.be8000000000.02 >>>>>>>>>>>>> is not >>>>>>>>>>>>> registered. >>>>>>>>>>>>> Nov 13 19:44:17 raspberrypi rsyslogd-2007: action 'action 17' >>>>>>>>>>>>> suspended, next retry is Sun Nov 13 19:45:47 2016 [try >>>>>>>>>>>>> http://www.rsyslog.com/e/2007 ] >>>>>>>>>>>>> Nov 13 19:44:54 raspberrypi kernel: [18523.645736] >>>>>>>>>>>>> w1_master_driver w1_bus_master1: Family 0 for 00.7e8000000000.c8 >>>>>>>>>>>>> is not >>>>>>>>>>>>> registered. >>>>>>>>>>>>> Nov 13 19:45:42 raspberrypi kernel: [18571.925336] >>>>>>>>>>>>> w1_master_driver w1_bus_master1: Family 0 for 00.fe8000000000.44 >>>>>>>>>>>>> is not >>>>>>>>>>>>> registered. >>>>>>>>>>>>> Nov 13 19:45:49 raspberrypi rsyslogd-2007: action 'action 17' >>>>>>>>>>>>> suspended, next retry is Sun Nov 13 19:47:19 2016 [try >>>>>>>>>>>>> http://www.rsyslog.com/e/2007 ] >>>>>>>>>>>>> >>>>>>>>>>>>> It will not connect and upload to the weather underground. >>>>>>>>>>>>> Not sure about what the w1_master is or how to register it. >>>>>>>>>>>>> >>>>>>>>>>>>> all help appreciated, >>>>>>>>>>>>> Thanks, >>>>>>>>>>>>> John >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> 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 [email protected]. >>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>> 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 [email protected]. >>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>> >>>>>>> >>>>>>> -- >>>>>> 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 [email protected]. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> -- >>> 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 [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
