nto
>what it thought that it was doing.
No,
only standard logs:
1333:M 06 May 04:36:43.019 * 1 changes in 60 seconds. Saving...
1333:M 06 May 04:36:43.025 * Background saving started by pid 4325
4325:C 06 May 04:36:46.745 * DB saved on disk
4325:C 0
ay 04:36:46.745 * DB saved on disk
4325:C 06 May 04:36:46.749 * RDB: 40 MB of memory used by copy-on-write
1333:M 06 May 04:36:46.825 * Background saving terminated with success
1333:M 06 May 04:37:47.018 * 1 changes in 60 seconds. Saving...
1333:M 06 May 04:37:47.026 * Background saving started by
loading data
into redis sever. Data is small 3-4 mil. keys every key contain around
150 symbols.
I have that problem on two servers, next server is database server with
postgresql
and that problem happened more often, usual once per day or for few
days.
I never play before with changing p
.066651] swapper/3 R running task0 0 1
0x0020
Regards,
Mitko
e was almost 7 years ago and I do not feel safe
now, I guess a lot of things have changed.
-- Steve
Regards,
Mitko
d not believe after a 3 years working CPU suddenly stop working
correctly.
I probably did not provide much information, but I did not write to
kernel mailing list a few years.
Regards,
Mitko
6 matches
Mail list logo
