Systemd unit file for 5.0.1

[Jay Linux]

Hi Team, 

I upgraded the irods server from 4.3.0 to 5.0.1 and after that my irods server is not starting up. Below is my systemd unit file. Please advise how to correct to make this to work?

I can see this binary "irodsctl" is deprecated now. I'm using RHEL9.6 . Please advise.

Below is my old systemd unit file config with v4.3.0

#cat /usr/lib/systemd/system/irods.service
[Unit]
Description=iRODS 4.3.1 Open Source Data Management
After=local-fs.target network.target

[Service]
WorkingDirectory=/var/lib/irods
User=irods
Environment="PATH=/bin:/usr/bin:/usr/sbin:/var/lib/irods"
ExecStart=/bin/bash -c "irodsctl start"
ExecReload=/usr/bin/touch /etc/irods/core.re
ExecStop=/bin/bash -c "irodsctl stop"
LimitNOFILE=131072
KillMode=control-group
Restart=on-failure
RestartPreventExitStatus=255
Type=forking

[Install]
WantedBy=multi-user.target

Thanks

jay

[Alan King]

Hi Jay,

It is recommended to use a modified version of the service file template included in the server package, as described here: https://docs.irods.org/5.0.1/getting_started/running/#managing-irods-via-the-service-manager For reference, the service template file can also be viewed here: https://github.com/irods/irods/blob/5.0.1/packaging/irods.service.template

Just from eyeballing the differences, I think you will want to at least modify the ExecStart, ExecReload, and ExecStop lines according to the "Starting the Server" and "Stopping the Server" docs:

https://docs.irods.org/5.0.1/getting_started/running/#starting-the-server

https://docs.irods.org/5.0.1/getting_started/running/#stopping-the-server

Hope that helps.

Alan

--
--
The Integrated Rule-Oriented Data System (iRODS) - https://irods.org
 
iROD-Chat: http://groups.google.com/group/iROD-Chat
---
You received this message because you are subscribed to the Google Groups "iRODS-Chat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to irod-chat+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/irod-chat/d5f6018a-cb93-4af7-b484-a63a926ea5d1n%40googlegroups.com.

--

Alan King

Senior Software Developer | iRODS Consortium

[Jay Linux]

Hi Alan, 

Thanks for the pointer. I will update the systemd file.

But somehow I'm getting a weired error when I manually excecute this command "/usr/sbin/irodsServer"

===

/usr/sbin/irodsServer
validate_configuration: [
    {
        "valid": false,
        "evaluationPath": "/properties/advanced_settings/required",
        "schemaLocation": "https://irods.org/configuration_schemas/v5/server_config.json#/properties/advanced_settings/required",
        "instanceLocation": "/advanced_settings",
        "error": "Required property 'checksum_read_buffer_size_in_bytes' not found."
    },
    {
        "valid": false,
        "evaluationPath": "/properties/plugin_configuration/properties/database/$ref/required",
        "schemaLocation": "https://irods.org/configuration_schemas/v5/database_config.json#/required",
        "instanceLocation": "/plugin_configuration/database",
        "error": "Required property 'technology' not found."
    },

===

This is my test environment and i would like to perform smooth migration from 4.3.0 to 5.0.1. Kindly share me the upgrade plan.

Thanks

Jay

[Alan King]

You need to run the upgrade_irods.py script after upgrading to iRODS 5 packages from iRODS 4. Please see https://docs.irods.org/5.0.1/getting_started/upgrading/#upgrading-to-irods-5-and-later. 

To view this discussion visit https://groups.google.com/d/msgid/irod-chat/8046451a-1b83-4778-aa2e-ad234e5a55b1n%40googlegroups.com.

[Jay Linux]

Thanks Alan