Stuck during installation

[Kim Spur]

It might be, because I'm a new-bee to rpi, but I have followed the quick-setup:

"If you are running a graphical interface, you can install by double-clicking the .deb file. Alternatively, if you are running from a command line, use the command:

sudo dpkg -i weewx_X.Y.Z-R_all.deb 
The installer will prompt for a location, latitude/longitude, altitude, station type, and parameters specific to your station hardware."

Since I'm a "windows-guy", I did the double-click version :)

No, I don't get prompt for anything during install, and after install I can't find the weewx.
Have tried to install on a new rpi II, and the latest noobs.
What do I do wrong?

Regards Kim

[Jose Antonio Garcia-Tenorio Ruiz]

Ummmm.....

any error message??

have you tried this??

sudo apt-get update

sudo apt-get upgrade

sudo apt-get -f install

sudo apt-get install apache2

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

--

_______________________________________________________

José A. Garcia

jan...@jantoni.es
ea4...@gmail.com

jagarci...@gmail.com

[Jose Antonio Garcia-Tenorio Ruiz]

http://www.weewx.com/docs/debian.htm

[Kim Spur]

No, not any error masseges of any kind.

Yes, I did an update/upgrade at first.

But did it again now, followed by your -f install and install apache2.

Made no difference....

When I double-click the weewx_3.4.4-1_all.deb file, it starts to install and it asks for the user and password (pi and raspberry.... default..)

Then it looks like it finishes the install, but nothing more happens, and no icons or new folders can be found ?

Just don't know what to do to startup the weewx ?

/Kim

[Glenn McKechnie]

Start up a terminal and type in ...
ls /etc/init.d/weewx

If it's installed then it should respond with ...
/etc/init.d/weewx

That's the start script. If you then type in ...
/etc/init.d/weewx status

the response will tell you if it's running or not. eg:-
Status of weewx weather system: running.

It should have prompted you for your preferences / details. If it is installed as per the above then type...
 sudo dpkg-reconfigure weewx

If the above yields nothing, ie: it's not installed then stay in the terminal and follow the commands, from that previously mentioned docs page, and install from the terminal.

[Kim Spur]

Den søndag den 28. februar 2016 kl. 22.28.27 UTC+1 skrev Glenn McKechnie:

Start up a terminal and type in ...
ls /etc/init.d/weewx

If it's installed then it should respond with ...
/etc/init.d/weewx

That's the start script. If you then type in ...
/etc/init.d/weewx status

the response will tell you if it's running or not. eg:-
Status of weewx weather system: running.

It should have prompted you for your preferences / details. If it is installed as per the above then type...
 sudo dpkg-reconfigure weewx

If the above yields nothing, ie: it's not installed then stay in the terminal and follow the commands, from that previously mentioned docs page, and install from the terminal.

This looks ok, right ?

pi@raspberrypi:~ $ ls /etc/init.d/weewx

/etc/init.d/weewx

pi@raspberrypi:~ $ /etc/init.d/weewx

Usage: /etc/init.d/weewx {start|stop|status|restart|reload}

pi@raspberrypi:~ $ /etc/init.d/weewx status

● weewx.service - LSB: weewx weather system

   Loaded: loaded (/etc/init.d/weewx)

   Active: active (exited) since søn 2016-02-28 21:53:24 CET; 53min ago

pi@raspberrypi:~ $ 

pi@raspberrypi:~ $ sudo dpkg-reconfigure weewx

using debconf configuration values from previous install

Saved configuration to /etc/weewx/weewx.conf

pi@raspberrypi:~ $ sudo dpkg-reconfigure weewx

using debconf configuration values from previous install

Saved configuration to /etc/weewx/weewx.conf

pi@raspberrypi:~ $ 

But if I type file:///var/www/weewx/index.html I get this:

 Unable to load page

Problem occurred while loading the URL file:///var/www/weewx/index.html

 

pi@raspberrypi:~ $ sudo tail -f /var/log/syslog

Feb 28 22:53:08 raspberrypi weewx[7440]: engine: pid file is /var/run/weewx.pid

Feb 28 22:53:08 raspberrypi weewx[7444]: engine: Using configuration file /etc/weewx/weewx.conf

Feb 28 22:53:08 raspberrypi weewx[7444]: engine: Loading station type Vantage (weewx.drivers.vantage)

Feb 28 22:53:08 raspberrypi weewx[7430]: Starting weewx weather system: weewx.

Feb 28 22:53:08 raspberrypi systemd[1]: Started LSB: weewx weather system.

Feb 28 22:53:08 raspberrypi weewx[7444]: vantage: No <ACK> received from console

Feb 28 22:53:08 raspberrypi weewx[7444]: engine: Unable to load driver: No <ACK> received from Vantage console

Feb 28 22:53:08 raspberrypi weewx[7444]:     ****  Exiting...

