Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - albatroz

Pages: [1] 2 3 ... 5
1
Moral: Don't install a software in production until it is at least on version x.1

2
It seems that these issues are not completely solved with the version 7.0.3
of Zarafa. I am still getting these errors:


Quote
servidor@mail:~$ tail -f /var/log/zarafa/server.log
Tue Nov 29 09:25:36 2011: 0x000000043ff120: SQL Failed: Out of range value for c
olumn 'val_ulong' at row 1, Query Size: 101, Query: "UPDATE properties SET val_u
long = val_ulong + -7 WHERE hierarchyid = 241 AND tag = 13827 AND type = 3"
Tue Nov 29 09:31:54 2011: 0x000000039340a0: SQL Failed: Deadlock found when tryi
ng to get lock; try restarting transaction, Query Size: 102, Query: "UPDATE prop
erties SET val_ulong = val_ulong + -1 WHERE hierarchyid = 1041 AND tag = 13826 A
ND type = 3"
Tue Nov 29 09:32:45 2011: 0x000000039340a0: SQL Failed: Lock wait timeout exceed
ed; try restarting transaction, Query Size: 102, Query: "UPDATE properties SET v
al_ulong = val_ulong + -1 WHERE hierarchyid = 1041 AND tag = 13827 AND type = 3"
Tue Nov 29 09:33:11 2011: 0x000000039340a0: SQL Failed: Deadlock found when tryi
ng to get lock; try restarting transaction, Query Size: 123, Query: "UPDATE prop
erties SET val_longint=val_longint-18713 WHERE tag=3592 AND type=20 AND hierarch
yid=1033 AND val_longint >=18713"
Tue Nov 29 09:36:57 2011: 0x000000043fa0a0: SQL Failed: Lock wait timeout exceed
ed; try restarting transaction, Query Size: 58, Query: "UPDATE hierarchy SET fla
gs=flags|1024 WHERE id IN(3405301)"
Tue Nov 29 09:38:08 2011: 0x00000001926b20: SQL Failed: Lock wait timeout exceed
ed; try restarting transaction, Query Size: 103, Query: "UPDATE properties SET v
al_ulong = val_ulong + 1 WHERE hierarchyid = 355783 AND tag = 13826 AND type = 3
"
Tue Nov 29 09:41:44 2011: Session failed to shut down: skipping clean
Tue Nov 29 09:44:09 2011: 0x000000017f85a0: SQL result failed: Lock wait timeout
 exceeded; try restarting transaction, Query: "SELECT val_ulong FROM properties
WHERE hierarchyid = 161 FOR UPDATE"
Tue Nov 29 09:48:53 2011: 0x000000027d2620: SQL Failed: Lock wait timeout exceed
ed; try restarting transaction, Query Size: 101, Query: "UPDATE properties SET v
al_ulong = val_ulong + 1 WHERE hierarchyid = 1110 AND tag = 13826 AND type = 3"
Tue Nov 29 09:49:18 2011: 0x00000003f24620: SQL Failed: Lock wait timeout exceed
ed; try restarting transaction, Query Size: 90, Query: "UPDATE hierarchy SET fla
gs=flags|1024 WHERE id IN(3408028,3408159,3408366,3408384,3408528)"
Tue Nov 29 09:52:12 2011: 0x00000003f24620: SQL Failed: Deadlock found when tryi
ng to get lock; try restarting transaction, Query Size: 101, Query: "UPDATE prop
erties SET val_ulong = val_ulong + -2 WHERE hierarchyid = 241 AND tag = 13826 AN
D type = 3"
^C
servidor@mail:~$ tail -f /var/log/zarafa/server.log
Tue Nov 29 09:31:54 2011: 0x000000039340a0: SQL Failed: Deadlock found when tryi
ng to get lock; try restarting transaction, Query Size: 102, Query: "UPDATE prop
erties SET val_ulong = val_ulong + -1 WHERE hierarchyid = 1041 AND tag = 13826 A
ND type = 3"
Tue Nov 29 09:32:45 2011: 0x000000039340a0: SQL Failed: Lock wait timeout exceed
ed; try restarting transaction, Query Size: 102, Query: "UPDATE properties SET v
al_ulong = val_ulong + -1 WHERE hierarchyid = 1041 AND tag = 13827 AND type = 3"
Tue Nov 29 09:33:11 2011: 0x000000039340a0: SQL Failed: Deadlock found when tryi
ng to get lock; try restarting transaction, Query Size: 123, Query: "UPDATE prop
erties SET val_longint=val_longint-18713 WHERE tag=3592 AND type=20 AND hierarch
yid=1033 AND val_longint >=18713"
Tue Nov 29 09:36:57 2011: 0x000000043fa0a0: SQL Failed: Lock wait timeout exceed
ed; try restarting transaction, Query Size: 58, Query: "UPDATE hierarchy SET fla
gs=flags|1024 WHERE id IN(3405301)"
Tue Nov 29 09:38:08 2011: 0x00000001926b20: SQL Failed: Lock wait timeout exceed
ed; try restarting transaction, Query Size: 103, Query: "UPDATE properties SET v
al_ulong = val_ulong + 1 WHERE hierarchyid = 355783 AND tag = 13826 AND type = 3
"
Tue Nov 29 09:41:44 2011: Session failed to shut down: skipping clean
Tue Nov 29 09:44:09 2011: 0x000000017f85a0: SQL result failed: Lock wait timeout
 exceeded; try restarting transaction, Query: "SELECT val_ulong FROM properties
