SYS_INVALID_INPUT_PARAM on repl_resource 4.3

[Alexander Haller]

Hello all,

my new 4.3 test system is getting spammed with this error:

{"log_category":"legacy","log_facility":"local0","log_level":"error","log_message":"[-]\t/irods_source/plugins/resources/replication/src/librepl.cpp:1611:repl_resource::repl_resource(const
std::string &, const std::string &) : status [SYS_INVALID_INPUT_PARAM]
errno [] -- message [token vector size != 2 during parsing of
[Replication resource for
testDatap]]\n\t[-]\t/irods_source/lib/core/src/irods_kvp_string_parser.cpp:95:irods::error
irods::parse_kvp_string(const std::string &, irods::kvp_map_t &, const
std::string &, const std::string &) : status [SYS_INVALID_INPUT_PARAM]
errno [] -- message [token vector size != 2 during parsing of
[Replication resource for
testDatap]]\n\t\t[-]\t/irods_source/lib/core/src/irods_kvp_string_parser.cpp:57:irods::error
irods::parse_token_into_kvp(const std::string &, irods::kvp_map_t &,
const std::string &) : status [SYS_INVALID_INPUT_PARAM] errno [] --
message [token vector size != 2 during parsing of [Replication resource
for
testDatap]]\n\n","server_host":"dev-storage-001","server_pid":1764659,"server_timestamp":"2022-07-29T11:18:13.276Z","server_type":"agent"}

setup:

ilsresc
demoResc:unixfilesystem
testDatap:passthru
└── testDatar:replication
├── test01Data:unixfilesystem
└── test02Data:unixfilesystem

ilsresc -l
resource name: demoResc
id: 10013
zone: heiTESTdevZone
type: unixfilesystem
location: dev-storage-001.XXXXX.XX-XXXX.de
vault: /var/lib/irods/Vault
free space:
free space time: : Never
status:
info:
comment:
create time: 01659092124: 2022-07-29.12:55:24
modify time: 01659092124: 2022-07-29.12:55:24
context:
parent:
parent context:
----
resource name: test01Data
id: 10020
zone: heiTESTdevZone
type: unixfilesystem
location: dev-storage-001.XXXXX.XX-XXXX.de
vault: /mnt/vol_data/irods/volvault/test01
free space:
free space time: : Never
status:
info:
comment:
create time: 01659092142: 2022-07-29.12:55:42
modify time: 01659092142: 2022-07-29.12:55:42
context: heiCLOUD volume resource 01 for testing
parent: 10019
parent context:
----
resource name: test02Data
id: 10021
zone: heiTESTdevZone
type: unixfilesystem
location: dev-storage-001.XXXXX.XX-XXXX.de
vault: /mnt/vol_data/irods/volvault/test02
free space:
free space time: : Never
status:
info:
comment:
create time: 01659092142: 2022-07-29.12:55:42
modify time: 01659092142: 2022-07-29.12:55:42
context: heiCLOUD volume resource 02 for testing
parent: 10019
parent context:
----
resource name: testDatap
id: 10018
zone: heiTESTdevZone
type: passthru
location: EMPTY_RESC_HOST
vault: EMPTY_RESC_PATH
free space:
free space time: : Never
status:
info:
comment:
create time: 01659092142: 2022-07-29.12:55:42
modify time: 01659092142: 2022-07-29.12:55:42
context: Root resource for testDatap
parent:
parent context:
----
resource name: testDatar
id: 10019
zone: heiTESTdevZone
type: replication
location: EMPTY_RESC_HOST
vault: EMPTY_RESC_PATH
free space:
free space time: : Never
status:
info:
comment:
create time: 01659092142: 2022-07-29.12:55:42
modify time: 01659092142: 2022-07-29.12:55:42
context: Replication resource for testDatap
parent: 10018
parent context:


this seems to work:

iput -KPR testDatap test.txt
0/1 - 0.00% of files done 0.000/0.000 MB - 0.00% of file sizes done
Processing test.txt - 0.000 MB 2022-07-29.13:17:47

ils -l test.txt
rods 0 testDatap;testDatar;test01Data 5
2022-07-29.13:17 & test.txt
rods 1 testDatap;testDatar;test02Data 5
2022-07-29.13:17 & test.txt

What does the SYS_INVALID_INPUT_PARAM error mean?

best,
Alexander

[Terrell Russell]

Hi Alex,

The context string is being parsed and you're seeing the parser not be happy with things like "Replication resource for testDatap" in there.

You can leave notes like that in the 'comment' or 'info' fields - rather than the context string.

$ iadmin modresc testDatap comment "Replication resource for testDatap"

Terrell

--
--
The Integrated Rule-Oriented Data System (iRODS) - https://irods.org

 iROD-Chat:  http://groups.google.com/group/iROD-Chat
---
You received this message because you are subscribed to the Google Groups "iRODS-Chat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to irod-chat+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/irod-chat/effcf202-549d-19ca-ba47-0c2743ccd4fc%40gmail.com.

[Alexander Haller]

On 01/08/2022 05.15, Terrell Russell wrote:
> You can leave notes like that in the 'comment' or 'info' fields - rather
> than the context string.
> $ iadmin modresc testDatap comment "Replication resource for testDatap"

thank you very much Terrell that was indeed my problem.

2 follow-up questions came up
1) What is the difference between "info" and "comment" and are there any
best practice regarding that?
2)for example context "comment=test" would also be something I could do?

best,
Alex

[Terrell Russell]

Excellent.

1) There is no difference between 'info' and 'comment' to the iRODS server (or any plugins) that I know of - you can use them interchangeably at this time.

2) Correct, the parsing of the context string is up to the particular plugin for that type of resource...

but the Consortium-released plugins have the convention of using semicolon-delimited key/value pairs, themselves equals-delimited...

e.g. 'a=b;c=d'

Terrell

--
--
The Integrated Rule-Oriented Data System (iRODS) - https://irods.org

 iROD-Chat:  http://groups.google.com/group/iROD-Chat
---
You received this message because you are subscribed to the Google Groups "iRODS-Chat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to irod-chat+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/irod-chat/04f19153-dfc2-9b00-8dcf-1c39cdc09c4f%40gmail.com.