When dealing with mem-leaks in my mod_perl-apps I ran into a curious apache-problem. After a while apache could not be started but failed with strange errors like: [emerg] (28)No space left on device: Couldn’t create accept lock or [crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lock Configuration Failed or [Wed Dec 07 00:00:09 2005] [error] (28)No space left on device: Cannot create SSLMutex There was definitely enough space on the device where the locks are stored (default /usr/local/apache2/logs/). I tried to explicetely different Lockfiles using the LockFile-directive but this did not help. I also tried a non-default AcceptMutex (flock) which then solved the acceptlock-issue and ended in the rewrite_log_lock-issue. Only reboot of the system helped out of my crisis.

Solution: There were myriads of semaphore-arrays left, owned by my apache-user.

## ipcs -s | grep apache

Removing this semaphores immediately solved the problem.


ipcs -s | grep apache | perl -e 'while () { @a=split(/\s+/); print `ipcrm sem $a[1]`}'

directadmin kurulu sunucuda. daha once default spamassassin kurulumu yapilmis. yukselticez.. su sekilde:

perl -MCPAN -e 'install Archive::Tar'
perl -MCPAN -e 'install IO::Zlib'
perl -MCPAN -e 'install Digest::SHA'
perl -MCPAN -e 'install Mail::SPF'
perl -MCPAN -e 'install Mail::DKIM'
cd /usr/local/directadmin/scripts
wget -O /usr/local/directadmin/scripts/packages/Mail-SpamAssassin-3.3.0.tar.gz http://www.ecoficial.com/apachemirror/spamassassin/source/Mail-SpamAssassin-3.3.0.tar.gz
perl -pi -e 's/3.2.5/3.3.0/' spam.sh
perl -pi -e 's/getFile $FILE;/#getFile $FILE;/' spam.sh
./spam.sh

not: toptan kopy paste yapma. satirlari tek tek yapistir. aksi takdirde sicma egilimi gosteriyor 😀

ISLEM BITINCE

sa-update komutunu calistir !!! calistirmazsan baslamiyor yeni spamassassin

NOT: centos 5.4 64 bit de sa-update can’t find LWP vs hata verirse:

yum install perl-libwww-perl

sonra sa-update

ty ty..