Feb 28 23:02:56 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Sun Feb 28 23:04:26 2016 [try http://www.rsyslog.com/e/2007 ]

Feb 28 23:07:11 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Sun Feb 28 23:08:41 2016 [try http://www.rsyslog.com/e/2007 ]

Davis Vantage Pro2 connected to Raspberry via USB/cable

\Kim 

[Glenn McKechnie]

That looks better in that it is installed and it is running.
The response you got saying

Usage: /etc/init.d/weewx {start|stop|status|restart|

reload}

is how you start | stop | etc weewx you just (as user pi) you'll need to prefix that command with sudo ie:-

 Usage: sudo /etc/init.d/weewx {start|stop|status|restart|reload}

You say it didn't prompt during install yet it seems to know you have a Vantage weather station? I'm a little
confused at that but, regardless, I'd manually check the text file /etc/weewx/weewx.conf with a text editor of your choice.
Familiarize yourself with it as you'll need to visit it more than once, any changes made to it will require a restart of the
 weewx daemon - that's where the sudo /etc/init.d/weewx {start|stop|status|restart|reload}  comes into it.

keep tailing syslog, it's your friend.
turn on debug (debug = 1 in the /etc/weewx/weewx.conf file)

keep posting log extracts to match your questions and help may be more forthcoming.

in fact , post your config file as well - weewx.conf - if you still have problems with the vantage.

I'd say you have no web page because your Vantage console isn't being picked up (no data, nothing to display)
Solve that and you'll be away - hopefully

[Thomas Keffer]

Kim,

Most likely you have a configuration problem with your Vantage, such as the wrong port number. 

Does it use a serial port, or a USB port?

Please post your configuration file. You should find it at /etc/weewx/weewx.conf

-tk

--

[Kim Spur]

Den mandag den 29. februar 2016 kl. 02.41.37 UTC+1 skrev Tom Keffer:

Kim,

Most likely you have a configuration problem with your Vantage, such as the wrong port number. 

Does it use a serial port, or a USB port?

Please post your configuration file. You should find it at /etc/weewx/weewx.conf

-tk

Yes, it is a Davis Vantage Pro2, connected via USB.

Have attached the config file, wich I have edited with a texteditor

/Kim 

[Thomas Keffer]

​Your configuration file looks fine. It assumes your VP2 is connected to /dev/ttyUSB0, which is a reasonable assumption. However, if you have other devices attached to your RPi it might not be. Here is one way to find out where your VP2 is really connected.

1. Disconnect your VP2;

2. Wait a couple of seconds;​

3. Reconnect it.

4. Use the following command

dmesg | tail

This will show the last few kernel messages. It will look something like:

[130078.866137] usb 1-1.2: new full-speed USB device number 8 using ehci-pci

[130078.958938] usb 1-1.2: New USB device found, idVendor=05ad, idProduct=0fba

[130078.958943] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[130078.958945] usb 1-1.2: Product: USB-Serial Controller

[130078.958948] usb 1-1.2: Manufacturer: Prolific Technology Inc.

[130078.959235] pl2303 1-1.2:1.0: pl2303 converter detected

[130078.962415] usb 1-1.2: pl2303 converter now attached to ttyUSB0

The exact text does not matter. What you are looking for is the device port (highlighted in yellow above). Use this ID with the prefix '/dev/'. (For example, 'ttyUSB0' becomes '/dev/ttyUSB0'). Make sure this matches what you have in your configuration file.

It's possible that disconnecting the VP2 and then reconnecting will solve your problems, but make sure the port ID matches what you are using in your configuration file.

-tk

--

[Kim Spur]

Den mandag den 29. februar 2016 kl. 15.06.04 UTC+1 skrev Tom Keffer:

​Your configuration file looks fine. It assumes your VP2 is connected to /dev/ttyUSB0, which is a reasonable assumption. However, if you have other devices attached to your RPi it might not be. Here is one way to find out where your VP2 is really connected.

1. Disconnect your VP2;

2. Wait a couple of seconds;​

3. Reconnect it.

4. Use the following command

dmesg | tail

This will show the last few kernel messages. It will look something like:

[130078.866137] usb 1-1.2: new full-speed USB device number 8 using ehci-pci

[130078.958938] usb 1-1.2: New USB device found, idVendor=05ad, idProduct=0fba

[130078.958943] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[130078.958945] usb 1-1.2: Product: USB-Serial Controller

[130078.958948] usb 1-1.2: Manufacturer: Prolific Technology Inc.

[130078.959235] pl2303 1-1.2:1.0: pl2303 converter detected

[130078.962415] usb 1-1.2: pl2303 converter now attached to ttyUSB0

The exact text does not matter. What you are looking for is the device port (highlighted in yellow above). Use this ID with the prefix '/dev/'. (For example, 'ttyUSB0' becomes '/dev/ttyUSB0'). Make sure this matches what you have in your configuration file.

It's possible that disconnecting the VP2 and then reconnecting will solve your problems, but make sure the port ID matches what you are using in your configuration file.

-tk

Result:

pi@raspberrypi:~ $ dmesg | tail

[65960.841152] usb 1-1.5: USB disconnect, device number 7

[66026.624859] usb 1-1.3: new low-speed USB device number 8 using dwc_otg

[66026.748025] usb 1-1.3: New USB device found, idVendor=045e, idProduct=00b0

[66026.748052] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[66026.748069] usb 1-1.3: Product: Microsoft® Digital Media Pro Keyboard

[66026.748085] usb 1-1.3: Manufacturer: Microsoft

[66026.763526] input: Microsoft Microsoft® Digital Media Pro Keyboard as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:045E:00B0.0007/input/input6

[66026.815673] hid-generic 0003:045E:00B0.0007: input,hidraw2: USB HID v1.11 Keyboard [Microsoft Microsoft® Digital Media Pro Keyboard] on usb-3f980000.usb-1.3/input0

[66026.838827] input: Microsoft Microsoft® Digital Media Pro Keyboard as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:045E:00B0.0008/input/input7

[66026.896102] hid-generic 0003:045E:00B0.0008: input,hidraw3: USB HID v1.11 Device [Microsoft Microsoft® Digital Media Pro Keyboard] on usb-3f980000.usb-1.3/input1

pi@raspberrypi:~ $ 

I have a Medion wireless mouse, a MS keyboard, and the Vantage Pro2 attached to USB

Regards, Kim 

[Thomas Keffer]

Did you disconnect and reconnect the VP2 before typing dmesg? There is no indication of the VP2 in the messages, just your keyboard.

-tk

--

[Kim Spur]

Den mandag den 29. februar 2016 kl. 15.33.26 UTC+1 skrev Tom Keffer:

Did you disconnect and reconnect the VP2 before typing dmesg? There is no indication of the VP2 in the messages, just your keyboard.

-tk

Dohh... I disconnected the keyboard and reconnected it... Dumass me....

Well, here we go again:

pi@raspberrypi:~ $ dmesg | tail

[77550.483021] ftdi_sio 1-1.3:1.0: device disconnected

[78109.385854] usb 1-1.3: new full-speed USB device number 11 using dwc_otg

[78109.513387] usb 1-1.3: New USB device found, idVendor=0403, idProduct=6001

[78109.513417] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[78109.513434] usb 1-1.3: Product: FT232R USB UART

[78109.513449] usb 1-1.3: Manufacturer: FTDI

[78109.513464] usb 1-1.3: SerialNumber: AK003U4R

[78109.521959] ftdi_sio 1-1.3:1.0: FTDI USB Serial Device converter detected

[78109.522178] usb 1-1.3: Detected FT232RL

[78109.526921] usb 1-1.3: FTDI USB Serial Device converter now attached to ttyUSB0

pi@raspberrypi:~ $ 

PS: Its NOT the original USB device in the VP2, but it works perfectly in Meteohub.

/Kim

[Kim Spur]

SYSlog:

pi@raspberrypi:~ $ sudo tail -f /var/log/syslog

Feb 29 18:48:05 raspberrypi avahi-daemon[368]: Invalid response packet from host 192.168.1.39.

Feb 29 18:48:28 raspberrypi avahi-daemon[368]: Invalid response packet from host 192.168.1.39.

Feb 29 18:48:28 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Mon Feb 29 18:49:58 2016 [try http://www.rsyslog.com/e/2007 ]

Feb 29 18:49:37 raspberrypi avahi-daemon[368]: Invalid response packet from host 192.168.1.39.

Feb 29 18:50:01 raspberrypi avahi-daemon[368]: Invalid response packet from host 192.168.1.39.

Feb 29 18:50:01 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Mon Feb 29 18:51:31 2016 [try http://www.rsyslog.com/e/2007 ]

Feb 29 18:50:05 raspberrypi avahi-daemon[368]: Invalid response packet from host 192.168.1.39.

Feb 29 18:50:05 raspberrypi avahi-daemon[368]: Invalid response packet from host 192.168.1.39.

Feb 29 18:50:08 raspberrypi avahi-daemon[368]: Invalid response packet from host 192.168.1.39.

Feb 29 18:54:18 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Mon Feb 29 18:55:48 2016 [try http://www.rsyslog.com/e/2007 ]

My RPI has IP 192.168.1.38 NOT 192.168.1.39 as in SYSlog __

[vince]

• The avahi stuff is unrelated to weewx and happens sometimes.   Try a google for "avahi-daemon invalid response packet from host" for many threads on the topic.

• The rsyslogd stuff is unrelated to weewx.  Try a google for "action 17 suspended" for many threads on the topic.

Now that you replugged your USB adaptor in and it's visible, try to restart weewx and see if it talks to the weather station finally.

[Kim Spur]

Restarted RPI, and VP2, and now I get data.

Next I have to figure out, how to display the live data on my website, but that's probaly another story :)

Thanks for the help.....

This thread is solved.

/Kim