db2dasdiag.log is filling up the filesystem

[rajdb2]

Hi, the db2dasdiag.log is filling up the filesystem completely. there
are entries being written every second in the db2dasdiag.log. The
entries are:

2005-08-16-12.13.40.241392 pid:215566 tid:1 level:2
DB2 tools - DB2 administration server - db2dasSearchDscvInit() probe:30
data #1 (4 bytes)
13

2005-08-16-12.13.40.241596 pid:215566 tid:1 level:2
DB2 tools - DB2 administration server - dasRootInit() probe:60
data #1 (4 bytes)
-1

2005-08-16-12.13.40.241670 pid:215566 tid:1 level:2
DB2 tools - DB2 administration server - rrm_main() probe:80
data #1 (4 bytes)
-3020

2005-08-16-12.13.40.335218 pid:221324 tid:1 level:2
Common - Generic Control Facility - gcf_start() probe:10
data #1 (4 bytes)
4407

2005-08-16-12.13.40.335363 pid:221324 tid:1 level:2
Common - Fault Monitor Facility - main() probe:110
called fmMainLogic()
return code 0x9000034E Failed to start the GCF service module
impact 0x900003A0 Failed to run the main logic of the fault monitor

2005-08-16-12.13.42.005620 pid:88936 tid:1 level:2
Common - Fault Monitor Facility - fmEmailNotify() probe:50
impact 0x90000371 The fault monitor daemon failed to send an e-mail
notification
data #1 (4 bytes)
-22295
data #2 (108 bytes)
db2fmd
The state of instance 'udbdas01' gcf module
'/udb/home/udbdas01/das/lib/libdb2dasgcf.a' is OPERABLE.
2005-08-16-12.13.42.005693 pid:88936 tid:1 level:2
Common - Fault Monitor Facility - fmMainLogic() probe:130
called fmEmailNotify()
return code 0x90000371 The fault monitor daemon failed to send an
e-mail notification
impact 0x90000371 The fault monitor daemon failed to send an e-mail
notification

I have deleted the db2dasdiag.log and created a new one, but at the
rate it is getting updated it will fill up the filesystem again
completely in 2 days. I need help on this issue.

thanks
raj