Re: systemd auto start and stop

What are the errors in your James.log file?

By the way, I had set up my James files to locate my logs in a configurable directory by setting up a ‘log_dir’ variable in the properties file and locating all logs in log_dir. That makes it easier for organizations that are required to move their logs to a certain directory for monitoring and sharing purposes when the James admin is separate from the server admin

Sent from my iPhone

> On Apr 19, 2021, at 2:26 AM, Scott <[email protected]> wrote:
> 
> Does anyone have a working james.service systemd file that will run correctly on Ubuntu 20.04 with the new Apache James 3.6?
> 
> I tried both configurations in this thread with failed results:  http://mail-archives.apache.org/mod_mbox/james-server-user/201901.mbox/%[email protected]%3E
> 
> The journalctl log message just said "Exit code" with either of those configurations. This was the last one I tried before I gave up:
> 
> [Unit]
> Description=Apache James 3.6 Mail Server
> After=network.target
> [Service]
> Type=forking
> Environment="JAVA_HOME=/usr/local/java"
> WorkingDirectory=/usr/local/james/bin 
> ExecStart=/usr/local/james/bin/james start
> ExecStop=/usr/local/james/bin/james stop
> RestartSec=10
> Restart=always
> [Install]
> WantedBy=multi-user.target
> 
> 
> What would happen when I would run "systemctl start james" was that it would start, run for 10-15 seconds, and then stop.
> 
> For those running James in a prod environment, what are you doing to auto-start and stop it on system reboots?
> 
> Scott
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>