[Info-ingres] Waiting indefinitely for the logging system to shut down

[Jean-Pierre Zuate]

I already se cases where recovery finish his job when Ingres start raiser
than he stop (because the failure conditions, lack of memory, something
bad, is still here).

After killing processes don't forget to clean memory segments.

And if your Ingres installation fail to stop gracefully and you need to
kill processes and clean memory, once it start again and recovery finish
his job without pain, don't forget to stop/start Ingres again.

It is important to have a clean stop and then a clean start before release
user activity ...

Regards,
--
Jean-Pierre Zuate

Le lun. 2 mars 2020 à 11:30, Martin Bowes <martin.bowes at ndph.ox.ac.uk> a
écrit :

> Hi Steve,
>
> The message means that the recovery system is processing your transaction
> log file, trying to work out what it needs to do to the information to give
> you a graceful shutdown.
>
> It can be interrupted by for example killing the iircp with a UNIX kill
> signal. A subsequent restart will recognise that the shutdown was not
> graceful and simply recommence processing the transaction log file locking
> you out until it has completed.
>
> So don't do that unless you are really sure it's something you need to do.
>
> Your best option is to do a: tail -f $II_SYSTEM/ingres/files/iircp.log
>
> This will give you confirmation the recovery process is actually doing
> something rather than just spinning its wheels.
>
> Marty
>
> -----Original Message-----
> From: Steve <s.anderson.au at gmail.com>
> Sent: 02 March 2020 00:59
> To: info-ingres at lists.planetingres.org
> Subject: [Info-ingres] Waiting indefinitely for the logging system to shut
> down
>
> The other day Ingres would not shutdown.
>
> Here are the messages in the error log when ingstop was issued:
>
> ..., lgmisc.c:1582         ]: Tue Feb 18 00:32:19 2020 E_DMA469_P
> ROCESS_HAS_DIED Process (00002F36) has died. A process attached to the
> logging and locking system has exited without going through n ormal cleanup
> processing. The system will now perform cleanup processing on behalf of the
> failed process.
>
> ..., lgkinit.c:1145        ]: Tue Feb 18 00:32:19 2020 E_DMA499_D
> EAD_PROCESS_INFO        Process (00002F36) died with info '(DEFAULT)'.
>
>
> Some processes had shutdown, but the name server, archiver and recovery
> processes were still running.
>
> When ingstop was issued for the second time, the following message was
> displayed:
>
> "Waiting indefinitely for the logging system to shut down"
>
> Trying to understand what the above means. For example, could the logging
> system have been waiting on the already shutdown DBMS servers?
>
> Thanks
> Steve
> _______________________________________________
> Info-ingres mailing list
> Info-ingres at lists.planetingres.org
> https://lists.planetingres.org/mailman/listinfo/info-ingres
> _______________________________________________
> Info-ingres mailing list
> Info-ingres at lists.planetingres.org
> https://lists.planetingres.org/mailman/listinfo/info-ingres
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.planetingres.org/pipermail/info-ingres/attachments/20200303/8a728c0f/attachment.html>