Apparently I spoke too soon, ASSP cleared out the folder after starting fully

All the best,
Colin Waring

On 11 Apr 2014 07:50, Colin Waring <co...@lanternhosting.co.uk> wrote:
>
> Hi Thomas, 
>
> I didn't have to wait long, it turns out two runs of rebuildspamdb are 
> enough to fill a 1GB tempdb folder now. 
>
> I have added the entry and ASSP starts back up without coredumping. tmpDB 
> does remain 100% full though 
>
> Has anything changed recently that would increase the tmpDB requirements? 
>
> All the best, 
> Colin Waring. 
>
> -----Original Message----- 
> From: Thomas Eckardt [mailto:thomas.ecka...@thockar.com] 
> Sent: 09 April 2014 09:23 
> To: ASSP development mailing list 
> Subject: Re: [Assp-test] ASSP fails with no error message when tmpDB folder 
> full 
>
> add the following line to 'lib/CorrectASSPcfg.pm' 
>
> $main::BDBMaxCacheSize = 0; 
>
> and restart assp. Tell me if it works or not. 
>
> Thomas 
>
>
>
> Von:    "Colin Waring" <co...@lanternhosting.co.uk> 
> An:     "'ASSP development mailing list'" 
> <assp-test@lists.sourceforge.net>, 
> Datum:  09.04.2014 09:56 
> Betreff:        [Assp-test] ASSP fails with no error message when tmpDB 
> folder full 
>
>
>
> Hi Folks, 
>
>
>
> At the weekend one of my mailservers died overnight. I had a quick check 
> over and saw that it was coredumping without any errors. I decided to 
> leave 
> it till the morning as the other servers could handle things. By morning 
> my 
> monitoring scripts had restarted it. 
>
>
>
> This morning I got up to the same issue, except the problem didn't go away 
> itself. 
>
>
>
> ASSP would core dump during startup without outputting any messages. If I 
> enabled debugging, not debug file was created. 
>
>
>
> I had to resort to strace to see that it was getting an error with space 
> on 
> the tmpDB folder which was indeed completely full. There was over a 
> gigabyte 
> of data contained in there, all relating to rebuildspamdb. Some was from 
> last night's run but some was from two nights prios. 
>
>
>
> I'm presuming that there is some code in the startup that clears up 
> leftover 
> rebuildspamdb data as I emptied the folder but did not remove it. After 
> starting ASSP the rebuild folder disappeared. 
>
>
>
> I suspect this code needs to be called much earlier in the startup 
> process. 
> I'll include the strace failure incase it gives an idea of where in the 
> process it needs to be moved to. 
>
>
>
> All the best, 
>
> Colin Waring. 
>
>
>
>
>
> stat64("/usr/local/assp/tmpDB", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=80, 
> ...}) = 0 
>
> stat64("/usr/local/assp/tmpDB/_cachecheck", {st_mode=S_IFDIR|0755, 
> st_size=80, ...}) = 0 
>
> lstat64("/usr/local/assp/tmpDB/_cachecheck/__db.001", 
> {st_mode=S_IFREG|0644, 
> st_size=0, ...}) = 0 
>
> unlink("/usr/local/assp/tmpDB/_cachecheck/__db.001") = 0 
>
> lstat64("/usr/local/assp/tmpDB/_cachecheck/__db.002", 0x8c07064) = -1 
> ENOENT 
> (No such file or directory) 
>
> lstat64("/usr/local/assp/tmpDB/_cachecheck/__db.003", 0x8c07064) = -1 
> ENOENT 
> (No such file or directory) 
>
> lstat64("/usr/local/assp/tmpDB/_cachecheck/__db.004", 0x8c07064) = -1 
> ENOENT 
> (No such file or directory) 
>
> lstat64("/usr/local/assp/tmpDB/_cachecheck/BDB-cachesize-test-error.txt", 
> {st_mode=S_IFREG|0644, st_size=98, ...}) = 0 
>
> unlink("/usr/local/assp/tmpDB/_cachecheck/BDB-cachesize-test-error.txt") = 
> 0 
>
> open("/usr/local/assp/tmpDB/_cachecheck/BDB-cachesize-test-error.txt", 
> O_WRONLY|O_CREAT|O_APPEND|O_LARGEFILE, 0666) = 4 
>
> _llseek(4, 0, [0], SEEK_END)            = 0 
>
> ioctl(4, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfaccc38) = -1 ENOTTY 
> (Inappropriate ioctl for device) 
>
> _llseek(4, 0, [0], SEEK_CUR)            = 0 
>
> fstat64(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 
>
> fcntl64(4, F_SETFD, FD_CLOEXEC)         = 0 
>
> time(NULL)                              = 1397029108 
>
> stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=3661, ...}) = 0 
>
> time(NULL)                              = 1397029108 
>
> open("/sys/devices/system/cpu/online", O_RDONLY|O_CLOEXEC) = 5 
>
> read(5, "0\n", 8192)                    = 2 
>
> close(5)                                = 0 
>
> write(4, "2014-04-09 08:38:28\nBDB cachesiz"..., 50) = 50 
>
> fcntl64(4, F_GETFL)                     = 0x8401 (flags 
> O_WRONLY|O_APPEND|O_LARGEFILE) 
>
> fstat64(4, {st_mode=S_IFREG|0644, st_size=50, ...}) = 0 
>
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
> = 
> 0xb6ee0000 
>
> _llseek(4, 0, [50], SEEK_CUR)           = 0 
>
> open("/usr/local/assp/tmpDB/_cachecheck/DB_CONFIG", O_RDONLY|O_LARGEFILE) 
> = 
> -1 ENOENT (No such file or directory) 
>
> stat64("/var/tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=4096, ...}) = 0 
>
> open("/usr/local/assp/tmpDB/_cachecheck/__db.001", 
> O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = 5 
>
> fcntl64(5, F_GETFD)                     = 0 
>
> fcntl64(5, F_SETFD, FD_CLOEXEC)         = 0 
>
> open("/usr/local/assp/tmpDB/_cachecheck/__db.001", 
> O_RDWR|O_CREAT|O_LARGEFILE, 0666) = 8 
>
> fcntl64(8, F_GETFD)                     = 0 
>
> fcntl64(8, F_SETFD, FD_CLOEXEC)         = 0 
>
> _llseek(8, 16384, [16384], SEEK_SET)    = 0 
>
> write(8, 
> "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 
> 8192) 
> = -1 ENOSPC (No space left on device) 
>
> write(4, "write: 0xbc3caf0, 8192: No space"..., 48) = 48 
>
> mmap2(NULL, 24576, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0) = 0xb66bd000 
>
> close(8)                                = 0 
>
> --- SIGBUS (Bus error) @ 0 (0) --- 
>
> +++ killed by SIGBUS (core dumped) +++ 
>
> ---------------------------------------------------------------------------- 
> -- 
> Put Bad Developers to Shame 
> Dominate Development with Jenkins Continuous Integration 
> Continuously Automate Build, Test & Deployment 
> Start a new project now. Try Jenkins in the cloud. 
> http://p.sf.net/sfu/13600_Cloudbees 
> _______________________________________________ 
> 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! 
> ******************************************************* 
>
>
>
>
> ------------------------------------------------------------------------------
>  
> Put Bad Developers to Shame 
> Dominate Development with Jenkins Continuous Integration 
> Continuously Automate Build, Test & Deployment 
> Start a new project now. Try Jenkins in the cloud. 
> http://p.sf.net/sfu/13600_Cloudbees 
> _______________________________________________ 
> Assp-test mailing list 
> Assp-test@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/assp-test 
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to