| View previous topic :: View next topic |
| Author |
Message |
imesg
Joined: 30 Jul 2005
Posts: 9
|
 Posted: Sun Aug 07, 2005 9:35 am Post subject: wview will not start |
 |
|
I had wview running nicely but I rebooted yesterday and now wview will not start.
This is on a gentoo linux box.
This is the log entry:
Aug 7 10:32:21 [wviewd] <2442277226> : radlib: wviewd started as a daemon ...
Aug 7 10:32:21 [wviewd] <2442277256> : station interface: serial ...
Aug 7 10:32:21 [wviewd] <2442277256> : console polling interval set to 15 seconds
Aug 7 10:32:21 [wviewd] <2442277256> : SQLDB extended archiving enabled ...
Aug 7 10:32:21 [wviewd] <2442277256> : vpifMediumInit: medium setup failed
Aug 7 10:32:21 [wviewd] <2442277256> : vpifMediumInit failed
Aug 7 10:32:22 [htmlgend] <2442278258> : wview daemon lock file /var/wview/wviewd.pid does not exist - aborting!
Aug 7 10:32:22 [htmlgend] <2442278258> : system init failed!_
Thanks for any help,
Gene |
|
| Back to top |
|
 |
mteel
Joined: 30 Jun 2005
Posts: 435
Location: Collinsville, TX
|
| Posted: Sun Aug 07, 2005 9:59 am Post subject: |
|
|
Are you using a serial or ethernet interface?
Did you re-run wviewconfig and change the device name?
Are you using a USB-to-serial adapter and somehow not load the proper driver for it when you rebooted?
If it is a serial interface, I would check to see that the serial device you have given wviewconfig works with minicom - this is only a preliminary test, but will let you know if there is a problem with the device (or driver if a USB adapter).
Mark |
|
| Back to top |
|
|
imesg
Joined: 30 Jul 2005
Posts: 9
|
| Posted: Sun Aug 07, 2005 10:00 am Post subject: |
|
|
Ok, disregard. I replugged the usb cable from the VP2 console now wview will start.
So no problem with wview but with usb. If anyone knows how to fix this let me know.
Thanks,
Gene |
|
| Back to top |
|
|
mteel
Joined: 30 Jun 2005
Posts: 435
Location: Collinsville, TX
|
| Posted: Sun Aug 07, 2005 10:00 am Post subject: |
|
|
| Test via minicom by issuing the "TEST" command - it should spit back a "TEST" response... |
|
| Back to top |
|
|
mteel
Joined: 30 Jun 2005
Posts: 435
Location: Collinsville, TX
|
| Posted: Sun Aug 07, 2005 10:38 am Post subject: |
|
|
Sounds like a USB serial driver problem or at least instability. What kernel are you running? 2.4 USB support is sometimes spotty...
You might google for your USB-to-serial device to see if you can find anything - I assume you are using a USB-to-Serial adapter?
Mark |
|
| Back to top |
|
|
mteel
Joined: 30 Jun 2005
Posts: 435
Location: Collinsville, TX
|
| Posted: Sun Aug 07, 2005 10:40 am Post subject: |
|
|
| It also may be that your USB serial driver is not detecting the device at boot, but is detecting it when hot-plugged... do you see any messages concerning detection at boot when you issue the "dmesg" command? |
|
| Back to top |
|
|
imesg
Joined: 30 Jul 2005
Posts: 9
|
| Posted: Mon Aug 08, 2005 8:46 am Post subject: |
|
|
| mteel wrote: | | It also may be that your USB serial driver is not detecting the device at boot, but is detecting it when hot-plugged... do you see any messages concerning detection at boot when you issue the "dmesg" command? |
Yep, it shows up after dmesg but hotplug picks is up. I think it is a usb problem. I routinly have to power cycle my printer to get that to work also.
Thanks all,
Gene |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
