Page 685 of 707 FirstFirst ... 185585635675683684685686687695 ... LastLast
Results 6,841 to 6,850 of 7066
  1. #6841
    Junior Member
    Join Date
    Feb 2014
    Location
    Russia, Moscow
    Posts
    19
    Hi.

    I can not setup email settings in AdKats, for sending reports and admin calls.
    I got this error
    EXCEPTION-7010-D-EmailProcessingThreadLoop-EmailProcessing26: [Error occured in mail processing thread. skipping loop.][System.Net.Mail.SmtpException: Время ожидания операции истекло.
    в System.Net.Mail.SmtpClient.Send(MailMessage message)
    в PRoConEvents.AdKats.EmailHandler.EmailProcessingTh readLoop()]

    What i do wrong?

  2. #6842
    Hi.How to disable auto-update plug-in?The plug-in was updated by itself although I prohibited it in the settings.I do not want it to be updated yet.
    2018-01-29_130615.png

  3. #6843
    Quote Originally Posted by keb2 View Post
    Hi.How to disable auto-update plug-in?The plug-in was updated by itself although I prohibited it in the settings.I do not want it to be updated yet.
    2018-01-29_130615.png
    There are 2 cases that override that setting:
    Being on a test version of the plugin. Test versions can have issues so auto-updates are forced on.
    Having a value in the LRT extension token setting. Integration between the loadout enforcer and AdKats requires updates for both plugins.

    If you aren't on a test version, and don't have a value in that extension token setting, you should be good.

    I would say revert back to 7.0.1.0 and make sure updates are disabled on startup.
    ____

  4. #6844
    Quote Originally Posted by Timm View Post
    Hi.

    I can not setup email settings in AdKats, for sending reports and admin calls.
    I got this error
    EXCEPTION-7010-D-EmailProcessingThreadLoop-EmailProcessing26: [Error occured in mail processing thread. skipping loop.][System.Net.Mail.SmtpException: Время ожидания операции истекло.
    в System.Net.Mail.SmtpClient.Send(MailMessage message)
    в PRoConEvents.AdKats.EmailHandler.EmailProcessingTh readLoop()]

    What i do wrong?
    Время ожидания операции истекло.

    The operation timed out.

    It cannot connect to your smtp server.
    ____

  5. #6845
    Junior Member
    Join Date
    Feb 2014
    Location
    Russia, Moscow
    Posts
    19
    Quote Originally Posted by ColColonCleaner View Post
    Время ожидания операции истекло.

    The operation timed out.

    It cannot connect to your smtp server.
    Why?

    Login information correct. I must open specific port on machine?

  6. #6846
    Quote Originally Posted by Timm View Post
    Why?

    Login information correct. I must open specific port on machine?
    Either port 465 or 587 are the usual ones for secure smtp connection.
    ____

  7. #6847
    Hello,

    Not sure if this is an Adkats issue or BFadmincp issue but I will start here.

    All of a sudden, I notice in our Ban list page on BFadminCP that all players who are permanently banned show the exact expiration date of Dec 31, 1969 4:00pm PST. If a temp ban is issued, it shows the correct expiration date to be in 2018, but all perm bans end on Dec 31, 1969 4:00pm PST!

    I have not made any changes so I have no idea of what caused this, but only change I have made is to Adkats which I simply updated to the most current version when it is released.

    Any Ideas?

  8. #6848
    Quote Originally Posted by SmackDown View Post
    Hello,

    Not sure if this is an Adkats issue or BFadmincp issue but I will start here.

    All of a sudden, I notice in our Ban list page on BFadminCP that all players who are permanently banned show the exact expiration date of Dec 31, 1969 4:00pm PST. If a temp ban is issued, it shows the correct expiration date to be in 2018, but all perm bans end on Dec 31, 1969 4:00pm PST!

    I have not made any changes so I have no idea of what caused this, but only change I have made is to Adkats which I simply updated to the most current version when it is released.

    Any Ideas?
    I haven't made changes to the ban system in a very long time, been a couple years since I changed it, at least by what I remember.

    Jan 1, 1970 00:00 UTC is the base of Epoch time, which is the same as Dec 31 1969 16:00 PST, what you're seeing, i'm not sure what would be setting that value though, whether it's on the database side or on the UI side.

    select * from adkats_bans where player_id = PLAYERIDHERE

    When you're looking at a player who is permabanned, look in the URL for their player ID and put it in this query. Then look at what the ban ending time actually is. If it's the correct time, 20ish years in the future, then you're good. But if that returns the 1970 value then we have a problem.

    EDIT: Is this only an issue for new bans? Or is this happening to old permabans as well?
    Last edited by ColColonCleaner; 29-01-2018 at 15:51.
    ____

  9. #6849
    Quote Originally Posted by ColColonCleaner View Post
    I haven't made changes to the ban system in a very long time, been a couple years since I changed it, at least by what I remember.

    Jan 1, 1970 00:00 UTC is the base of Epoch time, which is the same as Dec 31 1969 16:00 PST, what you're seeing, i'm not sure what would be setting that value though, whether it's on the database side or on the UI side.

    select * from adkats_bans where player_id = PLAYERIDHERE

    When you're looking at a player who is permabanned, look in the URL for their player ID and put it in this query. Then look at what the ban ending time actually is. If it's the correct time, 20ish years in the future, then you're good. But if that returns the 1970 value then we have a problem.

    EDIT: Is this only an issue for new bans? Or is this happening to old permabans as well?

    Seems to be only on the new bans, and it started for me on January 19, 2018. When I go in the Adkats_Bans and look at the latest bans on our servers, it is showing an expiration date of 1/30/2038 all bans. No bans listed are showing 1969 as they are in Adkats.
    Last edited by SmackDown; 30-01-2018 at 01:24.

  10. #6850
    Community Contributor
    Join Date
    Nov 2011
    Posts
    3,011
    January 19, 2018 plus 20 years = January 19, 2038. Uh oh. Unix Epoch rollover problem.
    https://youtu.be/QJQ691PTKsA
    Last edited by ty_ger07; 30-01-2018 at 01:27.

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •