i2group / analyze-deployment-tooling

Develop i2 Analyze configurations by using the configuration development environment. Review reference architectures for containerised deployments of i2 Analyze.
https://i2group.github.io/analyze-deployment-tooling/
Other
1 stars 1 forks source link

Problem with schema not being valid #36

Closed max-schuller5 closed 1 month ago

max-schuller5 commented 2 months ago

Describe the bug I'm getting the following logs. The schema was originally working but I made some updates not to the schema but the data fed to my schema to stop returning image urls because they were empty. The schema stopped working after I first collected from the updated source. I have reverted to the original code but the connector still doesn't work and throw this error.

[I2ANALYZE] 2024-09-24T23:57:23,533 62774224 [Default Executor-thread-18321] INFO  com.i2group.provisioning.UsersAndGroups@151 - [s: r: []] - Started loading user and group information from the persistence store.
[I2ANALYZE] 2024-09-24T23:57:23,604 62774295 [Default Executor-thread-18321] INFO  com.i2group.provisioning.UsersAndGroups@151 - [s: r: []] - Finished loading user and group information from the persistence store.
[I2ANALYZE] 2024-09-24T23:57:23,678 62774369 [Default Executor-thread-18321] INFO  com.i2group.provisioning.UsersAndGroups@151 - [s: r: []] - No changes were made in this provisioning cycle.
[I2AVAILABILITY] 2024-09-24 23:57:23,975 INFO  SolrHealthStatusLogger         - 'match_index1', 'ALL_REPLICAS_ACTIVE'.
[I2AVAILABILITY] 2024-09-24 23:57:23,971 INFO  SolrHealthStatusLogger         - 'daod_index', 'ALL_REPLICAS_ACTIVE'.
[I2AVAILABILITY] 2024-09-24 23:57:23,980 INFO  SolrHealthStatusLogger         - 'chart_index', 'ALL_REPLICAS_ACTIVE'.
[I2AVAILABILITY] 2024-09-24 23:57:23,980 INFO  SolrHealthStatusLogger         - 'highlight_index', 'ALL_REPLICAS_ACTIVE'.
[I2AVAILABILITY] 2024-09-24 23:57:24,003 INFO  SolrHealthStatusLogger         - 'vq_index', 'ALL_REPLICAS_ACTIVE'.
[I2AVAILABILITY] 2024-09-24 23:57:23,998 INFO  SolrHealthStatusLogger         - 'match_index2', 'ALL_REPLICAS_ACTIVE'.
[I2AVAILABILITY] 2024-09-24 23:57:24,015 INFO  SolrHealthStatusLogger         - 'main_index', 'ALL_REPLICAS_ACTIVE'.
[I2AVAILABILITY] 2024-09-24 23:57:24,030 INFO  SolrHealthStatusLogger         - 'recordshare_index', 'ALL_REPLICAS_ACTIVE'.
[I2ANALYZE] 2024-09-24T23:57:28,375 62779066 [Default Executor-thread-18321] INFO  com.i2group.provisioning.UsersAndGroups@151 - [s: r: []] - The JSON Web Token (JWT) cookie service is available.
[I2PROGRESS_MAIN] 2024-09-24T23:57:28,100.0,0,0
[I2ANALYZE] 2024-09-24T23:57:32,647 62783338 [Default Executor-thread-18321] INFO  com.i2group.disco.servlet.ApplicationLifecycleManager@151 - [s: r: []] - Checking access configuration:
[I2ANALYZE] 2024-09-24T23:57:32,651 62783342 [Default Executor-thread-18321] INFO  com.i2group.disco.servlet.ApplicationLifecycleManager@151 - [s: r: []] -    The application is configured for direct access, or you can set up a proxy server or load balancer to access it.
[I2ANALYZE] 2024-09-24T23:57:32,655 62783346 [Default Executor-thread-18321] INFO  com.i2group.disco.servlet.ApplicationLifecycleManager@151 - [s: r: []] - I2ANALYZE_STATUS:0002 - Application initialized successfully
[I2ANALYZE] 2024-09-24T23:57:38,322 62789013 [Default Executor-thread-18331] INFO  com.i2group.provisioning.UsersAndGroups@151 - [s:<unknown> r:8e600e6b-29d2-43ea-804d-10fb3738f010 []] - The OpenID Connect (OIDC) feature is not available. To enable the use of OIDC for authentication, see the documentation at https://docs.i2group.com/analyze/sec_claims_based.html
[I2ANALYZE] 2024-09-24T23:57:57,689 62808380 [Default Executor-thread-18333] WARN  com.i2group.opal.daod.schema.internal.SchemaExtractor@115 - [s:<unknown> r:05052395-45ce-46d6-be1d-8415623a50bd []] - The connector schema with shortname 'fivecast-onyx-connector' is not valid. The processing instruction target matching "[xX][mM][lL]" is not allowed.
[I2ANALYZE] 2024-09-24T23:57:57,692 62808383 [Default Executor-thread-18333] ERROR com.i2group.opal.daod.connectors.model.internal.ConnectorConfigModelFactory@70 - [s:<unknown> r:05052395-45ce-46d6-be1d-8415623a50bd []] - The connector schema with shortname 'fivecast-onyx-connector' is not valid. The processing instruction target matching "[xX][mM][lL]" is not allowed.
[I2ANALYZE] 2024-09-24T23:59:37,333 62908024 [Default Executor-thread-18365] WARN  com.i2group.opal.daod.schema.internal.SchemaExtractor@115 - [s:<unknown> r:741127b1-e543-4d62-b5ca-b14ea035ca14 []] - The connector schema with shortname 'fivecast-onyx-connector' is not valid. The processing instruction target matching "[xX][mM][lL]" is not allowed.
[I2ANALYZE] 2024-09-24T23:59:37,339 62908030 [Default Executor-thread-18365] ERROR com.i2group.opal.daod.connectors.model.internal.ConnectorConfigModelFactory@70 - [s:<unknown> r:741127b1-e543-4d62-b5ca-b14ea035ca14 []] - The connector schema with shortname 'fivecast-onyx-connector' is not valid. The processing instruction target matching "[xX][mM][lL]" is not allowed.
[I2ANALYZE] 2024-09-25T00:27:31,343 64582034 [Default Executor-thread-18961] INFO  com.i2group.provisioning.UsersAndGroups@151 - [s: r: []] - No changes were made in this provisioning cycle.

