Page 1 of 1

OpenEMM 2019 on openSuSE Tumbleweed?

Posted: Tue Aug 13, 2019 2:56 pm
by hwcgdt
Hello OpenEMM Admins :D

In the post "Install OpenEMM 2019 on Debian" you mention, that a SuSE Installation is possible (at least from the developers own tests).
Can I have a instruction document - or at least some hints, because the installer scripts does (obviously) not work and some packages have different names.

My Server is running a very up-to-date openSuSE Tumbleweed, hosting my websites (including HTTPS), a Mailserver (including TLS), and other services - so I like to add OpenEMM 2019, because the old version (OpenEMM 2013) is complaining about updates.

Thanks

Re: OpenEMM 2019 on openSuSE Tumbleweed?

Posted: Tue Aug 13, 2019 6:49 pm
by maschoff
We just finished polishing the source code of OpenEMM 2019, but we have not started our tests with Suse, yet. But we will do so after summer vacation.

I could imagine that several Suse tips for OpenEMM 2015 still apply for OpenEMM 2019, because while the GUI has changed a lot, the backend, which is distribution dependent, has not so much. The old 2015 docs are still available at SourceForge: https://sourceforge.net/projects/openem ... rsions%29/

If you have specific problems with Suse, feel free to ask here. Maybe we or other readers can help.

Re: OpenEMM 2019 on openSuSE Tumbleweed?

Posted: Sun Aug 18, 2019 6:39 pm
by hwcgdt
Hi Maschoff

so now I installed packages, configured as much as I could, ignored the openemm-Installer and started

Code: Select all

/usr/bin/python "./OpenEMMInstaller.py"
manually.
With the configurator I could define all setups for setenv.sh, cfgdb and emm.additional.properties.
But thats it.
The database and webapps is still empty - nothing happens.
and now when I try to start the installer.py again it complains about:

Code: Select all

No MTA (sendmail or postfix) is installed. Please install some.
But this server runs my mailserver with several domains, so I'm pretty sure that this is a false positive.

The 2015 docs didn't help, because there was a lot changing - especially an upgrade of the existing 2013 DB is no longer available(?).

Any ideas?

Thanks

Re: OpenEMM 2019 on openSuSE Tumbleweed?

Posted: Mon Aug 19, 2019 2:35 pm
by maschoff
The error message for the missing MTA is probably because the name of mailserver packages are different between RedHat and Suse. So, if your are sure, your mail server is working (any activity in /var/log/maillog?) you may ignore this message.

If you call menu 1 of the OpenEMMInstaller, do you get any hints indicating problems?

edit: I just put Suse support on the roadmap to show that we are serious about it: https://wiki.openemm.org/doku.php?id=start#roadmap

Re: OpenEMM 2019 on openSuSE Tumbleweed?

Posted: Tue Aug 20, 2019 6:13 am
by hwcgdt
Hello maschoff

ignore is not that easy, because next line is a sys.exit(1), I had to delete that line to make it work.
Yes the mailserver is up and running, I send and receive emails.

The Installer with menu status says:

Code: Select all

==========================
= OpenEMM Installer v2.2 =
==========================
Host: server5
Runtime Version: 19.07.011
Manual Version: Unknown
OpenEMM Version: Unknown
System-Url: Unknown
OpenEMMBackend Version: Unknown

Current menu: Show OpenEMM status

OpenEMM status:
Command 'backend.sh status' returned non-zero exit status 127
OS version: Welcome to openSUSE Tumbleweed 20190809 - Kernel \r (\l).

eno1: \4{eno1} \6{eno1}
enp24s0: \4{enp24s0} \6{enp24s0}


Web console: https://localhost:9090/
Python version: 2.7.16 (default, Mar 04 2019, 07:13:50) [GCC]
NO MTA (sendmail or postfix) found
DB client version: /usr/bin/mysql  Ver 15.1 Distrib 10.3.17-MariaDB, for Linux (x86_64) using readline 5.1
Database Connection: OK
Database version: MariaDB 10.3.17-MariaDB
OpenEMM database structure does NOT exist
Currently running database threads ratio (Current: 6, Maximum: 2): 3.0
Java version: 1.8.0_222 (OpenJDK)
Java JCE Unlimited-Key-Strength: OK
Tomcat version: 9.0.21.0
Wkhtml version: wkhtmltopdf 0.12.4
OpenEMMApplication is NOT running
Error while checking for Backend running
Exception: Command 'backend.sh status' returned non-zero exit status 127
Error: <class 'subprocess.CalledProcessError'>

