Skip to main content

Maintenance ended; however, it did not exit cleanly (256)

Comments

10 comments

  • cPanelLauren
    Hi @SG Websites Actually I'd like to see what the output is when you run the two scripts noted in the orignal output: bin/postgrescheck
    /scripts/check_unreliable_resolvers
    The errors encountered seem to be specific to errors on these two scripts.
    0
  • David40
    Hi, I get the same message today and when I run your code in WHM terminal I get [root@xxxxxxx ~]# bin/postgrescheck bash: bin/postgrescheck: No such file or directory [root@xxxxxxxx ~]# /scripts/check_unreliable_resolvers OK
    Should I open new Thread or waiting here for the response. Thank you Sorry for to quick response but going thro other emails I get from the server I note also this: Some of the server"s DNS resolvers fail to respond. ERROR I have had Three IP resolvers entered from the data center and I see that the problem is in third one IPv6 and I don't use IPv6 so I delete this optional resolver I hope that now will be ok. Is there anything that I should do now or Cpanel will try an update at a later time. Please, I am pretty new to root level WHM if instructions could be also on my level thank you.
    0
  • cPanelLauren
    Hi @David40 Can you run this (just copy/paste) /usr/local/cpanel/bin/postgrescheck
    It sounds like the resolver check was successful this time but I'm concerned due to the output in the update that you might be having intermittent issues. You can check your resolvers at WHM>>Network Configuration>>Resolver Configuration, I might suggest removing one entry and using Google's. 8.8.8.8 8.8.4.4
    0
  • David40
    Hi so sorry for late respond. I paste the code thro whm terminal and I get nothing just went in new line. [root@xxxxxxxx ~]# /usr/local/cpanel/bin/postgrescheck 0[root@xxxxxxxx ~]#
    Should I still change one resolver IP to google's?
    0
  • cPanelLauren
    Hi @David40 The postgrescheck completed fine. Yea go ahead and change the resolver to reflect google's DNS and re-run the update and let me know if you continue to have the same issue.
    0
  • dannylank
    Hello I have similar problem. I receive every day this email :
    0
  • cPanelLauren
    When you run the check unreliable resolvers check manually what is the output? [CODE=bash]/scripts/check_unreliable_resolvers --notify
    0
  • dannylank
    [root @ panel ~] # / scripts / check_unreliable_resolvers --notify perl: advertencia: la configuraci"n regional fall". - Removed Please Review This Thread -
    0
  • dannylank
    [root@panel ~]# /scripts/check_unreliable_resolvers --notify perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_CTYPE = "UTF-8", LANG = "es_CO.UTF-8" are supported and installed on your system. perl: warning: Falling back to a fallback locale ("es_CO.UTF-8"). ? Partial DNS resolver failure Resolver State 200.75.xx.xxx Normal 200.75.xx.xxx Normal 8.8.4.4 Normal 8.8.8.8 Normal fe80::1%enp0s17 Failed Use the "Resolver Configuration" interface (https://panel.example.com:2087/scripts2/setupresolvconf) to investigate or update the system"s DNS resolvers.
    0
  • cPanelLauren
    Does the following exist in the /etc/resolv.conf? fe80::1%enp0s17
    This appears to be an IPv6 IP address that doesn't resolve causing the /script to fail.
    0

Please sign in to leave a comment.