Re: [Wrapper-user] Trouble getting wrapper to run correctly using systemd

[Leif M. <lei...@ta...>]

Liong
If the Wrapper is being started correctly then yes, it is
probably something different between the user environment you were using
when running in console mode vs the environment which is present as a
service.
Please set the wrapper.debug=true property in the wrapper.conf file and try
running again in each case.
You can then compare the output between the two runs and hopefully the
cause will be obvious.
In not, please send both of those logs and the wrapper.conf file to us and
I would be happy to take a look.  (Make sure there is no proprietary
information in the logs)

The environment when running as a service can be an issue to get setup
correctly on all platforms.
The Wrapper makes it possible to define variable in the wrapper.conf as
well.

To always set the value:
set.FOOBAR=value

To set only if not already set:
set.default.FOOBAR=true

See here:
https://wrapper.tanukisoftware.com/doc/english/props-envvars.html

Cheers,
Leif

On Fri, Feb 26, 2021 at 4:52 PM Liong Kok Foo <lio...@re...>
wrote:

> Hi,
>
> I just took over a machine running wrapper 64bit 3.5.21. CentOS 7. Quite
> an old machine.
>
> It was developed by pass developer and I am the system admin trying to get
> the service to start during server reboot. It was disabled previously and
> had to be restarted manually everytime we reboot the machine. I tried
> enable it to start on reboot (systemctl enable testwrapper) and the service
> seems to start like expected. However, the program does not work properly.
> I then stopped the wrapper and start it manually using the start up script
> running it directly as root from the folder (./testwrapper start). This way
> program will work properly.
>
> I tried asking some developer about this and they mentioned maybe it is
> something to do with the environment variables.
>
> I am wondering if someone could shed some light into getting this wrapper
> run on reboot with the proper environment variables or whatever reason it
> is not working properly.
>
> Appreciate any comments.
> Thank you.
>