So as you can also see:
Database can be connected but the openemm db is empty.
I was also looking for some sql files, but I can't find them. I also see that the webapps directory is empty and therefore tomcat is dying, complaining about missing directories.
It looks as if there was a step missing, when the Installer started, but at the moment I don't see where...

Thanks

Re: OpenEMM 2019 on openSuSE Tumbleweed?

Posted: Tue Aug 20, 2019 11:05 am
by hwcgdt
Hello maschoff

I got new Information.
Now I installed a new RedHat7 server, following the steps from
https://wiki.openemm.org/doku.php

And I got the same Problems:

Code: Select all

==========================
= OpenEMM Installer v2.2 =
==========================
Host: ld9t0074.umobi.mobicorp.test
Runtime Version: 19.07.011
Manual Version: Unknown
OpenEMM Version: Unknown
System-Url: Unknown
OpenEMMBackend Version: Unknown

DB structure does not exist. (Maybe OpenEMM is not installed)
Mandatory emmProperties file is missing (Maybe OpenEMM is not installed): /home/openemm/webapps/emm/WEB-INF/classes/emm.properties
Mandatory emmWsProperties file is missing (Maybe OpenEMM Webservices is not installed): /home/openemm/webapps/webservices/WEB-INF/classes/emm-ws.properties

Current menu: Main

Please choose (Blank => Quit):
 1. Show OpenEMM status
 2. Configuration
 3. Security
   (Install or update package from AGNITAS Website) not available
 4. Install or update package from local file
   (Install or update package from AGNITAS Cloud) not available
 5. Restart OpenEMM
   (Send configuration and log files in email) not available
 0. Quit
 >
This is the Status output:

Code: Select all

==========================
= OpenEMM Installer v2.2 =
==========================
Host: ld9t0074.umobi.mobicorp.test
Runtime Version: 19.07.011
Manual Version: Unknown
OpenEMM Version: Unknown
System-Url: Unknown
OpenEMMBackend Version: Unknown

Current menu: Show OpenEMM status

