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 - scottdr

Pages: [1] 2
Installation and Upgrades / Re: Dovecot Permission Denied stats-writer
« on: February 10, 2022, 10:17:12 pm »
FYI: I managed to cure this by the following:
# cp /usr/lib/dovecot/dovecot-lda /usr/lib/dovecot/dovecot-lda-orig <== Always make a backup
# chgrp dovecot dovecot-lda                                                        <== Change group permission to dovecot (this group has write permissions to lock file)
# chmod 2755 /usr/lib/dovecot/dovecot-lda                                   <== Sets sticky bit so dovecot-lda is run as group=dovecot
# zs mail restart                                                                          <== Restart mail (probably not needed as dovecot-lda is run on a per email basis.

See for details.

I had this issue a few years ago. It is a config file problem. See this Forum post
Hope this helps.
Always make backup copies of the file you are changing.

Other modules / Re: zentyal webadmin
« on: June 10, 2020, 10:33:40 am »
I'm glad you got it sorted. Sorry that I did not get back to you.

Other modules / Re: zentyal webadmin
« on: June 07, 2020, 08:24:19 pm »
Dear hshafi,

That file looks OK. However, you have not answered any of the questions regarding if the process is running "nginx: master process /usr/sbin/nginx -c /var/lib/zentyal/conf/nginx.conf", or if there are any errors reported in /var/log/zentyal/zentyal.log (you could also check /var/log/zentyal/error.log.

Perhaps you could check to see if nginx is listening on the correct ports by running 'sudo lsof |grep 8443' (without the '), you should get an output similar to: -
nginx      13303              root    9u     IPv4              91944       0t0        TCP *:8443 (LISTEN)
nginx      13311          www-data    9u     IPv4              91944       0t0        TCP *:8443 (LISTEN)
nginx      13312          www-data    9u     IPv4              91944       0t0        TCP *:8443 (LISTEN)
nginx      13313          www-data    9u     IPv4              91944       0t0        TCP *:8443 (LISTEN)
nginx      13314          www-data    9u     IPv4              91944       0t0        TCP *:8443 (LISTEN)

If you do get these outputs then you should be able to get to the webadmin pages.

If you get no output, then nginx is not running. Check with  'sudo lsof' just to make sure that there are processes listening on your system

I hope this is of use to you. Please give some extra detail with your next response as it is hard to diagnose your issue without more information.

Other modules / Re: zentyal webadmin
« on: June 04, 2020, 12:00:02 pm »
You did not mention if there were any clues in the Zentyal log file /var/log/zentyal/zentyal.log. Please look at this log as soon as you do the zs webadmin restart command

The webadmin interface is served by nginx. if you run 'ps -ef |grep nginx' (without the ' quotes) you should see output like this below : -

root      13993      1  0 May27 ?        00:00:00 nginx: master process /usr/sbin/nginx -c /var/lib/zentyal/conf/nginx.conf
www-data  14001  13993  0 May27 ?        00:01:19 nginx: worker process
www-data  14002  13993  0 May27 ?        00:00:00 nginx: worker process
www-data  14003  13993  0 May27 ?        00:00:07 nginx: worker process
www-data  14004  13993  0 May27 ?        00:00:26 nginx: worker process

If you do see the above, can you send the contents of /var/lib/zentyal/conf/nginx.conf to check the settings?

Other modules / Re: zentyal webadmin
« on: June 03, 2020, 11:35:09 am »
Can you check /var/log/zentyal/zentyal.log for any clues/errors?
Do you get any errors when doing the zs webadmin start?
For example :  * Restarting Zentyal module: webadmin                                                                                                                                                                                                      [fail]
Error loading class: EBox::SysInfo error: Global symbol "$lastVersion" requires explicit package name (did you forget to declare "my $lastVersion"?) at /usr/share/perl5/EBox/ line 330.
BEGIN not safe after errors--compilation aborted at /usr/share/perl5/EBox/ line 444.
Compilation failed in require at (eval 692) line 1.
BEGIN failed--compilation aborted at (eval 692) line 1.

Thanks to Zentyal briefing to use this feature in the Community version.

Suggested updates to /usr/share/zentyal/smart-admin-report: -

## Server packages

Issue, the report states that there are 1 upgradable packages available when there is no packages in that state.

Line 140: Change "apt list --upgradable 2> /dev/null | wc -l" to "apt list --upgradable 2> /dev/null|awk '{if(NR>1)print}' | wc -l"

# Antivirus module #

Issue, Last ClamAV database update: the output is blank

Line 387  change "grep 'Database updated' /var/log/clamav/freshclam.log | tail -1 | awk '{print $1,$2,$3,$4,$5}'" to "clamscan --version |  awk '{split($0,a,"/");print a[3]}'"

This will detail the database date of the current signatures.

Tested successfully on Zentyal Community Edition Version 6.1.2 running on Ubuntu Linux 18.04.3, running as a VM on Hyper-V.

Added 10-Apr-2020

Line 142 Change "grep -ai zentyal-auto-updater /var/log/syslog | awk '{print $1,$2,$3}' | tail -1" to "grep -ai auto-updater /var/log/syslog | awk '{print $1,$2,$3}' | tail -1"

Line 144 Change "        grep -ai zentyal-auto-updater /var/log/syslog.1 | awk '{print $1,$2,$3}' | tail -1" to "        grep -ai auto-updater /var/log/syslog.1 | awk '{print $1,$2,$3}' | tail -1"

Installation and Upgrades / Re: Webadmin not Accessible
« on: December 10, 2019, 07:15:39 pm »
If you run 'sudo netstat -tulpn | grep nginx' you should get the actual port that you need to connect to,

My example is
"tcp        0      0  *               LISTEN      9189/nginx: master"

So try connecting to your internal IP address with https://<internal_ip>:8443/ and see if you get the webadmin login screen.



I can confirm that the Dashboard only shows users logged into the system either on the console or via a SSH connection. I can't throw any light on the roaming profiles issue.

I have modified /usr/share/zentyal/stubs/sogo/SOGo.conf-apache.mas and changed the line: -

RequestHeader set "x-webobjects-server-url" "https://%{REQUEST_HOST}e:443"

to: -

RequestHeader set "x-webobjects-server-url" "https://%{REQUEST_HOST}e"

Then restarted "SOGo Webmail" from the console.

I made a copy of SOGo.conf-apache.mas before making any changes just in case I made an error.

Hope this helps

Thanks to a CZ site with the answer

I've changed my users shortcuts to go straight to their Inbox URL https://<server-ip>/SOGo/so/<userID>/Mail/view

This seems to work OK.

It would be nice to have a cure, but I ran out of time researching where this NULL addition gets added

 run-parts --report /etc/cron.hourly
Can't locate object method "throw" via package "Can't locate object method "tableInfo" via package "EBox::AntiVirus" at /usr/share/perl5/EBox/ line 321.
" (perhaps you forgot to load "Can't locate object method "tableInfo" via package "EBox::AntiVirus" at /usr/share/perl5/EBox/ line 321.
"?) at /usr/share/zentyal/manage-logs line 31.
run-parts: /etc/cron.hourly/90zentyal-manage-logs exited with return code 25

I would be interested if this means something to those 'perl' experts  :)

Other modules / Re: Logging SMTP connections in Firewall logs
« on: May 29, 2018, 07:05:24 pm »
Firewall logs normally log dropped/rejected packets as a standard. You should see e-mails by locking at the Mail logs (assuming it is enabled), or you can monitor /var/log/mail.log to see connections made to your mail server. mail.log will show all connections to ports 25, 587, as well as IMAP and POP connections.

Zentyal uses Postfix as it's Message Transport Agent (MTA). Normally legitimate e-mails from the Internet will always have a FQDN format. Local PC's or compromised PC's generally will just send the PC name. The restriction is contained in the configuration file /etc/postfix/ and the restriction is  reject_non_fqdn_helo_hostname. This file is created from a master config file in the folder /usr/share/zentyal/stubs/mail. Always make a copy of any file you modify before modifying. I tend to create a copy with the date. e.g. cp In my version of Zentyal 5.1.1 the line to be removed is line 48 "$smtpRecipientRestrictions .= 'reject_non_fqdn_helo_hostname, ';"

After you have changed the line, restart the mail server and check that the reject_non_fqdn_helo_hostname is missing from the new file /etc/postfix/

Hope this helps you.

I am running 4.25 (still on Ubuntu 14.04LTS)
I keep a Network Object list of Banned IP's from mail spammers that try and use us either to send spam or relay. Those servers that continually fail SASL login or use false FQDN get added to this list weekly. A little like Fail2Ban (but I haven't got that to work yet :( )

Can anyone point me to how Zentyal generates this list of objects when selected through the WEB GUI interface where I can add, delete or modify them. I cannot find any text file or SQL table where they are stored and am not Perl savvy enough to work out the code.

Your help would be most appreciated.

Thank you

Pages: [1] 2