Expected behavior For my connector to be functioning

Hardware and Software information Fill in the following information: I'm running it in an ec2 box

OS: Linux ubuntu Version: ubuntu-noble-24.04-amd64-server i2 Analyze version: 4.4.4 Environment type: config-dev Deployment pattern: i2c_cstore

Colvin-Cowie-i2 commented 2 months ago

Hello, the error The processing instruction target matching "[xX][mM][lL]" is not allowed. means that your schema file has some unexpected characters in it, likely a space or new line, or unprintable character, before the opening <?xml declaration. Ensure that the schema file starts with <?xml and no other characters before that.

Anthony-Johnson-i2 commented 1 month ago

Hi @max-schuller5 did Colvin's comment last week help you to resolve your issue?

max-schuller5 commented 1 month ago

unfortunately that was not the issue, is there perhaps a specific line separator I need to use

Anthony-Johnson-i2 commented 1 month ago

Hi @Colvin-Cowie-i2 is there anything else that comes to mind?

Colvin-Cowie-i2 commented 1 month ago

There may be some unprintable characters or a BOM. You can try opening the schema file with Schema Designer, make a small change, and save it again and see whether there's any difference with the updated file. Otherwise it sounds like the schema that's being used isn't actually the one you're looking at - that there's another copy or the connector isn't being rebuilt with your local schema file.

max-schuller5 commented 1 month ago

Thanks for your help turns out it was not related to the schema itself but due to a different issues causing the response to return the schema 3 times