AWS Thinkbox Discussion Forums

Installation on Ubuntu 20.04.6 LTS

Deadline
#1

Hi,

I’m trying ( for some days now ) to install Deadline 10.3.2.1 on a Linux, but with no success. I’d really apreciate some help to solve this, as I’m new to Linux.

I took notes of the processes and will share a short version and a long version:

Short Version

  • Linux is on a virtual machine ( VM )
  • Linux version is Ubuntu 20.04.6 LTS
  • Clean install of the Deadline Repository
  • Installation tries to download MongoDB, but is unable to do so
  • Cancel and install database manually ( version 5.0.2 )
  • Deadline10db.service doesn’t start
  • Tried to install again, but using the manually installed database ( “Connection refused” )

Long Version

  • Linux is on a virtual machine ( VM )
  • Using Ubuntu 20.04.6 LTS

$ lsb_release -a

lsb_release -a
LSB Version:    core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.6 LTS
Release:        20.04
Codename:       focal
  • Clean install of the Deadline Repository

$ sudo ./DeadlineRepository-10.3.2.1-linux-x64-installer.run

  • install MongoDB on this machine? Yes

  • download MongoDB (requires internet connection)? Yes

Warning: Unable to run to
"/tmp/repoinstalltemp/mongo/mongodb-linux-x86_64-ubuntu2004-5.0.22/bin/mongod
--version" to verify the MongoDB binaries. Please ensure you're installing the
proper version of MongoDB for your operating system.
Press [Enter] to continue:
  • creating folders for the database
    $ sudo mkdir /opt/Thinkbox/DeadlineDatabase10/mongo
    $ sudo mkdir /opt/Thinkbox/DeadlineDatabase10/mongo/data
  • copy application folder
    $ sudo cp -r /mnt/install/Linux/MongoDB/5.0.2/application /opt/Thinkbox/DeadlineDatabase10/mongo
  • copy config file
    $ sudo cp /mnt/install/Linux/MongoDB/config.conf /opt/Thinkbox/DeadlineDatabase10/mongo/data
  • copy service script
    $ sudo cp /mnt/install/Linux/MongoDB/Deadline10db /etc/init.d
  • set permission
    $ sudo chmod 755 /etc/init.d/Deadline10d
  • start service
    $ sudo service Deadline10db start 
Job for Deadline10db.service failed because the control process exited with error code.
See "systemctl status Deadline10db.service" and "journalctl -xe" for details.
  • debug

$ sudo systemctl status Deadline10db.service

● Deadline10db.service - LSB: Mongo DB NoSQL Database.
     Loaded: loaded (/etc/init.d/Deadline10db; generated)
     Active: failed (Result: exit-code) since Thu 2024-06-20 15:19:38 UTC; 32s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 9825 ExecStart=/etc/init.d/Deadline10db start (code=exited, status=203/EXEC)

Jun 20 15:19:38 deadlineserver systemd[1]: Starting LSB: Mongo DB NoSQL Database....
Jun 20 15:19:38 deadlineserver systemd[9825]: Deadline10db.service: Failed to execute command: No such file or directory
Jun 20 15:19:38 deadlineserver systemd[9825]: Deadline10db.service: Failed at step EXEC spawning /etc/init.d/Deadline10db: No such file or directory
Jun 20 15:19:38 deadlineserver systemd[1]: Deadline10db.service: Control process exited, code=exited, status=203/EXEC
Jun 20 15:19:38 deadlineserver systemd[1]: Deadline10db.service: Failed with result 'exit-code'.
Jun 20 15:19:38 deadlineserver systemd[1]: Failed to start LSB: Mongo DB NoSQL Database..

$ sudo ps aux | grep mongo

<username>     9853  0.0  0.0   6432   720 pts/0    S+   15:21   0:00 grep --color=auto mongo

$ sudo journalctl -xe

