redis-server taking more cpu utilization

[narasimhasw@…]

Hi, We are using zental 2.0.2 version and redis-server is taking more cpu utilization. we are unable to run the ebox server.please help me out.

Regards, G Narasimha Rao. narasimhasw@…

[jacalvo@…]

Could you describe more your problem? The output of "top" or "ps aux" commands would be useful. Does this happen from the beginning or has suddenly start to happen? Which are your hardware specifications?

As we can't reproduce this, please reopen if you can provide enough information to diagnose your problem.

[narasimhasw@…]

Hi,

I am sending system server details and attached the (top and redis-server logs).Could you please check and give us the solution as soon as possible.

server details:

Model: Dell sc430 Ram: 4GB CPU:Intel(R) Pentium(R) D CPU 2.80GHz

Partition details: root@ebox-gwn:/var/log/ebox# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 448G 4.6G 421G 2% / none 1.9G 188K 1.9G 1% /dev none 1.9G 0 1.9G 0% /dev/shm none 1.9G 116K 1.9G 1% /var/run none 1.9G 0 1.9G 0% /var/lock none 1.9G 0 1.9G 0% /lib/init/rw

Thanks & Regards, G Narasimha Rao.

[narasimhasw@…]

Hi,

Can you please look into the issue and when we are adding entries in ebox server(zentyal 2.0.2 version) taking more cpu utilization simultaneously increasing the load average.

Please kindly check the issue.

Thanks & Regards, G Narasimha Rao.

Replying to narasimhasw@…:

Hi,

I am sending system server details and attached the (top and redis-server logs).Could you please check and give us the solution as soon as possible.

server details:

Model: Dell sc430 Ram: 4GB CPU:Intel(R) Pentium(R) D CPU 2.80GHz

Partition details: root@ebox-gwn:/var/log/ebox# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 448G 4.6G 421G 2% / none 1.9G 188K 1.9G 1% /dev none 1.9G 0 1.9G 0% /dev/shm none 1.9G 116K 1.9G 1% /var/run none 1.9G 0 1.9G 0% /var/lock none 1.9G 0 1.9G 0% /lib/init/rw

Thanks & Regards, G Narasimha Rao.

[jamor@…]

I am sorry but we are unable to reproduce your issue. Since you are using normal operations this will be likely the result of a unforeseeable combination of events.

Maybe reinstalling your server would fix things.

Anyway in version 2.1 we are using a newer version of redis so I think this would be a problem only for the 2.0 series.

Cheers,

Javier