Hi, I think the sasl handshake is the issue: On gateway: 2023-04-26T15:25:49.341+0700 7f7f04d21700 1 ERROR: failed to create push endpoint: due to: pubsub endpoint configuration error: unknown schema in: 2023-04-26T15:25:49.341+0700 7f7f04d21700 5 req 245249540 0.003999965s s3:delete_obj WARNING: publishing notification failed, with error: -22 2023-04-26T15:25:49.341+0700 7f7f04d21700 2 req 245249540 0.003999965s s3:delete_obj completing 2023-04-26T15:25:49.341+0700 7f7f04d21700 2 req 245249540 0.003999965s s3:delete_obj op status=0 2023-04-26T15:25:49.341+0700 7f7f04d21700 2 req 245249540 0.003999965s s3:delete_obj http status=204 2023-04-26T15:44:31.978+0700 7f7fc3e9f700 20 notification: 'bulknotif' on topic: 'bulk-upload-tool-ceph-notifications' and bucket: 'connectivity-bulk-upload-file-bucket' (unique topic: 'bulknotif_bulk-upload-tool-ceph-notifications') apply to event of type: 's3:ObjectCreated:Put' 2023-04-26T15:44:31.978+0700 7f7fc3e9f700 1 ERROR: failed to create push endpoint: due to: pubsub endpoint configuration error: unknown schema in: 2023-04-26T15:44:31.978+0700 7f7fc3e9f700 5 req 245262095 0.004999956s s3:put_obj WARNING: publishing notification failed, with error: -22 2023-04-26T15:44:31.978+0700 7f7fc3e9f700 2 req 245262095 0.004999956s s3:put_obj completing In kafka we see this: [2023-04-26 15:45:20,921] INFO [SocketServer listenerType=ZK_BROKER, nodeId=1] Failed authentication with /xx.93.1 (Unexpected Kafka request of type METADATA during SASL handshake.) (org.apache.kafka.common.network.Selector) [2023-04-26 15:45:21,921] INFO [SocketServer listenerType=ZK_BROKER, nodeId=1] Failed authentication with /xx.93.1 (Unexpected Kafka request of type METADATA during SASL handshake.) (org.apache.kafka.common.network.Selector) [2023-04-26 15:45:22,921] INFO [SocketServer listenerType=ZK_BROKER, nodeId=1] Failed authentication with /xx.93.1 (Unexpected Kafka request of type METADATA during SASL handshake.) (org.apache.kafka.common.network.Selector) Istvan Szabo Staff Infrastructure Engineer --------------------------------------------------- Agoda Services Co., Ltd. e: istvan.szabo@xxxxxxxxx<mailto:istvan.szabo@xxxxxxxxx> --------------------------------------------------- On 2023. Apr 27., at 15:08, Yuval Lifshitz <ylifshit@xxxxxxxxxx> wrote: Email received from the internet. If in doubt, don't click any link nor open any attachment ! ________________________________ Hi Istvan, Looks like you are using user/password and SSL on the communication channels between RGW and the Kafka broker. Maybe the issue is around the certificate? could you please increase RGW debug logs to 20 and see if there are any kafka related errors there? Yuval On Tue, Apr 25, 2023 at 5:48 PM Szabo, Istvan (Agoda) <Istvan.Szabo@xxxxxxxxx<mailto:Istvan.Szabo@xxxxxxxxx>> wrote: Hi, I'm trying to set a kafka endpoint for bucket object create operation notifications but the notification is not created in kafka endpoint. Settings seems to be fine because I can upload to the bucket objects when these settings are applied: NotificationConfiguration> <TopicConfiguration> <Id>bulknotif</Id> <Topic>arn:aws:sns:default::butcen</Topic> <Event>s3:ObjectCreated:*</Event> <Event>s3:ObjectRemoved:*</Event> </TopicConfiguration> </NotificationConfiguration> but it simply not created any message in kafka. This is my topic creation post request: https://xxx.local/? Action=CreateTopic& Name=butcen& kafka-ack-level=broker& use-ssl=true& push-endpoint=kafka://ceph:pw@xxx.local:9093 Am I missing something or it's definitely kafka issue? Thank you ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses. _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx<mailto:ceph-users@xxxxxxx> To unsubscribe send an email to ceph-users-leave@xxxxxxx<mailto:ceph-users-leave@xxxxxxx> _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |