Cheers for the reply.
I don't think backups are an option seen as I've moved completely from
Ubuntu 14.04 to Ubuntu 16.04.
Also, this issue has been around for months. It was causing a handful of
shutdowns a week with the occasional spat of more frequent shutdowns. It is
entirely possible that the errors are behaviour related and nothing to do
with the upgrade and that current email behaviour is triggering it big
style.
I'm not convinced though, unfortunately I'm not convinced of anything else
hence not having much to go on. I can't see any consistencies in the
behaviour leading up to the events.
I don't think it is database related. It happened on one of the mail
servers during the upgrade to 16.04 when ASSP had just started but I had
not yet got into the web interface to replace the corrupted encrypted
strings with the correct values so all database connections were in error.
The problem has already started again this morning so I can see this being
another fun day that either leads to a fix or having to put something else
in place.
On Wed, Oct 5, 2016 at 4:34 AM, K Post <nntp.p...@gmail.com> wrote:
> I've been reading here, but I haven't had anything to suggest. All seems
> quite odd if it was working prior to upgrading and downgrading didn't work.
>
>
> Could you spin up a backup of the installation after copying the current
> data? Sure you'd have an older corpus, but I'd think you could add the new
> files if necessary, manually replace whitelist etc.
>
>
> On Tue, Oct 4, 2016 at 5:48 PM, cw <colin.war...@gmail.com> wrote:
>
> > Further development on this today, very little.
> > I have moved both servers onto Ubuntu 16.04 LTS which means going from
> perl
> > 5.18 to 5.22 and rebuilding all perl modules from scratch.
> >
> > The admin user db did not work after the upgrade so I had to empty the
> > tables before it would come back online.
> >
> > I'm still getting delayed emails and assp shutting down telling me it is
> > unable
> > to detect any running worker.
> >
> > If this goes on much longer the MD will pull the plug and we'll end up
> > moving to a third party solution which is not something I want but if I
> > can't fix it I can't defend it :/
> >
> > ------------------------------------------------------------
> > ------------------
> > 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
>
>
------------------------------------------------------------------------------
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
