AWS Thinkbox Discussion Forums

AWS Portal services are not starting during boot (Linux)

Hi,

I’m having issues with auto starting the AWS Portal services during boot

I installed the Deadline Repository 10.4.0.8 on Rocky Linux 9.4

The database service, the client, the RCS and the webservice are running fine. I can see that those processes are running and I can connect a Windows client to the repository.

I then proceeded to install the AWS Portal Link and AWS Portel Asset server. The installation completed correctly but after reboot the awsportallink is not running

During my tests, I changed the way the awsportallink service starts
I removed the symbolic links from /etc/rc0.d, /etc/rc1.d, /etc/rc2.d… and I created a systemd unit file :

sudo nano /etc/systemd/system/awsportallinkservice.service

containing :

[Unit]
Description=AWSPortalLink startup script
After=network.target local-fs.target remote-fs.target
Requires=network.target local-fs.target remote-fs.target

[Service]
Type=forking
ExecStart=/etc/init.d/awsportallinkservice start
ExecStop=/etc/init.d/awsportallinkservice stop
User=root
Group=root
Restart=on-failure
StandardOutput=journal
StandardError=journal

[Install]
WantedBy=multi-user.target

I installed this unit file :

sudo systemctl daemon-reload
sudo systemctl enable awsportallinkservice.service

and rebooted

(BTW I did the same thing for the awsportalassetservershellscript )

After rebooting :

sudo service --status-all :
The AWSPortalAssetServer Service is not currently running.
The AWSPortalLink Service is not currently running.
The MongoDB Service For Deadline 10 is running with PID 950.

Looking at the systemd journal logs I see :

