TCPServer::Run() error after upgrading to latest 5.4

Use this forum if you want to discuss a problem or ask a question related to a hMailServer beta release.
FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-08 16:48

Yesterday i update my main server to last 5.4 and now im getting this errors randomly:

Code: Select all

"ERROR"   1944   "2011-07-08 15:13:04.765"   "Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 110. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 110. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"   1944   "2011-07-08 15:13:04.765"   "Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 143. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 143. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"   1944   "2011-07-08 15:13:04.765"   "Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 465. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 465. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"   1944   "2011-07-08 15:13:04.765"   "Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 993. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 993. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"   1944   "2011-07-08 15:13:04.765"   "Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 995. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 995. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
Anyone else is having this problem? Im sure there is nothing else running in this ports...and im using CurrPorts provided by bill to watch this.

I have ClamAV running on the server aswell.

^DooM^
Site Admin
Posts: 13861
Joined: 2005-07-29 16:18
Location: UK

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by ^DooM^ » 2011-07-08 17:01

Bind to the servers External IP Address rather than all IP's
If at first you don't succeed, bomb disposal probably isn't for you! ヅ

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-08 17:06

^DooM^ wrote:Bind to the servers External IP Address rather than all IP's
Think you mean bind to the server's actual network IP not the external one unless the server happens to be directly connected to internet with public IP assigned to nic (vs behind router doing nat/pat) :D
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-08 17:07

^DooM^ wrote:Bind to the servers External IP Address rather than all IP's
Done that, restarted, now we wait....

Thanks

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-08 17:08

FiShBuRn wrote: Done that, restarted, now we wait....

Thanks
Wait for what? Should see immediately if it is able to bind or not..
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-08 17:11

Bill48105 wrote:
FiShBuRn wrote: Done that, restarted, now we wait....

Thanks
Wait for what? Should see immediately if it is able to bind or not..
Bill
Server starts OK and works for a while but then TCPError appears...thats why we need to wait to see what happens

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-08 17:13

FiShBuRn wrote:
Bill48105 wrote:
FiShBuRn wrote: Done that, restarted, now we wait....

Thanks
Wait for what? Should see immediately if it is able to bind or not..
Bill
The server is working fine....then the errors start showing up...
HUH?! So the problem isn't immediate?? That is when hmail binds & listens.. There'd be no reason for it to unbind & rebind later unless you restarted or such. Well will be interesting to see if forcing to particular IP helps as that is very strange issue. Are you getting mail flow with the IP you entered? I might have missed it moving between threads but did you reply to DooM asking if you have transparent proxy (av/firewall/etc) running on the server?
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-08 17:16

the problem isnt immediate indeed, maybe hmail is crashing because is not restarded by me.

Yeap, email are flowing.

No, no transparent proxy (av/firewall/etc). Only apache, mysql and clamav...spamassassin is running on another machine.

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-08 17:18

Very strange. What do logs show leading up to those error then? Maybe that will give us clue..
Thx
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-08 17:26

Code: Select all

"SMTPD"	2036	0	"2011-07-08 15:11:48.812"	"TCP"	"DNS lookup: 41.240.125.94.dnsbl.njabl.org, 0 addresses found: (none), Match: False"
"SMTPD"	2036	0	"2011-07-08 15:11:48.906"	"TCP"	"DNS lookup: 41.240.125.94.zz.countries.nerd.dk, 1 addresses found: 127.0.2.131, Match: True"
"SMTPD"	2036	3813	"2011-07-08 15:11:48.906"	"94.125.240.41"	"SENT: 550 Rejected by country code filter"
"APPLICATION"	2036	"2011-07-08 15:11:48.906"	"hMailServer SpamProtection rejected RCPT (Sender: transitivepunditry@worldatlas.com, IP:94.125.240.41, Reason: Rejected by country code filter)"
"SMTPC"	2040	0	"2011-07-08 15:12:02.796"	"TCP"	"SMTPDeliverer - Message 1015584 - Connection failed: Host name: 195.170.168.136, message: Uma tentativa de ligação falhou porque o componente ligado não respondeu correctamente após um período de tempo, ou a ligação estabelecida falhou porque o anfitrião ligado não respondeu"
"APPLICATION"	2036	"2011-07-08 15:13:04.343"	"Starting servers..."
"APPLICATION"	1920	"2011-07-08 15:13:04.437"	"SMTPDeliverer - Message 1015584: Delivering message from someone@localdomain.com to someone@externaldomain.com. File: C:\Programas\hMailServer\Data\{24D8AECD-926F-41CD-9835-6D73133E9340}.eml"
"ERROR"	1944	"2011-07-08 15:13:04.765"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 25. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 25. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	1944	"2011-07-08 15:13:04.765"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 110. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 110. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	1944	"2011-07-08 15:13:04.765"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 143. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 143. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	1944	"2011-07-08 15:13:04.765"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 465. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 465. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	1944	"2011-07-08 15:13:04.765"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 993. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 993. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	1944	"2011-07-08 15:13:04.765"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 995. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 995. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"APPLICATION"	2036	"2011-07-08 15:13:04.781"	"Servers started."
"SMTPD"	1920	0	"2011-07-08 15:13:04.875"	"TCP"	"DNS - MX Lookup: external.com"
"SMTPD"	1920	0	"2011-07-08 15:13:04.921"	"TCP"	"DNS - MX Result: 5 IP addresses were found."

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-08 17:38

