In a LabVIEW DSC tag engine based SCADA System server computer displays error ' Insufficient disk space for logging system events'

[ACRELab Student]

In a LabVIEW DSC tag engine based SCADA System server computer displays error ' Insufficient disk space for logging system events'. When checked the folder where it is logging events the folder '...data' size is 0 KB. Also the computer hard disk and the netowork drive on which Tag engine files are located has plenty of empty space. All 600 tags event logging is already turned off, system event are kept for only 30 days. The error didn't allow client computer to access log file residing on the same network drive. it seems to be a LabVIEW I/O error. The current question listed on NI Website in various sections doesn't address this particular
issue. Interesting point is that at the same time the system was logging data using a LV program on local hard disk of server computer without any problems. The error was only displayed on the server computer. The server computer is connected to ABV SLC using OPC Lookout server.

Could it be an issue of Labview can only allocate certain portion of space available to it for this event logging purposes.

Any ideas/suggestions are highly appreciated.

[Ben]

I do not have DSC on th is machine but,

I seem to remeber a misc setting that let you specify how much disk space should be available for logging.

I would start poking around in the Tag config screen and look for one one of those engine settings. May be near the queue size setting screen.

That's all I can offer, I'll try to take a look later today if I get a chance.

Ben

[Ben]

Forget that other idea.

Under options >>> performance and disks, there are settings you should check that may help.

Ben

[Roli]

LabVIEW DSC logs the system events into a specific folder specified in the Tag Configuration Editor. If you go in LabVIEW to the menu Tools>Datalogging & Supervisory Control>Options>Advanced (Tab) you'll see the System Log path (default: ) which is the parent path to your SysLog directory. All the sys logs are stored in ASCII-files (.log).
Could you check if this directory's harddrive has enough space?
If not you might delete some old .log files.

Hope this helps
Roland

System Log is not in the same location as the Citadel Alarm/Event data.

[ACRELab Student]

Thanks Roland,
You are right, the Syslog folder size was 3.6 MB, as it had logged events for last 2 years. After deleing the older files i haven't seen the error.
Although the problem seems to be over, i don't understand why the system displyed error in the first place as the drive had 65% free space even before deleting the previous files in syslog folder under Labview. (We are using Labview and DSC module version 6.01). Also just as an observation, during the initial troubleshooting the number of days to keep the event files (under Tag configuration\Configure\Events) for only 1 day but still the system keeps all the files until it is deleted manually in Syslog folder.

But the system is back to normal operation.

Mehul

[Roli]

Mehul,

the error should just come up when your free diskspace is smaller than about 2MB. I guess DSC calls into a Windows function to check the free space on the HD. Maybe this fuctions returs something wrong.

What is your OS? (Win95, 98, 2000, XP?) How big is actually your HD/Partition?

Yes you are right the 'number of days to keep the events' should take affect for the Citadel Alarm&Event data. This does not effect the system .log files. You would need to delete the .log files manually or write a small observer.vi which would delete those files when they are too old.

Let me know, hope this helps
Roland

[ACRELab Student]

Thanks again Roland,
Out OS is NT. There are two partition in the hard disk. Drive C(2 GB) and Drive D(6.5 GB). The C drive of computer has other softwares loaded under the Program Files folder. All the SCADA system related softwares (LaBVIEW, Lookout etc)are loaded on the Program Files folder of D drive. I think your guess is correct about the DSC calling windows function to check the free spcae on the hard disk. The good thing is that whenever the error Dialog was displayed on the computer screen, all the LV programs were running normally and tags were updated with the PLC regularly.

Mehul