I've noticed another problem and this one is related to otrs.cleanup script, which is not "cleaning" var/spool folder properly. Well, it's not cleaning folder at all, files are staying in spool folder and everytime script is ran, it duplicates existing tickets from the old spool files. :-( If I run script manually it says this:
$ /opt/otrs/bin/otrs.cleanup /opt/otrs/bin/otrs.cleanup: !: not found Checking otrs spool dir... -n Starting otrs PostMaster... (/opt/otrs/var/spool/1) failed. -n Starting otrs PostMaster... (/opt/otrs/var/spool/10) failed. -n Starting otrs PostMaster... (/opt/otrs/var/spool/11) ...
Bit more of debugging info: $ cat 1 | ../../bin/PostMaster.pl unix dgram connect: Socket operation on non-socket at /opt/otrs/Kernel/System/Log/SysLog.pm line 64 unix dgram connect: Socket operation on non-socket at /opt/otrs/Kernel/System/Log/SysLog.pm line 64 no connection to syslog available at /opt/otrs/Kernel/System/Log/SysLog.pm line 64 Problematic line 64 from SysLog.pm is: # start syslog connect setlogsock('unix'); Message actually gets into OTRS, but after that it's not removed from spool folder. Any hint more than welcome. P.S. I'm running this on Solaris 5.8 (Intel platform). Best regards, Alex