OK that log snippet shows hmail starting up but I don't see it shutting down.. And there is 1 minute gap in logs. Was hmail stopped (maybe it puked & your event logs show why) and then windows restarted it again? (Again even logs should show you around that time)
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-08 17:42

Bill48105 wrote:OK that log snippet shows hmail starting up but I don't see it shutting down.. And there is 1 minute gap in logs. Was hmail stopped (maybe it puked & your event logs show why) and then windows restarted it again? (Again even logs should show you around that time)
Bill
because i dont have any message saying that is shutting down :s...event log shows that hmailserver crashed unexpectedly without any specific message and it tries to start it up again.

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-08 17:48

lol well duh. :D

So you have debug logging enabled & anything in there? You make any config changes or windows updates etc after (around time) you upgraded hmail?

The fact hmail crashed & then says ports are in-use when windows tries to start it back up again seems odd to me. Obviously we're missing critical piece here.
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-08 18:04

:P

with debug ive checked and nothing out of normal, no changes made server has up and running >100 days.

indeed...very strange.

Code: Select all

"DEBUG"	320	"2011-07-08 12:23:42.500"	"SD::~_InitiateExternalConnection-5"
"DEBUG"	320	"2011-07-08 12:23:43.375"	"Ending session 8"
"DEBUG"	320	"2011-07-08 12:23:43.515"	"SD::~_DeliverToExternalAccounts-2"
"DEBUG"	320	"2011-07-08 12:23:43.515"	"Collect delivery result"
"DEBUG"	1592	"2011-07-08 12:23:43.578"	"Creating session 10"
"DEBUG"	1540	"2011-07-08 12:23:43.656"	"Creating session 11"
"DEBUG"	320	"2011-07-08 12:23:43.703"	"Collect delivery result - Done"
"DEBUG"	320	"2011-07-08 12:23:43.703"	"SD::_RescheduleDelivery"
"DEBUG"	1540	"2011-07-08 12:23:43.750"	"Creating session 12"
"DEBUG"	1592	"2011-07-08 12:23:43.906"	"Reading messages from database."
"DEBUG"	2412	"2011-07-08 12:23:44.046"	"Closing TCP/IP socket"
"DEBUG"	1592	"2011-07-08 12:23:44.078"	"Creating session 13"
"DEBUG"	2136	"2011-07-08 12:23:44.234"	"Closing TCP/IP socket"
"DEBUG"	2136	"2011-07-08 12:23:44.265"	"Ending session 12"
"DEBUG"	1592	"2011-07-08 12:23:44.265"	"Closing TCP/IP socket"
"DEBUG"	1592	"2011-07-08 12:23:44.265"	"Ending session 11"
"DEBUG"	2412	"2011-07-08 12:23:44.265"	"Ending session 10"
"DEBUG"	1996	"2011-07-08 12:23:44.953"	"Closing TCP/IP socket"
"DEBUG"	1996	"2011-07-08 12:23:44.953"	"Ending session 13"
"DEBUG"	2136	"2011-07-08 12:23:44.953"	"Creating session 14"
"DEBUG"	2412	"2011-07-08 12:23:53.187"	"Application::InitInstance - Configuration loaded."
"APPLICATION"	2412	"2011-07-08 12:23:53.187"	"Starting servers..."
"DEBUG"	2232	"2011-07-08 12:23:53.281"	"SMTPDeliveryManager::Start()"
"DEBUG"	2600	"2011-07-08 12:23:53.281"	"Delivering message..."
"APPLICATION"	2600	"2011-07-08 12:23:53.281"	"SMTPDeliverer - Message 1015173: Delivering message from someone@localdomain.com to xxx. File: C:\Programas\hMailServer\Data\{19679F2B-2C2A-4D8C-B670-3E29034E1F10}.eml"
"DEBUG"	2600	"2011-07-08 12:23:53.296"	"Connecting to ClamAV virus scanner..."
"DEBUG"	1652	"2011-07-08 12:23:53.296"	"ExternalFetchManager::Start()"
"DEBUG"	2412	"2011-07-08 12:23:53.296"	"Starting message indexing thread..."
"DEBUG"	2600	"2011-07-08 12:23:53.296"	"Connecting to ClamAV stream port..."
"DEBUG"	2544	"2011-07-08 12:23:53.296"	"Indexing messages..."
"ERROR"	2032	"2011-07-08 12:23:53.609"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 25. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 25. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	2032	"2011-07-08 12:23:53.609"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 110. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 110. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	2032	"2011-07-08 12:23:53.609"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 143. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 143. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	2032	"2011-07-08 12:23:53.609"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 465. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 465. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	2032	"2011-07-08 12:23:53.609"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 993. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 993. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	2032	"2011-07-08 12:23:53.609"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 995. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 995. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"DEBUG"	2600	"2011-07-08 12:23:53.625"	"No virus detected: stream: OK"
"DEBUG"	2600	"2011-07-08 12:23:53.640"	"Connecting to ClamAV virus scanner..."
"DEBUG"	2600	"2011-07-08 12:23:53.640"	"Connecting to ClamAV stream port..."
"APPLICATION"	2412	"2011-07-08 12:23:53.640"	"Servers started."
"ERROR"	2600	"2011-07-08 12:23:54.703"	"Severity: 3 (Medium), Code: HM5406, Source: ClamAVVirusScanner::Scan, Description: Unable to connect to ClamAV stream port at localhost:1776."
"DEBUG"	2600	"2011-07-08 12:23:54.703"	"Connecting to ClamAV virus scanner..."
"DEBUG"	2600	"2011-07-08 12:23:54.703"	"Connecting to ClamAV stream port..."
"DEBUG"	2600	"2011-07-08 12:23:54.703"	"No virus detected: stream: OK"

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-08 18:21

ok so that log show no break in activity so hmail couldn't have crashed & restarted.. Heck the AV scan completes!

Wonder if the indexing messages entry is a clue or a fluke. You might consider turning off message indexing & see if that makes the error stop. I'll have a look at the code to see if there is anything in indexing that could possibly do that.
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-08 18:38

thanks Bill, i will do that and report later...

weird because hmailserver is running like 3/4 hours and then puff...strange!

stupid idea: maybe windows think that hmailserver crash and then tries to start it but hmailserver is running so we have that TCPserver errors messages. :S
Last edited by FiShBuRn on 2011-07-08 18:52, edited 1 time in total.

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-08 18:51

If that last log snippet was not edited it might give good clues. Do you see that indexing line around same time as the cannot bind errors in other spots?
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-08 18:53

i only had debug on in that time...in the next crash it was off, ive turn on once again but now we have to wait until he crashs or not :P

Ive this one right after the other i posted:

Code: Select all

"DEBUG"	768	"2011-07-08 12:26:44.078"	"SD::~_InitiateExternalConnection-5"
"DEBUG"	768	"2011-07-08 12:26:44.078"	"Ending session 6"
"DEBUG"	768	"2011-07-08 12:26:44.078"	"SD::~_DeliverToExternalAccounts-2"
"DEBUG"	768	"2011-07-08 12:26:44.078"	"Collect delivery result"
"DEBUG"	768	"2011-07-08 12:26:44.078"	"Collect delivery result - Done"
"DEBUG"	768	"2011-07-08 12:26:44.078"	"SD::_RescheduleDelivery"
"DEBUG"	1100	"2011-07-08 12:26:55.812"	"Application::InitInstance - Configuration loaded."
"APPLICATION"	1100	"2011-07-08 12:26:55.812"	"Starting servers..."
"ERROR"	1080	"2011-07-08 12:26:55.906"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 25. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 25. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	1080	"2011-07-08 12:26:55.906"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 110. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 110. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	1080	"2011-07-08 12:26:55.906"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 143. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 143. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	1080	"2011-07-08 12:26:55.906"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 465. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 465. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	1080	"2011-07-08 12:26:55.906"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 993. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 993. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"ERROR"	1080	"2011-07-08 12:26:55.906"	"Severity: 2 (High), Code: HM4316, Source: TCPServer::Run(), Description: Failed to bind to local port. Error: Normalmente só é permitido uma utilização de cada endereço de socket[nl](protocolo/endereço de rede/porta). Address: 0.0.0.0, Error code: 10048, Port: 995. This is often caused by another server listening on the same port.To determine which server is listening on the port, telnet your server on port 995. Make sure that no other email server is running and listening on this port, and then restart the hMailServer service."
"DEBUG"	780	"2011-07-08 12:26:55.906"	"SMTPDeliveryManager::Start()"
"DEBUG"	1264	"2011-07-08 12:26:55.906"	"Delivering message..."
"APPLICATION"	1264	"2011-07-08 12:26:55.906"	"SMTPDeliverer - Message 1015173: Delivering message from someone@localdomain.com to xxx. File: C:\Programas\hMailServer\Data\{19679F2B-2C2A-4D8C-B670-3E29034E1F10}.eml"
"DEBUG"	1264	"2011-07-08 12:26:55.921"	"Connecting to ClamAV virus scanner..."
"DEBUG"	1264	"2011-07-08 12:26:55.921"	"Connecting to ClamAV stream port..."
"DEBUG"	1100	"2011-07-08 12:26:55.921"	"Starting message indexing thread..."
"DEBUG"	2160	"2011-07-08 12:26:55.921"	"ExternalFetchManager::Start()"
"DEBUG"	2044	"2011-07-08 12:26:55.921"	"Indexing messages..."
"DEBUG"	1264	"2011-07-08 12:26:56.250"	"No virus detected: stream: OK"
"DEBUG"	1264	"2011-07-08 12:26:56.265"	"Connecting to ClamAV virus scanner..."
"DEBUG"	1264	"2011-07-08 12:26:56.265"	"Connecting to ClamAV stream port..."
"DEBUG"	1264	"2011-07-08 12:26:56.265"	"No virus detected: stream: OK"
"DEBUG"	1264	"2011-07-08 12:26:56.265"	"Connecting to ClamAV virus scanner..."
"DEBUG"	1264	"2011-07-08 12:26:56.265"	"Connecting to ClamAV stream port..."
"APPLICATION"	1100	"2011-07-08 12:26:56.281"	"Servers started."
"DEBUG"	1264	"2011-07-08 12:26:56.531"	"No virus detected: stream: OK"
"DEBUG"	1264	"2011-07-08 12:26:56.531"	"Connecting to ClamAV virus scanner..."
"DEBUG"	1264	"2011-07-08 12:26:56.531"	"Connecting to ClamAV stream port..."
"DEBUG"	1264	"2011-07-08 12:26:56.546"	"No virus detected: stream: OK"
"DEBUG"	1264	"2011-07-08 12:26:56.546"	"Connecting to ClamAV virus scanner..."
"DEBUG"	1264	"2011-07-08 12:26:56.546"	"Connecting to ClamAV stream port..."
"DEBUG"	1264	"2011-07-08 12:26:56.546"	"No virus detected: stream: OK"
"DEBUG"	1264	"2011-07-08 12:26:56.546"	"Connecting to ClamAV virus scanner..."
"DEBUG"	1264	"2011-07-08 12:26:56.546"	"Connecting to ClamAV stream port..."
"DEBUG"	1264	"2011-07-08 12:26:56.546"	"No virus detected: stream: OK"
"DEBUG"	1264	"2011-07-08 12:26:56.578"	"Connecting to ClamAV virus scanner..."
"DEBUG"	1264	"2011-07-08 12:26:56.593"	"Connecting to ClamAV stream port..."
"DEBUG"	1264	"2011-07-08 12:26:56.593"	"No virus detected: stream: OK"

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-08 19:00

