On Wednesday, September 13, 2017 at 9:31:57 AM UTC-4, [email protected] wrote: > > OK, assuming I am not as skilled as a programmer as you and that I am > reasonably skilled enough to set up weewx, Allstar, or Xastir and manage > cron jobs, how would I go about getting info from the log? Where do I run > this command and what command do I issue? > > Better yet, if I have run all of what I stated in the previous email, what > am I doing wrong? I am confused about how systemd stuff works. Does weewx > use systemd? I have executed autostarts with a sudo service > /etc/init.d/program_name defaults before but that is the extent of what I > know about doing stuff like this. >
mike, my response was not intended to be dismissive of your request - we really cannot help without seeing the log. the weewx user guide explains how to view the log: http://weewx.com/docs/usersguide.htm#monitoring in its default configuration, weewx sends messages to the system log. on debian systems that would be /var/log/syslog the system log will tell you exactly what is happening during system startup. it will also tell you (1) if weewx started, and (2) why weewx stopped if it was, in fact, started. you can view the log by tailing it in real time, e.g., 'sudo tail -f /var/log/syslog' or by looking at the latest n lines, e.g., 'sudo tail -500 /var/log/syslog' or by looking at the entire log, e.g., 'sudo more /var/log/syslog' we need to see the log from the time that the system started. if you are running a 'pure' systemd system that does not use rsyslog, you'll have to consult the systemd documentation to figure out how to view the system log. m
