sudo apt-get install nginx
sudo /etc/init.d/nginx start
NGINX defaults its web page location to /var/www/html on Raspbian so if you
want to change that you need to edit
/etc/nginx/sites-available/default
and edit the line
root /var/www/html/;
to
root /var/www/html/weewx/;
After that yo
base hold the historic data for you? You might
> not be able to push that back to the weather station but does that really
> matter?
>
> Susan
>
> On Monday, December 3, 2018 at 9:54:07 PM UTC+11, Gary Hopkins wrote:
>>
>> OK Update.
>>
>> I did get the new
put skin.conf back to the original state and then move
> your options into weewx, and then restart weewx.
>
> On Monday, December 3, 2018 at 5:59:07 PM UTC-5, Gary Hopkins wrote:
>>
>> Hi Pat,
>>
>> Which file takes priority, weewx.conf or skin.conf? By that I
Hi Pat,
Which file takes priority, weewx.conf or skin.conf? By that I mean if you
have something set to 1 in skin.conf and something set to 0 in weewx.conf
which wins?
Or
Am I right in thinking skin.conf gets parsed every single run but
weewx.conf only gets parsed when you re-start weewx? I a
OK Update.
I did get the new Pi but I've not installed it with weewx.
I was "fiddling" with the historic values on the WS and I went to delete
all the 2017 ones. Instead I accidentally deleted the 2018 ones so by then
it was too late.
Once I'd gone back and deleted all the 2017 entries and the
Will do my best and see what I can do.
Thanks
Gary
On Saturday, 1 December 2018 15:34:36 UTC, Thomas Keffer wrote:
>
> 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
4:13 UTC+2, 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
> 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 > wrote:
>
>> Dec 1 14:18
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 UT
Dec 1 14:18:16 raspberrypi weewx[2088]: engine: Initializing weewx version
3.8.2
Dec 1 14:18:16 raspberrypi weewx[2088]: engine: Using Python 2.7.13
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Dec 1 14:18:16 raspberrypi weewx[2088]: engine: Platform
Linux-4.14.79+-armv6l-with-de
On Saturday, 1 December 2018 10:51:28 UTC, Andrew Milner wrote:
>
> First of all get rid of the HUP in Cron - that does not help at all
>
> Both log sections seem to show more than pne occurrence of weewx to be
> running - look at the PIDs. You can only have one.
>
>
> Hi,
Actually heres a sni
Hi,
I can 100% assure you that weewx isn't running when the HUP happens. The
cron for that is a standard tiny script that checks first to make sure it's
not running before it restarts it.
#!/bin/bash
ps auxw | grep weewxd | grep -v grep > /dev/null
if [ $? != 0 ]
then
sudo systemctl
Hi,
Here's a better capture of the restart process. Not sure why it didn't have
all the extra info in the previous capture as it's from the exact same
process. I also modified some the parameters back to near their defaults
for clarity. Many thanks again.
G
Dec 1 10:33:26 raspberrypi weewx[2
Original Rasperry Pi Model B
8GB Class 4 SD Card
Latest Raspian installed through Noobs 3
Latest weewx installed following online guide through apt
Aercus WeatherRanger (WS1000 clone)
Used https://github.com/AussieSusan/HP1000 custom driver to grab events
over WiFi
weewx connects to the WS with n
14 matches
Mail list logo