Those logs look way too weird! As if 2 copies of hmail are running at same time! That would explain the bind errors & why the logs looks so weird (like messages being delivered WHILE hmail doing startup process and even though it cannot listen for connections!) but not sure how that is possible! When you installed 5.4 did you do an in-place upgrade of your existing hmail?? (Into same directory etc)
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-08 20:29

yes, like any other upgrade of hmailserver that i have done...:/

the hmailserver is running on this server since 2007, this is the first time that i have major problems.

btw now if hmail crash windows doesnt start it up again...just for testing...

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-08 21:20

Can you please verify there is only 1 hmail service & search to make sure there is only 1 hmailserver.exe on your server? And I assume you are not running the exe manually, just with the service control manager right?
Thanks,
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-08 22:01

Can you please verify there is only 1 hmail service & search to make sure there is only 1 hmailserver.exe on your server?

Checked, just one exe and one service.

And I assume you are not running the exe manually, just with the service control manager right?

Right.

The only thing ive done after i installed 5.4 was this query, that i found on other post:

Code: Select all

UPDATE hm_messages SET messagefilename=REPLACE(messagefilename, messagefilename, right(messagefilename,42))
To fix the error in diagnostic: ERROR : Full paths are stored in the database

Thanks Bill

rolaids0
Normal user
Normal user
Posts: 150
Joined: 2010-04-27 02:03
Location: Florida
Contact:

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by rolaids0 » 2011-07-08 23:43

You want to make sure that the path should be truncated at 42 characters....

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-08 23:47

i run that query to remove full paths from database...:)

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-09 00:40

FiShBuRn wrote:The only thing ive done after i installed 5.4 was this query, that i found on other post:

Code: Select all

UPDATE hm_messages SET messagefilename=REPLACE(messagefilename, messagefilename, right(messagefilename,42))
To fix the error in diagnostic: ERROR : Full paths are stored in the database

Thanks Bill
Do you know if the problem was there before that UPDATE?

Happen to have logs from before upgrade or the UPDATE to see if the problem existed before 5.4 or before UPDATE executed?

You happen to make a backup (sqldump) of the database before upgrade or before the UPDATE?

Browse the hm_messages table looking for odd looking paths? (A mucked up path could cause issues as hmail tries to rebuild the full path from that..)
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-09 00:54

Do you know if the problem was there before that UPDATE? Yes, it was there that why i use the UPDATE.

Happen to have logs from before upgrade or the UPDATE to see if the problem existed before 5.4 or before UPDATE executed? I have logs from before the upgrade but not with debug active.

You happen to make a backup (sqldump) of the database before upgrade or before the UPDATE? I have some dumps before the upgrade, i only made a dump from hm_messages before i ran the UPDATE.

Browse the hm_messages table looking for odd looking paths? (A mucked up path could cause issues as hmail tries to rebuild the full path from that..) I will have a look at this...

btw i have ran the DDS once again...

Edit: all paths are looking ok...its not possible if hmail found a error when he tries to rebuild the path to write that in logs?

Thanks

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-09 01:42

