From: "Serkan SUBASI" <ssubasi@turk.net> Subject: RE: [RadiusNT] RadiusNT v4 ERROR "dumpUsers: could not open c:\radius\cache/users for write." Date: Fri, 1 Nov 2002 13:52:24 +0200 Message-ID: <30F4F3CF4541AD40BAC8D48060B0F006032485@exchange.satelko.com>
I checked, but found that the disk was not full at that time
also just today same errors happened, and I checked the c:\radius\cache
directory, output follows
(today we run radiusnt v4.0.31)
***********
Nov 01 10:47:57 2002 [INFO]: SQL Statement: {CALL RadGetConfigs(44)}
Nov 01 10:47:57 2002 [INFO]: SQL Statement: {CALL RadGetConfigs(7)}
flOpen fail on c:\radius\cache/AccountTypes [No error]
flOpen fail on c:\radius\cache/DNIS [No error]
flOpen fail on c:\radius\cache/RadRejects [No error]
flOpen fail on c:\radius\cache/RoamServers [No error]
flOpen fail on c:\radius\cache/ServerAccess [No error]
flOpen fail on c:\radius\cache/proxyattributes [No error]
dumpUsers: could not open c:\radius\cache/users for write.
flOpen fail on c:\radius\cache/AccountTypes [No error]
flOpen fail on c:\radius\cache/DNIS [No error]
flOpen fail on c:\radius\cache/RadRejects [No error]
flOpen fail on c:\radius\cache/RoamServers [No error]
flOpen fail on c:\radius\cache/ServerAccess [No error]
flOpen fail on c:\radius\cache/proxyattributes [No error]
dumpUsers: could not open c:\radius\cache/users for write.
*************
Volume in drive C has no label.
Volume Serial Number is B03C-11BE
Directory of C:\radius\cache
28.11.2000 22:35 <DIR> .
28.11.2000 22:35 <DIR> ..
01.11.2002 11:32 286 acctlog.bak
01.11.2002 11:32 0 acctlog
08.10.2002 17:13 0 Calls_fields
08.10.2002 17:13 0 RadLogs_fields
08.10.2002 17:13 0 ServerPorts_fields
01.11.2002 04:09 6,454 AccountTypes
01.11.2002 04:09 37 RadRejects
01.11.2002 04:09 416 RoamServers
01.11.2002 04:09 2,320 ServerAccess
01.11.2002 12:24 0 cachedir.txt
08.10.2002 17:14 0 proxyattributes.bak
01.11.2002 04:09 0 proxyattributes
01.11.2002 04:09 2,992 DNIS
13 File(s) 12,505 bytes
2 Dir(s) 2,092,113,920 bytes free
pls. look carefully the file dates, and nobody access these files except
radiusnt
Serkan SUBASI
-----Original Message-----
From: Serkan Subaşı
Sent: 31 Ekim 2002 Perşembe 23:13
To: radiusnt@iea-software.com
Subject: RE: [RadiusNT] RadiusNT v4 ERROR "dumpUsers: could not open
c:\radius\cache/users for write."
c:\radius\cache directory exists, and the app have permissions to it,
but maybe the disk was full at the time these error logged, sorry if it
was.
:)
I am searching on this matter, because our system operators periodically
check some event logs, special application logs and cleans them,
BTW, can these types of critical errors be logged to another log file ?
and can radiusnt send an snmp trap for these ?
Serkan SUBASI
-----Original Message-----
From: Dale E. Reed Jr. [mailto:daler@iea-software.com]
Sent: Thu 2002-10-31 19:57
To: radiusnt@iea-software.com
Cc:
Subject: RE: [RadiusNT] RadiusNT v4 ERROR "dumpUsers: could not open
c:\radius\cache/users for write."
> -------------
> dumpUsers: could not open c:\radius\cache/users for write.
> flOpen fail on c:\radius\cache/AccountTypes [No error]
> flOpen fail on c:\radius\cache/DNIS [No error]
> flOpen fail on c:\radius\cache/RadRejects [No error]
> flOpen fail on c:\radius\cache/RoamServers [No error]
> flOpen fail on c:\radius\cache/ServerAccess [No error]
> flOpen fail on c:\radius\cache/proxyattributes [No error]
> dumpUsers: could not open c:\radius\cache/users for write.
> -------------
Does the c:\radius\cache directory exist and the app have permissions
to it? This is the disk cache trying to update/create those files.
Dale