A problem with WD just popped up

[Weather Display]

do you have passive mode set?

[TokKiwi]

Excerpt from his ftplogfull.txt:

TYPE I
200 Type set to I.
Checking for next FTP agenda....
there are 1 more things to do
Doing ftp upload
Checking there are files to upload
There are more files to upload
PASV
227 Entering Passive Mode (72,167,183,86,12,3).
STOR Default.html
125 Data connection already open; Transfer starting.
226 Transfer complete.
PASV
227 Entering Passive Mode (72,167,183,86,12,4).
STOR Defaultgraph.gif
125 Data connection already open; Transfer starting.
426 Connection closed; transfer aborted.
141: 426 Connection closed; transfer aborted.
PASV

From previous page.  It seems it is a problem with his host.

[Weather Display]

I would say it is a problem with the host
(even though they say it is not....if you search this forum, every single time, it has turned out to be a problem with the host
(e.g changing hosts and the problem is fixed)
but though try increasing the FTP time out maybe

[TokKiwi]

Unless it is a problem with packet closure and comms protocols and a timing issue... flags not received back or something? Not sure how the FTP all works.

[Terry]

OK, I found a possible solution to the FTP problems, I shut down WD and re-started it as a remote application (From one of the networked PC's) things seem to be running right, there has been no lock ups of the FTP uploads or data dropouts in the past few days.

It could be that WD doesn't like to be run as a main application on the server, running it as a remote application seems to make the FTP upload happy. (for now)

At least I can re-set WD from the remote location as it's much easier to get to that PC and re-start WD, hopefully WD will be happy and wont shut down at the 200 hour mark, time will tell.


Terry

[Terry]

OK back at this after some quick fun over the new years.( I hope everyone had a great start to their New Year)


The FTP upload problem is gone, I don't know what is involved with running WD as a remote program, nor what happened to cause the problem in the first place, as it ran fine for 5 years like that before this popped up, but the FTP problem has gone away.

However the 200 hour program lockup problem still remains, but is not that big a deal, as I don't have to go to the server to re-set WD, as running it via a remote connection to the server, I can reset it from home.

I would like to fix it, as resetting the program should not be needed.

Any thoughts?

[Weather Display]

not sure why you have that problem
I am no seeing that here
any others have that particular problem?

[jbrooks987]

I do have an issue with WD hanging every few days.  Although I've not counted the hours, 200 would be about right.  The fix (for me at least) is easy.  I have WD set to restart itself twice a week (control panel/ftp-internet setup/remote control-reboot.  I picked a time, picked two days, checked the option to restart WD instead of reboot, and I go happily about my business without a worry.

Brian, for what its worth, the problem started for me when you switched compilers.  I'm running WD on a dell with 4 gig ram, and windows vista home. Don't know why it happens - and really haven't worried about it because the above settings make it a "no issue" for me.

For that matter, if I keep upgrading to the latest build the program needs to be shut down anyway

Like I said - not an issue!

[Weather Display]

humm, maybe that particular problem is just with Ultimeter 2000 users in complete record mode?

[jbrooks987]

That could be - although to be honest I don't remember what mode mine is set to.   I think you said at the time that the new compiler was missing something that prevented you from compiling that routine.  But, anyway - to me it's a moot point.  It's a method that works for me and I seriously doubt that I've missed any records by missing two data points each week.

[Terry]

I do have an issue with WD hanging every few days.  Although I've not counted the hours, 200 would be about right.  The fix (for me at least) is easy.  I have WD set to restart itself twice a week (control panel/ftp-internet setup/remote control-reboot.  I picked a time, picked two days, checked the option to restart WD instead of reboot, and I go happily about my business without a worry.

Brian, for what its worth, the problem started for me when you switched compilers.  I'm running WD on a dell with 4 gig ram, and windows vista home. Don't know why it happens - and really haven't worried about it because the above settings make it a "no issue" for me.

For that matter, if I keep upgrading to the latest build the program needs to be shut down anyway

Like I said - not an issue!

Ahhhh Haaaa, so I'm not crazy, and not alone.


Well it's about 8.3 days between lockups, (200 hours) the funny thing was when I switched from 10 minutes to 15 minutes FTP updates the lockup time was shorter, you would think it would get longer, but it went from 200 hrs to 120 hrs.....????..... Strange.....

Maybe why some don't see this is because they have a shorter FTP upload time, mine is set to do an FTP upload and data refresh every ten minutes, maybe with a shorter update time (less then ten) this problem does not pop up? 


Jbrooks987, when you do the auto reset/reboot it doesn't affect the computer at all?
That is it doesn't re-boot the computer but only the WD program?

[jbrooks987]

No, it doesn't affect the computer at all IF you check the box beside the line "just restart weather display instead of rebooting windows".  That check box is just below the 7 check boxes for days.  With that option checked, WD shuts down, then restarts itself.  On my PC that may take 30 to 60 seconds total from shutdown to restarted and running.  Just make sure that you have chosen a time, clicked the right arrow to put the time in the box, put a check in the box by the day (or days) that you wish wd to restart, make sure the "reboot" button shows green and again, make sure there is a check beside the box "just restart weather display..."

I've also chosen a time that is at least a minute away from the times that wd sends the files to my web site. 

[Terry]

OK thanks for the info, I will try it out.

[Terry]

OK Jbrooks987, it look's like your little trick did the job, I have it set to update every 15 min, and re-boot just the WD program every 7 days at 11:00 PM.

The program has not locked up in the last 2 weeks, so it's running fine.

However this is just a work around, the problem sill lies at that 200 hr mark, resetting it at the 168 hr mark skips around the problem.

But it's working, I won't complain.


Thanks for the info Jbrooks987.