SOLVED: Config Error #1141

khimhoe · 2024-05-08T01:41:13Z

khimhoe
May 8, 2024

I tried to start Butler, but I'm getting the following error:

2024-05-08T01:38:42.883Z error: CONFIG: Getting host info: TypeError [ERR_INVALID_ARG_TYPE]: The "key" argument must be of type string or an instance of ArrayBuffer, Buffer, TypedArray, DataView, KeyObject, or CryptoKey. Received type number (137340747776)
2024-05-08T01:38:43.482Z verbose: Running as standalone app: true
2024-05-08T01:38:43.484Z verbose: New Relic account names/API keys/account IDs (via command line or config file): [
  {
    "accountName": "First NR account",
    "insertApiKey": "<API key 1 (with insert permissions) from New Relic>",
    "accountId": "<New Relic account ID 1>"
  },
  {
    "accountName": "Second NR account",
    "insertApiKey": "<API key 2 (with insert permissions) from New Relic>",
    "accountId": "<New Relic account ID 2>"
  }
]
2024-05-08T01:38:43.484Z debug: CONFIG: API doc mode=off
2024-05-08T01:38:43.488Z info: Enabled API endpoints: []

I'm not using New Relic. I tried to put some dummy value in it and also tried removing the value in the ApriKey and Account ID, but it doesn't work.

Running on Windows standalone exe. Butler version 12.3.0.

mountaindude · 2024-05-08T06:49:51Z

mountaindude
May 8, 2024
Maintainer

Happy to help if I can.

In order to help I need to know a) what command (incl command line options etc) you used to start Butler, and b) what the config file looks like.

You may want to do a find-replace of sensitive info (ip addresses, account names etc) in the config file before posting it here.
Or email it to me if you are comfortable doing that, goran -at- ptarmiganlabs -dot- com.

The config file is somewhat of a beast, but things tend to work out if you scale it down to only include the essentials.

0 replies

mountaindude · 2024-05-14T08:44:19Z

mountaindude
May 14, 2024
Maintainer

@khimhoe

Check out the just released version 12.4.0, which among other things include an updated template/sample config file.

The new config file makes it easier to get started and should help with the New Relic related errors you ran into.

The idea is simply to disable as many features as possible (most were already disabled in the previous config file version, but not all).

Some settings do need to be set, as they control how Butler connects to the Sense server.
These settings are listed at the beginning of the template config file.
Looks like this:

---
Butler:
  # General notes: 
  # - File and directory paths in this sample config file use Linux/Mac syntax, i.e. using forward slashes.
  #   Windows paths work just as well, just make sure to quote them with single or double quotes.
  # - All entries in the config file are mandatory in the sense that they must be present.
  #   However, if a feature is not used the corresponding config entries can contain 
  #   any value (for example the provided default ones).
  # - Butler will start using the settings in this file if the follwing settings are set first:
  #   - Butler.cert.clientCert: Set to the path of the client certificate file. If relative paths cause issues, use an absolute path.
  #   - Butler.cert.clientCertKey: Set to the path of the client key file. If relative paths cause issues, use an absolute path.
  #   - Butler.cert.clientCertCA: Set to the path of the CA certificate file. If relative paths cause issues, use an absolute path.
  #   - Butler.configEngine.host: Set to the IP or FQDN of the host where the Sense engine service is running.
  #   - Butler.configEngine.port: Set to the port where the Sense engine service is listening.
  #   - Butler.configQRS.host: Set to the IP or FQDN of the host where the Qlik Repository Service (QRS) is running.
  #   - Butler.configQRS.port: Set to the port where the Qlik Repository Service (QRS) is listening.
  # - Having set the above settings, Butler will start and run, but it will not do anything useful until you configure
  #   the various monitoring and notification settings, as described at https://butler.ptarmiganlabs.com.
  ...
  ...

0 replies

mountaindude · 2024-05-16T06:41:27Z

mountaindude
May 16, 2024
Maintainer

Adding to the above, the error messages you got indicate you have partial New Relic configuration settings in your Butler config file.
Removing or commenting out things like this:

Instead of this:

  thirdPartyToolsCredentials:
    newRelic:         # Array of New Relic accounts/insert keys. Any data sent to New Relic will be sent to both accounts. 
      - accountName: First NR account
        insertApiKey: <API key 1 (with insert permissions) from New Relic> 
        accountId: <New Relic account ID 1>
      - accountName: Second NR account
        insertApiKey: <API key 2 (with insert permissions) from New Relic> 
        accountId: <New Relic account ID 2>

You do this:

  thirdPartyToolsCredentials:
    newRelic:         # Array of New Relic accounts/insert keys. Any data sent to New Relic will be sent to both accounts. 
      # - accountName: First NR account
      #   insertApiKey: <API key 1 (with insert permissions) from New Relic> 
      #   accountId: <New Relic account ID 1>
      # - accountName: Second NR account
      #   insertApiKey: <API key 2 (with insert permissions) from New Relic> 
      #   accountId: <New Relic account ID 2>

