IBM Datapower on Linux
-
Does anyone have any experience with Datapower on Linux?
Simply put, it should be an installation through RPM, which I have all of the RPM. What I'm getting hung up on is the LUKS partitions which are apparently required, but not specified what needs to be done to configure these.
From IBM:
Resource requirements on Linux hosts
To install the DataPower Gateway, the host must meet the following requirements.
To install the RPM packages, the host must be running a supported 64-bit version of Linux.
2 GiB of free storage must be available on /opt.
5 GiB of free storage must be available on /var.
At least two free loop devices are needed, with another loop device when RAID storage is used.
RAID storage, if used, must be configured in the datapower.conf file.I'm not using raid, here I'm showing the disk layout and the loop devices.
The installation which is a simply
yum install xxx.image.x86_64.rpm xxx.common.x86_64.rpm
Which I then should have a stopped "datapower.service", but the service keeps crashing because it's looking for these LUKS partitions.
Nov 07 15:17:52 appconnect.localdomain systemd[1]: datapower.service: Scheduled restart job, restart counter is at 183. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit datapower.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Nov 07 15:17:52 appconnect.localdomain systemd[1]: Stopped DataPower Service. -- Subject: Unit datapower.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit datapower.service has finished shutting down. Nov 07 15:17:52 appconnect.localdomain systemd[1]: Starting DataPower Service... -- Subject: Unit datapower.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit datapower.service has begun starting up. Nov 07 15:17:53 appconnect.localdomain kernel: loop0: detected capacity change from 0 to 3774873600 Nov 07 15:17:55 appconnect.localdomain bash[105464]: Thu Nov 07 2024 15:17:55 ERR dpControl [pre-start][105464] Cannot unlock LUKS partition 'var_opt_ibm_datapower_datapower_img': Function not implemented (error 38) Nov 07 15:17:57 appconnect.localdomain systemd[1]: datapower.service: Control process exited, code=exited status=38 Nov 07 15:17:57 appconnect.localdomain datapower-control[105506]: Thu Nov 07 2024 15:17:57 ERR dpControl [post-stop][105506] Cannot open lockfile '/var/opt/ibm/datapower/datapower.img.lck': No such file or directory Nov 07 15:17:57 appconnect.localdomain datapower-control[105506]: Thu Nov 07 2024 15:17:57 ERR dpControl [post-stop][105506] Cannot close LUKS partition 'var_opt_ibm_datapower_datapower_img': No such device (error 19) Nov 07 15:17:58 appconnect.localdomain datapower-control[105506]: Thu Nov 07 2024 15:17:58 ERR dpControl [post-stop][105506] No Datapower loop mounts were found. Please reboot the system and verify tha the Datapower service starts up co> Nov 07 15:17:58 appconnect.localdomain systemd[1]: datapower.service: Control process exited, code=exited status=3 Nov 07 15:17:58 appconnect.localdomain systemd[1]: datapower.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- The unit datapower.service has entered the 'failed' state with result 'exit-code'. Nov 07 15:17:58 appconnect.localdomain systemd[1]: Failed to start DataPower Service. -- Subject: Unit datapower.service has failed -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit datapower.service has failed. -- -- The result is failed. Nov 07 15:17:58 appconnect.localdomain systemd[1]: datapower.service: Service RestartSec=100ms expired, scheduling restart. Nov 07 15:17:58 appconnect.localdomain systemd[1]: datapower.service: Scheduled restart job, restart counter is at 184. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Automatic restarting of the unit datapower.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Nov 07 15:17:58 appconnect.localdomain systemd[1]: Stopped DataPower Service. -- Subject: Unit datapower.service has finished shutting down -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit datapower.service has finished shutting down. Nov 07 15:17:58 appconnect.localdomain systemd[1]: Starting DataPower Service... -- Subject: Unit datapower.service has begun start-up -- Defined-By: systemd -- Support: https://access.redhat.com/support -- -- Unit datapower.service has begun starting up. Nov 07 15:17:59 appconnect.localdomain kernel: loop0: detected capacity change from 0 to 3774873600 Nov 07 15:18:01 appconnect.localdomain bash[105509]: Thu Nov 07 2024 15:18:01 ERR dpControl [pre-start][105509] Cannot unlock LUKS partition 'var_opt_ibm_datapower_datapower_img': Function not implemented (error 38)
-
I've never dealt with Datapower, but I suspect there's a configuration file related to
datapower-control
that may need some editing. -
@EddieJennings said in IBM Datapower on Linux:
I've never dealt with Datapower, but I suspect there's a configuration file related to
datapower-control
that may need some editing.So there is a configuration file, but there is no reference at all within the conf file (/var/ibm/datapower/datapower.conf) regarding the LUKS partition.
-
Never had the privilege to deal with Datapower on Linux. Though it looks very interesting.