Hi Luke,
Will send you both logs for nrservice (the very brief one of the nrservice instance which died during or immediately after computer boot, plus the 16,000 line log file of the nrservice instance which I manually started after the first one had died).
But note that I have ALREADY sent you the brief log written by nrservice when it dies immediately on booting, AS WELL AS the first 100 lines (of over 16,000 lines) of the second nrservice which runs all day after being manually started.
Are you sure you want 16,000 lines of log of an nrservice which is running for 10-12 hours with no problems and never crashed? You can have them. Unless you write back in the next four hours, I will send them to you this evening when I get back to my test server. But I don't understand why you prefer that to the log file produced by the nrservice which crashed, which is of course very brief precisely because it crashed while starting up.
I can tell you now, however, that if the random crashes do not recur over the next few days, but only the one crash on bootup occurs and my manual restart of nrservice then runs all day and all night, that I will not consider that a fatal flaw for my purposes. I will switch to using NeoRouter anyway, because I can live with that minor inconvenience. It is the random crashes on a sometimes unattended server which would be intolerable.
In any case, my production NeoRouter server box is very likely to be a 32-bit Ubuntu, SuSE Linux, or Windows box, which might not display the nrservice problems at all.
Thanks,
David E.
|