In case anyone else gets stuck in this problem, I wanted to share what I did to get James to automatically startup on Ubuntu 20.04 at boot time. Run the following commands (1-3):
1. nano /usr/local/sbin/james-start #!/bin/bash export JAVA_HOME=/usr/local/java cd /usr/local/james/bin nohup ./run.sh & 2. chmod 750 /usr/local/sbin/james-start 3. crontab -e add the following line: @reboot /usr/local/sbin/james-start I did those logged in as root. Rebooted the system and James was automatically started. I understand that this is not the best way to do this. I have found no clean way to shutdown James using the above method (I just killed the process), so we hope that when the system is shut down, James is not in the middle of writing mail. Maybe there is a built-in file or database integrity check when writing? But, I can say that it works, and thank DMatthews for his "perfect java email server" page. On Monday, April 19, 2021, 8:19:57 AM PDT, Garry Hurley <garry.hurley...@gmail.com> wrote: 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 <upo...@yahoo.com.invalid> 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/%3ce29099de-ec85-43f7-d25e-b7bde0628...@marcchamberlin.com%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: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
