Forum OpenACS Q&A: OpenACS Keepalive how to do it for windows based installation

what does the AOLserver error log report before the service stops? Are you using a Windows service to start and stop AOLserver?

best wishes
Brian

But, the time it stops responding this was the last message.All other messages are of "Notice" type so not posting.

Please let me know if you can make out something. Generally it happens on weekends and we cannot access project-open on Mondays.

==========================================================

[24/Mar/2012:05:31:46][1244.3180][-sched:23-] Notice: im_mail_import.process_mails0: Error creating '/web/projop/Maildir/spam' folder: 'mkdir ("/web/projop/Maildir/spam") failed:

no such file or directory'
[24/Mar/2012:05:31:54][1244.3136][-sched:16-] Notice: acs-mail-lite: about to load qmail queue
[24/Mar/2012:05:31:54][1244.3136][-sched:16-] Notice: acs_mail_lite::load_mail_dir: queue_dir=''
[24/Mar/2012:05:31:54][1244.3136][-sched:16-] Notice: acs_mail_lite::load_mail_dir: queue dir = /new/*, no messages
[24/Mar/2012:05:32:16][1244.1684][-sched:25-] Notice: sync: uid=32644, pid=50898, day=2012-03-20 00:00:00+05:30
[24/Mar/2012:05:32:16][1244.1684][-sched:25-] Error: Tcl exception:
ambiguous option "file": must be authpassword, authuser, channel, close, content, contentlength, contentsentlength, contentchannel, copy, driver, encoding, files, fileoffset,

filelength, fileheaders, flags, form, headers, host, id, isconnected, location, method, outputheaders, peeraddr, peerport, port, protocol, query, request, server, sock, start,

status, url, urlc, urlencoding, urlv, version, or write_encoded
while executing
"ns_conn $var"
(procedure "ad_conn" line 90)
invoked from within
"ad_conn file"
(procedure "ad_parse_template" line 15)
invoked from within
"ad_parse_template -params [list [list exception_count $exception_count] [list exception_text $exception_text]] "/packages/acs-tcl/lib/ad-return-com..."
(procedure "ad_return_complaint" line 2)
invoked from within
"ad_return_complaint 1 "

Yes, as server was not responding (I thought so! ) because project-open web page was not accessible, we manually tried to stop the service on 26th March. And as it was taking too much time to stop we just rebooted the machine.

Next time it happens, i will do telnet and see. We have observed the issue on 24 March, and after that on 13th April. So we have to wait for few weeks for it to reappear, most probable dates are either 28-29 April or 5-6 May.

I will update my observation and let you know what actually happened.

I tried to search for "how to kill the AOL-server in Win XP"
could not get satisfactory answers. Below is what i got :

1) Go to task manager -> select "nsd.exe" and end process tree

2) Use command "netstat -ano" , get PID for 8000 port, which is actual project open port and give command "taskkill /f /PID 5072

For both the methods when i see in services its showing -> AOLserver-projop "starting" but its not doing anything, again i have to stop it manually. But if i stop it immediately it gets stopped and i can restart it again.

I am new to this, and i really appreciate if you can confirm which way to be used to kill the server or i m doing totally wrong way.

Thanks,
Sujata

- the first error is triggered from you scheduled procedure 25. You can figure out, what this is either from nsstats.tcl, and if you do not have nsstats installed, from ds/shell (or nscp) by running there "lindex [ns_info scheduled] 25". Normally, "ad_return_complaint 1" should be followed by an error message. You should first figure out what your sched proc 25 is before digging into this to find the right spot easier. However, while this error is not intended behavior, it is most likely not related to the seconds error, which happened nearly 5 hours later.

- the second error happened in "im_company_internal_helper" in the package intranet-core, which is most likely a ]PO[ package, doing some timesheet calculation. Ask the PO-people why this fails. The snippet does not show, when exactly this error happened. We see from the snippet that at 10:10:34 the server is stopping. This is a strange time for a scheduled restart, most likely, someone stopped the server manually. The server was restarted 2min 16secs later - also most likely manually. The problem seems to me that a second server instance was started before the first server instance exited.

When the server stops, it shuts down the network connections (as shown in the log) and shuts down all other services such as scheduled procedures (it tries to finish these). Then you should see a message like "Notice: sched: shutdown complete", ... "Notice: driver: stopped: nssock", and finally "Notice: nsmain: AOLserver/4.5.1 exiting". The exact detail of the messages depend on the configuration and logging detail.

As we can see from the log at least the exit-message is missing. It looks to me, as if you have more or less 2 servers running, the first one hanging in shutdown state (but which as stopped accepting requests) and the second one waiting for the resources of the first, not being able to receive requests.

Since you are running under windows, you are most likely using the compiled version of Maurizio, which has the Tcl shutdown details already deactivated, which are discussed in the thread Brian mentioned. Since this version performs already "an exit without running all pending operations", the worst thing which might happens are truncated operations - but no hangs.

Are you performing scheduled restarts? If not, you should figure out, who or what is stopping your server (it does not do this by itself) and check there the stopping/starting conditions.