Prepare for the EWS / grommunio 2023.11.1 release
The current Debian package: grommunio-sync_2.0.38.12b2e4f-0_all.deb contains the new log file locations in crommunio-sync.conf:
location /Microsoft-Server-ActiveSync {
alias /usr/share/grommunio-sync/index.php;
access_log /var/log/nginx/nginx-sync-access.log;
error_log /var/log/nginx/nginx-sync-error.log;
...
- Edited
Sorry for being too unspecific: My issue is not with grommunio-sync.
root@:~# nginx -T | grep /var/log/grommunio/
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
access_log /var/log/grommunio/nginx-admin-access.log;
error_log /var/log/grommunio/nginx-admin-error.log;
access_log /var/log/grommunio/nginx-admin-access.log;
error_log /var/log/grommunio/nginx-admin-error.log;
error_log /var/log/grommunio/nginx-error.log;
access_log /var/log/grommunio/nginx-access.log;
Shouldn´t the update also provide new versions of the conf files in /etc/nginx/conf.d or do I need to update them manually?
No big deal at all, I just want to make shure if all the updates have been pushed to Debian 12 already.
nope, doesn´t help unfortunately.
Debian 12 repository does also have the grommunio-sync_2.0.38.12b2e4f-0_all.deb
, this should be good.
Which version of grommunio-common
contains the new logrotate stuff and the /etc/nginx/conf.d/grommunio.conf
, which points to the /var/log/nginx/
log folder?
I have grommunio-common 21.8eb9e0e-1+34.1
installed, but even with this, my /etc/nginx/conf.d/grommunio.conf
points to the /var/log/grommunio/
log folder. So either it is not overwritten when the package is installed or the Debian package in that version still points to the old location.
Nothing to really worry, I can easily fix this in the config file. It simply looks a bit strange to me.
- Edited
I think I got it: I modified /etc/nginx/conf.d/grommunio.conf
to adjust the port numbers.
It seems that the file is then completely skipped in the update. I would have expected at least a /etc/nginx/conf.d/grommunio.conf.dpkg-new
being created - but this is not the case.
Would be great if the packages could be adjusted so that at least dpgk-new files are written for all that lives under /etc. For the files where changes are more likely, I would even suggest to ask the admin if the file should be kept or overwritten when the installation is running.
On the Appliance, the directory /etc/nginx/conf.d contains two files, the file: grommunio.conf with content:
cat /etc/nginx/conf.d/grommunio.conf
include /usr/share/grommunio-common/nginx.conf;
/usr/share/grommunio-common/nginx.conf includes /usr/share/grommunio-common/nginx/upstreams.d/*.conf;
cat /usr/share/grommunio-common/nginx.conf
include /etc/grommunio-common/nginx/upstreams.d/*.conf;
include /usr/share/grommunio-common/nginx/upstreams.d/*.conf;
error_log /var/log/nginx/nginx-error.log;
access_log /var/log/nginx/nginx-access.log;
...
In /usr/share/grommunio-common/nginx/upstreams.d/ we find the corresponding include files:
ls -l /usr/share/grommunio-common/nginx/upstreams.d/
total 16
-rw-r--r-- 1 root root 75 Aug 3 12:03 grommunio-dav.conf
-rw-r--r-- 1 root root 77 Aug 24 21:02 grommunio-sync.conf
-rw-r--r-- 1 root root 75 Oct 31 16:14 grommunio-web.conf
-rw-r--r-- 1 root root 52 Oct 25 19:00 gromox.conf
This should be the same on Debian - I hope so.
No definitely not!
As I wrote above, I had the old log folder in /etc/nginx/conf.d/grommunio.conf
and I´m quite certain that this file was skipped from being updated because I modified it.
I now manually adjusted the log paths in this file and it is all good.
weini Would be great if the packages could be adjusted so that at least dpgk-new files
dpgk-new files will only be created, if the configuration file was modified by an admin and a new configuration file exists. In this case, there is now new configuration file for /etc/nginx/conf.d/grommunio.conf.
Sure, this was the /etc/nginx/conf.d/grommunio.conf
before I modified the log paths manually:
include /etc/grommunio-common/nginx/upstreams.d/*.conf;
include /usr/share/grommunio-common/nginx/upstreams.d/*.conf;
error_log /var/log/grommunio/nginx-error.log;
access_log /var/log/grommunio/nginx-access.log;
map $http_user_agent $filter_user_agent {
default 'unknown';
~(iPhone|iPad) ios;
~Android android;
~Linux linux;
~(Windows|MSIE|Mozilla) windows;
~Mac macos;
~(FreeBSD|OpenBSD|NetBSD) bsd;
~Outlook outlook;
~Thunderbird thunderbird;
}
map $http_host $this_host {
"" $host;
default $http_host;
}
map $http_x_forwarded_proto $the_scheme {
default $http_x_forwarded_proto;
"" $scheme;
}
map $http_x_forwarded_host $the_host {
default $http_x_forwarded_host;
"" $this_host;
}
map $http_upgrade $proxy_connection {
default upgrade;
"" close;
}
map $request_uri $topdir {
~(?<captured_topdir>^/[a-zA-Z0-9]+/[a-zA-Z0-9]+)[/] $captured_topdir;
}
server {
listen 20080;
listen [::]:20080;
server_name _;
return 301 https://$host$request_uri;
include /usr/share/grommunio-common/nginx/traffic_status_params*.conf;
}
server {
server_name _;
listen [::]:20443 ssl http2;
listen 20443 ssl http2;
#use real id and not from apache2 reverse proxy
real_ip_header X-Forwarded-For;
set_real_ip_from 127.0.0.1;
include /etc/grommunio-common/nginx/ssl_*.conf;
include /usr/share/grommunio-common/nginx/ssl_params.conf;
include /usr/share/grommunio-common/nginx/proxy_params.conf;
include /usr/share/grommunio-common/nginx/security.conf;
include /usr/share/grommunio-common/nginx/brotli-params*.conf;
include /usr/share/grommunio-common/nginx/traffic_status_params*.conf;
include /etc/nginx/conf.d/grommunio_custom-*.conf.include;
server_tokens off;
include /etc/grommunio-common/nginx/locations.d/*.conf;
include /usr/share/grommunio-common/nginx/locations.d/*.conf;
}
Please show the content of /usr/share/grommunio-common/nginx/upstreams.d/ with:
ls -l /usr/share/grommunio-common/nginx/upstreams.d/
Now I understand!
You are fully right, it was me tweaking my setup and causing the issue.
When adjusting my configuration, I moved some content from /usr/share/
into the conf files residing in /etc
as I needed to do some modification due to my reverse proxy setup in front of nginx.
So it is obvious why my configuration was not updated.
So sorry for stealing your time and many thanks for pointing me to the issue.
Thanks, @WalterH , for providing this information. Very much appreciated.
BTW: why did the developers decide to use non-specfic file names such as nginx-access.log
instead of package specific names such as grommunio-access.log
? My server is not just running grommunio. Can I rise this issue somewhere?
This commit clarifies how to enable EWS: https://github.com/grommunio/gromox/commit/6e623631ccc32226fd1019add12e08aba2eb8e17 for testing.
- Edited
Na dann bin ich auf die Release-Notes gespannt.
Konnte aber trotzdem nicht warten! Die neuen Icons im "Breeze"- Thema der WEB-GUI sind super.
Auf meinem Mac konnte ich ein Apple-Mail Konto einrichten, aber Apple Mail stürzt jedes Mal nach ca. 2 Sekunden ab. Kurz kann man einen gefüllten und aktuellen Posteingang erblicken, dann folgt der Absturz. Das warten wir mal wie gesagt ab!