Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 3 subscribers
  • Views 2481 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

smtpd daemon not running after email address change

jwerner

At a bit of a loss here.  Made a simple change to the admin's email address, and it appears that our daemon is messed.  IT is not critical, but none of our notifications are being sent out any more.

SMTP log:

2020:07:24-11:56:18 Claimsbridge-1 smtpd[31851]: MASTER[31851]: (Re-)loading configuration from Confd
2020:07:24-11:56:18 Claimsbridge-1 smtpd[31851]: MASTER[31851]: QR globally disabled, status one set to 'disabled'
2020:07:24-11:56:18 Claimsbridge-1 smtpd[31851]: MASTER[31851]: QR globally disabled, status two set to 'disabled'
2020:07:24-11:56:18 Claimsbridge-1 exim-in[31860]: 2020-07-24 11:56:18 exim 4.82_1-5b7a7c0-XX daemon started: pid=31860, no queue runs, listening for SMTP on port 25 (IPv4) port 587 (IPv4) and for SMTPS on port 465 (IPv4)
2020:07:24-11:56:44 Claimsbridge-1 smtpd[31856]: QMGR[31856]: Permanent database error detected, exiting.
2020:07:24-11:56:45 Claimsbridge-1 smtpd[31851]: MASTER[31851]: Queue manager died, shutting down.
2020:07:24-11:56:45 Claimsbridge-1 smtpd[31851]: MASTER[31851]: Termination requested, sending SIGTERM to child processes
2020:07:24-11:56:45 Claimsbridge-1 smtpd[31851]: MASTER[31851]: Exiting

I have tried killing and restarting the process.  No luck.

Admin notification log (this one should be simply for a login):

2020:07:24-12:37:41 Claimsbridge-2 postfix/qmgr[1573]: 787662266D: from=<do-not-reply@fw-notify.net>, size=893, nrcpt=1 (queue active)
2020:07:24-12:37:41 Claimsbridge-2 postfix/smtp[5690]: connect to localhost[127.0.0.1]:25: Connection refused
2020:07:24-12:37:41 Claimsbridge-2 postfix/smtp[5690]: 787662266D: to=<xxxx@claimsbridge.com>, relay=none, delay=0.16, delays=0.09/0.08/0/0, dsn=4.4.1, status=deferred (connect to localhost[127.0.0.1]:25: Connection refused)

any thoughts or help?  Can't roll back to an old backup since we made too many changes since...and I would have difficulty putting them all back in place.

Jason



This thread was automatically locked due to age.
Parents
  • +1

    Hello Jason,

    Thank you for contacting the Sophos Community.

    UPDATED: Actually if not in HA you don't need to run repctl.

    What does the system.log says?

    But it does seem like your database got corrupted,

    Can you access the database if you run:

    # psql -U postgres

    You might want to rebuild it by running the commands below, the commands are for HA configuration if your UTM is a standalone then run the same commands only once.

    If you decide to rebuild the database please do the following in both nodes:

    1. SSH onto the master UTM as root

    2. Duplicate the SSH session

    3. On the second SSH screen type in ha_utils ssh

    4. Become root user on the slave UTM

    5. On the main UTM type in killall repctl

    6. On the slave UTM type in killall repctl

    7. On the master UTM type in /etc/init.d/postgresql92 rebuild

    8. on the slave UTM type in /etc/init.d/postgresql92 rebuild

    9. Once done on both UTM. Type in repctl on both to start the repctl service

    Regards,

     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
Reply
  • +1

    Hello Jason,

    Thank you for contacting the Sophos Community.

    UPDATED: Actually if not in HA you don't need to run repctl.

    What does the system.log says?

    But it does seem like your database got corrupted,

    Can you access the database if you run:

    # psql -U postgres

    You might want to rebuild it by running the commands below, the commands are for HA configuration if your UTM is a standalone then run the same commands only once.

    If you decide to rebuild the database please do the following in both nodes:

    1. SSH onto the master UTM as root

    2. Duplicate the SSH session

    3. On the second SSH screen type in ha_utils ssh

    4. Become root user on the slave UTM

    5. On the main UTM type in killall repctl

    6. On the slave UTM type in killall repctl

    7. On the master UTM type in /etc/init.d/postgresql92 rebuild

    8. on the slave UTM type in /etc/init.d/postgresql92 rebuild

    9. Once done on both UTM. Type in repctl on both to start the repctl service

    Regards,

     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
Children
  • 0 in reply to emmosophos

    Emmanuel, in the past, I've not stopped and restarted repctl.  What is the advantage to doing that?

    Cheers - Bob

    PS To just rebuild the SMTP database, I got the following from fellow member Billybob eight years ago yesterday.  Are these still the correct commands?

    /var/mdw/scripts/smtp stop
    dropdb -U postgres smtp
    createdb -U postgres smtp
    /var/mdw/scripts/smtp start

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Hello Bob,

    Thank you for the comment.

    Yes actually this is only needed to stop the replication status of Master and Slave.

    I updated the thread. 

    I didn't know the commands you provided I will check them out!

    Regards,

     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support Videos | Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
Unfiltered HTML