Add more non-problematic strings to ResultAnalyzer

[amenk]

In src/AqBanking/Command/ShellCommandExecutor/ResultAnalyzer.php

This should be added:

    '/===== Getting Certificate =====/',

This might as well be needed on some setups - it does not seem to be critical - but there might be problems with Unicode Characters. Maybe we need a strict- and not-so-strict-mode

    '/Plugin "aqebics" not found/',
    '/Could not load backend "aqebics"/',
    '/Plugin "de" not found./',
    '/BankInfo plugin for country "de" not found/',

[eporsche]

Nowadays I also get the message:

Selecting PAIN format...

Which throws an error. Not sure if anyone else is experiencing this.

[amenk]

Which AqBanking version are you using? Might be a new message and seems to be save to ignore for me.

[eporsche]

That's very well possible:

Versions:
AqBanking-CLI: 6.4.1
Gwenhywfar : 5.8.0.0
AqBanking : 6.4.1.0

Full message is sth. like this:
[Date]:aqhbci(34):jobtransferbase.c: 1036: Selecting PAIN format [urn:iso:std:iso:20022:tech:xsd:pain.001.001.03]
when issuing new transfers.

[eporsche]

I also sometimes see this error message:

3:[Date]:gwen(32):padd.c:  649: Bad padding: leading bits must be zero (7)
3:[Date]:aqhbci(32):msgcrypt_rxh_common.c: 1274: here (-101)
3:[Date]:aqhbci(32):msgcrypt_rxh_common.c: 1275: Error verifying this data:
  Buffer:
  Pos            : 255 (00ff)
  Buffer Size    : 273
  Hard limit     : 16777216
  Bytes Used     : 255
  Bytes Reserved : 0
  Flags          : 00000001 ( OWNED )
  Mode           : 00000003 ( DYNAMIC ABORT_ON_MEMFULL )
  Bookmarks      : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
  Data:
   String size is 255:
   [Hex Code here]
3:[Date]:aqhbci(32):msgcrypt_rxh_common.c: 1754: Could not verify data with medium of user \"XXXX\" (-101)
3:[Date]:aqhbci(32):job_crypt.c:  166: Not signed by expected signer (1)
3:[Date]:aqhbci(32):job_crypt.c:  236: Job signed with unexpected key(s)(was expecting \"COMMERZBANK AG\"):
3:[Date]:aqhbci(32):job_crypt.c:  242: Signed unexpectedly with key \"?COMMERZBANK AG\"
3:[Date]:aqhbci(32):outbox.c:  451: Error in job \"JobSepaTransferMulti\": -1007 

This one is not save to exclude I guess. However the official mailing list could not help. Did you see this one as well?

[eporsche]

Hmm, had a look into the jobtransferbase.c it seems that the log level of "Selecting PAIN format" is error. I guess I need to ask the author if this is correct..

[amenk]

I think the loglevels are not very granular in AqBanking, I would be best du have a --quiet switch and we could avoid the filtering completely.

[amenk]

There is

7.1. AQBANKING_LOGLEVEL
-----------------------

This variable stores the loglevel to be used for AqBanking.
Possible values are: emergency, alert, critical, error, warning, notice,
info, debug and verbous. Each following log level includes the previous
one.

see https://github.com/aqbanking/aqbanking

maybe we should set this env to "error" or even "critical" when calling aqbanking-cli?

CC
@grummbeer

[grummbeer]

maybe we should set this env to "error" or even "critical"

It is already "error".

aqbanking-php/src/Command/ShellCommandExecutor.php

Lines 9 to 15 in 1fdb337

	class ShellCommandExecutor
	{
	public const ERROR_REPORTING = 'error';
	public function execute(string $shellCommand): Result
	{
	$shellCommand = 'AQBANKING_LOGLEVEL=' . self::ERROR_REPORTING .

No clue on this, can't provoke messages to see any difference in output from level error upwards.