Alright...trying that now. Sorry for the confusion, I'm obviously not used to Linux. I've attached the journalctl logs, they are showing Weewx now.
When I run the copy command above I get the following error: cp: '/etc/weewx/rsyslog.d/weewx.conf' and '/etc/rsyslog.d/weewx.conf' are the same file I see the weewx.log file now, but it is empty. On Monday, January 6, 2025 at 3:00:59 PM UTC-5 vince wrote: > I'm sorry but again you need to provide the weewx log data, not the os log > data (which is not including anything weewx for some reason). There is no > mention of weewx in your 'syslog' attachment at all. > > Since you seem to be running rsyslog according to one log snippet, you > might trying switching to rsyslog for your weewx logging to make finding > the log data easier. You can do this via: > > sudo cp /etc/weewx/rsyslog.d/weewx.conf /etc/rsyslog.d/weewx.conf > sudo systemctl restart rsyslog > sudo systemctl restart weewx > > Then your weewx logs will be in /var/log/weewx/weewx.log and nice and > easy to grab. You will probably need to use sudo to read them. > > (I tested the above using debian12 so it should work the same on anything > 'buntu) > > On Monday, January 6, 2025 at 11:43:49 AM UTC-8 Jonathan Emmert wrote: > >> Okay...progress. I ran the report again and got the exact same results. I >> changed my Default Command where I was outputting the json to a specific >> folder/file. I modified that to just export the json to the default >> location. That changed the logs and I am now seeing data generated. (New >> logs attached.) >> >> That being said, I still see 2 issues: >> 1. Mobile report showing errors >> 2. Not uploading to WeatherUnderground >> >> On Monday, January 6, 2025 at 2:14:25 PM UTC-5 vince wrote: >> >>> Your syslog doesn't mention weewx at all. Your journalctl log is under >>> 'one' second of data from initial startup. Give it another try please. >>> >>> On Monday, January 6, 2025 at 10:50:41 AM UTC-8 Jonathan Emmert wrote: >>> >>>> I gotcha - I was having some trouble getting those. I've attached 2 >>>> logs, both with a. 20 minute run. >>>> >>>> On Sunday, January 5, 2025 at 8:52:20 PM UTC-5 vince wrote: >>>> >>>>> 40 lines isn't enough. We need the debug=1 syslog from startup of the >>>>> weewx process through at least one or two reporting cycles (typically 10 >>>>> min+). >>>>> >>>>> >>>>> https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user#how-to-get-a-good-useful-log >>>>> >>>>> >>>>> On Sunday, January 5, 2025 at 4:51:15 PM UTC-8 Jonathan Emmert wrote: >>>>> >>>>>> Sorry about that. Are these what you needed? >>>>>> On Saturday, January 4, 2025 at 8:49:39 PM UTC-5 vince wrote: >>>>>> >>>>>>> A log in RTF format ? Please. Text files only. >>>>>>> >>>>>>> I see nothing in your file with the string weewx. See >>>>>>> https://www.weewx.com/docs/5.1/usersguide/monitoring/#status for >>>>>>> how to get the actual logs for your os. Be sure to set debug=1 in >>>>>>> weewx >>>>>>> and restart weewx afterward to get verbose logging. >>>>>>> >>>>>>> On Saturday, January 4, 2025 at 2:39:53 PM UTC-8 Jonathan Emmert >>>>>>> wrote: >>>>>>> >>>>>>>> I have just installed Weewx on Lubuntu (22.04.5) but it doesn't >>>>>>>> seem to be writing to the sqlite db. Relevant notes. >>>>>>>> >>>>>>>> - Installed directly from Git >>>>>>>> - Using a Vevor 7in1 Weather station >>>>>>>> - Communicating to the computer via rtl_433 >>>>>>>> - rtl_433 is running correctly (have the command line in >>>>>>>> sdr.py also writing a json which is updating as expected) >>>>>>>> - I have installed the weewx-sdr add-on >>>>>>>> - I have attached my syslog for a 15 minute run (debug = 1 >>>>>>>> enabled) >>>>>>>> >>>>>>>> Any help is appreciated. >>>>>>>> >>>>>>> -- 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 visit https://groups.google.com/d/msgid/weewx-user/c395c570-a3d7-4335-80ec-90af92bc75b1n%40googlegroups.com.
journalctl
Description: Binary data
