Re: unable to update due to write failure

John Mee <[email protected]>
Newsgroups gmane.comp.security.nessus.general
Message-ID <[email protected]>
>Message: 3
>Date: Mon, 28 Jul 2008 12:55:19 -0400
>From: Ron Gula <[email protected]>
>Subject: Re: unable to update due to write failure
>To: [email protected]
>Message-ID: <[email protected]>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>John Mee wrote:
>> On two of my machines, I am unable to complete updates and I get a message (~ unable to write file, update failed). I have tried checking to ensure that write protection isn't set and the user id is a member of the domain admin group. What am I doing wrong?
>> 
>
>I've not seen that error and would check the basics
>such as disk space usage.
>
>If it is a permissions problem, you should look for
>any changes that have occurred. Are you running the
>update as a different user, have there been any
>changes to your directory permissions, .etc, .etc
>
>Ron Gula
>Tenable Network Security

Actually, it turns out to be three machines:
1) All are putting it out Drive D
2) Two are FAT32 (one XP and one Win2k), one is NTFS (the other XP)
3) Two are XP professional, one is Win2k workstation
4) all have several (>3 gigabytes) of free space.
5) update is always run from an domain admin account
6) all directories have had permissions reset to clear any possible permissions issues.
7) When I tried to copy it to the FAT 32 drive, the copy died after 20,000 or so scripts (out of a total of 23,000 +/- scripts), but did not die on the NTFS partition, leading me to believe that the file counts may be an issue
8) When I performed the same operation on my XP/NTFS system, update was able to go successfully the first time.  The second time I tried to update, I got a message "Empty URL" 

_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.