Or simply this:

  thirdPartyToolsCredentials:
    newRelic:         # Array of New Relic accounts/insert keys. Any data sent to New Relic will be sent to both accounts.

Example 2

And instead of this (and other places where same info is used):

    newRelic:
      enable: false
      destinationAccount:
        event:                    # Failed/aborted reload tasks are sent as events to these New Relic accounts
          - First NR account
          - Second NR account
        log:                      # Failed/aborted reload tasks are sent as log entries to these New Relic accounts
          - First NR account
          - Second NR account

Do this:

    newRelic:
      enable: false
      destinationAccount:
        event:                    # Failed/aborted reload tasks are sent as events to these New Relic accounts
          # - First NR account
          # - Second NR account
        log:                      # Failed/aborted reload tasks are sent as log entries to these New Relic accounts
          # - First NR account
          # - Second NR account

You can also just remove the lines instead of commenting them out:

    newRelic:
      enable: false
      destinationAccount:
        event:                    # Failed/aborted reload tasks are sent as events to these New Relic accounts
        log:                      # Failed/aborted reload tasks are sent as log entries to these New Relic accounts

0 replies

PavelKassitchev · 2024-06-25T13:24:31Z

PavelKassitchev
Jun 25, 2024

Hi, newRelic lines are commented as in the samples above but I do get the same error

Butler version 12.4.0

0 replies

mountaindude · 2024-06-27T06:37:47Z

mountaindude
Jun 27, 2024
Maintainer

Thanks for reporting this. Sounds like you might have found a corner case that’s not covered by the config-file-verification code in Butler. I am traveling right now but will take a look at this when I get a chance, then update this ticket. Cheers, Göran

…

On Tue, 25 Jun 2024 at 15:24, PavelKassitchev ***@***.***> wrote: Hi, newRelic lines are commented as in the samples above but I do get the same error butler.PNG (view on web) <https://github.com/ptarmiganlabs/butler/assets/37771913/b5377a29-6128-4d38-b5ed-0224f14ea11a> Butler version 12.4.0 — Reply to this email directly, view it on GitHub <#1141 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAH3JDR7KVUDKDWD57PKXPTZJFVSJAVCNFSM6AAAAABHMBIXZCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQNZRG42DC> . You are receiving this because you commented.Message ID: ***@***.***>

0 replies

mountaindude · 2024-06-27T06:43:54Z

mountaindude
Jun 27, 2024
Maintainer

@PavelKassitchev
Is it possible for you to provide a copy of your config file?
Anonymise it if needed (scramble host names etc), but make sure to leave the structure intact.
This will make it vastly easier for me to understand what’s causing the issue.
Feel free to send it to goran ptarmiganlabs com if so.

What you experienced could be caused by a bug in Butler, but it could also be an incorrectly formatted config file.
If the latter there should ideally be a better error message - agreed.
Either way, without knowing what your config file looks like it will be difficult for me to replicate your issue and thus fixing it.

1 reply

PavelKassitchev Jun 27, 2024

Goeran, I am impressed by Butler family!)
Now I am looking at Ctrl-Q. Maybe my question is stupid but where can I find my auth-user-dir? I am comparatively new in Qlik and never used user directories...

PavelKassitchev · 2024-06-27T06:53:52Z

PavelKassitchev
Jun 27, 2024

Thank you Goeran for the quick reply. Attached is the config file. The only sensitive data, I think, was the server name. In the attached file it is replaced by "MySever" Thank you again! чт, 27 июн. 2024 г. в 09:44, Göran Sander ***@***.***>:

…

@PavelKassitchev <https://github.com/PavelKassitchev> Is it possible for you to provide a copy of your config file? Anonymise it if needed (scramble host names etc), but make sure to leave the structure intact. This will make it vastly easier for me to understand what’s causing the issue. Feel free to send it to goran ptarmiganlabs com if so. What you experienced could be caused by a bug in Butler, but it could also be an incorrectly formatted config file. If the latter there should ideally be a better error message - agreed. Either way, without knowing what your config file looks like it will be difficult for me to replicate your issue and thus fixing it. — Reply to this email directly, view it on GitHub <#1141 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJAFVCLTC3MXKNIA7YC2DO3ZJOYD5AVCNFSM6AAAAABHMBIXZCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQOJQGMYDM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

1 reply

mountaindude Jul 2, 2024
Maintainer

@PavelKassitchev
I can't find any config file - it must have gotten lost somewhere.
If you just email it to goran -at- ptarmiganlabs -dot- com I can take a look at it.

