On Wednesday, May 27, 2015 10:30:01 PM James Moe wrote: > ASSP v1.10.0(14299) > linux 3.16.7-21-desktop x86_64 > perl v5.20.1 built for x86_64-linux-thread-multi > > ASSP has been going into a zombie mode every 2 or 3 days. > This started after the system was upgraded (from opensuse 13.1 to > 13.2). It was a several point jump for PERL, 5.16 to 5.20. To even get > ASSP to run almost all of the additional modules needed an update. > In the zombie mode ASSP is unresponsive to mail connections, and > admin connections via browser. > Does anyone know what may be causing the "main loop" to stop looping?
No clue, I am not big on perl, and not very familiar with it. I had a variety of issues with 1.x, I was on 1.9.9-14284 at the end. It was more crashing and other issues on startup, SPF code, etc. But given it was not maintained much I switched to 2.x. With that I have still had some issues but not as before. I have seen some what of what your describing with 2.x. However I think because its multi-threaded or something. The admin interface still works, and it still logs, but it stops processing mail. I have to restart ASSP. But its been some time since that happened. I blame perl and modules more than ASSP code itself. As with 1.x that worked fine till perl updates blew it up. Seems that still happens at times, but hard to sway which module, if not some aspect of perl itself. I just tried to make sure I was on the latest version of it all. At times since on Gentoo I recompile perl and all of its modules anytime I have an issue with ASSP. That seems to help, but not always. I think ASSP might be using some old perl code in some places. Things no longer maintained such as IO::Socket::INET6. Which the core perl IO::Socket::IP supports IPv6 for some time, but ASSP still uses IO::Socket::INET6. I have been meaning to make a patch to update but I haven't got around to it, and not that familiar with perl. Tried to get some I know who are familiar and perl advocates to do that but they are busy with other stuff. That module I know has at least one issue I reported a bug on, but its no longer maintained, No release in some time. I still cannot use Schedule::Cron without it maxing out a thread and running away till I restart or kill ASSP. Not sure what causes that, seems that works fine for others. I am not blaming current maintainers/developers. I don't think it was an easy codebase to take over and/or maintain. From patching ASSP and doing things to package it. Its not really trivial perl code. If it was, I might have joined in development and/or ported to another language. Which I might seek to do someday. Tracking down where problems come from are not easy and I have had a variety of issues since like December. Mostly coming from Perl updates not ASSP updates. Prior to that, ASSP had been rock solid and stable for over a decade through many versions. Really quite frustrating, as I cannot imagine a mail server without ASSP given the stats from over a decade of use. Though at times its made mail very unreliable. Doesn't solve or address your problem, but your not really the only one experiencing issues. You might want to try to update to v2 and see if its any better. Though you might run into other problems. Unless you want to regress perl and modules. Not sure that is the best approach. -- William L. Thomson Jr. Obsidian-Studios, Inc. http://www.obsidian-studios.com ------------------------------------------------------------------------------ _______________________________________________ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
