The configured LOGFILE can not be modified.

BMWfan

Hey @ all,

iam trying to install z-push but i get this error in the meantime:

PHP Warning:  touch(): Unable to create file /var/log/z-push/z-push.log because Permission denied in /usr/share/z-push/lib/core/zpush.php on line 251
FatalMisconfigurationException: The configured LOGFILE can not be modified.
-e When upgrading from an earlier version you need to run 'z-push-admin -a fixstates'.

It seems the execution on setup has failed (see error above). Please fix the issue and run the command manually.

More information at https://wiki.z-hub.io/x/R4Ea

The command z-push-admin -a fixstates gives me the same error:

FatalMisconfigurationException: The configured LOGFILE can not be modified.

How can i fix this?

Best Regards

Daniel

fbartels

needs more info:

how did you try to install?
which os?

the obvious thing should be to allow your webserver write access to /var/log/z-push, but this should have been done by the packages automatically.

BMWfan

Thank you for your reply and Merry Christmas :-)

OS: Debian 9

I installed it over apt-get as described here: https://wiki.z-hub.io/display/ZP/Installation

I was wondering also why the Rights are not assigned after i installed it over the packet manager (apt-get).

Best Regards

Daniel

fbartels

So the issue is gone after using packages? In case you are using Apache, did you install the Apache config package?

BMWfan

@fbartels no, sorry for the bad explanation. I installed it over apt-get but have this problem (still).

fbartels

Can you show which packages you have actually installed? (e.g. dpkg - l | grep z-push)

itserv

This should be a simple one.

Make sure the directory defined in /etc/z-push/z-push.conf.php is writeable by your webserver, and remove (or chown) the files in the directory to www-data:www-data.

Here is my setting:

root@exchange64:~# grep -n LOGFILE /etc/z-push/z-push.conf.php 
110:    // The data will be saved into a dedicated file per user in the LOGFILEDIR
121:    define('LOGFILEDIR', '/var/log/z-push/');
122:    define('LOGFILE', LOGFILEDIR . 'z-push.log');
123:    define('LOGERRORFILE', LOGFILEDIR . 'z-push-error.log');

and

root@exchange64:~# ls -al /var/log/z-push/
total 213396
drwx------  2 www-data www-data      4096 Oct  5 09:33 .                       <---- This is critical
drwxr-xr-x 12 root     root          4096 Aug 30 06:25 ..
-rwx------  1 www-data www-data      2131 Nov  6 10:53 autodiscover-error.log
-rwx------  1 www-data www-data     17162 Nov  6 10:53 autodiscover.log
-rwx------  1 www-data www-data  56271690 Oct  5 15:31 spam-54b5b86d397d4a7285ff1f6ee601b834.log
-rwx------  1 www-data www-data   8397562 Nov 12 10:29 spam.log
-rwx------  1 www-data www-data 112765363 Dec 28 11:59 spam-nine0c2f371d7682.log
-rwx------  1 www-data www-data    245208 Dec 28 11:58 z-push-error.log
-rwx------  1 www-data www-data       786 Aug 30 06:07 z-push-error.log.1.gz
-rwx------  1 www-data www-data       649 Aug 28 14:31 z-push-error.log.2.gz
-rwx------  1 www-data www-data       534 Aug 27 14:33 z-push-error.log.3.gz
-rwx------  1 www-data www-data      1400 Aug 25 17:31 z-push-error.log.4.gz
-rwx------  1 www-data www-data  40485152 Dec 28 12:02 z-push.log
-rwx------  1 www-data www-data     50794 Aug 30 06:24 z-push.log.1.gz
-rwx------  1 www-data www-data     61992 Aug 29 06:22 z-push.log.2.gz
-rwx------  1 www-data www-data     55466 Aug 28 06:24 z-push.log.3.gz
-rwx------  1 www-data www-data     24586 Aug 27 06:24 z-push.log.4.gz

BMWfan

@fbartels said in The configured LOGFILE can not be modified.:

dpkg - l | grep z-push

ii  z-push-autodiscover                        2.4.5+0-0                                  all          Z-Push autodiscover
ii  z-push-backend-kopano                      2.4.5+0-0                                  all          Z-Push Kopano backend
ii  z-push-common                              2.4.5+0-0                                  all          open source implementation of the ActiveSync protocol
ii  z-push-config-apache                       2.4.5+0-0                                  all          Z-Push apache configuration
ii  z-push-ipc-sharedmemory                    2.4.5+0-0                                  all          Z-Push ipc shared memory provider
ii  z-push-kopano                              2.4.5+0-0                                  all          Z-Push for Kopano

Daniel,

try to run this commands:

chmod 755 /var/lib/z-push /var/log/z-push
chown www-data:www-data /var/lib/z-push /var/log/z-push

Now restart apache2 and see if it works.

BMWfan

@WalterHof i’ve already done this and it works, but i think fbartels wants to find out the reason why its not setting the rights automatically.

Nevertheless, thanks for your help.

Daniel,

this is an already known bug, I reported this bug many months ago - but it was not fixed up to today. I see this bug on every new installation and sometimes with upgrades.

fbartels

I have to disagree on the “known bug”. I see no problems with our packaging when deploying a fresh test system. I was therefore more searching for the “bug” in user behaviour ;-)

I see this on most installations and sometimes with upgrades.

Forgotten,
I fix this with the two lines mentioned above, so for me it is not longer an issue.

fbartels

This is btw the place where the packaging sets these permissions (for Debian based platforms): https://stash.z-hub.io/projects/ZP/repos/z-push/browse/build/deb/debian.z-push-config-apache.postinst#27-36,43-44

BMWfan

For me is the problem fixed, but nevertheless it was not functioning inbetween of the installation process.

mcdaniels

@WalterHof said in The configured LOGFILE can not be modified.:

chown www-data:www-data /var/lib/z-push /var/log/z-push

same for me : new installation -> Debian 9

fbartels

@mcdaniels Can you show which packages you have actually installed? (e.g. dpkg - l | grep z-push)

mcdaniels

@fbartels
sure:
z-push-backend-kopano 2.5.1+0-0
z-push-common 2.5.1+0-0
z-push-config-apache 2.5.1+0-0
z-push-ipc-sharedmemory 2.5.1+0-0
z-push-kopano 2.5.1+0-0

fbartels

@mcdaniels in that case you should not have had the need to chown the directory, as this action is part of the postinst action of z-push-config-apache.