I also put in a couple of $0.01 here. We saw that the server crashed because of old entries in AP:Notification form(and other approval forms)...
-- Jarl On 6/18/07, Axton <[EMAIL PROTECTED]> wrote:
4500 is in the approval server error message range if I am not mistaken. The error indicates that the application dispatcher process died, not the arserverd process. Make sure that the application pending for exists, then check for weird data in that form. There may be data from the old system that doesn't agree with the new one. A word of advice, don't post your passwords, even when encrypted, to a public forum. For safety's sake, you should go ahead and change those now. The encryption is reversible, and the algorithms are not well protected. Axton Grams On 6/18/07, Dwayne Martin <[EMAIL PROTECTED]> wrote: > Hi Mahesh, > > Thanks for your interest in this. > > arerror.log said, "Dispatch : AR System Application server terminated when a signal/exception was received by the server (ARAPPNOTE 4500)" > > ar.conf is: > # Directory that contains the database files, log files, and notification > # files for the AR server > Currency-Ratio-Client-Refresh-Interval: 60 > # > # > Server-Name: rem1 > Server-directory: /opt/remedy/db > Register-With-Portmapper: T > Multiple-ARSystem-Servers: T > TCD-Specific-Port: 0 > Db-name: ARSystem > Db-user: ARAdmin > Alternate-Approval-Reg: T > Dbhome-directory: /u01/app/ora10/product/10.2.0 > Oracle-SID: REMPRD > Plugin: /opt/remedy/bin/reportplugin.so > Plugin: /opt/remedy/bin/arealdap.so > Plugin: /opt/remedy/bin/ardbcconf.so > Plugin: /opt/remedy/bin/ServerAdmin.so > Plugin: /opt/remedy/bin/FlashboardObject.so > DSO-User-Password: ApluEfS5dsUZx39nHjp5aZzrpUqIMISYAZg1e5quQUjGgBh4gEixTzGuBtfqSj4s2JtGUSLTT26cyAiqTykS5sMMEbnGLNgwEaYwo3ub8KmV0iJUZJm9+g== > Remedy-App-Service-Password: UE4tB18EFU1cQxjklIr1G+3UoVcMePXwsbZY4lyWMRPhokK7wbDYZGnERY4/oFZRTvQNBppKiQRT0SrBSI+aErL9qWrTkFKM9k2Ns7ttIPsYtNulTCBCSw== > Mid-Tier-Service-Password: eUnGfxGSxL/QwhsbCsm+VfpUywKRb75nLHI+zfx1qSpy/p1zCDJXLX/Sv3KzlyhjrtjNUeJ85OvXRqUZOM2IFKAeLk1GeNCxNUMmk/Vzz4aUCBPwGfF+6w== > Submitter-Mode: 1 > Db-password: 6zS8VNd2S8rTVIFl3pgoBYxwhrCvwR3bj7QjnsA3yadDTOWBfBJIlkhdNyuCpXpV66FkElnk3x5eKfwEfM6SYeV2tYk7D3ZOJWZ0QdB4EwceZpGEJ7SWwQ== > # > AREA-LDAP-Port: 389 > AREA-LDAP-Hostname: ldap.jmu.edu > AREA-LDAP-Use-Groups: 0 > AREA-LDAP-UseSSL: F > AREA-LDAP-User-Base: ou=people,o=JMU > AREA-LDAP-User-Filter: uid=$\USER$ > AREA-LDAP-Bind-Password: [EMAIL PROTECTED]/[EMAIL PROTECTED];W<g! > AREA-LDAP-Bind-User: cn=authenticatedBrowser,ou=UtilityAccounts,o=JMU > > External-Authentication-RPC-Socket: 390695 > External-Authentication-Ignore-Excess-Groups: F > Allow-Guest-Users: F > # > Filter-Log-File: /opt/remedy/db/filter.log > User-Log-File: /opt/remedy/db/user.log > Thread-Log-File: /opt/remedy/db/thread.log > Alert-Log-File: /opt/remedy/db/alert.log > Arfork-Log-File: /opt/remedy/db/fork.log > Plugin-Log-File: /opt/remedy/db/plugin.log > Server-Group-Log-File: /opt/remedy/db/srvgrp.log > SQL-Log-File: /opt/remedy/db/sql.log > API-Log-File: /opt/remedy/db/api.log > > Crossref-Blank-Password: T > Homepage-Form: GN:ControlPanel > Email-Import-Form-By-Default: T > Preference-Server-Option: 1 > Full-Text-Disable-Searching: T > > Plugin-Log-Level: 1239528 > #Changed-By-Another-User : T > Debug-mode: 0 > > You asked for "armonitorlog". I am not aware of such a file. Please tell me more. > > In case you are interested, here is the armonitor.conf: > SNMP-agent-enabled: F > #/opt/remedy/bin/arsnmpd --server rem1 -f -c /opt/remedy/conf/arsnmpd.conf udp:161 > Monitor-directory: /opt/remedy > /opt/remedy/bin/arserverd -s rem1 -i /opt/remedy -l /etc/arsystem/rem1 > /opt/remedy/bin/arsvcdsp -s rem1 -d /opt/remedy > #/opt/remedy/bin/arservdsd -s rem1 -i /opt/remedy > /opt/remedy/bin/arplugin -s rem1 -i /opt/remedy > /usr/ar/AREmail/rem1/emaild.sh start > > We are at patch 2. > > We have the AREA LDAP plugin. > > The only application we have is Asset Management. We mainly use our own customized call tracking system. > > We didn't run a thread log, but we have another testing session scheduled for tomorrow and we can try it then. > > I'll appreciate any help you can give us. > > Thanks again, > Dwayne Martin > > ---- Original message ---- > >Date: Mon, 18 Jun 2007 06:33:03 -0700 > >From: Mahesh Patil <[EMAIL PROTECTED]> > >Subject: Re: Server crashes on Linux > >To: [email protected] > > > > ** > > Hi, > > > > Please share the arerror.log, thread.log, > > armonitorlog, ar.conf files. > > Also let us know the plugins installed, ARS patch > > details and what all applications you are running on > > the server. > > > > Thanks, > > Mahesh > > > > Dwayne Martin <[EMAIL PROTECTED]> wrote: > > > > Hello Everyone, > > > > We have a customized AR System on a HPUX-11 system > > that has worked fine for years. Now we have moved > > it to a supposedly-superior Red-Hat Linux v4 32 > > -bit system (ARS 7.01, Oracle 10.2). We tested the > > system with 15 users at once, and the ARS server > > crashed about ten times in two hours. > > > > Is there some system setting that might be causing > > this? > > > > Dwayne Martin > > James Madison University > > > > Dwayne Martin > > Computing Support > > James Madison University > > > > _______________________________________________________________________________ > > UNSUBSCRIBE or access ARSlist Archives at > > www.arslist.org ARSlist:"Where the Answers Are" > > > > > > > > ------------------------------------------------ > > > > Moody friends. Drama queens. Your life? Nope! - > > their life, your story. > > Play Sims Stories at Yahoo! Games. > > __20060125_______________________This posting was > > submitted with HTML in it___ > > Dwayne Martin > Computing Support > James Madison University > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
