Re: [weewx-user] Re: Apache is not showing /weewx on Ubuntu 16.04.1

[Thomas Keffer]

Mystery solved! Thanks, Matthew

I've started issue #137  to
track it.

-tk

On Wed, Jul 27, 2016 at 2:50 PM, mwall  wrote:

> On Wednesday, July 27, 2016 at 4:47:09 PM UTC-4, Tom Keffer wrote:
>>
>> I am not an apache expert either, but from what I can tell, the problem
>> is that the weewx Debian installs sets HTML_ROOT incorrectly. It's being
>> set to /var/www, when it should be /var/www/html.
>>
>
> blame it on more redhat-ification (and disregard for users) of debian.
>
> in debian 7 and earlier, DocumentRoot was /var/www
>
> in debian 8, DocumentRoot is /var/www/html
>
> in redhat and suse, DocumentRoot has been /var/www/html for quite some time
>
> there are at least two solutions:
>
> a) modify HTML_ROOT in weewx.conf:
>
> sudo sed -i -e 's%HTML_ROOT =.*%HTML_ROOT = /var/www/html/weewx%'
> /etc/weewx/weewx.conf
>
> b) create a symlink to the weewx report directory:
>
> sudo ln -s ../weewx /var/www/html
>
> i tend to prefer the latter, especially for systems such as rpi where the
> weewx reports are on a tmpfs to minimize sd card wear.
>
> i have not yet figured out a solution for the weewx .deb package that will
> work out-of-the-box with pre deb8 and post deb8 systems.  it would be nice
> if it worked with lighthttpd and nginx web servers as well as apache.
>
> 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+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.

Re: [weewx-user] Re: Apache is not showing /weewx on Ubuntu 16.04.1

[mwall]

On Wednesday, July 27, 2016 at 4:47:09 PM UTC-4, Tom Keffer wrote:
>
> I am not an apache expert either, but from what I can tell, the problem is 
> that the weewx Debian installs sets HTML_ROOT incorrectly. It's being set 
> to /var/www, when it should be /var/www/html. 
>

blame it on more redhat-ification (and disregard for users) of debian.

in debian 7 and earlier, DocumentRoot was /var/www

in debian 8, DocumentRoot is /var/www/html

in redhat and suse, DocumentRoot has been /var/www/html for quite some time

there are at least two solutions:

a) modify HTML_ROOT in weewx.conf:

sudo sed -i -e 's%HTML_ROOT =.*%HTML_ROOT = /var/www/html/weewx%' 
/etc/weewx/weewx.conf

b) create a symlink to the weewx report directory:

sudo ln -s ../weewx /var/www/html

i tend to prefer the latter, especially for systems such as rpi where the 
weewx reports are on a tmpfs to minimize sd card wear.

i have not yet figured out a solution for the weewx .deb package that will 
work out-of-the-box with pre deb8 and post deb8 systems.  it would be nice 
if it worked with lighthttpd and nginx web servers as well as apache.

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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Apache is not showing /weewx on Ubuntu 16.04.1

[vince]

The alternate solution is for you to edit weewx.conf to have it save its 
files in the place the webserver expects things.

The underlying issues are:

   - there are lots of webservers to pick from, they pick different 
   locations for document root
   - operating systems differ in where they set the webserver document root
   - 'versions' of a particular operating system also can change where they 
   set this

So weewx can't possibly keep track of this, there are too many 
ever-changing upstream providers of software.


The user/admin 'must' have enough knowledge to know how to get the files 
weewx generates into

the place 'they' want them to appear when viewed from a web browser.  There 
is no one-true-answer.



-- 
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.

[weewx-user] Re: Sensor Error (Started out of nowhere)

[Lymkin]

I know the sensors were working because I could see wind, temp, etc. 
changing over time.

I did end up clearing the memory and it has been stable for the past hour 
or so.  I'm wondering if it was trying to read memory and saw old 
values.not sure at this point.

On Wednesday, July 27, 2016 at 11:29:29 AM UTC-5, mwall wrote:
>
> On Wednesday, July 27, 2016 at 12:06:37 PM UTC-4, Lymkin wrote:
>>
>> I've started getting the following error and nothing logs to WUnderground 
>> anymore.
>>
>> weewx[975]: acurite: R1: ignoring stale data (rssi indicates no 
>> communication from sensors): 01 cf da 71 01 1d 15 69 00 00
>>
>> Was working fine and just started this behavior.  The Accurite display 
>> shows current values, so I know it is talking to the outdoor sensors.
>>
>> Any ideas?
>>
>
> how often does this happen?  for how long?
>
> how do you know that the display is talking to the sensors?  the display 
> will show the last values received, even if they are not current.
>
> when the rssi goes to zero, the sensor values reported by the console 
> cannot be trusted.  (the rssi is the second to last byte in the R1 message 
> you posted)
>
> it is possible that the firmware is confused and sends a value of 00 for 
> rssi no matter what the actual value is.  you would have to power cycle the 
> console to fix that.
>
> usually you can simply wait until the console re-establishes connection 
> and receives new data.
>
> if this happens often, then look for patterns in the log to see if you can 
> correlate bad rssi with radio interference sources.
>
> if it happens for extended periods, and you have ruled out rf 
> interference, then consider relocating the console so that it has a more 
> reliable signal from the sensors.
>
> or purchase one of the new acurite repeaters:
>
> https://www.acurite.com/wireless-signal-extender-for-acurite-sensors.html
>
> http://www.wxforum.net/index.php?topic=29898.0
>
> 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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Sensor Error (Started out of nowhere)