WHERE hierarchyid = 161 FOR UPDATE"
Tue Nov 29 09:48:53 2011: 0x000000027d2620: SQL Failed: Lock wait timeout exceed
ed; try restarting transaction, Query Size: 101, Query: "UPDATE properties SET v
al_ulong = val_ulong + 1 WHERE hierarchyid = 1110 AND tag = 13826 AND type = 3"
Tue Nov 29 09:49:18 2011: 0x00000003f24620: SQL Failed: Lock wait timeout exceed
ed; try restarting transaction, Query Size: 90, Query: "UPDATE hierarchy SET fla
gs=flags|1024 WHERE id IN(3408028,3408159,3408366,3408384,3408528)"
Tue Nov 29 09:52:12 2011: 0x00000003f24620: SQL Failed: Deadlock found when tryi
ng to get lock; try restarting transaction, Query Size: 101, Query: "UPDATE prop
erties SET val_ulong = val_ulong + -2 WHERE hierarchyid = 241 AND tag = 13826 AN
D type = 3"

3
Installation and Upgrades / Re: Can't find smtp authentification
« on: November 29, 2011, 01:10:55 pm »
Hello,
This thread explains all what you are asking :)

http://forum.zentyal.org/index.php/topic,8421.msg35024.html#msg35024

4
It seems however that Zarafa version 7.0.3 has its own set of problems ...  :-\
http://forums.zarafa.com/viewtopic.php?t=7636&p=34181

5
sudo apt-get upgrade zarafa
seems to have worked fine.

Just waiting for the hot working hours of tomorrow.
 ::)

6
Mmm... I am checking the components update tab of my server and it says nothing regarding Zarafa or Groupware module update.

7
My impression is that these deadlock error messages are the cause of the overload of MySQL
and the slowliness of my server.

Now my question is, what can I do to solve this issue?

BTW I have also found other error messages in /var/log/zarafa/server.log

Fri Nov 25 14:45:54 2011: Caught SIGSEGV (11), traceback:
Fri Nov 25 14:45:54 2011: 0x000000004bcef9 /usr/bin/zarafa-server(_Z7sigsegvi+0x
89) [0x4bcef9]
Fri Nov 25 14:45:54 2011: 0x007f949d1878f0 /lib/libpthread.so.0(+0xf8f0) [0x7f94
9d1878f0]

8
Spanish / Vaciado de cola de mensajes de correo
« on: November 24, 2011, 05:39:35 pm »
¿Hay algun comando que pueda usar para vaciar la cola de mensajes de Postfix?

9
I am planning to open relay for an app server so it can send emails through my
Zentyal email server. In this case, will I still need to use TLS encryption?

It happens that as I am not using a signed certificates some applications get
broken and I finish with an error like this on the Postfix log file
Nov 17 11:49:03 mail postfix/smtpd[10244]: lost connection after STARTTLS from u
nknown[172.19.39.11]

Ref: http://doc.zentyal.org/en/mail.html

10
Installation and Upgrades / Re: Zarafa services suddenly stopped
« on: November 13, 2011, 02:23:05 pm »
My impression is that most users are downloading their email via pop3 most of the time.
So as Zarafa needs to reindex the databases, this causes the load of MySQL.

Appart of that, maybe the software RAID-1 solution is not a good performance solution.

I have to mention that the server became stable only after I disabled mail filter options
(antispam and antivirus). So this makes me think that the amavis-new was also is not the best choice.

Has anybody seen ASSP?

11
Installation and Upgrades / Re: Zarafa services suddenly stopped
« on: November 10, 2011, 07:33:48 pm »
Thank you for the help

Here is the iotop output

Code: [Select]
Total DISK READ: 0.00 B/s | Total DISK WRITE: 505.02 K/s
  TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND
24718 be/4 mysql       0.00 B/s    3.88 K/s  ?unavailable?  mysqld
10550 be/4 syslog      0.00 B/s   15.54 K/s  ?unavailable?  rsyslogd -c4
  328 be/3 root        0.00 B/s   15.54 K/s  ?unavailable?  [jbd2/md2-8]
