[BlueOnyx:24931] Re: 5210R on AlmaLinux: z-push not working

[Michael Stauber]

Hi Andreas,

> thank you for the php-imap packet. The errors complaining about the missing module are gone now.
> Unfortunately we still didn't manage to get z-push working. We are now getting warnings like:
> 
> [ WARN] [XXXX] /usr/sausalito/ui/web/z-push/lib/syncobjects/syncobject.php:310 Array to string conversion (8)
> and
> [ WARN] [XXXX] /usr/sausalito/ui/web/z-push/lib/core/streamer.php:237 Array to string conversion (8)
> 
> Is there anyone who has z-push running on 5210R?
> 
> Maybe the installed z-push version is simply not PHP 7 compatible?
> Currently we have version 2.1.3, but it seems that support for PHP 7 was introduced with version 2.3.4:
> https://z-push.org/z-push-2-3-4-final-released/
And that's where my quiet Friday evening went right out of the window. ;-)

Yeah, you're right. This was an oversight. When I rolled up 5210R I made
a note to "fix Z-Push" and promptly forgot. So it got shipped with the
same "blueonyx-z-push" RPM that 5209R had. And of course the differences
in PHP versions (5.4 vs 7.2) made this an instant bust.

I went through the Z-Push site and repositories with a fine toothed comb
and what they have there is a bit of a mess.

The latest stable Z-Push is 2.6.2+0-122 and their install documentation
covers RHEL up to RHEL7.

The repositories have RPMs and the SRPM for RHEL8, *but* these seem to
be experimental. In fact the IMAP backend doesn't work due to the
absence of the RPM "php-awl", which is only present in the RHEL7
repository. Yet: I found the SRPM for that and built an RHEL8 version of
it, which seems to work. At least it doesn't throw any hideous PHP
version related errors.

Between the old version on 5209R that we shipped and this new
2.6.2+0-122 there are a legion of changes in regards to what goes where,
different/new config options, new Apache/Nginx related config snippets
and what not.

After a ton of fiddling, mending and some virgin sacrifices I managed to
cobble something together that *may* work.

I just rolled up YUM Updates for 5210R and pushed this out, although I
am NOT sure if it will work. As the whole Z-Push shebang only kicks in
when Z-Push is enabled via the GUI (which it normally isn't) I chose to
publish it right away and as is instead of dropping it into the
BlueOnyx-Testing repository first.

So please do a "yum clean all" and "yum update" on your 5210R and let me
know how this new Z-Push behaves for you. There *may* be config options
that still need to be tweaked in order to get it to work or perhaps
there is some room for further optimization.

You'll find the configs in /etc/z-push/ and the logfiles for Z-Push are
at these locations:

/var/log/z-push/z-push-error.log
/var/log/z-push/z-push.log

The way it works now is this:

If Z-Push is enabled via the GUI, the config files ...

/etc/admserv/conf.d/z-push.conf
/etc/httpd/conf.d/z-push.conf

... get created and this enables Z-Push on AdmServ and Apache. Apache
just does Proxies the requests to AdmServ via Localhost.

If Z-Push is disabled, then /etc/admserv/conf.d/z-push.conf gets
modified to drop all Z-Push redirects and it denies web access to the
directory where the Z-Push web content is located.

Additionally: If Z-Push is disabled, then /etc/httpd/conf.d/z-push.conf
will be deleted in case it is present. That removes the Proxy part of
the equation.

Like said: This is a bit experimental and I'd appreciate it, if you
could take a look and let me know what you find and how it works for you.

-- 
With best regards

Michael Stauber