Script Emailing is failing with an SQL Server Bug
tracked
John Codesmith
Sim to Sim / Script to Script Emailing is failing with this error:
mailtolsl@mail-in-agni-2.secondlife.io> (expanded from
<5243fc88-9820-3f0a-649c-eb5d4f803003@lsl.secondlife.com>): Command died
with status 11: "/opt/linden/indra/tools/mailglue/mailglue --grid=agni
--system=lsl". Command output: DBD::mysql::db do failed: Data too long for
column 'script_id' at row 1 at /opt/linden/indra/tools/mailglue/mailglue
line 492, <STDIN> line 136. DBD::mysql::db do failed: Data too long for
column 'script_id' at row 1 at /opt/linden/indra/tools/mailglue/mailglue
line 492, <STDIN> line 136. Unable to get task mail presence from
The email is a simple subject of: "123" to rule out any weird text strings or anything with no body text at all and sent to: 5243fc88-9820-3f0a-649c-eb5d4f803003@lsl.secondlife.com (prim key)
The Servers should not be failing like this.
AI Breakdown of the error:
Breakdown of the error message
DBD::mysql::db do failed: Data too long for column 'script_id'
DBD::mysql: This refers to the Perl database driver for MySQL, a database Linden Lab uses for its services.
Data too long for column 'script_id': This is the core problem. The email system tried to save a value into the script_id column of its database, but the value was too long for the column's defined size.
at row 1: This indicates the error occurred on the first row of data it tried to write.
Unable to get task mail presence from http://localhost:12040/service-proxy/task/...
This is a secondary error resulting from the first one. Because the initial database write failed, the mail system couldn't get a confirmation (task mail presence) from the internal service running on localhost (the Second Life server itself).
Thank you for looking into this. I really need LSL email to work for my system
Log In
John Codesmith
I will give it another try this weekend, today probably and give you my results - heck I will send it an email now and see. Well, it has been several minutes now and no kickback! - I think the issue might have been resolved somehow? - Thank you, Maestro!!
John Codesmith
AI:
This is an error bounce message from Second Life's mail server, not a recipient address with encoded characters.
What happened here:
You sent an email to 181453a7-540c-c9f7-67ed-109704248c3e@lsl.secondlife.com (a prim's email address)
Second Life's mail system (mail-in-agni-2.secondlife.io) tried to process it but failed
You received this bounce-back error from the mail system
The key error is:
DBD::mysql::db do failed: Data too long for column 'script_id' at row 1
This means Second Life's mail processing script tried to store something in a MySQL database column called script_id, but the data was too long for that column. This is a bug in Second Life's email-to-prim system, not something wrong with what you sent.
The error repeats twice and then says it couldn't get the task mail presence from their internal service.
What you're seeing in Hotmail is the bounce message showing you the technical details of why delivery failed. The original prim email address (181453a7-540c-c9f7-67ed-109704248c3e@lsl.secondlife.com) is valid format-wise, but Second Life's server had an internal database error when trying to process your simple "123" subject line email.
This appears to be a bug on Second Life/Linden Lab's end that should be reported to them.
Maestro Linden
marked this post as
tracked
John Codesmith
Hello Maestro, that email was sent from my hotmail account to 5243fc88-9820-3f0a-649c-eb5d4f803003@lsl.secondlife.com with a simple subject of 123 I sent to the address you see there - it is a script in world for receiving emails from another script. Delete an object in a sim if it gets lost / times out, to clean up. I sent the email from sim Mocha to Mocha - sender and receiver are 1 meter apart, same sim. With object to object, I simply never see the email received. AI recommended I try sending the email from my hotmail account and indicated the server has an SQL error by the error that was returned - seemed the server was trying to populate a field with more characters than the field could handle if you read the error
Maestro Linden
John Codesmith: Okay, interesting - I ask because the error message is behaving as though you had emailed
5243fc88-9820-3f0a-649c-eb5d4f803003%0A%09%3C5243fc88-9820-3f0a-649c-eb5d4f803003%40lsl.secondlife.com%3E@lsl.secondlife.com
.Testing yesterday, I couldn't reproduce the error message when I email either that malformed address or 5243fc88-9820-3f0a-649c-eb5d4f803003@lsl.secondlife.com. When I tested, the object had already lost its mail-in presence (which would happen if it were derezzed, script disabled, etc.).
In any case, the fact that you were able to see that error message at all is a bug. It seems that the mail-in service's sanitization of addresses (it should only accept UUID) needs some work.
Maestro Linden
marked this post as
under review
Maestro Linden
Hi John, thanks for the report. Your test email address does look well-formed. Just to check, is 5243fc88-9820-3f0a-649c-eb5d4f803003@lsl.secondlife.com the actual email address that you're trying to send to? Are you seeing the same error with any other objects?
I'm not immediately seeing this error with mail-in LSL scripts that were rezzed years ago nor with brand new scripts, including when sending with the same "123" subject and empty body. I'll dig around and look for details of this error internally.