Odd SQL issues

[Jason Waters]

Shawn,
   Did you see my DBITrace information?

On Wed, Jan 11, 2017 at 1:12 PM, Danita Zanre <danita at caledonia.net> wrote:

> Shawn,
>
> Not that I can see.  I’ve had Mailscanner stop logging to the database
> before, and reboot has fixed it, which could point to a stuck lock, but
> this time I rebooted and it was still not logging.  Next time it stops
> updating the database I’ll see if I can find a stuck lock.
>
>
> *Danita Zanrè*, *Move Out of the Office*
> I love my job, and you can too!
> Tel: (720) 319-7530 - Caledonia Network Consulting
> Tel: (720) 319-8240 - Move Out of the Office
>
>
> On January 11, 2017 at 12:11:18 PM, Shawn Iverson (
> iversons at rushville.k12.in.us) wrote:
>
> Danita,
>
> Is there a stuck lock on the mysql table(s)?  I am currently trying to
> figure out an issue with Mailscanner/mysql which is why I ask.
>
> On Wed, Jan 11, 2017 at 11:05 AM, Danita Zanre <danita at caledonia.net>
> wrote:
>
>> This morning we added more memory to our VM running
>> MailScanner/MailWatch.  After reboot, MailScanner logged that it was
>> sending messages to SQL, but no new entries were in the database.
>>
>> Jan 11 07:03:38 xeams MailScanner[31417]: Logging message
>> 92CB8EDE48.AF3D2 to SQL
>>
>>
>> Here is where we rebooted
>>
>>
>> Jan 11 07:09:16 xeams MailScanner[4361]: Started SQL Logging child
>>
>> Jan 11 07:09:22 xeams MailScanner[4878]: Started SQL Logging child
>>
>> Jan 11 07:09:27 xeams MailScanner[5348]: Started SQL Logging child
>>
>> Jan 11 07:09:33 xeams MailScanner[5621]: Started SQL Logging child
>>
>> Jan 11 07:09:38 xeams MailScanner[5788]: Started SQL Logging child
>>
>> Jan 11 07:12:27 xeams MailScanner[4878]: Logging message 209C7EDE37.AA97A
>> to SQL
>>
>> Jan 11 07:12:27 xeams MailScanner[5348]: Logging message 04FF9EDE3F.AA21D
>> to SQL
>>
>> Jan 11 07:12:27 xeams MailScanner[5348]: Logging message DF6B9EDE3C.ABB06
>> to SQL
>>
>> Jan 11 07:12:32 xeams MailScanner[5788]: Logging message 049DAEDE40.A9BBD
>> to SQL
>>
>> Jan 11 07:13:13 xeams MailScanner[5621]: Logging message 7383EEDE41.AADEE
>> to SQL
>>
>> I tried all kinds of things, and then ultimately turned Debug SQL = yes
>> just to see if I could SEE anything.  It started updating the database.  I
>> turned it back to Debug SQL = no and it stopped updating the database!  I’m
>> leaving it at “yes” for now - but why would this even matter?  Is there any
>> other downside to leaving this on?  I can’t even see where it is logging
>> any kind of “debug” info, but it’s keeping the database updates happening,
>> so I’m not touching it!
>>
>> Thanks for any insights here.
>>
>> *Danita Zanrè*, *Move Out of the Office*
>> I love my job, and you can too!
>> Tel: (720) 319-7530 - Caledonia Network Consulting
>> Tel: (720) 319-8240 - Move Out of the Office
>>
>>
>>
>>
>> --
>> MailScanner mailing list
>> mailscanner at lists.mailscanner.info
>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>
>>
>>
>
>
> --
> Shawn Iverson
> Director of Technology
> Rush County Schools
> 765-932-3901 x271 <(765)%20932-3901>
> iversons at rushville.k12.in.us
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by *Iris MailScanner* <http://iris.caledonia.net/>, and
> is
> believed to be clean.
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mailscanner.info/pipermail/mailscanner/attachments/20170111/86392438/attachment.html>