Opening a mailing list returns Internal Server Error

froi-manila

• April 24, 2019 02:40

Hi Guys seeking your advice with this. I have one account from our shared server having this issue. When I try to open or access this particular mailing list, it will return an error "Internal Server Error 500". I tried to reset the mailing list password and it failed. Return error is: Failed to change the password for the mailing list "operations@xxxxxxx.com.ph": The administrative request failed because of an error (ETIMEDOUT/110) with output: Timeout: Alarm This is the only mailing list who is having this issue under this domain. All other mailing lists under the same domain are fine. When I check /usr/local/cpanel/logs/error_log, this is what I get: [2019-04-24 15:39:11 +0800] info [cpaneld] Internal Server Error: "POST /cpsess8317094005/3rdparty/mailman/admin/operations_xxxxxxxx.com.ph/ HTTP/1.1" 500 Error ID 585f11907b1

• 

  cPanelLauren

  • April 24, 2019 19:51

  Hi @froi-manila Is anything noted in /usr/local/cpanel/3rdparty/mailman/logs/error?

  0
• 

  froi-manila

  • April 25, 2019 06:09

  Unfortunately can't see anything from that particular logs..

  0
• 

  cPanelLauren

  • April 25, 2019 14:11

  If you're unable to access those logs you'll need to contact your provider for further assistance resolving this issue.

  0
• 

  froi-manila

  • April 29, 2019 08:43

  I can access the logs. but there are no logs inside /usr/local/cpanel/3rdparty/mailman/logs/error in particular to this mailing list. I can error logs thoug through /usr/local/cpanel/logs/error_log and it is pretty related to the actual mailing list I am trying to investigate. again, all other mailing list under this domain is fine. below are the logs from /usr/local/cpanel/logs/error_log [2019-04-29 16:28:52 +0800] info [cpaneld] Internal Server Error: "POST /cpsess1604036915/3rdparty/mailman/admin/operations_xxxxxxxxxx.xxx.xx/ HTTP/1.1" 500 Error ID 19e719126755f [2019-04-29 16:31:17 +0800] info [whostmgrd] Successfully verified signature for cpanel (key types: release). [2019-04-29 16:31:30 +0800] info [cpsrvd] Request Timeout: "-" 408 Timeout while creating a secure connection [2019-04-29 16:32:31 +0800] info [cpsrvd] Request Timeout: "-" 408 Timeout while creating a secure connection [2019-04-29 16:32:42 +0800] info [cpsrvd] Request Timeout: "-" 408 Timeout while creating a secure connection [2019-04-29 16:33:48 +0800] info [cpsrvd] Request Timeout: "-" 408 Timeout while creating a secure connection [2019-04-29 16:34:41 +0800] info [cpsrvd] Request Timeout: "-" 408 Timeout while creating a secure connection [2019-04-29 16:35:32 +0800] info [cpsrvd] Request Timeout: "-" 408 Timeout while creating a secure connection [2019-04-29 16:36:35 +0800] info [cpsrvd] Request Timeout: "-" 408 Timeout while creating a secure connection [2019-04-29 16:36:44 +0800] info [cpsrvd] Request Timeout: "-" 408 Timeout while creating a secure connection [2019-04-29 16:36:58 +0800] info [cpsrvd] Request Timeout: "-" 408 Timeout while creating a secure connection [2019-04-29 16:37:34 +0800] info [whostmgrd] Successfully verified signature for cpanel (key types: release). [2019-04-29 16:38:47 +0800] info [cpsrvd] Request Timeout: "-" 408 Timeout while creating a secure connection
  - Removed -

  0
• 

  cPanelLauren

  • April 30, 2019 21:10

  Hi @froi-manila At the same time as these errors is anything noted in the cPhulkd logs? They're located at /usr/local/cpanel/logs/cphulkd.log /usr/local/cpanel/logs/cphulkd_errors.log
  

  0
• 

  froi-manila

  • May 04, 2019 06:37

  Hi @froi-manila At the same time as these errors is anything noted in the cPhulkd logs? They're located at /usr/local/cpanel/logs/cphulkd.log /usr/local/cpanel/logs/cphulkd_errors.log
  

  
  no errors from here related to the mailing list :(

  0
• 

  cPanelLauren

  • May 06, 2019 16:41

  If you have root access to the server, please feel free to open a ticket using the link in my signature. If you do open a ticket with us please update this thread with the ticket ID so we can follow up with the outcome here. Otherwise, if you don't have root access I'd suggest contacting your provider for further assistance. Thanks!

  0

Please sign in to leave a comment.