I missed the bit about init.d.
I haven't touched that for years. The stop command runs:
/usr/local/assp stop
It then removes the pid file if the stop command returns an exit code of 0
I never use the init.d restart command. ASSP shuts itself down and does not
start back up automatically. Nothing external is involved in the shutdown
either, I do have an external script that will start ASSP back up when it
stops but that will take a minimum of 5 minutes to kick in to be sure it
isn't a temporary error or a shut down command is still running.
On Wed, Oct 5, 2016 at 10:47 AM, cw <colin.war...@gmail.com> wrote:
> Thank you Thomas.
>
> useDB4IntCache - already set to off
> I've set WorkerLog to diagnostic and done the other steps.
> I don't have anything in CorrectASSPcfg.pm so as part of the
> troubleshooting I have previously deleted it and downloaded a fresh copy
> from SourceForge.
>
> I have to say that ASSP started up within seconds after clearing those
> files out - it normally takes several minutes and has always done.
>
> I looked at SF but only see 16275 in test (updated 3 days ago) so maybe it
> hasn't made its way live yet.
>
> On Wed, Oct 5, 2016 at 10:33 AM, Thomas Eckardt <
> thomas.ecka...@thockar.com> wrote:
>
>> I've provided an updated assp.pl (2.5.4 16279) in CVS /test. This version
>> shows some more information, if 'WorkerLog' is set to diagnostic.
>>
>> Thomas
>>
>>
>>
>>
>>
>> Von: cw <colin.war...@gmail.com>
>> An: ASSP development mailing list <assp-test@lists.sourceforge.net>
>> Datum: 05.10.2016 10:10
>> Betreff: Re: [Assp-test] unable to detect any running worker
>>
>>
>>
>> Hi Thomas,
>>
>> Thanks for chipping in. All modules are installed by running the latest
>> mod_inst.pl. Crypt::GOST on Ubuntu actually has a bug in it so it
>> requires
>> a minor edit to the code to get it to build. So that module was installed
>> by switching to /root/.cpan/build/Crypt-GOST-x-x-x and running:
>> make clean
>> perl Makefile.PL
>> make
>> make test
>> make install
>>
>> I run cpan-outdated -p|cpanm from time to time in order to keep modules up
>> to date as well so things don't stay stuck on old versions.
>>
>> Everything that is installed now is a completely fresh build as the
>> Upgrade
>> to 16.04 replaced perl 5.18 with 5.22 and all the modules therefore had to
>> be installed from scratch.
>>
>> I bypassed the issue by truncating the tables and setting up the users
>> again. With there only being one user it was easier to do that than muck
>> about with it - especially with the other bigger issue at hand.
>>
>> On Wed, Oct 5, 2016 at 8:59 AM, Thomas Eckardt
>> <thomas.ecka...@thockar.com>
>> wrote:
>>
>> > >to replace the corrupted encrypted
>> > strings with the correct values
>> >
>> > Was the 'Crypt::GOST' module from the SF download page at the old assp
>> > instance?
>> > If it was, did you install the 'Crypt::GOST' module from the SF download
>> > page, before you started the new assp instance?
>> >
>> > https://sourceforge.net/projects/assp/files/ASSP%20V2%
>> > 20multithreading/ASSP%20V2%20module%20installation/Crypt-GOST/
>> >
>> > Thomas
>> >
>> >
>> >
>> >
>> >
>> > Von: cw <colin.war...@gmail.com>
>> > An: ASSP development mailing list <assp-test@lists.sourceforge.net>
>> > Datum: 05.10.2016 09:52
>> > Betreff: Re: [Assp-test] unable to detect any running worker
>> >
>> >
>> >
>> > 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
>> >
>> >
>> >
>> >
>> > 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!
>> > *******************************************************
>> >
>> >
>> > ------------------------------------------------------------
>> > ------------------
>> > 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
>>
>>
>>
>>
>> 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!
>> *******************************************************
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> 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