[Lymkin]

I've started getting the following error and nothing logs to WUnderground 
anymore.

weewx[975]: acurite: R1: ignoring stale data (rssi indicates no 
communication from sensors): 01 cf da 71 01 1d 15 69 00 00

Was working fine and just started this behavior.  The Accurite display 
shows current values, so I know it is talking to the outdoor sensors.

Any ideas?

Thanks

-- 
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.

Re: [weewx-user] Re: Raspian TE923 USB Problem

[Dennis slagers]

>
>
>
> sudo cat /sys/bus/usb/drivers/usbhid/unbind
> cat: /sys/bus/usb/drivers/usbhid/unbind: Permission denied
>
> sudo echo -n $id:1.0 > /sys/bus/usb/drivers/usbhid/unbind
> -bash: /sys/bus/usb/drivers/usbhid/unbind: Permission denied
>
> even as root .. permission denied... 
>
>
> PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
> NAME="Raspbian GNU/Linux"
> VERSION_ID="8"
> VERSION="8 (jessie)"
> ID=raspbian
> ID_LIKE=debian
> HOME_URL="http://www.raspbian.org/;
> SUPPORT_URL="http://www.raspbian.org/RaspbianForums;
> BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs;
>
> drwxr-xr-x 2 root root0 Jul 27 16:31 .
> drwxr-xr-x 8 root root0 Jul 27 16:31 ..
> --w--- 1 root root 4096 Jul 27 16:31 bind
> lrwxrwxrwx 1 root root0 Jul 27 16:31 module -> 
> ../../../../module/usbhid
> -rw-r--r-- 1 root root 4096 Jul 27 16:31 new_id
> -rw-r--r-- 1 root root 4096 Jul 27 16:31 remove_id
> --w--- 1 root root 4096 Jul 27 16:31 uevent
> --w--- 1 root root 4096 Jul 23 15:34 unbind
> root@weatherstation:/sys/bus/usb/drivers/usbhid#
>

lsusb gives
root@weatherstation:/home/pi# lsusb
Bus 001 Device 005: ID 1130:6801 Tenx Technology, Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 

-- 
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.

Re: [weewx-user] Re: Apache is not showing /weewx on Ubuntu 16.04.1

[Andrew Milner]

The simple answer is to do what Vince said - put a symbolic link in the 
apache root.

Looking at other instructions, out of curiosity - from the quick start 
guide:

After about 5 minutes, open the station web page in a web browser. You 
should see your station information and data. 

*file:///var/www/weewx/index.html* 

If your hardware supports hardware archiving, then how long you wait will 
depend on the *archive interval* 
 set in your 
hardware. 


does the browser find the page??


Although if you have changed things in weewx.conf the files could now be 
being put into different places!!



On Wednesday, 27 July 2016 12:29:25 UTC+3, Vlad Rafeev wrote:

> > First, install a web server on the computer on which weewx is running
>
> From this line it is clear, that weewx is already running. So I install 
> apache2 according to this guide.
>
> The correct sequence is to install apache2 first and add weewx later?
>
> On Wednesday, July 27, 2016 at 11:19:59 AM UTC+2, Andrew Milner wrote:
>>
>> You're probably right in that it looks as though the guide assumes 
>> apache2 is installed first, before the deb install - although there then 
>> appear to be some linguistic issues with present tense used when maybe it 
>> should be future!! I don't use apache2 either - preferring lighttpd on my 
>> rpi.
>>
>

-- 
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.

Re: [weewx-user] Re: Apache is not showing /weewx on Ubuntu 16.04.1

[Andrew Milner]

You're probably right in that it looks as though the guide assumes apache2 
is installed first, before the deb install - although there then appear to 
be some linguistic issues with present tense used when maybe it should 
be future!! I don't use apache2 either - preferring lighttpd on my rpi.

On Wednesday, 27 July 2016 11:47:41 UTC+3, gjr80 wrote:
>
> Actually, if the issue was a Vince pointed out:
>
> You didn't add a symbolic link from your apache2 document root to the 
>> public_html tree weewx writes to.
>
>
> then I think under the circumstances it may not have been you and rather 
> the docs could be at fault.
>
> I am following this tutorial
>> http://weewx.com/docs/usersguide.htm#integrating_with_webserver
>>
>> 1. I have installed clean Ubuntu 16.04.1
>> 2. I have installed weewx from DEB package
>> 3. I have installed apache2 with "sudo apt-get install apache2" command
>> 4. I see test Apache page on localhost (its working)
>>
>
> The OP did a deb package install and the link he is following clearly says 
> all you need do is install apache2 and then go to http://localhost/weewx. 
> The bit about copying conf files etc clearly applies to a setup.py 
> install which the OP does not have.
>
> If there is a need to so something else other then 'install apache2 and 
> then open http://localhost/weewx' then perhaps the docs need a bit of 
> clarrification/further guidance. That being said, I am not an apache2 
> user.
>
> Gary
>

-- 
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.