Hello all.,

I had Ubuntu 14.04 LTS server upgraded to 16.04 LTS. Everything as far as java_home settings etc are correct. I can run all services, also deprecated php7 to php5.6 yet Xeams does not work nor start.

I think it might be something related to how the service script was updated.

If I do a sudo service xeams start I get the following now: status=203/EXEC

service xeams start
Job for xeams.service failed because the control process exited with error code. See "systemctl status xeams.service" and "journalctl -xe" for details.
root@ns17:/opt/Xeams# service xeams status
● xeams.service - LSB: Xeams SMTP Server and Spam Filter
Loaded: loaded (/etc/init.d/xeams; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2016-07-25 11:32:48 MDT; 2s ago
Docs: man:systemd-sysv-generator(8)
Process: 20101 ExecStart=/etc/init.d/xeams start (code=exited, status=203/EXEC)

Jul 25 11:32:48 ns17 systemd[1]: Starting LSB: Xeams SMTP Server and Spam Filter...
Jul 25 11:32:48 ns17 systemd[1]: xeams.service: Control process exited, code=exited status=203
Jul 25 11:32:48 ns17 systemd[1]: Failed to start LSB: Xeams SMTP Server and Spam Filter.
Jul 25 11:32:48 ns17 systemd[1]: xeams.service: Unit entered failed state.
Jul 25 11:32:48 ns17 systemd[1]: xeams.service: Failed with result 'exit-code'.

-- Unit xeams.service has begun starting up.
Jul 25 11:32:48 ns17 systemd[20101]: xeams.service: Failed at step EXEC spawning /etc/init.d/xeams: Exec format error
-- Subject: Process /etc/init.d/xeams could not be executed
-- Defined-By: systemd
-- Support: 
--
-- The process /etc/init.d/xeams could not be executed and failed.
--
-- The error number returned by this process is 8.
Jul 25 11:32:48 ns17 systemd[1]: xeams.service: Control process exited, code=exited status=203
Jul 25 11:32:48 ns17 systemd[1]: Failed to start LSB: Xeams SMTP Server and Spam Filter.
-- Subject: Unit xeams.service has failed
-- Defined-By: systemd
-- Support: 
--
-- Unit xeams.service has failed.
--
-- The result is failed.
Jul 25 11:32:48 ns17 systemd[1]: xeams.service: Unit entered failed state.
Jul 25 11:32:48 ns17 systemd[1]: xeams.service: Failed with result 'exit-code'.

Trying to find any clues about it. Looks like the service script is not executing properly now.

Any suggestions?

Thanks,

C.

First try to discover whether the system startup script is bad or the application. Manually run /opt/Xeams/run.sh. If Xeams runs then look at the startup configuration. If not, then eliminate the startup scripts as a cause.

Check /opt/Xeams/logs/Xeams.log.

Xeams is a Java application and requires a working Java Runtime. And that is it, it doesn't require anything else.

The Xeams website encourages downloading bundles of Xeams and a Java runtime. I think it is preferable to not supply a bundle if a Java runtime is a package in the base OS and is reasonably easy to get. Then when the OS is upgraded then the Java runtime is updated.

There are two possibilities, first the Java runtime might be too old and incompatible. You could install openjdk from Ubuntu and alter run.sh and environment variables to use it, or maybe rename /opt/Xeams to something else, install a new complete copy of Xeams and use the KB article to copy relevant configuration etc. from the old installation. The second could be ACLs and permissions. I am used to selinux on CentOS where OS upgrades can expose more strict security policies. Ubuntu uses a different security policy system from CentOS where I don't know the details, but you could investigate log files for it.

Hi,

Might be digging in the past, but this is the exact same issue that I'm having now.

How could I fix this without breaking my current Xeams settings?
I do not wish to install a new instance of Xeams.

Can't read the logs as well. I receive a permission denied.
Can I do a chmod without breaking it for Xeams?

Thanks in advance!

Laurens,

Are you running Xeams as "root", if not try that. 

Hi Pascha,

Tried that as well.

It simply doesn't start when I try with Ubuntu server 16.0.4

Ok, created a new Xeams server from scratch. Thanks the the clustering feature this has become much more easier!

Only thing I need to set up now is my Clamav for scanning the incoming e-mails.