Error Connection Closed Gracefully
Contents |
of these buttons! Sign In Register Categories Recent Discussions In this Discussion Joffrey July 2015 ntozier August 2015 padma August 2015 osTicket v1.9.12 (stable), osTicket v1.10-RC.2 (Release Candidate) connection closed gracefully ftp now available! Go get it now [resolved] email is not working padma July connection closed gracefully sendmail 2015 edited August 2015 in Troubleshooting and Problems Hi there,when i tried to create a new ticket .i'm not receiving
Connection Closed Gracefully Delphi
any email,alerts ...can anyone please help me how to setup/configure emails.Regards,padma Comments Joffrey July 2015 Pls let us know more about your configuration, alerts/notices & mail. padma July 2015 Hi joffrey,thanks for your
Connection Closed Gracefully Hatası
reply.i deployed the osticket (v 1.8.10)into the xampp server.every thing is working well.but i'm not receiving any emails .i.e when i'm creating new ticket,closing , updating or transferring the tickets to staff.for email configuration i did modify the php.ini file in the xampp folderthe following things i have setup into the php.ini fileSMTP = smtp.gmail.comsmtp_port = 587sendmail_from = mygmailaccountsendmail_path="C:\xampp\mailtodisk\mailtodisk.exe"then i went to the adminpanel->diagnostics-> tried to connection closed gracefully smtp test the mail.it says Test email sent successfullybut ihaven't receive any email( i have added my anthergmailid into TO address ).even i tried to create a new ticket with new user . still the emails are not working...i'm new to php .please help me on this that what i'm missing.thank you so much ntozier July 2015 I don't know what mailtodisk.exe s but I have never used it, nor had to use it.Instead of configuring PHP (php.ini) try adding your SMTP settings in osTicket. padma July 2015 hi ntozer,when i try to add the smtp settings for adding a new email.im getting the below error[09-Jul-2015 13:13:55 Europe/Berlin] PHP Fatal error: Maximum execution time of 30 seconds exceeded in C:\xampp\htdocs\Helpdesk\include\class.mailfetch.php on line 141I'm using the below smtp setting for incoming and outgoing mailsmail fetching:im using status:enablehost:pop.gmail.comport:995outgoing mail:status:enablehost:smtp.gmail.comport:465AuthenticationRequired:No ntozier July 2015 This:PHP Fatal error: Maximum execution time of 30 seconds exceededmeans that the script is taking over 30s to run, and your PHP is killing the process because it exceeded the time out that you have set in the php.ini. Try raising the value in your php.ini for max_execution_time, and restarting the apache. padma July 2015 Hi Ntozier,
execution and Indy will catch and handle the exception. http://osticket.com/forum/discussion/85971/resolved-email-is-not-working For Clients The server side of this connection has disconnected normally but your client has attempted to read or write to the connection. You http://www.indyproject.org/kb/whydoikeepgettingeidconnc.htm should trap this error using a try..except or in C++ Builder, a try..catch block. There is more detail about the EIdConnClosedGracefully exception in an article at the Indy Portal titled Connection Closed Gracefully. Please also see the help file for possible further information. See also: •Why does Indy raise exceptions as part of its normal operation?•Why do I get 10038 exceptions raised when I shut down my servers?
For more information about the Indy Project visit the Indy Project Page Advertising 21 Visitors Online Connection Closed Gracefully Author: Chad Z. Hower Homepage: http://www.atozedsoftware.com Many Indy users are annoyed by the EIdConnClosedGracefully exception that is raised with Indy servers, especially the HTTP and other servers. EIdConnClosedGracefully is an exception signaling http://www.swissdelphicenter.com/en/showarticle.php?id=1 that the connection has been closed by the other side intentionally. This is not the same as a broken connection which would cause a connection reset error. If the other side has closed the connection and the socket is read or written to, EIdConnClosedGracefullywill be raised by Indy. This is similar to attempting to read or write to a file that has been closed without your knowledge. In some cases this is a true exception connection closed and your code needs to handle it. In other cases (typically servers) this is a normal part of the functioning of the protocol and Indy handles this exception for you. Even though Indy catches it, when running in the IDE the debugger will be triggered first. You can simply press F9 to continue and Indy will handle the exception, but the constant stopping during debugging can be quite annoying. In the cases where Indy catches the connection closed gracefully exception, your users will never see an exception in your program unless it is run from the IDE. Simple solution Because the EIdConnClosedGracefullyis a common exception especially with certain servers it descends from EIdSilentException. On the Language Exceptions tab of Debugger Options (Tools Menu) you can add EIdSilentException to the list of exceptions to ignore. After this is added the exceptions will still occur in the code and be handled, but the debugger will not stop the program to debug them. Is it an error? All exceptions are not errors. Many developers have been taught or assumed that all exceptions are errors. However this is not the case, and this is why they are called exceptions and not errors. Exceptions are exactly that - exceptions. Delphiand C++ Builder use exceptions to handle errors in an elegant way. However exceptions have other uses besides errors as well. EAbort is one example of an exception that is not necessarily an error. Exceptions such as these are used to modify standard program flow and communicate information to a higher calling level where they are trapped. Indy uses exceptions in such a way as well. Why is it an exception? Many users have commented that maybe it there should be a return value to signal this condition instead of an exception. However this is the wrong approach i