I've hit a road block, and would like some help

[ACiD GRiM]

I'm confused by the documentation and my actual results. I've
successfully compiled everything while following the user manual and
quick start guide, but when I run wviewconfig, I get a sqlite error
that the config table doesn't exist in wview-conf.sdb. I'm not too
experienced with sqlite, but even if I add the table to /etc/wview/
wview-conf.sdb, I get the error. I ./configure'd it properly to look
in /etc/wview.

Also, is it possible to just make an html page that has the data
table, and nothing else?

[Michael]

Hi

You will find there are plenty of people here willing to help.

The first thing you next to do is include wview log files from /var/
log on my system its /var/log/user.log

Also dumps of the errors from any command like errors you get

Then with this info people can work out what's going on

Cheers
Michael

[Graham Eddy]

has anyone got wviewmgmt working on ubuntu hardy?

i had it working on ubuntu jaunty. i had to migrate to another platform,
which will be running hardy due to other dependencies. everything works
fine, except trying to access wviewmgmt using browser

after logging in, at wviewmgmt/system_status.php i get message
"SqliteDBOpen /usr/local/etc/wview/wview-conf.sdb failed: could not find
driver". i have installed the php5 & sqlite3 modules. the message seems
to indicate a missing php5-sqlite3 interface but this module has been
installed. i can find no pdo_sqlite.so even after installation

google tells me there are some existing php5 lacks interfacing sqlite3
(specifically, no PDO support for sqlite3). my present theory is that
the php5/sqlite3 interface problem was resolved in later version of
ubuntu and not back-ported to hardy. hence my question: has anyone got
wviewmgmt working on hardy?
------------------------------------------------------------------------
*Graham Eddy*

[ACiD GRiM]

Thanks for the thread hijack...