I'd have to look at the source code & find where the path rebuild happens to see if there is chance for some sort of crash there or what kind of logging could be there. Any time you make manual changes to the database you run risk of issues. I'd guess even more so if you had hmail running while you did the database changes. But even if that is the case not sure how having a messed up file path could cause what your logs show. I recall martin saying he made changes to the code to help hmail recover if there was a problem & perhaps something happens & hmail tries to restart but your logs make it look like it was running fine & delivering an email when hmail was starting which doesn't seem likely.

At this point I doubt what you are seeing is a bug in 5.4 but more likely something unique with your server. Not saying it's impossible but the stuff isn't adding up or making sense.
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-09 11:20

When i made that UPDATE the hmail was stopped...i stopped him, make backup of hm_messages and then i UPDATE, then i startup hmail just fine...

Dunno...but thanks for helping me :) hope we find some kind of a fix because i cant go back without losing some email...

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-11 12:03

bad news, after weekend without crashes...today hmail crash, ive disabled the ability to windows restart the service so hmail as stopped without those errors messages.

Code: Select all

"DEBUG"	2440	"2011-07-11 10:39:26.703"	"Delivering message..."
"APPLICATION"	2440	"2011-07-11 10:39:26.703"	"SMTPDeliverer - Message 1017188: Delivering message from someone@localdomain.com to xxx. File: C:\Programas\hMailServer\Data\{6685539C-B4B4-4F07-8310-3EF89C0F571B}.eml"
"DEBUG"	2440	"2011-07-11 10:39:26.703"	"Applying rules"
"DEBUG"	2440	"2011-07-11 10:39:26.703"	"Applying rule"
"DEBUG"	2440	"2011-07-11 10:39:26.703"	"Applying rule"
"DEBUG"	2440	"2011-07-11 10:39:26.703"	"Applying rule"
"DEBUG"	2440	"2011-07-11 10:39:26.703"	"Performing local delivery"
"DEBUG"	2440	"2011-07-11 10:39:26.703"	"Copying mail contents"
"DEBUG"	2400	"2011-07-11 10:39:26.703"	"Closing TCP/IP socket"
"DEBUG"	344	"2011-07-11 10:39:26.703"	"Ending session 11040"
"DEBUG"	2440	"2011-07-11 10:39:26.781"	"Applying rules"
"DEBUG"	2440	"2011-07-11 10:39:26.781"	"Saving message: {924F4075-32D7-4EFD-B302-92BAF654618F}.eml"
"DEBUG"	2440	"2011-07-11 10:39:26.937"	"AWStats::LogDeliverySuccess"
"DEBUG"	2440	"2011-07-11 10:39:26.937"	"Copying mail contents"
"DEBUG"	2408	"2011-07-11 10:39:26.937"	"Closing TCP/IP socket"
"DEBUG"	2408	"2011-07-11 10:39:26.937"	"Ending session 11039"
"DEBUG"	2440	"2011-07-11 10:39:26.953"	"Applying rules"
"DEBUG"	2440	"2011-07-11 10:39:26.953"	"Saving message: {F86D55A9-3A22-4352-899C-F9F2F427AEFB}.eml"
"DEBUG"	2440	"2011-07-11 10:39:26.953"	"AWStats::LogDeliverySuccess"
"DEBUG"	2440	"2011-07-11 10:39:26.968"	"Applying rules"
"DEBUG"	2440	"2011-07-11 10:39:26.968"	"Saving message: {6685539C-B4B4-4F07-8310-3EF89C0F571B}.eml"
"DEBUG"	2440	"2011-07-11 10:39:26.968"	"AWStats::LogDeliverySuccess"
"DEBUG"	2440	"2011-07-11 10:39:26.968"	"Local delivery completed"
"APPLICATION"	2440	"2011-07-11 10:39:26.968"	"SMTPDeliverer - Message 1017188: Message delivery thread completed."
"DEBUG"	2400	"2011-07-11 10:39:28.140"	"SMTPClientConnection::~_Continue sendfile"
"SMTPC"	1532	0	"2011-07-11 10:39:28.437"	"TCP"	"SMTPDeliverer - Message 1017025 - Connection failed: Host name: 195.170.168.136, message: Uma tentativa de ligação falhou porque o componente ligado não respondeu correctamente após um período de tempo, ou a ligação estabelecida falhou porque o anfitrião ligado não respondeu"
"DEBUG"	1788	"2011-07-11 10:39:28.468"	"SMTPClientConnection::~_Continue sendfile"
"DEBUG"	2100	"2011-07-11 10:39:28.640"	"SD::~_InitiateExternalConnection-5"
"DEBUG"	2100	"2011-07-11 10:39:28.640"	"Ending session 11035"
"DEBUG"	2100	"2011-07-11 10:39:28.640"	"SD::~_DeliverToExternalAccounts-2"
"DEBUG"	2100	"2011-07-11 10:39:28.640"	"Collect delivery result"
"DEBUG"	2100	"2011-07-11 10:39:28.640"	"Collect delivery result - Done"
"DEBUG"	2100	"2011-07-11 10:39:28.640"	"SD::_RescheduleDelivery"
"DEBUG"	2392	"2011-07-11 10:39:29.578"	"Creating session 11041"
"DEBUG"	1532	"2011-07-11 10:39:29.656"	"Closing TCP/IP socket"
"DEBUG"	2400	"2011-07-11 10:39:29.906"	"SMTPClientConnection::~_Continue sendfile"
"DEBUG"	1532	"2011-07-11 10:39:29.906"	"Ending session 11041"
"DEBUG"	1788	"2011-07-11 10:39:30.562"	"SMTPClientConnection::~_Continue sendfile"
"DEBUG"	1840	"2011-07-11 10:39:35.187"	"SMTPClientConnection::~_Continue sendfile"
"DEBUG"	1840	"2011-07-11 10:39:35.187"	"SMTPClientConnection::~_Continue sendfile"
"DEBUG"	1840	"2011-07-11 10:39:35.187"	"SMTPClientConnection::~_Continue sendfile"
"DEBUG"	1840	"2011-07-11 10:39:35.187"	"SMTPClientConnection::~_Continue sendfile"

