Does anyone have a working recipe for starting/stopping Unidata when the system boots on Redhat 8? Looks like it's as easy as creating an entry in /etc/systemd/system/unidata.service, but if someone has a working config they'd be willing to share that will save some experimentation :_)
https://medium.com/@benmorel/creating-a-linux-service-with-systemd-611b5c8b91d6
It doesn't look to hard to do the basics of startud and stopud, but curious if anyone is having systemd restart ud when stopped? That seems like a bad idea.
Thanks for any advice!
Ian
------------------------------
Ian McGowan
Principal Consultant
Rocket Forum Shared Account
------------------------------
Configuring systemd for Unidata startup on Redhat 8
+1Does anyone have a working recipe for starting/stopping Unidata when the system boots on Redhat 8? Looks like it's as easy as creating an entry in /etc/systemd/system/unidata.service, but if someone has a working config they'd be willing to share that will save some experimentation :_)
https://medium.com/@benmorel/creating-a-linux-service-with-systemd-611b5c8b91d6
It doesn't look to hard to do the basics of startud and stopud, but curious if anyone is having systemd restart ud when stopped? That seems like a bad idea.
Thanks for any advice!
Ian
------------------------------
Ian McGowan
Principal Consultant
Rocket Forum Shared Account
------------------------------
https://medium.com/@benmorel/creating-a-linux-service-with-systemd-611b5c8b91d6
It doesn't look to hard to do the basics of startud and stopud, but curious if anyone is having systemd restart ud when stopped? That seems like a bad idea.
Thanks for any advice!
Ian
------------------------------
Ian McGowan
Principal Consultant
Rocket Forum Shared Account
------------------------------
There is a Knowledge article for UniVerse with a script that looks like it can be edited for UniData - please see https://my.rocketsoftware.com/RocketCommunity/articles/Tech_Note/UniVerse-11-2-4-does-not-start-automatically-on-RHEL-7-1478612245090
Regards
JJ
------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------
Ian,
There is a Knowledge article for UniVerse with a script that looks like it can be edited for UniData - please see https://my.rocketsoftware.com/RocketCommunity/articles/Tech_Note/UniVerse-11-2-4-does-not-start-automatically-on-RHEL-7-1478612245090
Regards
JJ
------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------
There is a Knowledge article for UniVerse with a script that looks like it can be edited for UniData - please see https://my.rocketsoftware.com/RocketCommunity/articles/Tech_Note/UniVerse-11-2-4-does-not-start-automatically-on-RHEL-7-1478612245090
Regards
JJ
------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------
Does anyone have a working recipe for starting/stopping Unidata when the system boots on Redhat 8? Looks like it's as easy as creating an entry in /etc/systemd/system/unidata.service, but if someone has a working config they'd be willing to share that will save some experimentation :_)
https://medium.com/@benmorel/creating-a-linux-service-with-systemd-611b5c8b91d6
It doesn't look to hard to do the basics of startud and stopud, but curious if anyone is having systemd restart ud when stopped? That seems like a bad idea.
Thanks for any advice!
Ian
------------------------------
Ian McGowan
Principal Consultant
Rocket Forum Shared Account
------------------------------
https://medium.com/@benmorel/creating-a-linux-service-with-systemd-611b5c8b91d6
It doesn't look to hard to do the basics of startud and stopud, but curious if anyone is having systemd restart ud when stopped? That seems like a bad idea.
Thanks for any advice!
Ian
------------------------------
Ian McGowan
Principal Consultant
Rocket Forum Shared Account
------------------------------
Any troubleshooting hints? RHEL 8 and Universe 11.3
------------------------------
Scott Clift
CAC Financial Corp
US
------------------------------
+1I've followed the instructions to the letter, everything seems to be in the proper place, but it does not work.
Any troubleshooting hints? RHEL 8 and Universe 11.3
------------------------------
Scott Clift
CAC Financial Corp
US
------------------------------
Any troubleshooting hints? RHEL 8 and Universe 11.3
------------------------------
Scott Clift
CAC Financial Corp
US
------------------------------
Does this help ata l?
https://www.howtogeek.com/devops/how-to-add-your-own-services-to-systemd-for-easier-management/
Please watch for system environment variable settings as well - user local settings will not be applied..
Regards,
JJ
------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------
+1I've followed the instructions to the letter, everything seems to be in the proper place, but it does not work.
Any troubleshooting hints? RHEL 8 and Universe 11.3
------------------------------
Scott Clift
CAC Financial Corp
US
------------------------------
Any troubleshooting hints? RHEL 8 and Universe 11.3
------------------------------
Scott Clift
CAC Financial Corp
US
------------------------------
The TechNote @John Jenkins linked is an exact copy of what we use, so it does work.
Can you post the output from this command:
systemctl status universe.service --full
------------------------------
Gregor Scott
Software Architect
Pentana Solutions Pty Ltd
Mount Waverley VIC AU
------------------------------
We have been using systemd to start/stop UV for a number of years.
The TechNote @John Jenkins linked is an exact copy of what we use, so it does work.
Can you post the output from this command:
------------------------------
Gregor Scott
Software Architect
Pentana Solutions Pty Ltd
Mount Waverley VIC AU
------------------------------
The TechNote @John Jenkins linked is an exact copy of what we use, so it does work.
Can you post the output from this command:
systemctl status universe.service --full
------------------------------
Gregor Scott
Software Architect
Pentana Solutions Pty Ltd
Mount Waverley VIC AU
------------------------------
------------------------------
John Thompson
Precision Solutions, Inc.
North port FL US
------------------------------
We have been using systemd to start/stop UV for a number of years.
The TechNote @John Jenkins linked is an exact copy of what we use, so it does work.
Can you post the output from this command:
------------------------------
Gregor Scott
Software Architect
Pentana Solutions Pty Ltd
Mount Waverley VIC AU
------------------------------
The TechNote @John Jenkins linked is an exact copy of what we use, so it does work.
Can you post the output from this command:
systemctl status universe.service --full
------------------------------
Gregor Scott
Software Architect
Pentana Solutions Pty Ltd
Mount Waverley VIC AU
------------------------------
here is the output:
root@cubsserver2 ~]# systemctl status universe.service --full
● universe.service - Rocket UniVerse Service
Loaded: loaded (/etc/systemd/system/universe.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2023-08-09 11:43:07 CDT; 7min ago
Process: 41557 ExecStart=/etc/rc.d/init.d/uv.rc start (code=exited, status=203/EXEC)
Aug 09 11:43:07 cubsserver2.localdomain systemd[1]: Starting Rocket UniVerse Service...
Aug 09 11:43:07 cubsserver2.localdomain systemd[1]: universe.service: Control process exited, code=exited status=203
Aug 09 11:43:07 cubsserver2.localdomain systemd[1]: universe.service: Failed with result 'exit-code'.
Aug 09 11:43:07 cubsserver2.localdomain systemd[1]: Failed to start Rocket UniVerse Service.
------------------------------
Scott Clift
CAC Financial Corp
US
------------------------------
+1here is the output:
root@cubsserver2 ~]# systemctl status universe.service --full
● universe.service - Rocket UniVerse Service
Loaded: loaded (/etc/systemd/system/universe.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2023-08-09 11:43:07 CDT; 7min ago
Process: 41557 ExecStart=/etc/rc.d/init.d/uv.rc start (code=exited, status=203/EXEC)
Aug 09 11:43:07 cubsserver2.localdomain systemd[1]: Starting Rocket UniVerse Service...
Aug 09 11:43:07 cubsserver2.localdomain systemd[1]: universe.service: Control process exited, code=exited status=203
Aug 09 11:43:07 cubsserver2.localdomain systemd[1]: universe.service: Failed with result 'exit-code'.
Aug 09 11:43:07 cubsserver2.localdomain systemd[1]: Failed to start Rocket UniVerse Service.
------------------------------
Scott Clift
CAC Financial Corp
US
------------------------------
Scott,
On UniVerse I'd check the license status as root ('su' is fine):
# cd `cat /.uvhome`; bin/uvregen -z
Please note that these are backward single quotes ` and not '
For UniData, set and export the environment variables UDTHOME and LANG and also set PATH to include the UniData bin directory, 'cd' to the UniData home directory and run bin/confcmd -z
Otherwise check the root level files exist in case the have been removed:
/.unishared
/.uvhome (UniVerse only)
/.uvdls (UniVerse only)
For UniData it's a little different for the root level files as UniData allows concurrent installations whereas UniVerse does not. As well as the UniData root level files (which includes /.unishared), check the UDTHOME, PATH and LANG environment variables are correctly set
Was there a system change or housekeeping activity on a previously working system that might have caused this? e.g.
- Moving a VM
- Copying a VM (note: a separate UniVerse or UniData license and license number is required for each installed instance, so moving is fine, but if copying you will need another license)
- File housekeeping / removal. I've seen the root level files over-enthusiastically removed many times.
- Change in user or file permissions - including file ACLs for UniVerse 12 or later.
If this system has not previously worked then permissions either on installation or startup and licensing are favourite.
Regards
JJ
------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------
Scott,
On UniVerse I'd check the license status as root ('su' is fine):
# cd `cat /.uvhome`; bin/uvregen -z
Please note that these are backward single quotes ` and not '
For UniData, set and export the environment variables UDTHOME and LANG and also set PATH to include the UniData bin directory, 'cd' to the UniData home directory and run bin/confcmd -z
Otherwise check the root level files exist in case the have been removed:
/.unishared
/.uvhome (UniVerse only)
/.uvdls (UniVerse only)
For UniData it's a little different for the root level files as UniData allows concurrent installations whereas UniVerse does not. As well as the UniData root level files (which includes /.unishared), check the UDTHOME, PATH and LANG environment variables are correctly set
Was there a system change or housekeeping activity on a previously working system that might have caused this? e.g.
- Moving a VM
- Copying a VM (note: a separate UniVerse or UniData license and license number is required for each installed instance, so moving is fine, but if copying you will need another license)
- File housekeeping / removal. I've seen the root level files over-enthusiastically removed many times.
- Change in user or file permissions - including file ACLs for UniVerse 12 or later.
If this system has not previously worked then permissions either on installation or startup and licensing are favourite.
Regards
JJ
------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------
Hi,
Withdrawn, missed earlier posts
I noticed that the post subject relates to UniData startup but Scott's systemd is for UniVerse. Scott, could you please post the systemd service definition, it may have UniVerse remnants in it.
------------------------------
Chris Turner Turner
Services Manager
Meier Business Systems PTY LTD
Carnegie VIC AU
------------------------------
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
