FYI, I've run ASSP on various Windows boxes for the last 15+ years. I've
never noticed this happening, not even back in the days of Windows 2000,
I have always run ASSP's service as a separate user though. I don't know
if this info is particularly helpful to you, but figured I'd share. It
securing ASSP with a separate user account has the added benefit of
insuring the log files roll over, great!
On Wed, Nov 22, 2017 at 12:15 PM, Steve Tetley <steve.tet...@xyplan.com>
wrote:
> Dear Scott,
>
>
>
> I have run into this issue before and believe it’s a windows issue rather
> than ASSP.
>
>
>
> I got around it by creating a new local admin account on the server and
> running the ASSP service under this account.
>
>
>
> To be sure, also add Create / write permissions for that user on the top
> level ASSP folder and allow inheritance.
>
>
>
> Regards
>
>
>
> Steve
>
>
>
> *From:* Thomas Eckardt [mailto:thomas.ecka...@thockar.com]
> *Sent:* 20 November 2017 06:48
> *To:* a...@hollsco.com; ASSP development mailing list <
> assp-test@lists.sourceforge.net>
> *Subject:* Re: [Assp-test] Log rollovers
>
>
>
> All logs are only written by the MainThread.
> Make sure,that there is no other process locking the maillog.txt file if
> it is closed by assp. For example, an online filesystem virus scanner
> (defender or any other). Configure exceptions for the assp folder.
>
> Thomas
>
>
>
>
>
> Von: "Scott MacLean" <a...@hollsco.com>
> An: "ASSP Development Mailing List" <assp-test@lists.sourceforge.
> net>
> Datum: 20.11.2017 05:07
> Betreff: [Assp-test] Log rollovers
> ------------------------------
>
>
>
>
> Hi Thomas,
>
> Some time ago, I mentioned to you that periodically my logs did not roll
> over - ASSP would continue writing to the previous day's log and I would
> end up with logs containing two and sometimes three days worth of data.
>
> When this occurred, I would see:
>
> Oct-04-17 00:00:00: Rolling log file -- archive will be saved as
> 'logs/17-10-03.maillog.txt'
> error: unable to rename file D:/ASSP/logs/maillog.txt to
> D:/ASSP/logs/17-10-03.maillog.txt - Permission denied
>
> Oct-02-17 00:00:01: Rolling log file -- archive will be saved as
> 'logs/17-10-01.maillog.txt'
> error: unable to rename file D:/ASSP/logs/maillog.txt to
> D:/ASSP/logs/17-10-01.maillog.txt - Permission denied
>
> Nov-08-17 00:00:00: Rolling log file -- archive will be saved as
> 'logs/17-11-07.maillog.txt'
> error: unable to rename file D:/ASSP/logs/maillog.txt to
> D:/ASSP/logs/17-11-07.maillog.txt - Permission denied
>
> I am now running ASSP on an entirely new platform, with much more CPU,
> much more memory, much faster storage (all SSD) and much lower overall
> CPU load, on a different Perl (Strawberry instead of Active State) - and
> yet I still see this happening at least once a week.
>
> Usually - but not always - I see a "Main_Thread got connection request"
> IMMEDIATELY after the "Rolling log file" log entry, with several lines
> where the Main Thread is transferring the connection, and then the log
> rolling fails with Permission Denied.
>
> I can't say for sure without looking at the code, but is it possible
> that because the log is being written to by a different thread/worker
> when it is rolling the log, it is unable to rename the file?
>
> Would it be worthwhile giving the rename process several retries if it
> fails the first time, to try to get around this issue?
>
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>
>
>
> DISCLAIMER:
> *******************************************************
> This email and any files transmitted with it may be confidential, legally
> privileged and protected in law and are intended solely for the use of the
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no
> known virus in this email!
> *******************************************************
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Assp-test mailing list
> Assp-test@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
