MSSQL environment restore: internal server error (Status code 500) on creation of rulesets

Question

MSSQL environment restore: internal server error (Status code 500) on creation of rulesets

Closed this issue 6 years ago · 15 comments

After a complete backup, I tried to restore a single MSSQL environment (as all our testing had been with oracle to date). I made the necessary edits to the base.Json file to contain only the one MSSQL environment as well as the correlating application.json file to add passwords for the connectors.

I ended up with an internal server error, status code 500 during creation of rule sets.

2018-05-01 12:35:29.600 [main] DEBUG com.delphix.masking.initializer.maskingApi.endpointCaller.ApiCallDriver - Response body: {"errorMessage":"Encountered internal server error, please see the logs for more details"}

2018-05-01 12:35:29.600 [main] ERROR com.delphix.masking.initializer.maskingApi.SetupDriver - Got status code: [500] with message [Encountered internal server error, please see the logs for more details] trying to hit URL: [http://myhostname.

Attached is a tail of the All.log file:
MSSQL_TailOfAll.log
:8282/masking/api/table-metadata] [POST]

slusardi01 commented 6 years ago

Resent

Answer 1 · 2018-06-10T06:00:28.000Z

@slusardi01 can you provide the masking logs at the time of these calls?

Answer 2 · 2018-06-11T15:58:41.000Z

Ben, When you are requesting Masking Logs, would these be the same logs generated on the virtualization engine for support logs ??

Answer 3 · 2018-06-12T15:01:20.000Z

@slusardi01 yep! If you create a support bundle and then look in the masking/logs/AppLogs/ folder, those are the logs that I am talking about.

I will send you my email address privately so that you can send me those logs directly and don't have to post them publicly.

Answer 4 · 2018-06-12T15:52:08.000Z

Okay. We have a disk issue at the moment that is impeding the creation of the logs. As soon as that is resolved, I could work on that.

Answer 5 · 2018-06-12T16:10:19.000Z

@slusardi01, no problem. When you get the disk issue figured out, please send the logs to masking-object-manager@delphix.com so we can take a look at the internal server error.

Answer 6 · 2018-06-12T16:17:52.000Z

will do, thank you

Answer 7 · 2018-06-13T17:39:00.000Z

I have the support bundle from the engine. I can not email as the file is > 34MB which hits our email threshold limitation. Do you have a location I can post/ftp the file to instead ? Additionally, I can not Putty to the masking engine to find the logs you seek in masking/logs/AppLogs. Sysadmin puts you into the CLI, and I do not have my own login so I can not sudo to delphix like we do on the VM targets. If there are other suggestions, please let me know. Thank you.

Answer 8 · 2018-06-13T19:33:53.000Z

You should be able to unpack the support bundle, and then those logs should be in the masking folder of the support bundle. If that doesn't work we can have you upload the support bundle to the same way you would for a support case.

Answer 9 · 2018-06-13T19:41:17.000Z

Okay. I will give that a try. Thank you Suzanne

…

________________________________ From: Ben Page <notifications@github.com> Sent: Wednesday, June 13, 2018 3:33 PM To: delphix/masking-initializer Cc: Lusardi, Suzanne C; Mention Subject: Re: [delphix/masking-initializer] MSSQL environment restore: internal server error (Status code 500) on creation of rulesets (#1) You should be able to unpack the support bundle, and then those logs should be in the masking folder of the support bundle. If that doesn't work we can have you upload the support bundle to the same way you would for a support case. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_delphix_masking-2Dinitializer_issues_1-23issuecomment-2D397058783&d=DwMCaQ&c=RyOedRvjc7OSsfc0bTI76Q&r=k_tclXU9T3ON6hXM8x8J_qGH921EvN2meQgRTKqwL24&m=TE22LbeJ-xQs5RiVFi7LxxV13gm4w-tYQ2-cIe20rzs&s=6javUaJ3QvuRQ4oz96EC5Hl15fwguYf1xxcmjypbS10&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AlQRbAiHn24IUFA38XKAOL7O2yDl8eEuks5t8WkhgaJpZM4T1Y-2DR&d=DwMCaQ&c=RyOedRvjc7OSsfc0bTI76Q&r=k_tclXU9T3ON6hXM8x8J_qGH921EvN2meQgRTKqwL24&m=TE22LbeJ-xQs5RiVFi7LxxV13gm4w-tYQ2-cIe20rzs&s=QOaJLz31o0-gb3lM47OML1uXYLBpdqN5LjhrzCk7H4M&e=>. The information contained in this message may be privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify your representative immediately and delete this message from your computer. Thank you.

Answer 10 · 2018-06-13T20:24:17.000Z

I was able to extract the log folder from the masking directory. Email is on its way.

Answer 11 · 2018-06-19T12:24:29.000Z

@slusardi01 sorry for the delay.

Could you please resend that email to masking-object-manager@delphix.com. Our email filters were misconfigured so we did not receive the email.

Thanks!

Answer 12 · 2018-07-03T11:33:15.000Z

Uploading support bundle from masking engine through Delphix support site.

Answer 13 · 2018-07-03T22:06:48.000Z

I found the following in the masking logs at the time of the error noted above.

2018-05-01 16:35:29,600  [http-nio-8282-exec-21] ERROR c.dmsuite.common.utils.DBConnection - Error while getting sql server Connection Object
java.sql.SQLException: Login failed for user '<USER_NAME>'.
	at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372)
	at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
	at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
	at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:603)
	at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:352)
	at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
	at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:185)
	at java.sql.DriverManager.getConnection(DriverManager.java:664)

So it looks like it is failing to authenticate with your database.

Did you fill in the passwords for this backup file? See this section in the README for information on filling in the passwords. This section was accidentally removed from the README in a previous version, so this part of the restore process might have been overlooked.

Answer 14 · 2018-07-05T12:25:07.000Z

Thank you Ben. My notes in the top of the ticket indicate connector files were edited for passwords. At least I know it's a connection issue now and have a place to start to further troubleshoot. Thank you.