You're right Ivan,
my bad !
Swap has grown quickly and has been full... Ok, it was a test with
another instance... so I'll kill this other instance :(
Thx for your help Ivan,
next time, I'll check my graphs :s
Nice shot ;)
Ivan Markin :
> Probably there is a memory leakage somewhere that makes
A good way to explore !
Exact, some swap is used... may be full of it !
Have to check it...
> Probably there is a memory leakage somewhere that makes everything fail
> and get process eventually killed by OS.
--
Petrusko
C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5
signature.asc
Petrusko:
> Got it too,
> Sooo many lines in my log file.
> [...]
> Jan 22 06:37:37.000 [warn] assign_to_cpuworker failed. Ignoring.
> Jan 22 06:37:37.000 [warn] assign_to_cpuworker failed. Ignoring.
> Jan 22 06:37:37.000 [warn] circuit_mark_for_close_(): Bug: Duplicate
> call to
Hi!
Yes, since I set the "Address "line in torrc, this message was gone.
But ... I nevertheless get the "clock jumped" warning once a day:
"Jan 21 18:34:53.000 [warn] Your system clock just jumped 398 seconds
forward; assuming established circuits no longer work."
3-6 minutes difference is
