If everything else checks out. 2GB ram infers an older server. On that assumption CMOS battery going bad causes random reboots. Also malicious virus who has wound its way into RAM. Recommend new MoBo battery.
On Wed, Aug 29, 2018 at 2:29 PM, Niklas Merz <[email protected]> wrote: > >> > well, there's no good answer for that, as it depends on much data you >> have. But I do run a throwaway instance on an f1-micro GCE (600MB), >> where I barely have any data, and I feel that's pretty close to being >> the minimum. >> > > Ok my VM with 2 GB RAM for about 20GB data in perkeep should be fine. I > ran some uploads and watched the usage and it looked good. > > > Np. let's try to make some progress. >> Since you don't see any error or panic stack trace, I guess we can try >> to check that you don't see any of the "regular" termination messages >> either. So, at the end of the log, do you see any of the messages that >> are in the handleSignals func from >> https://perkeep.org/server/perkeepd/perkeepd.go ? >> Secondly, could you add a logging message at the very end of this same >> file, right after >> if testHookServerUp.call(); !testHookWaitToShutdown.call() { >> select {} >> } >> ? >> Normally, we should never get past this select{}. So if by any chance >> we do, it would be interesting to know about it. >> > > Ok I will try that and watch out for another termination. > > Thank you and I will report back with results. > > -- > You received this message because you are subscribed to the Google Groups > "Perkeep" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Perkeep" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