-- Support: http://www.ubuntu.com/support
--
-- The process /etc/init.d/Deadline10db could not be executed and failed.
--
-- The error number returned by this process is ERRNO.
Jun 20 15:19:38 deadlineserver systemd[1]: Deadline10db.service: Control process exited, code=exited, status=203/EXEC
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit Deadline10db.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 203.
Jun 20 15:19:38 deadlineserver systemd[1]: Deadline10db.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit Deadline10db.service has entered the 'failed' state with result 'exit-code'.
Jun 20 15:19:38 deadlineserver systemd[1]: Failed to start LSB: Mongo DB NoSQL Database..
-- Subject: A start job for unit Deadline10db.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit Deadline10db.service has finished with a failure.
--
-- The job identifier is 924 and the job result is failed.
Jun 20 15:19:38 deadlineserver sudo[9816]: pam_unix(sudo:session): session closed for user root
Jun 20 15:20:10 deadlineserver sudo[9849]:  <username> : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/bin/systemctl status Deadline10db.service
Jun 20 15:20:10 deadlineserver sudo[9849]: pam_unix(sudo:session): session opened for user root by <username>(uid=0)
Jun 20 15:21:04 deadlineserver sudo[9849]: pam_unix(sudo:session): session closed for user root
Jun 20 15:21:36 deadlineserver sudo[9852]:  <username> : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/bin/ps aux
Jun 20 15:21:36 deadlineserver sudo[9852]: pam_unix(sudo:session): session opened for user root by <username>(uid=0)
Jun 20 15:21:36 deadlineserver sudo[9852]: pam_unix(sudo:session): session closed for user root
Jun 20 15:28:53 deadlineserver sudo[9870]:  <username> : TTY=pts/0 ; PWD=/opt/Thinkbox/DeadlineDatabase10/mongo/data ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Jun 20 15:28:53 deadlineserver sudo[9870]: pam_unix(sudo:session): session opened for user root by <username>(uid=0)
Jun 20 15:30:34 deadlineserver sudo[9870]: pam_unix(sudo:session): session closed for user root
Jun 20 15:35:53 deadlineserver kernel: traps: mongo[9887] trap invalid opcode ip:5591d41ec62a sp:7ffc2a5fc670 error:0 in mongo[5591d2076000+2e15000]
Jun 20 15:36:05 deadlineserver kernel: traps: mongod[9897] trap invalid opcode ip:55a4fc066dca sp:7fffd28cdc80 error:0 in mongod[55a4f7f94000+5244000]
Jun 20 15:44:22 deadlineserver sudo[9902]:  <username> : TTY=pts/0 ; PWD=/tmp ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Jun 20 15:44:22 deadlineserver sudo[9902]: pam_unix(sudo:session): session opened for user root by <username>(uid=0)
  • install using already installed database
Warning: An error occurred while configuring the database:

Could not connect to any of the specified Mongo DB servers defined in the
"Hostname" parameter of the "settings/connection.ini" file in the root of the
Repository.

The following errors were encountered:

* deadlineserver: Connection refused
* 127.0.1.1: Connection refused

If someone has faced a simmilar problem or has any idea, I really would like to hear from you.

Thank you

#2

Hi,

I finally found the problem and a solution.

When starting the service I got a message simmilar to this one

mongod.service - MongoDB Database Server
Loaded: loaded (/lib/systemd/system/mongod.service; disabled; vendor preset: enabled)
Active: failed (Result: core-dump) since Fri 2021-07-30 18:50:50 CDT; 5min ago
Docs: https://docs.mongodb.org/manual
Process: 125616 ExecStart=/usr/bin/mongod --config /etc/mongod.conf (code=dumped, signal=ILL)
 Main PID: 125616 (code=dumped, signal=ILL)

I searched for the part “( code=dumped, signal=ILL )” and found someone with the same error.

The “signal=ILL” part of the systemctl output means that MongoDB failed to start because of an illegal instruction.
This is caused by MongoDB 5 and later requiring AVX to run.

I it found here : ubuntu - MongoDB error - Failed with result 'core-dump' - Super User

Our server is a “little bit” old and doesn’t support AVX. So I downloaded a previous version of MongoDB ( 4.4.29 ) and was abble to install both deadline database and deadline repository. Now I’ll start testing everything.

I hope this can help someone with the same problem.

Thank you

Privacy | Site terms | Cookie preferences