25666 be/4 openldap    0.00 B/s    3.88 K/s  ?unavailable?  slapd -d ~p/slapd.d/
19100 be/4 openldap    0.00 B/s    3.88 K/s  ?unavailable?  slapd -d ~p/slapd.d/
25305 be/4 mysql       0.00 B/s   15.54 K/s  ?unavailable?  mysqld
21315 be/4 mysql       0.00 B/s    3.88 K/s  ?unavailable?  mysqld
31598 be/4 mysql       0.00 B/s   15.54 K/s  ?unavailable?  mysqld
31599 be/4 mysql       0.00 B/s   19.42 K/s  ?unavailable?  mysqld
31600 be/4 mysql       0.00 B/s    7.77 K/s  ?unavailable?  mysqld
21670 be/4 mysql       0.00 B/s   11.65 K/s  ?unavailable?  mysqld
 3332 be/4 postfix     0.00 B/s    0.00 B/s  ?unavailable?  cleanup -~unix -u -c
 1643 be/4 www-data    0.00 B/s   23.31 K/s  ?unavailable?  apache2 -k start
 9856 be/4 openldap    0.00 B/s    3.88 K/s  ?unavailable?  slapd -d ~p/slapd.d/
22480 be/4 mysql       0.00 B/s    7.77 K/s  ?unavailable?  mysqld

12
Installation and Upgrades / Re: Zarafa services suddenly stopped
« on: November 10, 2011, 07:14:27 pm »
The server is a HP ProLiant DL120 G6 with 4GB of RAM and 2 SATA hard-drives in software RAID-1
BTW in the lists of services you will see the md2_raid1 service running...

13
Installation and Upgrades / Re: Zarafa services suddenly stopped
« on: November 10, 2011, 04:10:50 pm »
I tried /etc/init.d/ebox zarafa restart
but it didn't work.

but this one did
/etc/init.d/zentyal zarafa restart

14
Installation and Upgrades / Re: Zarafa services suddenly stopped
« on: November 09, 2011, 09:22:40 pm »
I have the impression that at certain moments MySQL and Zarafa services have a high CPU usage.

Maybe a tuning is required.

What do you think of the following list of processes?

Code: [Select]
top - 15:30:47 up  1:50,  2 users,  load average: 2.53, 2.31, 2.12
Tasks: 222 total,   2 running, 220 sleeping,   0 stopped,   0 zombie
Cpu(s): 18.6%us,  1.6%sy,  0.0%ni, 58.8%id, 21.1%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   4051728k total,  3633700k used,   418028k free,   162808k buffers
Swap: 11718584k total,        0k used, 11718584k free,  2206192k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
26681 root      20   0 88336 7840 5128 R   56  0.2   0:01.70 zarafa-dagent
 1144 mysql     20   0  406m  57m 8160 S    8  1.5   5:37.53 mysqld
 9016 root      20   0  339m  85m 5984 S    7  2.2   6:09.18 zarafa-server
25664 openldap  20   0  411m  11m 5768 S    4  0.3   0:56.14 slapd
 5523 root      20   0  279m  76m 5044 S    1  1.9   1:08.77 zarafa-indexer
 5703 root      20   0  113m  11m 4504 S    1  0.3   0:48.43 Xorg
 5704 root      20   0  148m  20m 8152 S    1  0.5   0:51.05 lxdm-greeter-gt
    7 root      20   0     0    0    0 S    0  0.0   0:00.15 ksoftirqd/1
  293 root      20   0     0    0    0 S    0  0.0   0:20.72 md2_raid1
  328 root      20   0     0    0    0 S    0  0.0   0:05.45 jbd2/md2-8
  914 servidor  20   0 19328 1512 1064 R    0  0.0   0:01.79 top
  995 syslog    20   0  184m 1828 1036 S    0  0.0   0:05.59 rsyslogd
 1115 asterisk  20   0  922m 218m  11m S    0  5.5   0:02.34 asterisk
    1 root      20   0 61992 3080 1956 S    0  0.1   0:01.26 init
    2 root      20   0     0    0    0 S    0  0.0   0:00.00 kthreadd
    3 root      RT   0     0    0    0 S    0  0.0   0:00.03 migration/0
    4 root      20   0     0    0    0 S    0  0.0   0:00.16 ksoftirqd/0

15
Is anybody else noticing messages like these in this log file?
/var/log/zarafa/server.log

Wed Nov  9 14:22:16 2011: 0x00000001d15ba0: SQL Failed: Deadlock found when trying to get lock; try restarting transaction, Query Size: 72, Query: "INSERT INTO hierarchy (parent, type, flags, owner) values(592, 5, 0, 24)"

BTW,
There are references in Zarafa forums
-> http://goo.gl/b18iT

Pages: [1] 2 3 ... 5