Messages

1

Email and Groupware / Re: Zentyal 5 454 4.7.1 relay access denied on virtual domains

« on: March 10, 2017, 04:24:55 pm »

5.0.5 adding <% join(',', @vdomains) %> , which apparently solved this issue for you, has broken something else for me

Mar 10 15:32:28 posta postfix/smtpd[15614]: NOQUEUE: reject: RCPT from localhost[127.0.0.1]: 550 5.1.1 <user@virtual-domain>: Recipient address rejected: User unknown in local recipient table;

my solution: removing vdomains from mydestination https://forum.zentyal.org/index.php/topic,4688.msg105749.html#msg105749
found another IMHO related alternate solution: https://tracker.zentyal.org/issues/5239

Kindly advice, please.

2

Installation and Upgrades / FoundRe: Recipient address rejected: User unknown in local recipient table

« on: March 10, 2017, 03:46:40 pm »

Recently upgraded Zentyal to 5.0, it was some pain, but our main service (postfix) is worked. Mostly. Until today.
Now it`s refuse to send messages to local virtual domain:
"Recipient address rejected: User unknown in local recipient table".

same here, found solution
/usr/share/zentyal/stubs/mail/main.cf.mas

Code: [Select]

mydestination = $myorigin,$myhostname,localhost,localhost.$mydomain,<% join(',', @vdomains) %>
does not play nice with virtual_mailbox_domains

my fix was copy the stub to custom one and remove the vdomains
/etc/zentyal/stubs/mail/main.cf.mas

Code: [Select]

mydestination = $myorigin,$myhostname,localhost,localhost.$mydomain

EDIT: found alternate solution in the tracker https://tracker.zentyal.org/issues/5239

3

Installation and Upgrades / Re: sogod consumes all the RAM available

« on: September 17, 2015, 01:32:02 pm »

Confirmed occurrence on Zentyal 4.1, SOGo 2.3.1, after en masse switch to sogo webmail usage

in /var/log/sogo/sogo.log memory-hungry process PID's logs
Sep 14 11:07:34 sogod [8883]: 192.168.106.2 "GET /SOGo/ HTTP/1.1" 200 4281/0 0.036 11290 62% -748K
Sep 14 11:07:39 sogod [8883]: <0x0x7ff663705cf8[NGImap4Client]> Note: no key found for sorting, using 'DATE': (null)
Sep 14 11:08:38 sogod [5475]: [WARN] <0x0x7ff662ed87b8[WOWatchDogChild]> pid 8883 has been hanging in the same request for 1 minutes
Sep 14 11:09:38 sogod [5475]: [WARN] <0x0x7ff662ed87b8[WOWatchDogChild]> pid 8883 has been hanging in the same request for 2 minutes
and the warning about hangup repeats every minute. This happened for every client (web interface mostly) that was rejected with
"No child available to handle incoming request!". For me it was not related to user profile, it seems.

I've implemented a solution from this thread (20 workers in the stub sogo.mas), everything seems to be back to normal now. You really got me out of a pickle.

An amusing desperate measure:
To keep the server alive, I kept killing those frozen processes

Code: [Select]

tail -f /var/log/sogo/sogo.log | grep --line-buffered  "1 minute" | sed -u 's/^.*pid\ //' | sed -u 's/\ .*//' | while read proces; do kill -9 $proces; echo -n "Delikvent: "$proces" " ; date ; done

4

Installation and Upgrades / Re: 4.0 iso boot issue in Gen 2 Hyper-V

« on: September 17, 2015, 08:56:25 am »

Since this post I have abandoned installing from Zentyal Installer iso. Solution for me was installing minimal Ubuntu 14.04 into Gen2. I have followed "Best Practices for running Linux on Hyper-V" and then installed Zentyal from repositories using instructions from Installation Guide.

5

Installation and Upgrades / Re: 4.0 iso boot issue in Gen 2 Hyper-V

« on: November 04, 2014, 07:18:21 am »

Did you do a MD5 check on the ISO to make sure the file is ok?

Thank you for the response. Of course I did. Moreover - the iso boots fine in Gen1...

6

Installation and Upgrades / [SOLVED] 4.0 iso boot issue in Gen 2 Hyper-V

« on: October 31, 2014, 11:32:49 am »

Hello, Everyone.

I have a problem booting from x64 iso of Zentyal 4.0, when I set up a Generation 2 virtual machine in Hyper-V 2012R2 for new installation, even with Secure Boot turned off. In Generation 1 the same iso booted with no problem.

With Ubuntu Server 14.04LTS there were no issues booting in Generation 2.

Any ideas as to why is this a problem for Zentyal?

Thank you.


ITMakovec