^DooM^
Site Admin
Posts: 13861
Joined: 2005-07-29 16:18
Location: UK

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by ^DooM^ » 2011-07-11 12:08

Is this running on a VM?
If at first you don't succeed, bomb disposal probably isn't for you! ヅ

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-11 12:18

Nop :/

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-11 12:27

I got this error when i has connected to hmailserver admin, then hmail restarted:

Code: Select all

ExceptionType: COMException
HelpLine: 
Message: A chamada de procedimento remoto falhou. (Exception from HRESULT: 0x800706BE)
Source: Interop.hMailServer
StackTrace:    at hMailServer.IInterfaceApplication.get_Status()
   at hMailServer.Administrator.ucStatus.ShowStatistics()
   at hMailServer.Administrator.ucStatus.timerServerStats_Tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
TargetSite: hMailServer.Status get_Status()
Maybe this can lead to something?

^DooM^
Site Admin
Posts: 13861
Joined: 2005-07-29 16:18
Location: UK

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by ^DooM^ » 2011-07-11 12:34

If at first you don't succeed, bomb disposal probably isn't for you! ヅ

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-11 12:40

^DooM^ wrote:Does this apply?

http://support.microsoft.com/kb/896989
Nop, because im still using Windows Server 2000

Thansk anyway ^Doom^

^DooM^
Site Admin
Posts: 13861
Joined: 2005-07-29 16:18
Location: UK

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by ^DooM^ » 2011-07-11 12:48

Server 2000 was last updated in 2005 so any OS fixes are out the window. Any other errors showin in the event log at all that may be causing issues? COM errors mainly but anything may help.
If at first you don't succeed, bomb disposal probably isn't for you! ヅ

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-11 12:55

^DooM^ wrote:Server 2000 was last updated in 2005 so any OS fixes are out the window. Any other errors showin in the event log at all that may be causing issues? COM errors mainly but anything may help.
No more errors only this...im also searching for that error and possible fixe maybe this new version is not compatible with server 2000...

^DooM^
Site Admin
Posts: 13861
Joined: 2005-07-29 16:18
Location: UK

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by ^DooM^ » 2011-07-11 12:57

It's possible, Martin upgraded the internals to fix the IOCP error that some people were having, I am wondering if those fixes are not compatible with an older OS. If so Martin will need to change the requirements.
If at first you don't succeed, bomb disposal probably isn't for you! ヅ

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-11 12:59

eheh...i never had those errors...well i think im doomed :s

rolaids0
Normal user
Normal user
Posts: 150
Joined: 2010-04-27 02:03
Location: Florida
Contact:

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by rolaids0 » 2011-07-11 13:06

I had lots of issues with 2000, same as you are seeing. I upgraded to 2003 and all the issues went away. If you're not able to upgrade, then you may be out of luck. I could repeat it by connecting to an exchange server that was failing (half open connections). Since the O/S is so old I don't foresee a fix coming along.

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-11 13:09

Yes, but im only getting errors with this version :/ too bad for me, old versions allways worked without a problem.

^DooM^
Site Admin
Posts: 13861
Joined: 2005-07-29 16:18
Location: UK

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by ^DooM^ » 2011-07-11 13:31

You can pick up a copy of 2003 web edition for much cheapness these days!
If at first you don't succeed, bomb disposal probably isn't for you! ヅ

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-11 13:40

yeah i know but i need to have 100% sure that is a SO problem and no fix is avaiable...

^DooM^
Site Admin
Posts: 13861
Joined: 2005-07-29 16:18
Location: UK

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by ^DooM^ » 2011-07-11 14:20

I can guarantee there will be no fixes to hMail unless more users have the same problem or you can track down the exact issue that can be replicated elsewhere.
If at first you don't succeed, bomb disposal probably isn't for you! ヅ

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-11 15:20

^DooM^ wrote:I can guarantee there will be no fixes to hMail unless more users have the same problem or you can track down the exact issue that can be replicated elsewhere.
thanks for your guarantee im only saying that because if i upgrade my server and other stuff to end up wth the same situation...i have to make sure that is SO problem not any kind of configuration problem.

