Domino on Linux/Unix, Troubleshooting, Best Practices, Tips and more ...

Domino on Linux Start Script 3.1.3 with changed way to request it

Daniel Nashed  30 October 2017 05:43:05
Just updated the start script to a new version with some minor changes.
There was one issue with systemd on shutdown and I made a change in the way config files are used.

Most of the new features are coming in either thru projects or when I want something for my own environment.
I don't get much feedback or feature requests beside that.

One change triggered by a project was how config files apply. We wanted to use the same configuration for all servers.
But we wanted special settings for the Traveler servers. So I changed the way the config files apply.
Now you can use a general config and additional or changed parameters for individual servers.
That way you can have a general config that you deploy automatically and you keep a server specific file with changes.

So in that case the general config would be /etc/sysconfig/rc_domino_config.
And the specific config would be for example: /etc/sysconfig/rc_domino_config_notes.

This would also work in partitioned environments where each server has a basic configuration and you want additional parameters for a partition.
On the other side even on partitioned servers you could use variables which depend on variables like the DOMINO_USER.


Changed way to request the start script

I am also changing the way you can request the new version. Until now I had a request form.
Now you just send a mail to dominostartscript  at nashcom.de with the subject "script".

The old implementation was a servertask which read the data posted in database.
I switched to a pre-delivery agent with some additional logic to check the message.
So for example I am not triggering an automatic reply if the message is a reply or is an autosubmitted message.

I am not yet updating the start script page and want to see first how this works with requests coming in thru the blog.
And I hope you like the new way to request the start script? Any feedback is welcome.

-- Daniel



--------------
Change History
--------------

V3.1.3 30.10.2017

Problems Solved
---------------

Fixed an issue with systemd in combination with server controller.
Now the server controller correctly shutsdown when the service is stopped


New Features
------------

listini -- displays server's notes.ini

Changes
-------

Changed sample rc_domino_config_notes setting DOMINO_PRE_SHUTDOWN_COMMAND to "tell traveler shutdown"


V3.1.2 01.09.2017

New Features
------------

New check if Domino ".res" files exist and readable to generate warnings

New short cut command "res" for "resources"

Changes
-------

In previous version either the server specific config file was used or the default config file.

The config files are now used in the following order to allow more flexible configurations:

- First the default config-file is loaded if exists (by default: /etc/sysconfig/rc_domino_config)
- In the next step the server specifc config-file (by default: /etc/sysconfig/rc_domino_config_notes) is included.
- The server specific config file can add or overwrite configuration parameters.

This allows very flexible configurations. You can specify global parameters in the default config file and have specific config files  per Domino partition.
So you can now use both config files in combination or just one of them.

Comments

1Tihomir Pantovic  30.10.2017 10:50:38  Domino on Linux Start Script 3.1.3 with changed way to request it

Maybe, no one is requesting special features because you already put more than needed in :)

I just requested and got (after 10 minutes) script, it looks like agent works as expected.

Personally, I prefer old way of requesting script, it looks like "more natural way":

read about version in browser, request it in browser, get it to email

vs. read about version in browser, open mail/tab, send, wait (have I addressed it good?).

You can leave both ways :)

2Daniel Nashed  30.10.2017 14:05:39  Domino on Linux Start Script 3.1.3 with changed way to request it

The time lag came from a grey listing because of missing good rating.

You should get a reply immediately.

I am changing the way to implement it for multiple reasons.

One is that you don't need to fill in a form and you cannot type a wrong email address.

The other is that the mail was send by a servertask and I am changing that now to the pre-delivery agent.

The code does a lot of other things including richtext rewirting and I would have needed to spend time testing it on 64bit.

So I am updating the server that is running this application finally to 64bit -- because since FP8 there is only Linux64 support.

That means it would need Q&A effort to continue the forms based requester. The code runs unchanged since 2000..

And it was a good opportunity to play with pre-delivery agents doing auto reply.

-- Daniel

3Tihomir Pantovic  30.10.2017 16:49:31  Domino on Linux Start Script 3.1.3 with changed way to request it

You know your setup, and certainly you'll choose wisely :)

If you are playing with standard Domino Agents - few things from this KB { Link } were new for me recently (when I used it)

4rosyidi  02.11.2017 7:09:28  Domino on Linux Start Script 3.1.3 with changed way to request it

Hi Daniel,

thanks for updating the script,

I just upgrade domino server 9 using centOS 7 which have problem when implementing this script. I use partition environment.

the error message like this :

Unit rc_domino_nodinapp01.service has begun starting up.

Nov 02 12:48:03 nd.basecampnet.lan rc_domino_script[56129]: Unknown platform 'uname'

Nov 02 12:48:03 nd.bascempnet.lan systemd[1]: rc_domino_nodinapp01.service: control process exited, code=exited status=1

Nov 02 12:48:03 nd.basecampnet.lan systemd[1]: Failed to start IBM Domino Server (nodinapp01).

-- Subject: Unit rc_domino_nodinapp01.service has failed

-- Defined-By: systemd

-- Support: { Link }

--

-- Unit rc_domino_nodinapp01.service has failed.

--

-- The result is failed.

Nov 02 12:48:03 nd.basecampnet.lan systemd[1]: Unit rc_domino_nodinapp01.service entered failed state.

Nov 02 12:48:03 nde.basecampnet.lan systemd[1]: rc_domino_nodinapp01.service failed.

Nov 02 12:48:03 nd.basecampnet.lan polkitd[703]: Unregistered Authentication Agent for unix-process:56123:5919945 (system bus name :1.355, object path /org/freedesktop

before this I use your previous script for many years, just fine and running well.

--Rosyidi--


  • [IBM Lotus Domino]
  • [Domino on Linux]
  • [Nash!Com]
  • [Daniel Nashed]