2026-04-12 00:43:04 127.0.0.1 RESPONSE /null/ 554d22314916e040c8ed7032542994ae {"rc":101,"message":"invalid api call","cause":"no request","post_data":""} 2026-04-12 01:05:01 127.0.0.1 REQUEST cron_remove_logs a3f8cfa6eb20f6b1bdf8490dce964f88 {"request":"cron_remove_logs"} 2026-04-12 01:05:01 127.0.0.1 ERROR cron_remove_logs a3f8cfa6eb20f6b1bdf8490dce964f88 {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_22.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_22.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - \nInvalidAccessKeyId<\/Code>The AWS Access Key Id you provided does not exist in our records.<\/Message>AKIA3F4XZBKBTROK5XAQ<\/AWSAccessKeyId>7FHD41GE6VY6C1XF<\/RequestId>X3AQShMbpFM+Cb\/WVeZENNj72TyJgLQXPs3SbwTeYh7a+aacP09h1bP+N9c0TauT\/YlPa4q6imE=<\/HostId><\/Error>)"} 2026-04-12 01:05:01 127.0.0.1 ERROR cron_remove_logs a3f8cfa6eb20f6b1bdf8490dce964f88 {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_23.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_23.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - \nInvalidAccessKeyId<\/Code>The AWS Access Key Id you provided does not exist in our records.<\/Message>AKIA3F4XZBKBTROK5XAQ<\/AWSAccessKeyId>7FH9P0BHA2FGD0G1<\/RequestId>rRRbqFkEfwUCc0jk+hqwdpdBDNvNVgisCkmVeuXqQtlVuCqaSe6mIS21wvKoMW\/xafbFfahYhoQ=<\/HostId><\/Error>)"} 2026-04-12 01:05:01 127.0.0.1 ERROR cron_remove_logs a3f8cfa6eb20f6b1bdf8490dce964f88 {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_24.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_24.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - \nInvalidAccessKeyId<\/Code>The AWS Access Key Id you provided does not exist in our records.<\/Message>AKIA3F4XZBKBTROK5XAQ<\/AWSAccessKeyId>7FH9KC3N5T5N3JR6<\/RequestId>NVaDgA8UDXbCyZ+VJCVoY50hvW6t0X7FAfDsCyklO+FROkX0kaDdYVxv5uRmx3fcwBwDxIdJAkA=<\/HostId><\/Error>)"} 2026-04-12 01:05:01 127.0.0.1 ERROR cron_remove_logs a3f8cfa6eb20f6b1bdf8490dce964f88 {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_25.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_25.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - \nInvalidAccessKeyId<\/Code>The AWS Access Key Id you provided does not exist in our records.<\/Message>AKIA3F4XZBKBTROK5XAQ<\/AWSAccessKeyId>7FHD6B6A4F6J552K<\/RequestId>8xWlesS3R7aRY9hqz2uVGDgBDL1PKno+VSnYQxJ62kwaYny+MWqhOUyr9FTRa09HAaEPg\/ZBFC4=<\/HostId><\/Error>)"} 2026-04-12 01:05:01 127.0.0.1 ERROR cron_remove_logs a3f8cfa6eb20f6b1bdf8490dce964f88 {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_26.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_26.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - \nInvalidAccessKeyId<\/Code>The AWS Access Key Id you provided does not exist in our records.<\/Message>AKIA3F4XZBKBTROK5XAQ<\/AWSAccessKeyId>7FH2XSFXTERZZPW4<\/RequestId>yiEL+xffo6+OEvquk0vRPpyHAr0Tg9XZ8yOQcVBVy9fA4+wmPIy4xFodAAesYFWXHinDRpCrJH8=<\/HostId><\/Error>)"} 2026-04-12 01:05:01 127.0.0.1 ERROR cron_remove_logs a3f8cfa6eb20f6b1bdf8490dce964f88 {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_27.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_27.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - \nInvalidAccessKeyId<\/Code>The AWS Access Key Id you provided does not exist in our records.<\/Message>AKIA3F4XZBKBTROK5XAQ<\/AWSAccessKeyId>7FH79P9BMNJBQZ0E<\/RequestId>FLe\/4M\/fGlNClkJNYFgaU5yYcofcJCt8hQ1BhI24UsXZogkmuKZXPuQfzk9BW2hEW4mBCRfzQAI=<\/HostId><\/Error>)"} 2026-04-12 01:05:01 127.0.0.1 INFO cron_remove_logs a3f8cfa6eb20f6b1bdf8490dce964f88 Removed 0 files 2026-04-12 01:05:01 127.0.0.1 RESPONSE cron_remove_logs a3f8cfa6eb20f6b1bdf8490dce964f88 {"rc":0,"message":"success"} 2026-04-12 12:00:03 127.0.0.1 DEBUG /null/ 918b9702f2be899cf4500db11cd5cf7b MailerQueue: TO: ranf216@gmail.com, FROM: Paypoint , SUBJECT: PayPoint - System Error - API Errors list 2026-04-12 12:00:03 127.0.0.1 DEBUG /null/ 918b9702f2be899cf4500db11cd5cf7b MailerQueue: TO: idanedr@gmail.com, FROM: Paypoint , SUBJECT: PayPoint - System Error - API Errors list 2026-04-12 12:01:01 127.0.0.1 DEBUG /null/ 9fafd3f35a96dc10d6860e1df40f3b0d TO: ranf216@gmail.com, FROM: Paypoint 2026-04-12 12:01:01 127.0.0.1 DEBUG /null/ 9fafd3f35a96dc10d6860e1df40f3b0d SUBJECT: PayPoint - System Error - API Errors list 2026-04-12 12:01:01 127.0.0.1 DEBUG /null/ 9fafd3f35a96dc10d6860e1df40f3b0d MESSAGE:
2026-04-12 01:05:01   127.0.0.1   REQUEST   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"request":"cron_remove_logs"}
2026-04-12 01:05:01   127.0.0.1   ERROR   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_22.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_22.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - <?xml version=\"1.0\" enco
2026-04-12 01:05:01   127.0.0.1   ERROR   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_23.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_23.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - <?xml version=\"1.0\" enco
2026-04-12 01:05:01   127.0.0.1   ERROR   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_24.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_24.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - <?xml version=\"1.0\" enco
2026-04-12 01:05:01   127.0.0.1   ERROR   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_25.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_25.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - <?xml version=\"1.0\" enco
2026-04-12 01:05:01   127.0.0.1   ERROR   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_26.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_26.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - <?xml version=\"1.0\" enco
2026-04-12 01:05:01   127.0.0.1   ERROR   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_27.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_27.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - <?xml version=\"1.0\" enco
2026-04-12 01:05:01   127.0.0.1   INFO   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   Removed 0 files
2026-04-12 01:05:01   127.0.0.1   RESPONSE   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"rc":0,"message":"success"}
2026-04-12 12:01:01 127.0.0.1 DEBUG /null/ 9fafd3f35a96dc10d6860e1df40f3b0d Response: 401 2026-04-12 12:01:02 127.0.0.1 DEBUG /null/ 9fafd3f35a96dc10d6860e1df40f3b0d TO: idanedr@gmail.com, FROM: Paypoint 2026-04-12 12:01:02 127.0.0.1 DEBUG /null/ 9fafd3f35a96dc10d6860e1df40f3b0d SUBJECT: PayPoint - System Error - API Errors list 2026-04-12 12:01:02 127.0.0.1 DEBUG /null/ 9fafd3f35a96dc10d6860e1df40f3b0d MESSAGE:
2026-04-12 01:05:01   127.0.0.1   REQUEST   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"request":"cron_remove_logs"}
2026-04-12 01:05:01   127.0.0.1   ERROR   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_22.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_22.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - <?xml version=\"1.0\" enco
2026-04-12 01:05:01   127.0.0.1   ERROR   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_23.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_23.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - <?xml version=\"1.0\" enco
2026-04-12 01:05:01   127.0.0.1   ERROR   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_24.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_24.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - <?xml version=\"1.0\" enco
2026-04-12 01:05:01   127.0.0.1   ERROR   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_25.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_25.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - <?xml version=\"1.0\" enco
2026-04-12 01:05:01   127.0.0.1   ERROR   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_26.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_26.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - <?xml version=\"1.0\" enco
2026-04-12 01:05:01   127.0.0.1   ERROR   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"rc":341,"message":"s3 failed to save file (Error executing \"PutObject\" on \"https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_27.log\"; AWS HTTP error: Client error response [url] https:\/\/s3.us-west-1.amazonaws.com\/com.iuetechnologies.paypoint.prod\/\/log_archive\/2026_03_27.log [status code] 403 [reason phrase] Forbidden InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - <?xml version=\"1.0\" enco
2026-04-12 01:05:01   127.0.0.1   INFO   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   Removed 0 files
2026-04-12 01:05:01   127.0.0.1   RESPONSE   cron_remove_logs   a3f8cfa6eb20f6b1bdf8490dce964f88   {"rc":0,"message":"success"}
2026-04-12 12:01:02 127.0.0.1 DEBUG /null/ 9fafd3f35a96dc10d6860e1df40f3b0d Response: 401