If something odd came up in logs or in event log it would be more easy to catch up the problem :s

rolaids0
Normal user
Normal user
Posts: 150
Joined: 2010-04-27 02:03
Location: Florida
Contact:

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by rolaids0 » 2011-07-11 15:50

I can assure you its an OS/Library compatibility issue.

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-11 16:15

I don't see a crash in those latest logs.

That exception dump looks like from GUI which is common if you leave gui open when you restart hmail service or if service crashes while it is left open. Not likely useful.

Didn't realize you were on windows 2000. Very possible 5.4 is not compatible on win2k & I recall somewhere talk of no longer providing support for win2k because of so many known issues especially in tcp/ip stack among other things. You *might* be able to try upgrading tcp/ip files from 2k3 but hell if I want to see you make your server worse. lol I will say I did most of my testing of 5.4 tracking down IOCP errors using win2k and although I could easily get the IOCP crashes to happen with 1st release of 5.4 (and pretty much every version of 5.x too) I was not able to force it to happen after fixes were in place. No idea why you'd be having issues but to me doesn't look like your issue is the same and likely unique to you & your setup there and quite likely being on old 2k is a part of it.
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-11 16:28

I don't see a crash in those latest logs. - but hmail crashed after the last line ive posted.

I believe in you Bill because ive the same version running on my secundary (backup) server and no problems so far..

dunno what to do more? any ideas Bill?

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-11 16:51

FiShBuRn wrote:I don't see a crash in those latest logs. - but hmail crashed after the last line ive posted.

I believe in you Bill because ive the same version running on my secundary (backup) server and no problems so far..

dunno what to do more? any ideas Bill?
Perhaps it crashed was just saying the logs don't show it.

Swap servers. :D Is the secondary 2k as well? Odds are there are difference between them even if just settings/scripts/rules/etc

Got me at this point. I'd try disabling anything you can like rules to see if it helps. Otherwise you might need to consider rolling back to 5.3 (which would be a nightmare or you'd lose all email since your last backup) or maybe upgrade to 2k3 or migrate to new server. Thing is none of those are guaranteed to work so could be for nothing or just make it worse.
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-11 16:57

indeed, yeah would be great if a could swap servers, nah other server runs 2k8.

Thats my fear, change a lot of things and keep the problem...eheh...i will try to disable some stuff like u say and see what happens.

Rollback will be a pain the *** :/ for now i made a batch file that search for hmailserver.exe in tasklist every 3 minutes and if the process doesnt exist service is started.

Is it possible that the new feature of ClamAV could cause this in my system? besides the upgrade, that the only thing that ive changed between versions...maybe i will try it in old way...

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-11 17:17

FiShBuRn wrote:indeed, yeah would be great if a could swap servers, nah other server runs 2k8.

Thats my fear, change a lot of things and keep the problem...eheh...i will try to disable some stuff like u say and see what happens.

Rollback will be a pain the *** :/ for now i made a batch file that search for hmailserver.exe in tasklist every 3 minutes and if the process doesnt exist service is started.

Is it possible that the new feature of ClamAV could cause this in my system? besides the upgrade, that the only thing that ive changed between versions...maybe i will try it in old way...
2k is soooo dated, it should have been retired a LONG time ago. lol

Well sometimes you need to risk breaking things (and sometimes end up making things worse) to try & fix them. Trick is to do changes in a smart fashion & always have backups.

Rollback should be possible with script to 'fix' all the file paths back to original full paths then install older 5.3.x but yeah not trivial especially since no one has made that script yet. :D

Many of us use the clamd client built into 5.4 without a problem but yes seems you are the only one we know of with the issues you have so I'd consider anything possible at this point & something like that should be easy to test with & without to see..
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

^DooM^
Site Admin
Posts: 13861
Joined: 2005-07-29 16:18
Location: UK

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by ^DooM^ » 2011-07-11 17:57

hMail runs fine on 2k8 x64 btw
If at first you don't succeed, bomb disposal probably isn't for you! ヅ

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-12 16:23

Well the problem is something about the email because today hmail has crashing a lot of times in this part:

Code: Select all

"SMTPD"	2576	0	"2011-07-12 14:58:50.640"	"TCP"	"DNS - Query failure. Treating as temporary failure. Query: somedomain.com.pt, Type: 15, DnsQuery return value: 9002."
"DEBUG"	2576	"2011-07-12 14:58:50.640"	"Failed to resolve email servers (MX lookup). Domain name: somedomain.com.pt."
"APPLICATION"	2576	"2011-07-12 14:58:50.640"	"SMTPDeliverer - Message 1019387: No mail servers could be found for the address service@somedomain.com.pt."
Then i restarted, then crash at same place all the time, i had to remove those EML.

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-12 16:29

Very strange. If you are convinced it is DNS issue you might consider trying a different DNS server (in your network settings because that is what hmail uses, windows default dns server(s).

Btw I recall MANY issues with DNS (tcp/ip in general) with windows 2000. I think there is a way to replace DLL's from 2k3 to help but that part of my brain had done garbage collection a LONG LONG LONG time ago.
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-12 16:36

hey Bill im not convinced but for the first hmail crashed on something that we can see...dunno...im using google dns, allways used this one i dont think this is the problem :s

I think 5.4 is not compatible with 2000 maybe he should put a warn is this...what you think? If other version worked without a problem for years...

Bill any hint to made a script to fix the path back to original 5.3.x?

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-12 17:09

Well i figure a way to fix the full path, is there other things that i need to change? Like BD changes that 5.4 made? or when i install 5.3 bd will be fixed for that version?

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-12 17:22

FiShBuRn wrote:hey Bill im not convinced but for the first hmail crashed on something that we can see...dunno...im using google dns, allways used this one i dont think this is the problem :s

I think 5.4 is not compatible with 2000 maybe he should put a warn is this...what you think? If other version worked without a problem for years...

Bill any hint to made a script to fix the path back to original 5.3.x?
Could very well be compatibility between 2000 & hmail 5.4 BUT as I said I did most of my testing with 2000 because the person who found way to reliably reproduce the IOCP stuff was using 2000 so that's what I used and the 'fixed' 5.3.4 & 5.4 no longer gave me those errors on the same 2000 box which made us think it was fixed and shows that 5.4 must work with 2k or at least within the scope of my testing which did not include delivering to outside (so no dns/mx lookups) and no public blacklist lookups (so again no dns) so always possible is dns issue.

I looked back & the file we changed 'back in the day' to make 2000 work better was dnsapi.dll which I *think* was from 2k3 server or some microsoft hotfix. We put it in the same folder as the old mail server software EXE (not hmail mind you but another mail server that had dire dns problems with 2k server) and rebooted (to clear out existing DLL from memory) and all worked way better although we had various other issues from time to time. You might consider trying a replacement dnsapi.dll in either the hmail bin folder or replace the actual one in system32 (making backup of course) but realizing risks in doing that.. (in other words be prepared to boot on recovery cd like active@ boot cd to be able to switch dll's back if needed). Anyway something to consider doing before trying to roll back to 5.3..
FiShBuRn wrote:Well i figure a way to fix the full path, is there other things that i need to change? Like BD changes that 5.4 made? or when i install 5.3 bd will be fixed for that version?
Are you SURE you got the path rebuild path method set? Are you pulling the domain & account/user from a different table?
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-12 17:33

Btw I found a zip copy of the dnsapi.dll I used back in the day & it is dated 2002 & version 5.0.2195.6012 & says Windows 2000 so I think this was a special hotfix release not from 2k3.
Bill
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-12 18:15

Can u send me that Bill? My last shot on this.

Im building full path based on this information from Martin: <DataDirectory><Domain><Account><FirstTwoCharactersOfFileName><FileName>.

Are you pulling the domain & account/user from a different table? Yes, i will tested and compare it with my old sql dumps before applying but yes. I will post the script here if you want to have a look...its not finished yet
Last edited by FiShBuRn on 2011-07-12 18:34, edited 1 time in total.

FiShBuRn
Normal user
Normal user
Posts: 88
Joined: 2007-06-29 16:43

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by FiShBuRn » 2011-07-12 18:21

Bill48105 wrote:Btw I found a zip copy of the dnsapi.dll I used back in the day & it is dated 2002 & version 5.0.2195.6012 & says Windows 2000 so I think this was a special hotfix release not from 2k3.
Bill
The version of my file is 5.0.2195.7280

Bill48105
Developer
Developer
Posts: 6192
Joined: 2010-04-24 23:16
Location: Michigan, USA

Re: TCPServer::Run() error after upgrading to latest 5.4

Post by Bill48105 » 2011-07-12 18:34

FiShBuRn wrote:The version of my file is 5.0.2195.7280
Hmm so yours is likely newer. Either microsoft broke something in newer version or that is not it. :D

Btw my rough method of rebuilding file paths was:
Need to grab messageacccountid from hm_messages & lookup their account & domain from hm_accounts using that then update messagefilename in hm_messages to prepend DatafolderPath\theirdomain\theiraccount\originalfilename.eml & repeat for every message in hm_messages likely only doing ones that have messagetype = 2 which means delivered

In either case I'd have backups of your database & realize it is very risky.. I'd certainly test on a test server 1st. :D once paths are fixed (view some ot make sure they look right) then the other changes between 5.3.x & 5.4 shouldn't matter or are less critical. I thought I posted them up but you can view the upgrade SQL file in the DBScripts folder inside the hmail folder. You definitely need to manually change the db version value though. Then you should be able to install 5.3.4 over 5.4, select your existing database & cross your fingers. (Again I'd do trial runs on test server, even if using backups from your real server..)
hMailServer build LIVE on my servers: 5.4-B2014050402
#hmailserver on FreeNode IRC https://webchat.freenode.net/?channels=#hmailserver
*** ABSENT FROM hMail! Those in IRC know how to find me if urgent. ***

Post Reply