1

Topic: General slowness

Hello everyone

We are using GLPI in a standard instalation. No special issues.
Apache+MySQL…

Our database has in this moment 22 entities and 322 users, 21 mailgates that
take mails by imap. We are using it with either internet explorer 8, firefox or
chrome.

The problem is that we cannot work properly because the application freezes really often and we have to wait till it comes back.

Example:

Using firefox, after manually registering a ticket it freezes. Any other user can work in the meanwhile, it just freezes for one user. But if this user opens the application on another browser it works fine.

It usually happens when you perform some actions in a row. If we create a new entity and we begin entering users, it will freeze every 4 or 5 users.

We find the application highly interesting and we are looking forward to use it, but this problem is really annoying sometimes.

Thanks for reading and if you need any further information please do not hesitate to ask.

Cheers

2

Re: General slowness

version of glpi ?
how do you fetch emails ?

3

Re: General slowness

GLPI Version is 0.72.4.

We fetch emails from 21 different folders of an IMAP mailbox. Mail and GLPI are on different servers but on the same LAN.

4

Re: General slowness

is the freeze about 15 seconds?

any processes running on glpi server with rsh during freeze?

[user@glpi-server ~]$ ps -ef| grep rsh
root      8865     1  0 20:28 ?        00:00:00 /usr/bin/rsh my.imap.server -l apache exec /etc/rimapd

Carsten

5

Re: General slowness

how do you call the cron.php page ? using wget or using php CLI ?

6

Re: General slowness

@Carsten

root      4182     1  0 15:41 ?        00:00:00 /usr/bin/rsh 192.168.2.200 -l wwwrun exec /etc/rimapd
root      4192     1  0 15:41 ?        00:00:00 /usr/bin/rsh 192.168.2.200 -l wwwrun exec /etc/rimapd
root      4199     1  0 15:41 ?        00:00:00 /usr/bin/rsh 192.168.2.200 -l wwwrun exec /etc/rimapd
root      4201     1  0 15:42 ?        00:00:00 /usr/bin/rsh 192.168.2.200 -l wwwrun exec /etc/rimapd
root      4203     1  0 15:42 ?        00:00:00 /usr/bin/rsh 192.168.2.200 -l wwwrun exec /etc/rimapd
root      4210     1  0 15:42 ?        00:00:00 /usr/bin/rsh 192.168.2.200 -l wwwrun exec /etc/rimapd
root      4213     1  0 15:42 ?        00:00:00 /usr/bin/rsh 192.168.2.200 -l wwwrun exec /etc/rimapd
root      4215     1  0 15:43 ?        00:00:00 /usr/bin/rsh 192.168.2.200 -l wwwrun exec /etc/rimapd
root      4217     1  0 15:43 ?        00:00:00 /usr/bin/rsh 192.168.2.200 -l wwwrun exec /etc/rimapd
root      4224     1  0 15:43 ?        00:00:00 /usr/bin/rsh 192.168.2.200 -l wwwrun exec /etc/rimapd
root      4237     1  0 15:43 ?        00:00:00 /usr/bin/rsh 192.168.2.200 -l wwwrun exec /etc/rimapd
root      4243     1  0 15:44 ?        00:00:00 /usr/bin/rsh 192.168.2.200 -l wwwrun exec /etc/rimapd

These processes keep growing to a certain point keeping the app frozen and then they finish themselves and the application comes back to life

root      4247     1  0 15:44 ?        00:00:00 /usr/bin/rsh 192.168.2.200 -l wwwrun exec /etc/rimapd

7

Re: General slowness

@ Carsten

The freeze is random, and usually longer than 15 seconds

8

Re: General slowness

On my glpi installation I had these 15 seconds timeouts when imap server was contacted via cron. Take a look in your glpi cron.log. You will see

mailgate task was done (15.41s)

I fixed this by appending /norsh option to the connection string in field 'hosts' in glpi table glpi_mailgate. Like

{my.imap.server/imap/novalidate-cert/notls/norsh}

Maybe one of the devs can put the /norsh option into the mailgate setup page.

  Carsten