Quitting Indigo Server - received slow quit signal

For an unknown reason today, Indigo shut down and my Mac mini powered off. I am assuming this was some kind of controlled power-down, as it did not restart as one would expect with a "dirty" power loss.

I suspect this is all due to some problems I am having with an APC UPS in which I changed the battery but yet is still not playing nicely. I do run the APC agent on the mac mini, so it has the authority to shut down the computer.

I am pretty sure that none of the other connected equipment lost power, though that can be difficult to assess.

In the Indigo logs, though, I did see these entries at what I assume was the point of failure.

Code: Select all

2020-02-24 14:13:34.964   Application   Quitting Indigo Server - received slow quit signal
2020-02-24 14:13:34.965   Application   Quitting Indigo Server - stopping plugins

Followed by stopping of a bunch of plugins and various interface errors.

Is this what would be expected if the APC Agent was attempting to close active programs and perform a controlled shutdown?

[jay (support)]

Is this what would be expected if the APC Agent was attempting to close active programs and perform a controlled shutdown?

Yes. In fact, this is what you'd see in the logs if you selected Shutdown or Restart from the Apple menu. macOS sends a signal to Indigo that it should shut down, so it starts an orderly shutdown.

Thanks Jay. Looks like I need to see if I can fix the UPS to let it know it has a new battery. I think there's a calibration process I read about somewhere.

So, strangely I had this overnight as well. No idea why, at approx 1:15am Indigo got the slow quit signal and closed, but the mac remained running and I dont use an UPS.

This is from the indigo logs

Code: Select all

2022-03-28 01:13:54.316   Application   Indigo Cocoa client disconnected
2022-03-28 01:13:54.514   Application   Quitting Indigo Server - received slow quit signal
2022-03-28 01:13:54.547   Application   Quitting Indigo Server - stopping plugins


and this from the mac console from system.log

Code: Select all

Mar 28 01:01:28 Mac-mini syslogd[120]: ASL Sender Statistics
Mar 28 01:11:29 Mac-mini syslogd[120]: ASL Sender Statistics
Mar 28 01:13:53 Mac-mini sessionlogoutd[92108]: DEAD_PROCESS: 166 console
Mar 28 01:27:35 Mac-mini syslogd[120]: ASL Sender Statistics
Mar 28 01:41:08 Mac-mini syslogd[120]: ASL Sender Statistics

The timing makes me think they are linked but no idea what that DEAD_PROCESS is or why that triggered Indigo to close. You can see that the Mac stays running after that.

Any ideas?

[jay (support)]

Code: Select all

Mar 28 01:01:28 Mac-mini syslogd[120]: ASL Sender Statistics
Mar 28 01:11:29 Mac-mini syslogd[120]: ASL Sender Statistics
Mar 28 01:13:53 Mac-mini sessionlogoutd[92108]: DEAD_PROCESS: 166 console
Mar 28 01:27:35 Mac-mini syslogd[120]: ASL Sender Statistics
Mar 28 01:41:08 Mac-mini syslogd[120]: ASL Sender Statistics

The sessionlogoutd seems to imply that perhaps something tried to log out the account under which the server was running - that would cause macOS to send the quit signal to the client and server, which appears from your Indigo log snippits to be what happened (the client quit, which is the first disconnected message, then the server got the signal from macOS to quit, which it did). Not sure what the DEAD_PROCESS thing is about though. Maybe this post might help?

Cheers Jay. Let me look at the Mac side some more