Regarding Ctrl-Q and the ´auth-user-dir` question, please post a question in that Github repository, so things are kept in the right place.
The link is https://github.com/ptarmiganlabs/ctrl-q/discussions/categories/q-a

PavelKassitchev · 2024-07-03T04:26:13Z

PavelKassitchev
Jul 3, 2024

Hello Goeran, Indeed the file was missed. Trying to send it again вт, 2 июл. 2024 г. в 19:06, Göran Sander ***@***.***>:

…

@PavelKassitchev <https://github.com/PavelKassitchev> I can't find any config file - it must have gotten lost somewhere. If you just email it to goran -at- ptarmiganlabs -dot- com I can take a look at it. Regarding Ctrl-Q and the ´auth-user-dir` question, please post a question in that Github repository, so things are kept in the right place. The link is https://github.com/ptarmiganlabs/ctrl-q/discussions/categories/q-a — Reply to this email directly, view it on GitHub <#1141 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJAFVCPG62NCEXMDCZVUQ5DZKLFXVAVCNFSM6AAAAABHMBIXZCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSMZYHAZDS> . You are receiving this because you were mentioned.Message ID: ***@***.***>

0 replies

PavelKassitchev · 2024-07-03T04:32:05Z

PavelKassitchev
Jul 3, 2024

production.txt
O! I understood. Github doesn't alow yaml files. I have just converted to simple txt

0 replies

mountaindude · 2024-07-03T10:51:30Z

mountaindude
Jul 3, 2024
Maintainer

I tried to start Butler, but I'm getting the following error:

2024-05-08T01:38:42.883Z error: CONFIG: Getting host info: TypeError [ERR_INVALID_ARG_TYPE]: The "key" argument must be of type string or an instance of ArrayBuffer, Buffer, TypedArray, DataView, KeyObject, or CryptoKey. Received type number (137340747776)

@khimhoe, the latest Butler version (12.4.2, available here) should take care of the ERR_INVALID_ARG_TYPE error you got.
Long story short, there was a corner-case bug that showed itself in some rare conditions, which your server matched/triggered.

The default New Relic config has also been cleaned up, so things should be smoother with the latest version.

0 replies

khimhoe · 2024-07-05T02:37:31Z

khimhoe
Jul 5, 2024
Author

Hi Goran, Just tested it, and it works fine now without any error! Thank you. :)

…

On Wed, Jul 3, 2024 at 6:51 PM Göran Sander ***@***.***> wrote: I tried to start Butler, but I'm getting the following error: 2024-05-08T01:38:42.883Z error: CONFIG: Getting host info: TypeError [ERR_INVALID_ARG_TYPE]: The "key" argument must be of type string or an instance of ArrayBuffer, Buffer, TypedArray, DataView, KeyObject, or CryptoKey. Received type number (137340747776) @khimhoe <https://github.com/khimhoe>, the latest Butler version (12.4.2, available here <https://github.com/ptarmiganlabs/butler/releases/tag/butler-v12.4.2>) should take care of the ERR_INVALID_ARG_TYPE error you got. Long story short, there was a corner-case bug that showed itself in some rare conditions, which your server matched/triggered. The default New Relic config has also been cleaned up, so things should be smoother with the latest version. — Reply to this email directly, view it on GitHub <#1141 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPBSOIAQF72W7HXKAULRQLZKPJUPAVCNFSM6AAAAABHMBIXZCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSNBWG43DK> . You are receiving this because you were mentioned.Message ID: ***@***.***>

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

SOLVED: Config Error #1141

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 11 comments 2 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

SOLVED: Config Error #1141

khimhoe May 8, 2024

Replies: 11 comments · 2 replies

mountaindude May 8, 2024 Maintainer

mountaindude May 14, 2024 Maintainer

mountaindude May 16, 2024 Maintainer

Example 2

PavelKassitchev Jun 25, 2024

mountaindude Jun 27, 2024 Maintainer

mountaindude Jun 27, 2024 Maintainer

PavelKassitchev Jun 27, 2024

PavelKassitchev Jun 27, 2024

mountaindude Jul 2, 2024 Maintainer

PavelKassitchev Jul 3, 2024

PavelKassitchev Jul 3, 2024

mountaindude Jul 3, 2024 Maintainer

khimhoe Jul 5, 2024 Author

khimhoe
May 8, 2024

Replies: 11 comments 2 replies

mountaindude
May 8, 2024
Maintainer

mountaindude
May 14, 2024
Maintainer

mountaindude
May 16, 2024
Maintainer

PavelKassitchev
Jun 25, 2024

mountaindude
Jun 27, 2024
Maintainer

mountaindude
Jun 27, 2024
Maintainer

PavelKassitchev
Jun 27, 2024

mountaindude Jul 2, 2024
Maintainer

PavelKassitchev
Jul 3, 2024

PavelKassitchev
Jul 3, 2024

mountaindude
Jul 3, 2024
Maintainer

khimhoe
Jul 5, 2024
Author