wview 5.11.0 Released

[Mark S. Teel]

http://www.wviewweather.com

Note: Sourceforge is sucking this morning so wait an hour or so for the
tarball to be propagated. APT users, the wviewweather.com repository is
updated and ready to go now!

5.11.0 01-09-2009
--------------------

radlib version required: 2.9.0 or newer

1) Fix log buffer overflow for FTP verbosity.

2) Modify FTP to execute multiple smaller ftp commands to avoid large
command
lines which may timeout.

3) Added an FTP marker file indicating the last update time for FTP.
This allows
only new files to be transferred, saving time and bandwidth.

4) Added new SSH configuration parameters for remote port number and remote
ssh login username.

5) Added ability to automatically update the configuration database
during update
of existing installations when new configuration parameters are
added in
future releases.

[Tagman9]

Thanks Mark! I've intalled the new release and will let you know how
it goes. Thanks again!

- Ed

[TN_Yankee]

Thanks for your work, Mark. Three hours and running now, which is at
least 2 hours longer than I could keep the ftp running on 5.10.3.

I'm glad you were able to keep & improve upon the ftp enhancements, as
well.

Mike

[Tagman9]

So far so good!!

[TN_Yankee]

Unfortunately, ftp is still stopping after a period of time, though
without running the cpu to 90%+. It just dies silently. It's done
this 3 times now since the upgrade, including this time within 20
minutes of a reboot (due to my CWOP barometer problem, in another
thread). Other times it ran for more than a few hours.

The services status table shows ftp is running, normal operation,
rules defined = 6, and rules sent = 33. Top does not show it as a
zombie.

[Tagman9]

OK.. Spoke too soon..

FTP's stopped sending. However the service isn't consuming all CPU as
before. Last update was at 16:33:10..

ftp_marker file = 1263159075

I will turn verbose logging back on the wviewftpd service and restart
so I can hopefully capture something meaningful.

On Jan 10, 11:50 am, Tagman9 <etagga...@gmail.com> wrote:
> So far so good!!

[stinkiest]

i'd like to report the same issue. what cant i do to provide more info
for debugging?

[Mark S. Teel]

Yes, please do. That's what the change was all about was getting
feedback about the connection.

I'll bet the folks that are still having problems always did but the old
implementation forked a new child for each invocation of tnftp and did
not "wait" on it for completion. Now the wviewftpd daemon does wait,
causing the stoppage. Your server's are probably hanging on the
transaction and the new implementation requires they finish. The old
implementation would just continue to fork new instances when the time
came to transfer. I also bet you had defunct instances of the FTP child
hung on the tnftp call in the past. But it kept updating on subsequent
forks, thus appearing to be just fine.

BTW, my FTP runs like a clock against my local server.

Mark

[Graham Eddy]

ftp has two ends, ours and the remote end. after a quick sanity check of our end, we need to establish which end is causing the problem - it is just as likely not our fault. for example, last time i mentioned this, the person quickly ran tnftp manually after having problem with automation - and the other end rejected the ftp connection request (problem was at remote end)!

i know this doesn't explain wviewftpd consuming 99% etc - there are (have been recently, at least) problems on our end. it is possible that wviewftpd gets into trouble when the remote end doesn't behave properly

but it looks to me like there are multiple issues, some at our end and some at (our respective) remote end, and a single silver bullet at our end only does not exist

---

Graham Eddy

[Tagman9]

I get that. I will validate that godaddy's FTP is working next time
it occurs. However I wouldn't suspect their FTP having an issue for
over an hour. Plus the FTP works when restarting wview. Perhaps
I'll try a retry or quit parameter with tnftp
to see if that helps.

- Ed

On Jan 10, 6:39 pm, Graham Eddy <graham.e...@gmail.com> wrote:
> ftp has two ends, ours and the remote end. after a quick sanity check of
> our end, we need to establish which end is causing the problem - it is
> just as likely not our fault. for example, last time i mentioned this,
> the person quickly ran tnftp manually after having problem with
> automation - and the other end rejected the ftp connection request
> (problem was at remote end)!
>
> i know this doesn't explain wviewftpd consuming 99% etc - there are
> (have been recently, at least) problems on our end. it is possible that
> wviewftpd gets into trouble when the remote end doesn't behave properly
>
> but it looks to me like there are multiple issues, some at our end and
> some at (our respective) remote end, and a single silver bullet at our
> end only does not exist

> ------------------------------------------------------------------------
> *Graham Eddy*

[stinkiest]

i'm not sure what to do other than posting this crap from syslog.

this is immediately after a restart

Jan 10 21:15:10 Weather1 htmlgend[4501]: <1263176110323> : Generated:
69 ms: 17 images, 14 template files
Jan 10 21:16:10 Weather1 htmlgend[4501]: <1263176170344> : Generated:
93 ms: 17 images, 14 template files
Jan 10 21:16:15 Weather1 wviewftpd[4515]: <1263176175250> : FTP-RULE:
sending *.png
Jan 10 21:16:15 Weather1 wviewftpd[4515]: <1263176175308> : FTP-
COMMAND: /usr/bin/tnftp -iV -u ftp://xxx...@whiteoakhillweather.net16.net/public_html/wview/
./barom.png ./baromday.png ./barommonth.png ./baromweek.png ./
baromyear.png ./dayrain.png ./dew.png ./dewyear.png ./
heatchillcomp.png ./heatchillmonthcomp.png ./heatchillweekcomp.png ./
hindex.png ./hindexyear.png ./hiwspeedday.png ./hiwspeedmonth.png ./
hiwspeedweek.png ./hiwspeedyear.png ./humid.png ./humidday.png ./
humiddial.png ./humidmonth.png ./
Jan 10 21:16:15 Weather1 wviewftpd[4515]: <1263176175308> : FTP-
COMMAND: umidweek.png ./humidyear.png ./monthrain.png ./
netRainDay.png
Jan 10 21:16:23 Weather1 wviewftpd[4515]: <1263176183497> : FTP-
COMMAND: /usr/bin/tnftp -iV -u ftp://xxxx...@whiteoakhillweather.net16.net/public_html/wview/
./netRainMonth.png ./netRainYear.png ./rainday.png ./rainmonth.png ./
rainrate.png ./rainweek.png ./rainyear.png ./stormrain.png ./
temp.png ./tempdaycomp.png ./tempdial.png ./tempmonthcomp.png ./
tempweekcomp.png ./tempyear.png ./wchill.png ./wchillyear.png ./
wdirday.png ./wdirmonth.png ./wdirweek.png ./wdiryear.png ./wind.png ./
wspeedday.png ./wspeed
Jan 10 21:16:23 Weather1 wviewftpd[4515]: <1263176183497> : FTP-
COMMAND: onth.png ./wspeedweek.png ./wspeedyear.png ./yearrain.png
Jan 10 21:16:41 Weather1 wviewftpd[4515]: <1263176201412> : FTP-RULE:
sending *.htm
Jan 10 21:16:41 Weather1 wviewftpd[4515]: <1263176201412> : FTP-
COMMAND: /usr/bin/tnftp -iV -u ftp://xxxxx...@whiteoakhillweather.net16.net/public_html/wview/
./Current.htm ./Daily.htm ./Monthly.htm ./Weekly.htm ./Yearly.htm ./
almanac.htm ./index-day.htm ./parameterlist.htm
Jan 10 21:16:46 Weather1 wviewftpd[4515]: <1263176206466> : FTP-RULE:
sending *.html
Jan 10 21:16:46 Weather1 wviewftpd[4515]: <1263176206466> : FTP-
COMMAND: /usr/bin/tnftp -iV -u ftp://xxxxxx...@whiteoakhillweather.net16.net/public_html/wview/
./index.html
Jan 10 21:16:50 Weather1 wviewftpd[4515]: <1263176210118> : FTP-RULE:
sending *.xml
Jan 10 21:16:50 Weather1 wviewftpd[4515]: <1263176210118> : FTP-
COMMAND: /usr/bin/tnftp -iV -u ftp://xxxxxx...@whiteoakhillweather.net16.net/public_html/wview/
./wxrss.xml
Jan 10 21:16:51 Weather1 wviewftpd[4515]: <1263176211837> : FTP-RULE:
sending Archive/*.txt
Jan 10 21:16:51 Weather1 wviewftpd[4515]: <1263176211838> : FTP-
COMMAND: /usr/bin/tnftp -iV -u ftp://xxxxxx...@whiteoakhillweather.net16.net/public_html/wview/
Archive/ARC-2010-01-10.txt
Jan 10 21:16:53 Weather1 wviewftpd[4515]: <1263176213117> : FTP-RULE:
sending NOAA/*.txt
Jan 10 21:16:53 Weather1 wviewftpd[4515]: <1263176213118> : FTP-
COMMAND: /usr/bin/tnftp -iV -u ftp://xxxxxx...@whiteoakhillweather.net16.net/public_html/wview/
NOAA/NOAA-2009-12.txt NOAA/NOAA-2009.txt NOAA/NOAA-2010-01.txt NOAA/
NOAA-2010.txt
Jan 10 21:16:55 Weather1 wviewftpd[4515]: <1263176215255> : FTP-DONE:
sent 66 files
Jan 10 21:16:55 Weather1 wviewftpd[4515]: <1263176215256> : FTP: 6
rules processed
Jan 10 21:17:01 Weather1 wpa_supplicant[950]: CTRL-EVENT-SCAN-RESULTS
Jan 10 21:17:01 Weather1 CRON[4578]: (root) CMD ( cd / && run-parts
--report /etc/cron.hourly)
Jan 10 21:17:10 Weather1 htmlgend[4501]: <1263176230334> : Generated:
83 ms: 17 images, 14 template files
Jan 10 21:17:15 Weather1 wviewftpd[4515]: <1263176235250> : FTP: 0
rules processed
Jan 10 21:18:10 Weather1 htmlgend[4501]: <1263176290320> : Generated:
70 ms: 17 images, 14 template files
Jan 10 21:18:15 Weather1 wviewftpd[4515]: <1263176295251> : FTP: 0
rules processed
Jan 10 21:19:01 Weather1 wpa_supplicant[950]: CTRL-EVENT-SCAN-RESULTS
Jan 10 21:19:10 Weather1 htmlgend[4501]: <1263176350321> : Generated:
71 ms: 17 images, 14 template files
Jan 10 21:19:15 Weather1 wviewftpd[4515]: <1263176355251> : FTP: 0
rules processed
Jan 10 21:20:02 Weather1 CRON[4608]: (smmsp) CMD (test -x /etc/init.d/
sendmail && /usr/share/sendmail/sendmail cron-msp)
Jan 10 21:20:03 Weather1 sm-msp-queue[4624]: My unqualified host name
(Weather1) unknown; sleeping for retry
Jan 10 21:20:10 Weather1 htmlgend[4501]: <1263176410322> : Generated:
72 ms: 17 images, 14 template files
Jan 10 21:20:15 Weather1 wviewftpd[4515]: <1263176415250> : FTP: 0
rules processed

[stinkiest]

sorry forgot to note that for some reason wviewftpd runs every minute
on the 15 second mark, ie FTP: 0
> rules processed

On Jan 10, 9:24 pm, stinkiest <stinkiestb...@yahoo.com> wrote:
> i'm not sure what to do other than posting this crap from syslog.
>
> this is immediately after a restart
>
> Jan 10 21:15:10 Weather1 htmlgend[4501]: <1263176110323> : Generated:
> 69 ms: 17 images, 14 template files
> Jan 10 21:16:10 Weather1 htmlgend[4501]: <1263176170344> : Generated:
> 93 ms: 17 images, 14 template files
> Jan 10 21:16:15 Weather1 wviewftpd[4515]: <1263176175250> : FTP-RULE:
> sending *.png
> Jan 10 21:16:15 Weather1 wviewftpd[4515]: <1263176175308> : FTP-

> COMMAND: /usr/bin/tnftp -iV -u ftp://xxxx...@whiteoakhillweather.net16.net/public_html/wview/

> ./barom.png ./baromday.png ./barommonth.png ./baromweek.png ./
> baromyear.png ./dayrain.png ./dew.png ./dewyear.png ./
> heatchillcomp.png ./heatchillmonthcomp.png ./heatchillweekcomp.png ./
> hindex.png ./hindexyear.png ./hiwspeedday.png ./hiwspeedmonth.png ./
> hiwspeedweek.png ./hiwspeedyear.png ./humid.png ./humidday.png ./
> humiddial.png ./humidmonth.png ./
> Jan 10 21:16:15 Weather1 wviewftpd[4515]: <1263176175308> : FTP-
> COMMAND: umidweek.png ./humidyear.png ./monthrain.png ./
> netRainDay.png
> Jan 10 21:16:23 Weather1 wviewftpd[4515]: <1263176183497> : FTP-

> COMMAND: /usr/bin/tnftp -iV -u ftp://xxxxxx...@whiteoakhillweather.net16.net/public_html/wview/

> ./netRainMonth.png ./netRainYear.png ./rainday.png ./rainmonth.png ./
> rainrate.png ./rainweek.png ./rainyear.png ./stormrain.png ./
> temp.png ./tempdaycomp.png ./tempdial.png ./tempmonthcomp.png ./
> tempweekcomp.png ./tempyear.png ./wchill.png ./wchillyear.png ./
> wdirday.png ./wdirmonth.png ./wdirweek.png ./wdiryear.png ./wind.png ./
> wspeedday.png ./wspeed
> Jan 10 21:16:23 Weather1 wviewftpd[4515]: <1263176183497> : FTP-
> COMMAND: onth.png ./wspeedweek.png ./wspeedyear.png ./yearrain.png
> Jan 10 21:16:41 Weather1 wviewftpd[4515]: <1263176201412> : FTP-RULE:
> sending *.htm
> Jan 10 21:16:41 Weather1 wviewftpd[4515]: <1263176201412> : FTP-

> COMMAND: /usr/bin/tnftp -iV -u ftp://xxxxxxxx...@whiteoakhillweather.net16.net/public_html/wview/

> ./Current.htm ./Daily.htm ./Monthly.htm ./Weekly.htm ./Yearly.htm ./
> almanac.htm ./index-day.htm ./parameterlist.htm
> Jan 10 21:16:46 Weather1 wviewftpd[4515]: <1263176206466> : FTP-RULE:
> sending *.html
> Jan 10 21:16:46 Weather1 wviewftpd[4515]: <1263176206466> : FTP-

> COMMAND: /usr/bin/tnftp -iV -u ftp://xxxxxxxxx...@whiteoakhillweather.net16.net/public_html/wview/

> ./index.html
> Jan 10 21:16:50 Weather1 wviewftpd[4515]: <1263176210118> : FTP-RULE:
> sending *.xml
> Jan 10 21:16:50 Weather1 wviewftpd[4515]: <1263176210118> : FTP-

> COMMAND: /usr/bin/tnftp -iV -u ftp://xxxxxxxxxx...@whiteoakhillweather.net16.net/public_html/wview/

> ./wxrss.xml
> Jan 10 21:16:51 Weather1 wviewftpd[4515]: <1263176211837> : FTP-RULE:
> sending Archive/*.txt
> Jan 10 21:16:51 Weather1 wviewftpd[4515]: <1263176211838> : FTP-

> COMMAND: /usr/bin/tnftp -iV -u ftp://xxxxxxxxx...@whiteoakhillweather.net16.net/public_html/wview/

> Archive/ARC-2010-01-10.txt
> Jan 10 21:16:53 Weather1 wviewftpd[4515]: <1263176213117> : FTP-RULE:
> sending NOAA/*.txt
> Jan 10 21:16:53 Weather1 wviewftpd[4515]: <1263176213118> : FTP-

> COMMAND: /usr/bin/tnftp -iV -u ftp://xxxxxxxxxx...@whiteoakhillweather.net16.net/public_html/wview/

[Graham Eddy]

meaningless until you can show us the ftp rules in your config

---

Graham Eddy

[TN_Yankee]

Although it was 3 hours after ftp stopped sending files, I was able to
ftp into my remote ISP account by command line without any hickups.

I just stopped wview, & during the down time I unchecked a couple of
the verbose logging options, including wvalarmd (since I don't have
any alarms set anyway). A few minutes after starting, I got this
message:

Jan 10 21:57:54 comet wviewftpd[4917]: <1263178674308> : FTP-COMMAND: /
usr/bin/tnftp -iV -u ftp://karnsweather:xxx...@home.comcast.net/ NOAA/
NOAA-2009.txt NOAA/NOAA-2010-01.txt NOAA/NOAA-2010.txt
Jan 10 21:57:56 comet wviewftpd[4917]: <1263178676027> : FTP-DONE:
sent 161 files
Jan 10 21:57:56 comet wviewftpd[4917]: <1263178676027> : FTP: 6 rules
processed
Jan 10 21:57:56 comet wviewftpd[4917]: <1263178676027> : FTP: 0 rules
processed
Jan 10 21:58:15 comet wviewftpd[4917]: <1263178695323> : FTP: 0 rules
processed
Jan 10 21:58:35 comet wvpmond[4925]: <1263178715895> :
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jan 10 21:58:35 comet wvpmond[4925]: <1263178715895> : PMON >>>> /usr/
bin/wvalarmd did not respond to poll!
Jan 10 21:58:35 comet wvpmond[4925]: <1263178715895> : PMON >>>>
OLDPID: 4907
Jan 10 21:58:35 comet wvpmond[4925]: <1263178715895> : PMON >>>>
SIGTERM: /usr/bin/wvalarmd
Jan 10 21:58:35 comet wvpmond[4925]: <1263178715895> : PMON >>>>
waiting for /usr/bin/wvalarmd to exit
Jan 10 21:58:37 comet wvpmond[4925]: <1263178717896> : PMON >>>>
starting: /usr/bin/wvalarmd
Jan 10 21:58:37 comet wvalarmd[4965]: <1263178717997> : radlib:
wvalarmd started as a daemon ...
Jan 10 21:58:38 comet wvalarmd[4965]: <1263178718010> : ALARM daemon
not enabled - exiting...
Jan 10 21:58:39 comet wvpmond[4925]: <1263178719899> : PMON: failed to
OPEN /var/lib/wview/wvalarmd.pid!
Jan 10 21:58:39 comet wvpmond[4925]: <1263178719919> : PMON >>>>
GETPID /usr/bin/wvalarmd failed: No such file or directory
Jan 10 21:58:39 comet wvpmond[4925]: <1263178719919> : PMON >>>>
Process Monitor shutting down:
Jan 10 21:58:39 comet wvpmond[4925]: <1263178719919> : PMON >>>>
Please report this incident to wview Forums
Jan 10 21:58:39 comet wvpmond[4925]: <1263178719919> : radProcessWait:
exit flag is set!
Jan 10 21:58:39 comet wvpmond[4925]: <1263178719919> : exiting
normally...
Jan 10 21:59:01 comet wviewd[4898]: <1263178741060> : vproRunState:
LOOP WAKEUP failed
Jan 10 21:59:10 comet htmlgend[4903]: <1263178750440> : Generated: 190
ms: 20 images, 14 template files

I'm guessing this is not related at all to ftp issues, but thought it
should be reported nevertheless. As I mentioned above, I have no
alarms set, and have not touched any setting on the wviewmanagement
alarms page.

wview is still running, including ftp.

mike

[Graham Eddy]

sounds like wvalarmd is enabled - perhaps when wviewconfig was first run and set up wviewmgmt.
if you don't want wvalarmd, use wviewmgmt (or wviewconfig) to disable it

re wvalarmd errors, i have been getting these, though not lately - i had done quite a a big of diagnosis but still working on it when the errors stopped (i had been fixing other system-related problems at same time). my theory is that wvalarmd got locked up (waiting on something that never wakes it) and that lockup stopped it from responding to pmon's poke, so pmon killed wvalarmd and restarted it, only for the lockup to cycle over & over. i didn't get to the point of determining a workaround. all i can suggest is a reboot, presuming it is something ephemeral outside the processes (e.g. shmem) causing it

it is not ftp related - unless there is a common underlying problem with ephemeral data

---

Graham Eddy

[Mark S. Teel]

I've explained it already, maybe read my posts ...

[TN_Yankee]

Per wviewmanagement, wvalarmd is not enabled. Wview is still running
along, including ftp, so I'll just keep an eye on it.

I've also been having NOAA monthly report generation issues, but those
have been minor compared to my ftp experiences lately.

mike

[TN_Yankee]

Whoops - while wvalarmd wasn't enabled, process monitoring for it
was. I've now disabled it, too.

On Jan 11, 7:04 am, TN_Yankee <kw...@comcast.net> wrote:
> Per wviewmanagement, wvalarmd is not enabled.  Wview is still running
> along, including ftp, so I'll just keep an eye on it.

mike

[Tagman9]

OK.. Something a bit different this morning.. I noticed that
wviewd_vpro is consuming 100% CPU..

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
21492 root 20 0 16044 4380 1232 R 100 0.4 86:05.70
wviewd_vpro

I do have verbose logging turned on for wviewd and see these errors
in the tail of the log..

Jan 11 05:45:04 server wviewd[21492]: <1263206704940> : storing record
for 2010-01-11 05:45
Jan 11 05:49:04 server wviewd[21492]: <1263206944632> : wakeupConsole:
Write ERROR!
Jan 11 05:49:07 server wviewd[21492]: <1263206947133> : wakeupConsole:
Write ERROR!
Jan 11 05:49:09 server wviewd[21492]: <1263206949633> : wakeupConsole:
Write ERROR!
Jan 11 05:49:12 server wviewd[21492]: <1263206952133> : wakeupConsole:
Write ERROR!
Jan 11 05:49:14 server wviewd[21492]: <1263206954633> : wakeupConsole:
Write ERROR!
Jan 11 05:49:17 server wviewd[21492]: <1263206957133> : wakeupConsole:
Write ERROR!
Jan 11 05:49:17 server wviewd[21492]: <1263206957133> :
wviewd:vproErrorState: received stimulus 5

it's currently 7:21AM and there are no wviewd or wvhttpd log messages
after the last one here.

When I restart I get:

root@server:~# /etc/init.d/wview start
Starting wview daemons:
htmlgend[29636]: <1263213101437> : system init failed!
wvalarmd[29637]: <1263213101441> : wviewd process is not running -
aborting!
wvcwopd[29638]: <1263213101445> : wviewd process not running -
aborting!
wvhttpd[29639]: <1263213101455> : wviewd process no running -
aborting!
wviewftpd[29640]: <1263213101460> : wview daemon lock file /var/lib/
wview/wviewd.pid does not exist - aborting!
wviewsshd[29641]: <1263213101465> : wviewd process not running -
aborting!
wvpmond[29642]: <1263213101469> : wviewd process not running -
aborting!

Looks list at 5:48 something reset my USB...?!?! That's Odd?

Jan 11 05:48:57 server kernel: [145476.472127] usb 2-2: USB
disconnect, address 3
Jan 11 05:48:57 server kernel: [145476.472409] cp210x ttyUSB0: cp210x
converter now disconnected from ttyUSB0
Jan 11 05:48:57 server kernel: [145476.472449] cp210x 2-2:1.0: device
disconnected
Jan 11 05:48:57 server kernel: [145476.712527] usb 2-2: new full speed
USB device using uhci_hcd and address 4
Jan 11 05:48:57 server kernel: [145476.880751] usb 2-2: configuration
#1 chosen from 1 choice
Jan 11 05:48:57 server kernel: [145476.887673] cp210x 2-2:1.0: cp210x
converter detected
Jan 11 05:48:57 server kernel: [145477.000053] usb 2-2: reset full
speed USB device using uhci_hcd and address 4
Jan 11 05:48:57 server kernel: [145477.147765] usb 2-2: cp210x
converter now attached to ttyUSB1

Any Ideas? Looks like the cp210x reconnected, after the reset, but
how come wviewd didn't see it?

Rebooting the server, wviewd started normally and had no problems
connecting to the cp210x..

Any help would be greatly appreciated. Thanks!! - Ed

[Mark S. Teel]

Your USB-serial driver reset and came back as ttyUSB1. There is another
thread on Google concerning "ttyUSB0 vs. ttyUSB1" you should read for
solutions.

Obviously, if you are having communication problems with the station,
FTP, CWOP, HTML generation, etc. will not be working properly.

[Tagman9]

Good Catch!! Thanks Mark, I didn't notice that.

[Tagman9]

Since I'm runnining ubuntu 9.10, I've referenced by /dev/serial/by-
id/...

It loaded fine:

Jan 11 09:02:26 server wviewd[4572]: <1263218546635> : Vantage Pro on /
dev/serial/by-id/usb-
Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0
opened ...

I tested by disconnecting the usb port and reconnecting..

Jan 11 09:12:29 server kernel: [ 2399.320344] cp210x ttyUSB0: cp210x

converter now disconnected from ttyUSB0

Jan 11 09:12:34 server kernel: [ 2403.711450] usb 2-2: cp210x

converter now attached to ttyUSB1

The symbolic link now points to ttyUSB1

lrwxrwxrwx 1 root root 13 2010-01-11 09:12 usb-
Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0 -
> ../../ttyUSB1

However, I'm still getting the following error...and wviewd_vpro is
consuming 100% cpu...

Jan 11 09:12:37 server wviewd[4572]: <1263219157307> : wakeupConsole:
Write ERROR!
Jan 11 09:12:39 server wviewd[4572]: <1263219159807> : wakeupConsole:
Write ERROR!
Jan 11 09:12:42 server wviewd[4572]: <1263219162307> : wakeupConsole:
Write ERROR!
Jan 11 09:12:44 server wviewd[4572]: <1263219164808> : wakeupConsole:
Write ERROR!
Jan 11 09:12:47 server wviewd[4572]: <1263219167308> : wakeupConsole:
Write ERROR!
Jan 11 09:12:49 server wviewd[4572]: <1263219169808> : wakeupConsole:
Write ERROR!
Jan 11 09:12:49 server wviewd[4572]: <1263219169808> :

wviewd:vproErrorState: received stimulus 5

Did I miss something?? This time, I can restart wview without issue,
I'm just concerned if my USB resets as it did this morning and having
to manually restart wviewd.

Thanks!- Ed

[explorer900]

Thank you very much, Mark, for your quick responding and providing a
solution for our ftp issue! I appreciate such a quich reaction very
much! The ftp stuff is working much better and more transparent now.
The only thing is - as already reported by other users - that the ftp
transfer is still quitting after some hours of work, while the other
processes are continueing normally. Unfortunately that happened, when
I (after a successfull try with verbose logging on - 000010011)
switched the verbose logging off and restarted wview. So I will
investigate that in the next days to collect some more informations.

Thanks again
Stefan