If you can connect from a desktop to the server via SQL -- and your ARS server is in a different location -- then Hardening is not the issue.. If you can connect from a desktop to the server via sql - But... the DB-Oracle is on the SAME server -- then it could be Hardening.
I would just ask the Unix/MS Admin if it was hardened... Recently -- Surely Change management is in place right? -- I know.. some places it is not. -- another thing to check.. just stop the ARS server and restart ./arsystem stop ./arsystem start -- I have seen this crash on startup before, with no apperent reason. -- You can also put in Debug mode in the ar.conf, and check the logs.. example:: Debug-mode: 131072 -- Then Check the logs -- ensure your logs are new names otherwise you will have to Sift alot. Hope that helps some... ;-) On 1/28/08, ZHANG, ERIC L <[EMAIL PROTECTED]> wrote: > > Thanks, Patrick! > > I checked on database and I don't see any problem. You brought up a good > question, hardening. Of cause they never tell anyone about hardening a > server until there is a problem. But in this case, for starter, how can > I link the problem to hardening? > > Thanks, > Eric > > On Mon, 28 Jan 2008 16:04:23 -0500, patrick zandi <[EMAIL PROTECTED]> > wrote: > > >Debug -- > >->can you sqlplus into the server from your desktop? > >-->Listener up, DB up. > >----> can you ping the DB server name. > >------> Did they Harden the server without telling you? > >--------> Oralce Tables full? > >TNSPing will help as well.. > > > >That is a starter for me. > > > > > >On 1/28/08, ZHANG, ERIC L <[EMAIL PROTECTED]> wrote: > >> > >> Hello, all! > >> > >> We have seen that arpluin dies every 90 seconds, which results in > other > >> processes to be terminated. armonitor keeps restarting all the > >> processes. I have looked at the logs (api, sql, filter, escalation, > and > >> > >> plugin) and don't have any clues what causes it. > >> > >> > >> ********************** > >> ARS 7.0.01 patch 6 > >> Solaris 9 > >> Oracle 10gR2 > >> ITSM 7.0.02 patch 3 > >> ********************** > >> > >> This is from armonitor.log: > >> > >> Mon Jan 28 09:39:54 2008 (ARNOTE 0) > >> Mon Jan 28 09:39:54 2008 AR Monitor version 7.0.01 Patch 006 > >> 200712062121 started. > >> Mon Jan 28 09:39:54 2008 (ARNOTE 0) > >> Mon Jan 28 09:39:54 2008 AR Monitor started. > >> Mon Jan 28 09:39:54 2008 (ARNOTE 0) > >> Mon Jan 28 09:39:54 2008 ARMonitor child process (pid:5845) > started. > >> ./arserverd > >> Mon Jan 28 09:45:24 2008 (ARNOTE 0) > >> Mon Jan 28 09:45:24 2008 Server indicates that it's up. > >> > >> Mon Jan 28 09:45:24 2008 (ARNOTE 0) > >> Mon Jan 28 09:45:24 2008 ARMonitor child process (pid:5865) > started. > >> ./arsvcdsp > >> Mon Jan 28 09:45:25 2008 (ARNOTE 0) > >> Mon Jan 28 09:45:25 2008 ARMonitor child process (pid:5866) > started. > >> ./arplugin > >> Mon Jan 28 09:45:25 2008 (ARNOTE 0) > >> Mon Jan 28 09:45:25 2008 ARMonitor child process (pid:5867) > started. > >> ./arcmdbd.sh > >> Mon Jan 28 09:45:25 2008 (ARNOTE 0) > >> Mon Jan 28 09:45:25 2008 ARMonitor child process (pid:5868) > started. > >> ./arrecond.sh > >> Mon Jan 28 09:46:56 2008 (ARNOTE 0) > >> Mon Jan 28 09:46:56 2008 ARMonitor child process (pid:5866) died > >> with > >> 0. > >> ./arplugin > >> Mon Jan 28 09:46:56 2008 (ARNOTE 0) > >> Mon Jan 28 09:46:56 2008 Current ARMonitor child process > (pid:5845). > >> ./arserverd > >> Mon Jan 28 09:46:56 2008 (ARNOTE 0) > >> Mon Jan 28 09:46:56 2008 Current ARMonitor child process > (pid:5865). > >> ./arsvcdsp > >> Mon Jan 28 09:46:56 2008 (ARNOTE 0) > >> Mon Jan 28 09:46:56 2008 Current ARMonitor child process > (pid:5867). > >> ./arcmdbd.sh > >> Mon Jan 28 09:46:56 2008 (ARNOTE 0) > >> Mon Jan 28 09:46:56 2008 Current ARMonitor child process > (pid:5868). > >> ./arrecond.sh > >> Mon Jan 28 09:46:56 2008 (ARNOTE 0) > >> Mon Jan 28 09:46:56 2008 ARMonitor child process (pid:5871) > started. > >> ./arplugin > >> Mon Jan 28 09:46:56 2008 (ARNOTE 0) > >> Mon Jan 28 09:46:56 2008 ARMonitor child process (pid:5868) died > >> with > >> 256. > >> ./arrecond.sh > >> Mon Jan 28 09:46:56 2008 (ARNOTE 0) > >> Mon Jan 28 09:46:56 2008 Current ARMonitor child process > (pid:5845). > >> ./arserverd > >> Mon Jan 28 09:46:56 2008 (ARNOTE 0) > >> Mon Jan 28 09:46:56 2008 Current ARMonitor child process > (pid:5865). > >> ./arsvcdsp > >> Mon Jan 28 09:46:56 2008 (ARNOTE 0) > >> Mon Jan 28 09:46:56 2008 Current ARMonitor child process > (pid:5871). > >> ./arplugin > >> Mon Jan 28 09:46:56 2008 (ARNOTE 0) > >> Mon Jan 28 09:46:56 2008 Current ARMonitor child process > (pid:5867). > >> ./arcmdbd.sh > >> Mon Jan 28 09:46:56 2008 (ARNOTE 0) > >> Mon Jan 28 09:46:56 2008 ARMonitor child process (pid:5872) > started. > >> ./arrecond.sh > >> Mon Jan 28 09:48:26 2008 (ARNOTE 0) > >> Mon Jan 28 09:48:26 2008 ARMonitor child process (pid:5871) died > >> with > >> 0. > >> ./arplugin > >> Mon Jan 28 09:48:26 2008 (ARNOTE 0) > >> Mon Jan 28 09:48:26 2008 Current ARMonitor child process > (pid:5845). > >> ./arserverd > >> Mon Jan 28 09:48:26 2008 (ARNOTE 0) > >> Mon Jan 28 09:48:26 2008 Current ARMonitor child process > (pid:5865). > >> ./arsvcdsp > >> Mon Jan 28 09:48:26 2008 (ARNOTE 0) > >> Mon Jan 28 09:48:26 2008 Current ARMonitor child process > (pid:5867). > >> ./arcmdbd.sh > >> Mon Jan 28 09:48:26 2008 (ARNOTE 0) > >> Mon Jan 28 09:48:26 2008 Current ARMonitor child process > (pid:5872). > >> ./arrecond.sh > >> Mon Jan 28 09:48:27 2008 (ARNOTE 0) > >> Mon Jan 28 09:48:27 2008 ARMonitor child process (pid:5877) > started. > >> ./arplugin > >> Mon Jan 28 09:48:27 2008 (ARNOTE 0) > >> Mon Jan 28 09:48:27 2008 ARMonitor child process (pid:5872) died > >> with > >> 256. > >> ./arrecond.sh > >> Mon Jan 28 09:48:27 2008 (ARNOTE 0) > >> Mon Jan 28 09:48:27 2008 Current ARMonitor child process > (pid:5845). > >> ./arserverd > >> Mon Jan 28 09:48:27 2008 (ARNOTE 0) > >> Mon Jan 28 09:48:27 2008 Current ARMonitor child process > (pid:5865). > >> ./arsvcdsp > >> Mon Jan 28 09:48:27 2008 (ARNOTE 0) > >> Mon Jan 28 09:48:27 2008 Current ARMonitor child process > (pid:5877). > >> ./arplugin > >> Mon Jan 28 09:48:27 2008 (ARNOTE 0) > >> Mon Jan 28 09:48:27 2008 Current ARMonitor child process > (pid:5867). > >> ./arcmdbd.sh > >> Mon Jan 28 09:48:27 2008 (ARNOTE 0) > >> Mon Jan 28 09:48:27 2008 ARMonitor child process (pid:5878) > started. > >> ./arrecond.sh > >> > >> > >> > ________________________________________________________________________ > ___ > ____ > >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > >> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > >> > > > > > > > >-- > >Patrick Zandi > > > >Dev Technology Group --> www.devtechnology.com > >Exceeding your Expectations ! > > > >_______________________________________________________________________ > ___ > _____ > >UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > >Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > -- Patrick Zandi Dev Technology Group --> www.devtechnology.com Exceeding your Expectations ! _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
