View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004147 | SOGo | OpenChange backend | public | 2017-04-13 14:12 | 2017-05-30 19:30 |
Reporter | Colmar0 | Assigned To | ludovic | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | suspended | ||
Platform | 16.04.2 LTS | OS | Ubuntu | OS Version | 16.04 |
Product Version | 3.2.8 | ||||
Summary | 0004147: Can not start apache2 and mysql start error with ocsmanager.conf configuration | ||||
Description | mysql does not start and apache2 get following error message after trying to start it: Apr 13 15:29:50 sogo-test2 apache2[11330]: * The apache2 configtest failed. | ||||
Additional Information | ocsmanager.conf: [autodiscover] apache2.conf: This is the main Apache server configuration file. It contains theconfiguration directives that give the server its instructions.See http://httpd.apache.org/docs/2.4/ for detailed information aboutthe directives and /usr/share/doc/apache2/README.Debian about Debian specifichints.# Summary of how the Apache 2 configuration works in Debian:The Apache 2 web server configuration in Debian is quite different toupstream's suggested way to configure the web server. This is because Debian'sdefault Apache2 installation attempts to make adding and removing modules,virtual hosts, and extra configuration directives as flexible as possible, inorder to make automating the changes and administering the server as easy aspossible.It is split into several files forming the configuration hierarchy outlinedbelow, all located in the /etc/apache2/ directory:# /etc/apache2/|-- apache2.conf| `-- ports.conf|-- mods-enabled| |-- *.load| `-- *.conf|-- conf-enabled| `-- *.conf`-- sites-enabled`-- *.conf# * apache2.conf is the main configuration file (this file). It puts the piecestogether by including all remaining configuration files when starting up theweb server.# * ports.conf is always included from the main configuration file. It issupposed to determine listening ports for incoming connections which can becustomized anytime.# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/directories contain particular configuration snippets which manage modules,global configuration fragments, or virtual host configurations,respectively.# They are activated by symlinking available configuration files from theirrespective *-available/ counterparts. These should be managed by using ourhelpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. Seetheir respective man pages for detailed information.# * The binary is called apache2. Due to the use of environment variables, inthe default configuration, apache2 needs to be started/stopped with/etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will notwork with the default configuration.Global configuration# # ServerRoot: The top of the directory tree under which the server'sconfiguration, error, and log files are kept.# NOTE! If you intend to place this on an NFS (or otherwise network)mounted filesystem then please read the Mutex documentation (availableat <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);you will save yourself a lot of trouble.# Do NOT add a slash at the end of the directory path.# # The accept serialization lock file MUST BE STORED ON A LOCAL DISK.# # PidFile: The file in which the server should record its processidentification number when it starts.This needs to be set in /etc/apache2/envvars# # Timeout: The number of seconds before receives and sends time out.# # KeepAlive: Whether or not to allow persistent connections (more thanone request per connection). Set to "Off" to deactivate.# # MaxKeepAliveRequests: The maximum number of requests to allowduring a persistent connection. Set to 0 to allow an unlimited amount.We recommend you leave this number high, for maximum performance.# # KeepAliveTimeout: Number of seconds to wait for the next request from thesame client on the same connection.# These need to be set in /etc/apache2/envvarsUser ${APACHE_RUN_USER} # HostnameLookups: Log the names of clients or just their IP addressese.g., www.apache.org (on) or 204.62.129.132 (off).The default is off because it'd be overall better for the net if peoplehad to knowingly turn this feature on, since enabling it means thateach client request will result in AT LEAST one lookup request to thenameserver.# ErrorLog: The location of the error log file.If you do not specify an ErrorLog directive within a <VirtualHost>container, error messages relating to that virtual host will belogged here. If you do define an error logfile for a <VirtualHost>container, that host's errors will be logged there and not here.# # LogLevel: Control the severity of messages logged to the error_log.Available values: trace8, ..., trace1, debug, info, notice, warn,error, crit, alert, emerg.It is also possible to configure the log level for particular modules, e.g."LogLevel info ssl:warn"# Include module configuration:IncludeOptional mods-enabled/.load Include list of ports to listen onInclude ports.conf Sets the default security model of the Apache2 HTTPD server. It doesnot allow access to the root filesystem outside of /usr/share and /var/www.The former is used by web applications packaged in Debian,the latter may be used for local directories served by the web server. Ifyour system is serving content from a sub-directory in /srv you must allowaccess here, or in any related virtual host.<Directory /> <Directory /usr/share> <Directory /var/www/> #<Directory /srv/> Options Indexes FollowSymLinksAllowOverride NoneRequire all granted#</Directory> AccessFileName: The name of the file to look for in each directoryfor additional configuration directives. See also the AllowOverridedirective.# # The following lines prevent .htaccess and .htpasswd files from beingviewed by Web clients.# # The following directives define some format nicknames for use witha CustomLog directive.# These deviate from the Common Log Format definitions in that they use %O(the actual bytes sent including headers) instead of %b (the size of therequested file), because the latter makes it impossible to detect partialrequests.# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.Use mod_remoteip instead.# Include of directories ignores editors' and dpkg's backup files,see README.Debian for details.Include generic snippets of statementsIncludeOptional conf-enabled/*.conf Include the virtual host configurations:IncludeOptional sites-enabled/*.conf vim: syntax=apache ts=4 sw=4 sts=4 sr noetSOGo.conf: Alias /SOGo.woa/WebServerResources/ \ <Directory /usr/lib/GNUstep/SOGo/>
</Directory> Uncomment the following to enable proxy-side authentication, you will thenneed to set the "SOGoTrustProxyAuthentication" SOGo user default to YES andadjust the "x-webobjects-remote-user" proxy header in the "Proxy" sectionbelow.# For full proxy-side authentication:#<Location /SOGo> AuthType XXXRequire valid-userSetEnv proxy-nokeepalive 1Allow from all#</Location> For proxy-side authentication only for CardDAV and GroupDAV from externalclients:#<Location /SOGo/dav> AuthType XXXRequire valid-userSetEnv proxy-nokeepalive 1Allow from all#</Location> ProxyRequests OffProxyRequests OnSetEnv proxy-nokeepalive 1ProxyPreserveHost OnWhen using CAS, you should uncomment this and install cas-proxy-validate.pyin /usr/lib/cgi-bin to reduce server overloading# ProxyPass /SOGo/casProxy http://localhost/cgi-bin/cas-proxy-validate.py<Proxy http://localhost/app/cas-proxy-validate.py>Order deny,allowAllow from your-cas-host-addr</Proxy>ProxyPass /SOGo http://127.0.0.1:20000/SOGo retry=0Enable to use Microsoft ActiveSync supportNote that you MUST have many sogod workers to use ActiveSync.See the SOGo Installation and Configuration guide for more details.# ProxyPass /Microsoft-Server-ActiveSync \http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync \retry=60 connectiontimeout=5 timeout=360<Proxy http://127.0.0.1:20000/SOGo>adjust the following to your configurationRequestHeader set "x-webobjects-server-port" "443"RequestHeader set "x-webobjects-server-name" "sogo-test2.rz.augsburg.de"RequestHeader set "x-webobjects-server-url" "https://sogo-test2.rz.augsburg.de"When using proxy-side autentication, you need to uncomment andadjust the following line:RequestHeader unset "x-webobjects-remote-user"RequestHeader set "x-webobjects-remote-user" "%{REMOTE_USER}e" env=REMOTE_USERRequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"AddDefaultCharset UTF-8Order allow,denyAllow from all</Proxy>For Apple autoconfiguration<IfModule rewrite_module> | ||||
Tags | No tags attached. | ||||
Don't use OpenChange - it is likely set to be removed from SOGo. |
|
Is there any official statement about this? |
|
It was discussed in the mailing list a couple of weeks go. |
|
Who was discussing it? |
|
https://lists.inverse.ca/sogo/arc/users/2017-03/msg00158.html |
|
This discussion seems to be between the sogo users. |
|
I am involved in that discussion. |
|
OpenChange is dead - setting for removal from SOGo. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2017-04-13 14:12 | Colmar0 | New Issue | |
2017-04-13 14:18 | ludovic | Note Added: 0011716 | |
2017-04-13 14:21 | Colmar0 | Note Added: 0011717 | |
2017-04-13 14:23 | ludovic | Note Added: 0011718 | |
2017-04-13 14:36 | Colmar0 | Note Added: 0011721 | |
2017-04-13 14:39 | ludovic | Note Added: 0011722 | |
2017-04-13 14:42 | Colmar0 | Note Added: 0011723 | |
2017-04-13 15:18 | ludovic | Note Added: 0011724 | |
2017-05-30 19:30 | ludovic | Note Added: 0011859 | |
2017-05-30 19:30 | ludovic | Status | new => resolved |
2017-05-30 19:30 | ludovic | Resolution | open => suspended |
2017-05-30 19:30 | ludovic | Assigned To | => ludovic |