WD Crashes Ver 10.16u, followed by failure of watchdog

Archive Archived Weather Display Problems
1

I have no idea what caused the crash, I was sleeping :slight_smile: The crashes are below. WD is running again now, after I ended all the attempted recovery tasks spawned by the watchdogs.

The watchdog did not really work very well. I ended up with 16 watchdogs running, 5 wdmysql’s and 5 WeatherDisplays. I have these suggestions:

WDisplay should check if a watch dog is already running before starting a new one. The watch dog itself should not allow multiple instances of itself to run. The same applies to wdmysql.exe. And finally if WD is starting and another instance is already running, then just end one of them automatically - there is not point in having multiple intances of WD displaying a window saying that another instance is running (because the watchdogs keep starting new ones). Just abort the new instance or kill the old instance.

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 9/9/2004
Time: 12:43:19 AM
User: N/A
Computer: WBOT
Description:
Faulting application weatherd.exe, version 10.15.5.0, faulting module kernel32.dll, version 5.1.2600.2180, fault address 0x0001eb33.

For more information, see Help and Support Center at Microsoft Support.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 77 65 61 ure wea
0018: 74 68 65 72 64 2e 65 78 therd.ex
0020: 65 20 31 30 2e 31 35 2e e 10.15.
0028: 35 2e 30 20 69 6e 20 6b 5.0 in k
0030: 65 72 6e 65 6c 33 32 2e ernel32.
0038: 64 6c 6c 20 35 2e 31 2e dll 5.1.
0040: 32 36 30 30 2e 32 31 38 2600.218
0048: 30 20 61 74 20 6f 66 66 0 at off
0050: 73 65 74 20 30 30 30 31 set 0001
0058: 65 62 33 33 0d 0a eb33…

And again

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 9/9/2004
Time: 4:37:53 PM
User: N/A
Computer: WBOT
Description:
Faulting application weatherd.exe, version 10.15.5.0, faulting module kernel32.dll, version 5.1.2600.2180, fault address 0x0001eb33.

For more information, see Help and Support Center at Microsoft Support.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 77 65 61 ure wea
0018: 74 68 65 72 64 2e 65 78 therd.ex
0020: 65 20 31 30 2e 31 35 2e e 10.15.
0028: 35 2e 30 20 69 6e 20 6b 5.0 in k
0030: 65 72 6e 65 6c 33 32 2e ernel32.
0038: 64 6c 6c 20 35 2e 31 2e dll 5.1.
0040: 32 36 30 30 2e 32 31 38 2600.218
0048: 30 20 61 74 20 6f 66 66 0 at off
0050: 73 65 74 20 30 30 30 31 set 0001
0058: 65 62 33 33 0d 0a eb33…

And again
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 9/9/2004
Time: 4:38:57 PM
User: N/A
Computer: WBOT
Description:
Faulting application weatherd.exe, version 10.15.5.0, faulting module kernel32.dll, version 5.1.2600.2180, fault address 0x0001eb33.

For more information, see Help and Support Center at Microsoft Support.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 77 65 61 ure wea
0018: 74 68 65 72 64 2e 65 78 therd.ex
0020: 65 20 31 30 2e 31 35 2e e 10.15.
0028: 35 2e 30 20 69 6e 20 6b 5.0 in k
0030: 65 72 6e 65 6c 33 32 2e ernel32.
0038: 64 6c 6c 20 35 2e 31 2e dll 5.1.
0040: 32 36 30 30 2e 32 31 38 2600.218
0048: 30 20 61 74 20 6f 66 66 0 at off
0050: 73 65 74 20 30 30 30 31 set 0001
0058: 65 62 33 33 0d 0a eb33…

And again
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 9/9/2004
Time: 4:39:04 PM
User: N/A
Computer: WBOT
Description:
Faulting application weatherd.exe, version 10.15.5.0, faulting module kernel32.dll, version 5.1.2600.2180, fault address 0x0001eb33.

For more information, see Help and Support Center at Microsoft Support.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 77 65 61 ure wea
0018: 74 68 65 72 64 2e 65 78 therd.ex
0020: 65 20 31 30 2e 31 35 2e e 10.15.
0028: 35 2e 30 20 69 6e 20 6b 5.0 in k
0030: 65 72 6e 65 6c 33 32 2e ernel32.
0038: 64 6c 6c 20 35 2e 31 2e dll 5.1.
0040: 32 36 30 30 2e 32 31 38 2600.218
0048: 30 20 61 74 20 6f 66 66 0 at off
0050: 73 65 74 20 30 30 30 31 set 0001
0058: 65 62 33 33 0d 0a eb33…