Oct 25 22:01:25 deadline-vm.home systemd[1]: Reached target Remote File Systems.
Oct 25 22:01:25 deadline-vm.home systemd[1]: Starting Deadline10db Startup Script...
Oct 25 22:01:25 deadline-vm.home systemd[1]: Starting AWSPortalAssetServer startup script...
Oct 25 22:01:25 deadline-vm.home systemd[1]: Starting AWSPortalLink startup script...
Oct 25 22:01:25 deadline-vm.home systemd[1]: Starting Crash recovery kernel arming...
Oct 25 22:01:25 deadline-vm.home systemd[1]: TPM2 PCR Barrier (User) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41c>
Oct 25 22:01:25 deadline-vm.home systemd[1]: Starting Permit User Sessions...
Oct 25 22:01:25 deadline-vm.home su[958]: (to root) root on none
Oct 25 22:01:25 deadline-vm.home systemd[1]: Finished Permit User Sessions.
Oct 25 22:01:25 deadline-vm.home su[962]: (to root) root on none
Oct 25 22:01:25 deadline-vm.home bash[907]: 'nogui' Is not a flag or a setting
Oct 25 22:01:25 deadline-vm.home systemd[1]: Started Deferred execution scheduler.
Oct 25 22:01:26 deadline-vm.home Deadline10db[936]: The MongoDB Service For Deadline 10 has been started.
Oct 25 22:01:26 deadline-vm.home systemd[1]: Started Command Scheduler.
Oct 25 22:01:26 deadline-vm.home systemd[1]: Started Getty on tty1.
Oct 25 22:01:26 deadline-vm.home crond[971]: (CRON) STARTUP (1.5.7)
Oct 25 22:01:26 deadline-vm.home crond[971]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 68% if used.)
Oct 25 22:01:26 deadline-vm.home crond[971]: (CRON) INFO (running with inotify support)
Oct 25 22:01:26 deadline-vm.home systemd[1]: Reached target Login Prompts.
Oct 25 22:01:26 deadline-vm.home systemd[1]: Started Deadline10db Startup Script.
Oct 25 22:01:26 deadline-vm.home systemd[1]: Created slice User Slice of UID 0.
Oct 25 22:01:26 deadline-vm.home systemd[1]: Starting User Runtime Directory /run/user/0...
Oct 25 22:01:26 deadline-vm.home systemd[1]: Finished User Runtime Directory /run/user/0.
Oct 25 22:01:26 deadline-vm.home systemd[1]: Starting User Manager for UID 0...
Oct 25 22:01:26 deadline-vm.home systemd[1001]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)
Oct 25 22:01:26 deadline-vm.home bash[913]: 'nogui' Is not a flag or a setting
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Queued start job for default target Main User Target.
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Created slice User Application Slice.
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Mark boot as successful after the user session has run 2 minutes was skipped because of an unmet condition check (ConditionUser=!@system).
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Started Daily Cleanup of User's Temporary Directories.
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Reached target Paths.
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Reached target Timers.
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Starting D-Bus User Message Bus Socket...
Oct 25 22:01:26 deadline-vm.home systemd[1001]: PipeWire PulseAudio was skipped because of an unmet condition check (ConditionUser=!root).
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Listening on PipeWire Multimedia System Sockets.
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Starting Create User's Volatile Files and Directories...
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Listening on D-Bus User Message Bus Socket.
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Reached target Sockets.
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Finished Create User's Volatile Files and Directories.
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Reached target Basic System.
Oct 25 22:01:26 deadline-vm.home systemd[1]: Started User Manager for UID 0.
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Reached target Main User Target.
Oct 25 22:01:26 deadline-vm.home systemd[1001]: Startup finished in 156ms.
Oct 25 22:01:26 deadline-vm.home systemd[1]: Started Session c1 of User root.
Oct 25 22:01:26 deadline-vm.home systemd[1]: Started Session c2 of User root.
Oct 25 22:01:26 deadline-vm.home su[962]: pam_unix(su:session): session opened for user root(uid=0) by (uid=0)
Oct 25 22:01:26 deadline-vm.home su[958]: pam_unix(su:session): session opened for user root(uid=0) by (uid=0)
Oct 25 22:01:26 deadline-vm.home systemd[1]: session-c1.scope: Deactivated successfully.
Oct 25 22:01:26 deadline-vm.home su[962]: pam_unix(su:session): session closed for user root
Oct 25 22:01:26 deadline-vm.home Deadline10db[950]: {"t":{"$date":"2024-10-25T20:01:26.280Z"},"s":"W",  "c":"CONTROL",  "id":23320,   "ctx":"-","msg":"Option: Given key is deprecated. Please use prefe>
Oct 25 22:01:26 deadline-vm.home Deadline10db[950]: {"t":{"$date":"2024-10-25T20:01:26.281Z"},"s":"W",  "c":"CONTROL",  "id":23320,   "ctx":"-","msg":"Option: Given key is deprecated. Please use prefe>
Oct 25 22:01:26 deadline-vm.home Deadline10db[950]: {"t":{"$date":"2024-10-25T20:01:26.283Z"},"s":"I",  "c":"CONTROL",  "id":20697,   "ctx":"-","msg":"Renamed existing log file","attr":{"oldLogPath":">
Oct 25 22:01:26 deadline-vm.home su[958]: pam_unix(su:session): session closed for user root
Oct 25 22:01:26 deadline-vm.home systemd[1]: session-c2.scope: Deactivated successfully.
Oct 25 22:01:26 deadline-vm.home su[1108]: (to root) root on none
Oct 25 22:01:26 deadline-vm.home su[1109]: (to root) root on none
Oct 25 22:01:26 deadline-vm.home systemd[1]: Started Session c3 of User root.
Oct 25 22:01:26 deadline-vm.home systemd[1]: Started Session c4 of User root.
Oct 25 22:01:26 deadline-vm.home su[1108]: pam_unix(su-l:session): session opened for user root(uid=0) by (uid=0)
Oct 25 22:01:26 deadline-vm.home su[1109]: pam_unix(su-l:session): session opened for user root(uid=0) by (uid=0)
Oct 25 22:01:26 deadline-vm.home su[1108]: pam_unix(su-l:session): session closed for user root
Oct 25 22:01:26 deadline-vm.home awsportalassetservershellscript[938]: The AWSPortalAssetServer Service has been started.
Oct 25 22:01:26 deadline-vm.home su[1109]: pam_unix(su-l:session): session closed for user root
Oct 25 22:01:26 deadline-vm.home awsportallinkservice[948]: The AWSPortalLink Service has been started.
Oct 25 22:01:26 deadline-vm.home avahi-daemon[709]: Server startup complete. Host name is deadline-vm.local. Local service cookie is 2389494284.
Oct 25 22:01:26 deadline-vm.home systemd[1]: session-c3.scope: Deactivated successfully.
Oct 25 22:01:26 deadline-vm.home awsportallinkservice[1240]: Shutting down the AWSPortalLink Service...
Oct 25 22:01:26 deadline-vm.home systemd[1]: session-c4.scope: Deactivated successfully.
Oct 25 22:01:26 deadline-vm.home awsportalassetservershellscript[1204]: The AWSPortalAssetServer Service has been stopped.
Oct 25 22:01:26 deadline-vm.home systemd[1]: awsportalassetservershellscript.service: Deactivated successfully.
Oct 25 22:01:26 deadline-vm.home systemd[1]: Started AWSPortalAssetServer startup script.
Oct 25 22:01:26 deadline-vm.home kernel: block dm-0: the capability attribute has been deprecated.
Oct 25 22:01:27 deadline-vm.home kdumpctl[967]: kdump: kexec: loaded kdump kernel
Oct 25 22:01:27 deadline-vm.home kdumpctl[967]: kdump: Starting kdump: [OK]
Oct 25 22:01:27 deadline-vm.home systemd[1]: Finished Crash recovery kernel arming.
Oct 25 22:01:27 deadline-vm.home awsportallinkservice[1240]: The AWSPortalLink Service has been stopped.
Oct 25 22:01:27 deadline-vm.home systemd[1]: awsportallinkservice.service: Deactivated successfully.
Oct 25 22:01:27 deadline-vm.home systemd[1]: Started AWSPortalLink startup script.
Oct 25 22:01:27 deadline-vm.home systemd[1]: Reached target Multi-User System.

Contents of /var/log/awsportallinkservice.log :

2024-10-25 22:01:25: 'start' invoked...
2024-10-25 22:01:26: The AWSPortalLink Service has been started.
2024-10-25 22:01:26: Full AWSPortalLink log can be found in /var/log/awsportallinkservice.log
2024-10-25 22:01:26: 'start' operation finished with exit code '0'.
2024-10-25 22:01:26: 'stop' invoked...
2024-10-25 22:01:26: Shutting down the AWSPortalLink Service...
2024-10-25 22:01:27: The AWSPortalLink Service has been stopped.
2024-10-25 22:01:27: 'stop' operation finished with exit code '0'.
2024-10-25 22:02:07: 'status' invoked...
2024-10-25 22:02:07: The AWSPortalLink Service is not currently running.
2024-10-25 22:02:07: 'status' operation finished with exit code '3'.

Checking the status of the service:

sudo service awsportallinkservice status
The AWSPortalLink Service is not currently running.

However, I can start it doing :

sudo service awsportallinkservice start

confirmed with :

sudo service awsportallinkservice status
The AWSPortalLink Service is running with PID 3157.

And I can see in top that a python process with PID 3157 is running

In summary, everything seems to work, except the AWS services do not start during boot. What should I do to make it start those services automatically ?

I found a workaround :

I created a cron job to launch both AWS services :

sudo nano ~/start_aws_services.sh

#!/bin/bash
DEADLINE_PATH=/opt/Thinkbox/Deadline10/bin
sudo service awsportallinkservice start >> ~/start_aws_portallink.log 2>&1
sudo service awsportalassetservershellscript start >> ~/start_aws_portalasset.log 2>&1

Make the /start_aws_services.sh executable :
sudo chmod +x ~/start_aws_services.sh

Edit crontab
crontab -e
add this line :
@reboot ~/start_aws_services.sh

Configure sudo to allow the script to run without password :
sudo visudo

Add :

USERNAME ALL=(ALL) NOPASSWD: /usr/sbin/service awsportallinkservice start
USERNAME ALL=(ALL) NOPASSWD: /usr/sbin/service awsportalassetservershellscript start

(replace USERNAME by the name of the admin user)

Privacy | Site terms | Cookie preferences