Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
mnagy
Contributor II
Contributor II

Update areplicate rpm fails to start service.

During the update of areplicate rpm to November 2023 SR1, service fails to start as root, but will start when connected a attunity:
sl-******:/ora_home/stage # rpm -Uvh --prefix /qlik areplicate-2023.11.0-282.x86_64.rpm
Verifying... ################################# [100%]
Preparing... ################################# [100%]
Updating / installing...
1:areplicate-2023.11.0-282 ################################# [ 50%]
Failed to start service areplicate
Not all services have been started
warning: %post(areplicate-2023.11.0-282.x86_64) scriptlet failed, exit status 10
Cleaning up / removing...
2:areplicate-2022.11.0-208 ################################# [100%]

Also noticed the /etc/init.d/areplicate files is missing now:
attunity@sl-*******:~ > ls -l /etc/init.d/areplicate
ls: cannot access '/etc/init.d/areplicate': No such file or directory

How do we correct this?

 

Thanks,

Marty

 

Labels (1)
1 Solution

Accepted Solutions
mnagy
Contributor II
Contributor II
Author

Thank you for the quick response.

So, the rpm looks good, and we normally use the attunity account to start and stop areplicate. The previous version we were running did have the /etc/init.d/areplicate file, but the application of the new rpm has appeared to remove it.  When I look at our existing November 2022 installs, they do show the service in a failed state:
sl-*******2i:~ # systemctl status areplicate
● areplicate.service - SYSV: Attunity Replicate service management
Loaded: loaded (/etc/rc.d/init.d/areplicate; generated)
Active: failed (Result: exit-code) since Tue 2024-01-23 10:52:54 CST; 3 months 26 days ago
Docs: man:systemd-sysv-generator(8)
Process: 1245 ExecStart=/etc/rc.d/init.d/areplicate start (code=exited, status=126)

A follow up question, if we do not wish to use systemctl to managed it and just use the attunity account, is there anything further we need to do? 
 

View solution in original post

3 Replies
TauseefKhan
Creator III
Creator III

Hi @mnagy,

The issue of the service failing to start as root after the update to the November 2023 SR1 version of Areplicate RPM could be due to a few reasons:

  • Permissions or ownership issues: Ensure that the user running the service (typically the attunity user) has the necessary permissions and ownership of the Areplicate files and directories.
  • Conflicting configurations: Check if there are any existing configurations or settings that might be interfering with the new Areplicate installation.
  • Dependency issues: Verify that all the required dependencies for the Areplicate service are installed and up-to-date.
    • To troubleshoot this issue, you can try the following steps:
      1. Check the Areplicate service logs for any error messages or clues about the failure.
      2. Ensure that the Areplicate user has the necessary permissions to access the required files and directories.
      3. Try starting the Areplicate service manually as the attunity user to see if it starts successfully.
      4. If the issue persists, you may need to uninstall the current version of Areplicate and perform a clean installation of the November 2023 SR1 version.

        Missing /etc/init.d/areplicate File:
        • The absence of the /etc/init.d/areplicate file is likely due to the Areplicate service being managed by a different system, such as systemd, instead of the traditional init.d system.
        • In modern Linux distributions, the preferred method for managing services is through systemd, which uses .service files instead of the traditional init.d scripts.
        • To check the Areplicate service status and manage it using systemd, you can use the following commands:
          • Check the Areplicate service status: systemctl status areplicate
          • Start the Areplicate service: systemctl start areplicate
          • Stop the Areplicate service: systemctl stop areplicate
          • Enable the Areplicate service to start automatically on system boot: systemctl enable areplicate
mnagy
Contributor II
Contributor II
Author

Thank you for the quick response.

So, the rpm looks good, and we normally use the attunity account to start and stop areplicate. The previous version we were running did have the /etc/init.d/areplicate file, but the application of the new rpm has appeared to remove it.  When I look at our existing November 2022 installs, they do show the service in a failed state:
sl-*******2i:~ # systemctl status areplicate
● areplicate.service - SYSV: Attunity Replicate service management
Loaded: loaded (/etc/rc.d/init.d/areplicate; generated)
Active: failed (Result: exit-code) since Tue 2024-01-23 10:52:54 CST; 3 months 26 days ago
Docs: man:systemd-sysv-generator(8)
Process: 1245 ExecStart=/etc/rc.d/init.d/areplicate start (code=exited, status=126)

A follow up question, if we do not wish to use systemctl to managed it and just use the attunity account, is there anything further we need to do? 
 

SushilKumar
Support
Support

Hello @mnagy 

It is always requested to install and upgrade QLIK on LINUX by root directly . 

not with SUDO as well. Request you try with root once and see for stop and start you may use Attunity user. 

Regards

Sushil Kumar