OpenEMM status:
Command 'backend.sh status' returned non-zero exit status 127
OS version: Red Hat Enterprise Linux Server release 7.6 (Maipo)
Python version: 2.7.5 (default, Jun 11 2019, 12:19:05)  [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
Postfix Version: 2.10.1
DB client version: /bin/mysql  Ver 15.1 Distrib 5.5.60-MariaDB, for Linux (x86_64) using readline 5.1
Database Connection: OK
Database version: MariaDB 5.5.60-MariaDB
OpenEMM database structure does NOT exist
Currently running database threads ratio (Current: 1, Maximum: 1): 1.0
Java version: 1.8.0_212 (OpenJDK)
Java JCE Unlimited-Key-Strength: OK
Tomcat version: 9.0.21.0
Wkhtml version: wkhtmltopdf 0.12.5 (with patched qt)
OpenEMMApplication is NOT running
Error while checking for Backend running
Exception: Command 'backend.sh status' returned non-zero exit status 127
Error: <class 'subprocess.CalledProcessError'>

And if I look into the DB - it is empty
Same with /home/openemm/webapps

Is there something missing in the openemm-runtime-19.07.011.tar.gz package?
Because if I grep for sql into OpenEMMInstaller.py
I also see
fullDbScriptSuccess = Utilities.executeSqlScriptFile(Environment.applicationUserWebappsDirectory + "/emm/WEB-INF/sql/mysql/emm-mysql-fulldb-basic.sql")

which is the sql to fill the DB?
So when the /home/openemm/webapps/emm is missing, the whole installation will fail?

TNX

Re: OpenEMM 2019 on openSuSE Tumbleweed?

Posted: Tue Aug 20, 2019 4:37 pm
by maschoff
Looks like you have neither installed the openemm backend nor the openemm frontend. Try menu 4 and see what you are offered for installation.

Re: OpenEMM 2019 on openSuSE Tumbleweed?

Posted: Fri Sep 06, 2019 8:09 pm
by hwcgdt
Hello maschoff

you are right. I misunderstood the options y/N, cancel when coming to the upgrade/install menu. :shock:
For me No and cancel was the same. Instead it means N is skip this point and then I came to the rest. :oops:
So now database is configured, frontend is there and I can login.
So next I try to setup a test mailing to check the mail server connections.

BTW: It looks great till now :D

Thanks

Re: OpenEMM 2019 on openSuSE Tumbleweed?

Posted: Mon Sep 09, 2019 3:45 pm
by hwcgdt
Ok, so now I got a little progress.
First I realized that the problem with missing MTA is the call to postconf. Without path you get at SuSE the remark "The absolute path ist /usr/sbin/postconf. So you probably need superuser privileges" - with an exitcode 127.
When replacing the call in OpenEMMInstaller.py with absolute path - everything is OK
When importing an old addresslist using CSV - everything is OK, but I could not import the connection to the mailinglist. I had to do this by hand.
The first mailing test with one admin, one test and one enduser failed, while email of system diagnosis works.

When searching in logs I came along the xmlback command, that will not fire.
Calling by hand it gave me an error of missing libssl and libcrypt libraries.
The libssl problem could be solved by creating a symbolic link to the existing version, but it seems that I came to a dead end, because:

Code: Select all

/xmlback -r -unc -q -l -E/home/openemm/temp/error3428756181141620699.tmp -opreview:path=/home/openemm/temp/preview6178344765422306616.xml /home/openemm/var/spool/META/AgnMail-0=D20190908221442=1=3=00001=liaMngA.xml.gz
./xmlback: /usr/lib64/libcrypto.so.10: version `libcrypto.so.10' not found (required by ./xmlback)
And when I checked the backend:

Code: Select all

 ./backend.sh status
once        : incomplete (1 files remaining: /home/openemm/scripts/once/tag-install.sh)
mailout     : running
update      : stopped
trigger     : running
generate    : running
mta         : running
pickdist    : running
slrtscn     : stopped
direct-path : running
bav-update  : running
bavd        : stopped
bav         : running
mlcontrol   : running
and calling

Code: Select all

/home/openemm/scripts/once/tag-install.sh
luatc: /usr/lib64/libcrypto.so.10: version `libcrypto.so.10' not found (required by luatc)
luatc: /usr/lib64/libcrypto.so.10: version `libcrypto.so.10' not found (required by luatc)
luatc: /usr/lib64/libcrypto.so.10: version `libcrypto.so.10' not found (required by luatc)
luatc: /usr/lib64/libcrypto.so.10: version `libcrypto.so.10' not found (required by luatc)
luatc: /usr/lib64/libcrypto.so.10: version `libcrypto.so.10' not found (required by luatc)
luatc: /usr/lib64/libcrypto.so.10: version `libcrypto.so.10' not found (required by luatc)
luatc: /usr/lib64/libcrypto.so.10: version `libcrypto.so.10' not found (required by luatc)
googling at this problem pointed me to compiling libssl with the right version string (not version number) which is different in RHEL and SuSE.

So how can I go on at that point, or is this the end for Openemm @ OpenSuSE?

Thanks

Re: OpenEMM 2019 on openSuSE Tumbleweed?

Posted: Mon Sep 09, 2019 4:40 pm
by maschoff
We are in the final phase of preparing some code modifications and writing a doc on how to compile and install OpenEMM 2019 with Suse 15.

Re: OpenEMM 2019 on openSuSE Tumbleweed?

Posted: Mon Sep 09, 2019 8:20 pm
by hwcgdt
OK, so as a (maybe) last message in this topic:
I was cheating with the library, copying the /usr/lib64/libcrypto.so.1.0.2k from a Centos test installation to my server as /usr/lib64/libcrypto.so.10
and now most functions are working
- I'm able to send mailings
- The preview is also working (was showing a weird error before)

What I still see:
I get a

Code: Select all

Table 'openemm.dkim_key_tbl' doesn't exist
when generating diagnose report
and when I try to use the assistent to create a new mailing, I receive an Error 500
Image

Thanks