I'm running Red Hat 5.4, and I don't see /var/log/user or /var/log/
root (I'm running this as root right now).

################################################################################
!!!!!!!!!!!!!!!! READ THIS BEFORE
PROCEEDING !!!!!!!!!!!!!!!!

--> System Configuration for wview

--> Values in parenthesis are your existing values (if they exist) or
defaults -
they will be used if you just hit enter at the prompt...

--> Note: This script will save the existing wview-conf.sdb file to
/etc/wview/wview-conf.old before writing the new file
based on your answers here - if that is not what you want,
hit CTRL-C now to
abort this script!

################################################################################

pausing 3 seconds ...

-------------------------------------------------------------

PARAMETER: SQL error: no such table: config
():


################################################################################
--> wview Configuration Complete!
--> Now run wviewhtmlconfig to select your site skin.
################################################################################


_______________________
dmesg

Bluetooth: RFCOMM ver 1.8
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
eth0: no IPv6 routers present
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { AbortedCommand }
ide: failed opcode was: 0xec





____________________________
/var/log/messages

Nov 8 04:02:07 weathermon2 syslogd 1.4.1: restart.
Nov 8 21:16:21 weathermon2 dhclient: DHCPREQUEST on eth0 to
172.16.1.4 port 67
Nov 8 21:16:21 weathermon2 dhclient: DHCPACK from 172.16.1.4
Nov 8 21:16:21 weathermon2 dhclient: bound to 172.16.52.5 -- renewal
in 117445 seconds.

[ACiD GRiM]

This is my configure command:

./configure --exec-prefix=/usr --prefix="" --datadir=/usr --enable-
station-vpro --htmldir=/var/www/html/html

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking whether struct tm is in sys/time.h or time.h... time.h
checking for struct tm.tm_zone... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for wvstrncpy in -lc... no
checking for gdImageCreate in -lgd... yes
checking for exp in -lm... yes
checking for png_write_chunk in -lpng... yes
checking for sqlite3_open in -lsqlite3... yes
checking for radSystemGetUpTimeMS in -lrad... yes
checking for inflate in -lz... yes
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking for unistd.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking for pid_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... (cached)
time.h
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking for sys/time.h... (cached) yes
checking for unistd.h... (cached) yes
checking for alarm... yes
checking for working mktime... yes
checking return type of signal handlers... void
checking whether lstat dereferences a symlink specified with a
trailing slash... yes
checking whether stat accepts an empty string... no
checking for localtime_r... yes
checking for memset... yes
checking for mkdir... yes
checking for pow... yes
checking for strrchr... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating stations/Makefile
config.status: creating stations/Simulator/Makefile
config.status: creating stations/VantagePro/Makefile
config.status: creating stations/VantagePro/vpconfig/Makefile
config.status: creating stations/WS-2300/Makefile
config.status: creating stations/WMR918/Makefile
config.status: creating stations/WXT510/Makefile
config.status: creating stations/WXT510/wxt510config/Makefile
config.status: creating htmlgenerator/Makefile
config.status: creating alarms/Makefile
config.status: creating cwop/Makefile
config.status: creating http/Makefile
config.status: creating ftp/Makefile
config.status: creating ssh/Makefile
config.status: creating procmon/Makefile
config.status: creating wviewconfig/Makefile
config.status: creating wviewmgmt/Makefile
config.status: creating dbexport/Makefile
config.status: creating examples/Makefile
config.status: creating examples/Debian/Makefile
config.status: creating examples/FedoraCore/Makefile
config.status: creating examples/FreeBSD/Makefile
config.status: creating examples/MacOSX/wview/Makefile
config.status: creating examples/NSLU2/Makefile
config.status: creating examples/SuSE/Makefile
config.status: creating utilities/Makefile
config.status: creating utilities/wlk2sqlite/Makefile
config.status: creating utilities/sqlite2wlk/Makefile
config.status: creating utilities/archive-be2le/Makefile
config.status: creating utilities/archive-le2be/Makefile
config.status: creating utilities/hilowcreate/Makefile
config.status: creating config.h
config.status: executing depfiles commands

[mteel]

Not sure what you are trying to accomplish with "--prefix="" ", but it
is not good. If you want wview directories in /etc and /var, use "--
prefix=/" - an empty string makes no sense. I would not muck with it
and let the prefix be "/usr/local" - the default.

[ACiD GRiM]

I just uninstalled, reconfigured, and installed with the default
prefixes and now I get

/usr/local/bin/wviewconfig
wview configuration database NOT FOUND

[mteel]

I'm betting you did not execute "make install-env" like the User
Manual states... That target will create the default configuration
database.

> ...
>
> read more »

[ACiD GRiM]

You are psychic! Years of just "make install" made me skip over that.
Let me go through this, and I'll post back if I have any more trouble.

> ...
>
> read more »

[Mark S. Teel]

I'm going to fix the automake setup so the install-env target will be
removed and its contents automatically executed when "make install" is
executed. This causes too many problems and there is no longer a need
for "install-env" to be a separate target.

Glad it worked out OK.

Mark

[ACiD GRiM]

Ok, I got the config scripts to run, but I'm trying to get the web
management interface working. Right now, if I run login.php, and use
wview as the PW, I get a white page, as well as the other php pages.
my wview-conf.sdb is in /etc/wview, so I don't know if that's the
problem, but I don't see any config file in wviewmgmt to change the
target.

Also, what is the best way to have multiple wview's running getting
data from different weather stations? I'd assume it's a command line
switch for wviewd_vpro, but there is no --help.

> ...
>
> read more »

[Graham Eddy]

i use "make install" separately from "make install-env" quite often.
i update images-user.c, use "make" and "make install" to install the
updated binaries *without* replacing my custom environment.
i understand the issue and agree "make install" should be the default
for setting stuff up.
could we have a "make install-bin" for just replacing the binaries?
------------------------------------------------------------------------
*Graham Eddy*

On 10/11/2009 2:04 PM, Mark S. Teel wrote:
> I'm going to fix the automake setup so the install-env target will be
> removed and its contents automatically executed when "make install" is
> executed. This causes too many problems and there is no longer a need
> for "install-env" to be a separate target.
>
> Glad it worked out OK.
>
> Mark

[deleted]

[Mark S. Teel]

make install-env has migrated over the years from being only for new
installs (and being destructive) to the current version which is
non-destructive and can/should/will be used all the time. There is no
benefit or purpose now for an install-bin - that is the behavior of
install (which includes install-env) as of 5.7.0. It does not replace
or destroy existing data or configuration, only creates them if they do
not exist. If you have an existing install, make install = make
install-bin.

[Graham Eddy]

i'm happy that my need has already been anticipated - thanks
------------------------------------------------------------------------
*Graham Eddy*

[Gerry Creager]

I'd also prefer to have 'em separated. I've several other applications
I use on a regular basis where I once believed a single, great, unified
"make install" command would be useful, but discovered, as Graham
mentions, that the occasional tweak might cause me to reinstall
recompiled code, but I don't want to retweak environment cariables,
UIDs, etc.

+1 on Graham's comment, but +1 to Mark for thinking about how to make
things even better.

gerry

[Gerry Creager]

I should have read all my e-mail before responding. I, too, and happy
with your explanation, Mark. Thanks!

gerry