Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ra/SAPHanaRA* - HANA_CALL reason for inner timeout? #122

Open
PeterPitterling opened this issue Sep 27, 2022 · 2 comments
Open

ra/SAPHanaRA* - HANA_CALL reason for inner timeout? #122

PeterPitterling opened this issue Sep 27, 2022 · 2 comments

Comments

@PeterPitterling
Copy link
Contributor

PeterPitterling commented Sep 27, 2022

2cc0fba introduced an inner timeout call for the command to be executed

unfortunately, the commit comment does not provide more insights.

The reason for this clarification is the current modification to get rid of the HDBSettings.sh call. The inner timeout does not like 'cdpy' as first command. see #121

an additional true as first command would work around this, but the question is, whether this 2nd timeout could be removed at all ?!

@PeterPitterling
Copy link
Contributor Author

a fix for the cdpy issue would be to use the pre_script variable as offered in PR #124

[[ $cmd == python* ]] && pre_script="cdpy" || pre_script="true"

timeout --foreground -s 9 60 su - oqladm -c "(cdpy; timeout --foreground -s 9 60 python landscapeHostConfiguration.py)"

@angelabriel
Copy link
Collaborator

The first timeout is for the 'pre_cmd', especially for the 'su ' to handle situations, where the user authentication is not working (e.g. sidadm user defined in ldap or Active Directory). The second timeout is for the called HANA command like systemReplicationStatus.py or others. So we can NOT remove the second timeout.
And as a side note - everything added after the '$pre_cmd' is running in context of the used shell of the sidadm user, which might be bash or csh. Especially the 'csh' had caused me headaches in the past 😅 as I'm not used to work in csh environments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants