wviewweather.com

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

User n5rat wrote:

Folks,
I installed the Davis USB to serial driver that comes with the mac version of their software package. It does work, at least it works with their software.

I've completed the install up to the wviewconfig step. When it asks for the data port I get the following error.

Physical Interface the VP console is connected to (serial or ethernet)
(serial): /dev/tty.SLAB_USBtoUART
/dev/tty.SLAB_USBtoUART is not a valid physical interface - must be one of serial or ethernet!

Any suggestions?

Thanks.

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

Yes, follow the directions which state give it one of "serial" or "ethernet". For MacOSX versions of Weatherlink, I believe you received a USB-to-Serial adapter and associated driver. So you should select "serial" for this question.

After you enter serial for that question, you will enter the device name "/dev/tty.SLAB_USBtoUART" when it asks for the device name.

If it works for WL, it will work for wview.

Thanks,
Mark

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

FYI, it is possible to use ethernet serial servers such as the Atop GW21E or Lantronix MSS1-T to interface your VP console, thus not needing a separate USB adapter at all. That is why there is the choice on that question for "serial" or "ethernet".

Mark

n5rat · Joined: 01 Aug 2005 Posts: 7 Location: scottsdale, az

I've gotten everything installed, but I can't seem to start the software. I don't get an error when I run the start "wview daemons" , but when I looked at the console log I see the following.

Aug 1 15:15:49 mini SystemStarter[5072]: Unknown service: wview daemons

Also, as an FYI, in the vpinstall script, the /usr/local/bin doesn't get changed to /opt/local/bin by using the --prefix=/opt/local. I had to manually edit the vpinstall script to get it to work.

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

OK, we have now officially left my area of expertise Wink

Those startup scripts and instructions were kindly provided by another user who has an operational wview on Mac. I added the instructions based on a "HOWTO" I found for OSX boot startup of daemons.

Try to use "wview" instead of "wview daemons" in your start command. Also, I don't know if MacOSX picks up that wview start directory automatically or it needs to be rebooted. When you get it to work, let me know what I need to fix in the instructions.

Yes, the vpinstall script is something I am going to have to work out for you Mac folks. Was your VP station new? If not, there was no need to run it anyway. Further, you can get by with just using the on-screen console wizard and skipping the vpinstall script even if it is a new station.

Thanks for the feedback - that is why I am waiting to release 1.6.3 so we can iron out all of these discrepancies for Mac installs.

Mark

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

I just confirmed that it should be "wview" instead of "wview daemons" - I will correct the Guide now.

Thanks,
Mark

n5rat · Joined: 01 Aug 2005 Posts: 7 Location: scottsdale, az

OK. Killing the daemons from "wview daemons" gets it to start. And stop.

I'm getting data in the archive folder I created. I'm getting images in my img directory. I'm not getting any HTML code in my html directory.

Here's the console log.

mini wviewd[5308]: <1951677779> : station interface: serial ...
mini wvalarmd[5313]: <1951678828> : /etc/wview/wvalarm.conf does not exist - exiting...

mini wviewftpd[5317]: <1951678861> : /etc/wview/wviewftp.conf does not exist - exiting...
mini wviewsshd[5319]: <1951678875> : /etc/wview/wviewssh.conf does not exist - exiting...

mini SystemStarter[5302]: wview daemons (5305) did not complete successfully
mini SystemStarter[5302]: The following StartupItems failed to properly start:
mini SystemStarter[5302]: /Library/StartupItems/wview
mini SystemStarter[5302]: - execution of Startup script failed

I've checked the paths and all seem correct. The blank html docs are in the etc/wview/ directory. htmlgend is a running process. But no html documents have been created.

Any suggestions?

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

The generated images and html files will be in /var/wview/img - if you have files being created there, you are in business. Open /var/wview/img/index.html with your favorite browser.

Not sure what you mean by "killing the daemons" - I had to change from "wview daemons" to "wview" to get that SystemStarter utility to work.

/etc/wview/html is where the templates are stored - what wview uses to generate web pages in /var/wview/img... there will be no html files in there, only htx.

The complaints about "did not complete successfully" probably are because the ftp, ssh and alarm daemons are not configured to run so they start up and immediately exit - which is fine, but the SystemStartup is cranky about it.

Read the User Manual - under troubleshooting you will see some comments concerning how to look at running daemons and what is normal and what is not. If wviewd and htmlgend are running, you see log messages concerning adding archive records for specific times, and the html and image files are generated in /var/wview/img, you are in good shape.

Mark

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

Ok, I resolved the issue with the SystemStarter complaining because the optional daemons were exiting (as they should if not enabled). I also added more content to the Quick Start procedure to give tips for determining if wview is running properly and where to find your new homepage.

1.6.3 is released with these changes.

Did you ever get your wview up and running and locate your homepage?

Mark

wmiler · Joined: 21 Jul 2005 Posts: 24 Location: Florida

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

Well, whatever works for you - I use /sbin/SystemStarter start "wview", as documented for MacOSX, and it works just fine for me. Also, by placing those two files under the wview directory (as you originally suggested), it will be started at boot. Do a man on SystemStarter, it is part of the MacOSX-ification of FreeBSD 4.4.

I added a "SystemConsole -S" command at the bottom of the start routine and it alleviated SystemStarter complaining about the daemons that were exiting (as they should). It is in the 1.6.3 distro...

Mark

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

Just a few SystemStarter references:

http://www.macosxhints.com/article.php?story=20021003061516722

http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/SystemStarter.8.html

Mark

wmiler · Joined: 21 Jul 2005 Posts: 24 Location: Florida

What, me read the manual? Surprised

Thanks for the links though.

n5rat · Joined: 01 Aug 2005 Posts: 7 Location: scottsdale, az

Well, I've got two more problems now.
I decided to start over fresh with wview-1.6.3 and that solved most of my configuration issues, but now I have these two problems.

I tried an FTP transfer and got this problem.

1. wviewftp.conf doen't parse my username correctly when trying to establish an ftp connection. My ftp login takes the form of user@domain for the user name.

Then I tried to host locally, and got problem 2. Data is being generated locally, and so are images, but no html.

2. htmlgend is crashing before creating any html. I can provide a crashlog of htmlgend if that would help.

So wview is running, I'm just having problems displaying the data.

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

Yes, please provide a text file to me with all wview logs from the beginning of startup to the "crash". You can attach it here or email to me at mteel@users.sourceforge.net. Never heard of this one before...

We'll worry about ftp after you get the generation working.

Mark