latest build missing libgsoapssl++-kopano

fbartels

@soenke-martens said in latest build missing libgsoapssl++-kopano:

any news on the centos build?

No, unfortunately our build system is currently blocking this.

@soenke-martens said in latest build missing libgsoapssl++-kopano:

Can i download an older but working version somewhere?

We are not keeping archives of the master downloads, but our official releases are still available for this os.

soenke.martens

Hi @fbartels , you’ve added a EPEL version of RHEL7 kopano-core :)
Looks promising!
best regards, Sönke

@soenke-martens

When can we use the kopano epel source?

@ckruijntjens

@fbartels is it correct that the epel version is still missing this package?

longsleep

@ckruijntjens said in latest build missing libgsoapssl++-kopano:

@fbartels is it correct that the epel version is still missing this package?

Some packages (including python3-daemon) were missing from the publish job and were just added. So dependency wise, RHEL_7_EPEL_7 should now install fine.

This repository requires EPEL_7 for Python 3.6 and in case PHP is required (like for Kopano Webapp or Z-Push), things are build with PHP 7.3 from the Remi repository. See https://blog.remirepo.net/pages/Config-en which also contains instructions how to add EPEL_7.

Any feedback on these packages is greatly appreciated.

@longsleep @fbartels

I could upgrade to latest kopano version. I also upgraded php5 to php 7.3 now all services are start but i get an error 500 with the webapp. The following error is logged by apapche:

PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/lib64/php/modules/kopano_smime.so’ (tried: /usr/lib64/php/modules/kopano_smime.so (/usr/lib64/php/modules/kopano_smime.so: undefined symbol: _zval_dtor_func), /usr/lib64/php/modules//usr/lib64/php/modules/kopano_smime.so.so (/usr/lib64/php/modules//usr/lib64/php/modules/kopano_smime.so.so: cannot open shared object file: No such file or directory)) in Unknown on line 0

how can this be fixed?

longsleep

@ckruijntjens

@ckruijntjens said in latest build missing libgsoapssl++-kopano:

/usr/lib64/php/modules/kopano_smime.so’

The SMIME plugin does not work in this repository yet. So either remove or disable it for now.

This post is deleted!

This post is deleted!

This post is deleted!

This post is deleted!

for your info it had to do with the .htaccess file. this is not revognised

<IfModule mod_php5.c>
php_value post_max_size 5000M
php_value upload_max_filesize 5000M

@fbartels i think i found an error after the upgrade i cannot restore from backup.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “/usr/lib/python3.6/site-packages/kopano/service.py”, line 192, in start
_daemon_helper(self.main, self, self.log)
File “/usr/lib/python3.6/site-packages/kopano/service.py”, line 47, in _daemon_helper
func()
File “/usr/lib/python3.6/site-packages/kopano_backup/init.py”, line 384, in main
self.restore(data_path)
File “/usr/lib/python3.6/site-packages/kopano_backup/init.py”, line 461, in restore
for folder in restore_root.folders():
SystemError: <built-in function delete_IMAPITable> returned a result with an error set

longsleep

@ckruijntjens said in latest build missing libgsoapssl++-kopano:

@fbartels i think i found an error after the upgrade i cannot restore from backup.

The above exception was the direct cause of the following exception:

You only pasted the one of the exceptions. Can you please also post the exception before since that one might bring more light into this.

@longsleep

Hi guys @fbartels

This is the full error.

@longsleep @fbartels

Any news on the kopano restore email item error above?

@fbartels

Am i doing something wrong? Yust upgraded to the latest version but sill can not restore an item with kopano-backup?

@longsleep @fbartels

Any response?

fbartels

@ckruijntjens sorry, I have not made any tests with these binaries myself, therefore I cannot answer your questions.

@fbartels

Thank you for your reply. I will watch the issue and see if it will be resolved in the next update otherwise i will make a test setup to see if the issue is also there