2.5.0 beta1 - Errors in z-push-top.php
-
I am also getting the same error reported from active connections
08/04/2019 12:01:42 [11572] [FATAL] [myUser] [myDevice] Fatal error: /usr/share/z-push/backend/ipcsharedmemory/ipcsharedmemoryprovider.php:44 - Declaration of IpcSharedMemoryProvider::__construct($type, $allocate, $class) must be compatible with IIpcProvider::__construct($type, $allocate, $class, $serverKey) (64)
-
In both cases - z-push-top.php and real connections, adding a 4th parameter ($serverKey) to the constructor eliminates the error
public function __construct($type, $allocate, $class, $serverKey) {but, as I don’t know what it is used for, I don’t know if there is any other code that is needed to handle it.
-
Hi liverpoolfcfan,
which repository are you using? It looks like something went wrong during the upgrade.
IpcSharedMemoryProvider constructor already has the serverKey parameter:
Manfred
-
This is the content of the z-push.repo file
[z-push]
name=Z-Push noarch Enterprise Linux 7 - $basearch
baseurl=http://repo.z-hub.io/z-push:/pre-final/RHEL_6_PHP_56
failovermethod=priority
enabled=1
gpgcheck=0 -
Hi liverpoolfcfan,
I’ve dowloaded the rpm from http://repo.z-hub.io/z-push:/pre-final/RHEL_6_PHP_56 and also there IpcSharedMemoryProvider constructor already has the serverKey parameter.
Manfred
-
Hi Manfred,
I have checked the repo download and I too can see the $serverKey is in there. However, it looks like that version is not getting pulled down to my system.
When I run z-push-top.php it reports version number 2.5.0.beta1+0
The rpm file is labeled with version 2.5.0.beta1+0-215
If I run yum update it checks the repository but does not pull down the newer file.
Could there be a switch that wasn’t flicked to publish the newer update?
-
Hi liverpoolfcfan,
$serverKey was there in the constructor of ipcsharedmemory since 2.5.0.beta1+0. I’m not aware of any switches.
Could you try if this happen with the final repository as well?
Manfred
-
I ran “yum update” a couple of days ago (and again just now) - I am still using the pre-final repository. For now z-push-top shows
Z-Push: 2.5.0.beta1+58
Is this as expected?
-
Hi Vincent,
I’ve tagged the release/2.5 branch with 2.5.1.beta0 after 2.5.0 final release, but it looks like the build system didn’t trigger and hasn’t picked up the changes. I’ve run the services manually and pre-final repository now contains Z-Push 2.5.1.beta0+0.
Manfred
-
I will try another “yum update” and let you knoow what happens.
-
Hi liverpoolfcfan,
you probably have to install z-push-ipc-sharedmemory package: https://forum.kopano.io/post/13506
Manfred
-
That worked. Now showing Z-Push: 2.5.1.beta0+0
Is ip-sharedmemory package just packaging up a file I already have on my system from the pre-package days?
-
@liverpoolfcfan said in 2.5.0 beta1 - Errors in z-push-top.php:
That worked. Now showing Z-Push: 2.5.1.beta0+0
Is ip-sharedmemory package just packaging up a file I already have on my system from the pre-package days?
Yes.
Manfred
