It could also be a kernel problem. It would be most helpful if the other RPi is running a different kernel.
-tk On Sat, Dec 1, 2018 at 7:30 AM Gary Hopkins <xxgb...@gmail.com> wrote: > Hi, > > Thanks for the info. I have a new Pi 3+ coming this afternoon as I was > worried the one I have was busted in some way. I will post back once that's > arrived and I've had a chance to try it out. I've also been given a Pi > image from someone who already has this up and running and working so all > else fails I can give that a go. > > I could run it in a VM too I guess but I'd rather crack it on the Pi first. > > Cheers > > Gary > > On Saturday, 1 December 2018 15:04:13 UTC, Thomas Keffer wrote: >> >> They don't happen very often, but usually these abrupt crashes without >> anything in the log is due to a low-level driver or hardware failure. >> Something on the USB bus. >> >> Do you have another RPi or, even better, a x86-based PC you can try it on? >> >> -tk >> >> On Sat, Dec 1, 2018 at 6:38 AM Gary Hopkins <xxg...@gmail.com> wrote: >> >>> Dec 1 14:18:16 raspberrypi weewx[2088]: engine: Debug is 1 >>> >>> Line 6 of the capture you're replying to. >>> weewx in not running >>> Disabled the cron >>> >>> Thanks for the help. >>> >>> G >>> >>> On Saturday, 1 December 2018 14:32:57 UTC, mwall wrote: >>>> >>>> >>>> >>>> On Saturday, December 1, 2018 at 9:25:46 AM UTC-5, Gary Hopkins wrote: >>>>> >>>>> >>>>> sudo weewxd /etc/weewx/weewx.conf >>>>> >>>>> From the command line itself it doesn't show anything until it starts >>>>> taking in data and then I get >>>>> >>>>> REC: 2017-04-06 12:29:39 BST (1491478179) altimeter: 30.4319672166, >>>>> appTemp: 52.5740750576, barometer: 30.28595518, cloudbase: 2734.00530669, >>>>> dateTime: 1491478179.0, dewPoint: 6.7, dewpoint: 44.0235577061, ET: >>>>> 7.10130638221e-05, heatindex: 53.96, humidex: 53.96, inDewpoint: >>>>> 50.7669159193, inHumidity: 59, inTemp: 65.48, interval: 5, maxSolarRad: >>>>> None, outHumidity: 69, outTemp: 53.96, pressure: 29.9227363337, radiation: >>>>> 3.38595106551, rain: 0.0, rainRate: 0, usUnits: 1, UV: 0, windchill: >>>>> 53.96, >>>>> windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: >>>>> 0.0 >>>>> >>>>> Which repeats (I can post them all but they really are just more of >>>>> the same) and then stops and returns me a to a command prompt with no >>>>> massages. >>>>> >>>> >>>> you should try setting debug=1 >>>> >>>> be sure that weewx is not already running, and be sure that your cron >>>> task is disabled while you are running weewx directly. >>>> >>>> @aussisusan (or some enterprising python sleuth) will probably have to >>>> help you at this point. you'll have to check the code for cases where a >>>> try-except block is catching all exceptions, not just the intended >>>> exception. a generic catch block like that will hide the exception trace >>>> that would otherwise tell you where the failure is coming from. >>>> >>>> it is also possible that your system is shutting down the weewxd >>>> process, but that is typically accompanied by some kind of output from the >>>> system, even if it is simply 'Killed'. >>>> >>>> m >>>> >>> -- >>> 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+...@googlegroups.com. >>> 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 weewx-user+unsubscr...@googlegroups.com. > 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