2

good ideas
i will see what i can do (now that I have method of knowing what processes are running)
all that crash info is of no use to me
but, anything in the file programerrorlog.txt
(best if before you restart wd)

3

Resetting rain daily value , day: 1
Resetting wind/temperature daily value , day: 1
Resetting rain daily value , day: 2
Resetting wind/temperature daily value , day: 2
Resetting rain daily value , day: 3
Resetting wind/temperature daily value , day: 3
Resetting rain daily value , day: 4
Resetting wind/temperature daily value , day: 4
Resetting rain daily value , day: 5
Resetting wind/temperature daily value , day: 5
Resetting rain daily value , day: 6
Resetting wind/temperature daily value , day: 6
Resetting rain daily value , day: 7
Resetting wind/temperature daily value , day: 7
Resetting rain daily value , day: 8
Resetting wind/temperature daily value , day: 8
ERROR: Cannot create file c:\wdisplay\webfiles\realtimegraph2.gif at time/date 2:50:45 PM 08/09/04
Cannot create file c:\wdisplay\webfiles\curr72hourgraph.gif
ERROR: Cannot create file c:\wdisplay\webfiles\index.gif at time/date 9:20:42 PM 08/09/04
Cannot create file c:\wdisplay\webfiles\curr24hourgraph.gif
Resetting rain daily value , day: 9
Resetting wind/temperature daily value , day: 9
ERROR: I/O error 32 at time/date 12:43:01 AM 9/9/2004
ERROR: I/O error 32 at time/date 4:37:30 PM 9/9/2004
ERROR: I/O error 32 at time/date 4:38:34 PM 9/9/2004
ERROR: I/O error 32 at time/date 4:38:45 PM 9/9/2004

4

note the programerrorlog keeps getting appended to now
(you can clear it)

I/O error:
maybe a file is locked/in use by another program, such as a virus checker, etc

5

No virus checkers on this machine. No other sofwtare running except Apache and Mysql. Did anything special to get WD running again, other than ending all the WD/wdmysql/watchdog processes and manually starting WD.

Perhaps you could look at a tool like http://www.eurekalog.com/faq.php, whch would modify your delphi executable to include detailed information when an unhandled exception occurs - I think it would help you figure out these crashes much more quickly.

/Ian

6

http://www.eurekalog.com/log.txt shows a sample of what a crash report from Eureka contains.

7

i have seen that add on before…and have though about using it
i will see about trialing it and purchasing it…

8

It is only $24 to $79 seems like a great deal, and has a money back guarantee!

9

just intalled the delphi service pack 1, that was needed, OK
that was a 28mb download…it could never do that before on dial up…hence i could not use the eureka log, which needs the service pack 1 installed!
(and service pack 1 fixes a memory access violation with netmeeting in use on windows 2000…maybe even xp?)

10

good news
purchased it
installed it
will now compile and upload a new version with it in it :slight_smile:

11

hey, and it works great!!!

i forced a floating point error in the code
the euraka log came up with a window, clicked on details, and it gave an error address, which i was able to plug into the compiler,and it jumped straight to that segment of code where the error occured!!!

i will upload this debug version (i can easily remove the debugger)
now :slight_smile:

12

Great news, I hope this proves to be a big help to you.

One thing to remember with this type of tool Brian is that you may have to keep archives of each version of the source code, otherwise you may not be able to use the address in the error log because the executeable no longer matches your latest source code.

I do not know how delphi handles this, but typicically in C you need a map file, and in C# you need the program debug database (symbol map), along with the corresponding exact source code.

If this turns out to be the case with Delphi and Eureka log, then you might want to consider using some version control software e.g. CVS, Clearcase etc.
/Ian

13

i have noticed yes that it will jump to where the error should be in the code,.,but if i have added some more lines of text…it will be out by that many lines of text ( i have already found a i/o error with the noaa download forecast file, and have now put in i/o error trapping (which i use for all other files, but missed that file)
in 10.17d