Skip to content
This repository has been archived by the owner on Aug 5, 2022. It is now read-only.

Intel PODM 2.3 connect PSME Compute Agent Simulator but PSQLException: ERROR: operator does not exist #93

Open
housemic opened this issue Oct 8, 2018 · 7 comments
Labels

Comments

@housemic
Copy link

housemic commented Oct 8, 2018

Dear Intel -
in the configuration -
Intel PODM 2.3 connect Intel REST server 2.3 and Intel PSME Compute Agent Simulator 2.3,
but PODM application log has the error message - PSQLException: ERROR: operator does not exist: text ,
Could you have comments for my debugging? thank you.

Intel PODM 2.3 IP Address - 10.3.0.1
Intel REST server 2.3 and Intel PSME Compute Agent Simulator 2.3 IP address - 10.3.0.2

Attachment 1 -
2018-10-08-podm1-2p3-01-install-curl-log -
the file has PDOM error messages -
2018-10-08-podm1-2p3-01-install-curl-log.zip

Attachment 2 -
2018-10-08-podm1-2p3-02-curl-log -
The file is the result that in PODM server I use curl to GET PSME resource and works normally -
2018-10-08-podm1-2p3-02-curl-log.zip

Attachment 3 -
2018-10-08-podm1-2p3-03-pod-manager-healthcheck-log -
The file is the result I run pod-manager-healthcheck -
2018-10-08-podm1-2p3-03-pod-manager-healthcheck-log.zip

@housemic housemic changed the title Intel PODM 2.3 connect PSME Compute Agent Simulator but PSQLException: ERROR: operator does not exist: text Intel PODM 2.3 connect PSME Compute Agent Simulator but PSQLException: ERROR: operator does not exist Oct 8, 2018
@RobertCMa
Copy link

Hi @housemic ,

This can refer to postgresql-9.5-main.log. It can start from checking endpoint and its related properties.

2018-10-08 09:36:10.940 CST [67974] podm@podm ERROR: operator does not exist: text ~~ bytea at character 1291
2018-10-08 09:36:10.940 CST [67974] podm@podm HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts.
2018-10-08 09:36:10.940 CST [67974] podm@podm STATEMENT: select endpoint0_.id as id2_31_, endpoint0_1_.event_source_context as event_so3_31_, endpoint0_1_.version as version4_31_, endpoint0_1_.description as descript5_31_, endpoint0_1_.global_id as global_i6_31_, endpoint0_1_.is_complementary as is_compl7_31_, endpoint0_1_.name as name8_31_, endpoint0_1_.status as status9_31_, endpoint0_.endpoint_authentication_password as endpoint1_38_, endpoint0_.endpoint_authentication_username as endpoint2_38_, endpoint0_.composed_node_id as compose11_38_, endpoint0_.computer_system_id as compute12_38_, endpoint0_.entity_id as entity_i3_38_, endpoint0_.fabric_id as fabric_13_38_, endpoint0_.host_reservation_memory_bytes as host_res4_38_, endpoint0_.endpoint_metadata_id as endpoin14_38_, endpoint0_.device_id as device_i5_38_, endpoint0_.subsystem_id as subsyste6_38_, endpoint0_.subsystem_vendor_id as subsyste7_38_, endpoint0_.vendor_id as vendor_i8_38_, endpoint0_.processor_id as process15_38_, endpoint0_.endpoint_protocol as endpoint9_38_, endpoint0_.storage_service_id as storage16_38_, endpoint0_.zone_id as zone_id17_38_ from endpoint endpoint0_ inner join discoverable_entity endpoint0_1_ on endpoint0_.id=endpoint0_1_.id inner join endpoint_identifier identifier1_ on endpoint0_.id=identifier1_.endpoint_id where identifier1_.durable_name like ('%'||$1||'%')

@housemic
Copy link
Author

Dear Robert CMa
Thank you.
Could you help the questions:

Q 2 : the error message : operator does not exist: text ~~ byte,
Does it mean that the error is related to data types are mismatched ? (text and byte)

Q 3 : Where I find the source code for the above statement : select endpoint _0 ...

Housemic

@RobertCMa
Copy link

Hi @housemic,

The log and source are from postgresql. You can check on the postgresql forum for more detail.

@housemic
Copy link
Author

Dear RobertCMa -
Q 4-
How to dump the data for the SQL STATEMENT: select endpoint0_.id as id2_31_, endpoint0_1_.event_source_context as ... ?

because I want to debug that to survey the issue is related to database record or not.

thank you.
House

@housemic
Copy link
Author

Dear RobertCMa -
I test 2 cases and got these results -
case 1 -
Intel PODM "2.2" connects to "Intel PSME rest server 2.2+ PSME Compute Agent Simulator 2.2", not found the issue.

case 2 -
Intel PODM "2.3" connects to "Intel PSME rest server 2.2+ PSME Compute Agent Simulator 2.2", the issue still happens.

Q 5-
by above cases, I think Intel PODM 2.3 has the issue when it connects to PSME 2.3, Could you help to check ? thank you.

House

@housemic
Copy link
Author

Dear RobertCMa,
for Q 3 -
I found postgresql. related information about QueryExecutorImpl.java, (in #96)
and
Could you help Q 4 and Q 5 ? thank you
House

@boucherv
Copy link

boucherv commented Dec 18, 2018

Hi @housemic,

I have exactly the same issue .. you fix it since October ?

Any update on this issue from @RobertCMa or @tmacieje ?

Thanks in advance,
Valentin

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

No branches or pull requests

3 participants