Clocks going back ...

[chris_j_hunter]

was it just us, or did others also have a shut-down & re-launch provoked just-after 2am on Sunday, when the clocks went back ... ??

[JonS]

We had the same issue. Strange its worked fine before. Looking in the logs looks like it was prompted by defibrillator

Defibrillator version = Idratek Defibrillator version 1.0.8
Log Date = 28-10-2012
Log Time = 01:00:00
Communication lost with Cortex - Re-booting PC
Last Network running state was nsMainProcessingLoop

[chris_j_hunter]

yep, our logs seemed to show the same ...

only, in our case, Windows put a spanner in the works ...

we were away, and when we got back we found it waiting for us to choose an account ...

'bit like the lemon soap paper napkins in HHGTTU ...

ie: thirty hours, with the rain pouring down ... and we innocently, miles away, relying on Cortex doing its bit ... and Cortex interrupted & not got going again ...

not a disaster, this time, thank goodness ...

by a whisker ...

[stachoo]

We had exactly the same issue... with a scary announcement that the system would shut down. I haven't checked the exact causes and assumed it was caused by the time shift.

[Karam]

We are aware of the issue and investigating. Chris's more disasterous result highlights an important reminder - that you need to check that you set up the PC such that it auto reboots on power resume, does not require a user login (only one user - administrator), then auto launches Cortex and auto runs the network. The latter two are normally set up by default when you install Cortex, but the former is obviously dependent on your PC. It is worthwhile performing a 'pull the plug' test as part of a maintenance check. That is, with the PC running the network kill the power to it for a few minutes and then re-power. If you're a bit squeemish about killing the PC in this way or have a chunky UPS, then at least you should shut down and then switch back on to check that there are no obstacles after the power up.

[chris_j_hunter]

ours has also been fine before - clocks changing & power-cuts & brutal tests - but we did a Cortex update in May (IIRC) and are still installing & setting-up & trying things out ... which means, along the way, we change many things, and so maybe anything's possible ...

we've also found setting-changes don't always take when we expect them to (not to say we're right) - eg: when, in Cortex, we tick Auto-run in Network Supervisor, and Save, and push the PC's power-button, to turn it off, and push it again to turn it on, we find Idranet does not run, because the setting-change doesn't stick ... ie: we have to Exit Cortex then push the power-button ...

in other words, don't rely on having set things up - be sure to try it for-real, and every now & then, too !

NB: on ours, pushing the power-button causes Cortex to be dumped, but Windows to log-off first, so we imagine it's also kind to its drives, too ...

[mcockerell]

We didn't see this problem - we're still running Cortex 25.

Martin