Thanks all! We're checking the logs ASAP! I think it is tied to the os libraries somehow....still trying to figure it out.
William Rentfrow wrentf...@stratacominc.com Office: 715-204-3061 or 701-232-5697x25 Cell: 715-498-5056 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Stone, Brian Sent: Wednesday, May 04, 2016 10:24 AM To: arslist@ARSLIST.ORG Subject: Re: arforkd - Linux upgrade issue It might be related to the os libraries which might be causing segment faults while executing the arforkd process. You could set your ulimit to unlimited(ulimit -c unlimited) to generate a dump. It should go to the ARSystem/bin dir Also this is from KA331603 A log file name can be specified for the daemon by adding the line Arfork-Log-File: xxx to the AR System server's configuration file, where xxx is replaced by the name of the file to which the arforkd should write its log. If a log file name for the arforkd is specified, the arforkd will automatically be started by the server with logging turned on. Note that setting the name of the arforkd log file will have no effect until the arforkd is restarted, since the filename is passed to the process when it is started. Unlike the AR System server, the fork daemon does not perform circular logging, nor does it rename a log file if the file exists when the daemon starts. Instead, the daemon always appends its output to the file. This should ensure that we can learn the last action performed by a daemon if it dies without worrying that the log file will be removed if the process is restarted twice. If the arforkd is started without specifying a log file and logging is turned on, it will write its log to its standard output. Logging is turned on by sending the arforkd a SIGUSR1 signal and turned off by sending the process a SIGUSR2 signal. If a fork daemon log file is to be removed while the arforkd is running, logging should be turned off before removing the file. Otherwise, the file will remain open as long as the process continues logging, even though the file's directory entry has been removed. A last note: if the arforkd executable is not installed in the same directory as the AR System server executable, the server will not be able to start the fork daemon. In that case, the server will produce an error message and fall back to running child processes itself. ________________________________ From: Action Request System discussion list(ARSList) [arslist@ARSLIST.ORG] on behalf of Grooms, Frederick W [frederick.w.gro...@xo.com] Sent: Wednesday, May 04, 2016 11:10 AM To: arslist@ARSLIST.ORG Subject: Re: arforkd - Linux upgrade issue ** arforkd is started internally from arserverd Is there any message giving an error in the arerror log on the startup? Fred From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of William Rentfrow Sent: Wednesday, May 04, 2016 9:47 AM To: arslist@ARSLIST.ORG Subject: arforkd - Linux upgrade issue ** Hi all - We've been upgrading Linux on some older servers running ARS/ITSM 7.6.04x. Some of them work. Some do not - the ones that do not give a message saying arforkd is not running. And sure enough it's not. I'm having a brain cramp - where/how is arforkd started? I don't see it referenced in the arsystem file or any of the *.sh files, and it's not in the armonitor.conf file or ar.conf. ??? William Rentfrow wrentf...@stratacominc.com<mailto:wrentf...@stratacominc.com> Office: 715-204-3061 or 701-232-5697x25 Cell: 715-498-5056 _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2016.0.7596 / Virus Database: 4563/12149 - Release Date: 05/02/16 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
