XI 3.0: Startup/Shutdown problem

Hi everybody.
In our scenario we have a JDBC Sender channel: we noticed that when the XI machine is stopped/restarted (without stopping the sender channel before)we have some error in the firsts polling cycles: that is, it seems that the Adapter is already running but the XI Engine is not ready to process the message, then the messages get an error.
My question is: it is possible to control the activation of the channel/adapter in order to:
- startup the channel only after the XI engine is fully operational
- schedule the closure/opening of the channel to allow the maintenance of the XI Box
Thanks in advance
Alessandro

Hi,
We can maintain the Adapter availability time in RWB.
Go to RWB>Communication channel monitoring>Avalability planning, where we can maintain the days and hours as per requirement.
Here we can give the availability timing for the channels, so that after our XI server starts up then channels will also start.
If this issue is resolved then kindly close the thread.
Regards,
Nutan
Edited by: nutan champia on Apr 16, 2010 10:57 AM

Similar Messages

A205 Startup/Shutdown Problems

I have a Toshiba A205 that is a few years old (out of warranty) that I'm having big problems with. It takes me several attempts to start it up. Sometimes it freezes on the Windows loading screen and sometimes it appears to start all the way to the desktop but is actually frozen and requires a hard shutdown. Often times, when I actually DO get it functioning, it'll freeze in the middle of what I'm doing and require a hard shutdown. If I ever put the computer to sleep, it'll guaranteed be frozen when I open the lid again to try to wake it up. It came with Vista but I did a complete hard drive format and installed Windows 7 Ultimate and that didn't fix anything. I did a memtest86 and all came back normal. Does anyone have any ideas? Thanks!
Solved!
Go to Solution.

I just had an a205-s4567 that would boot in safe mode and operate all day long, but would freeze at random times when booting into normal mode on Vista. After many hours of trying different drivers, etc. etc. etc. I noticed the processor speed switch in the bios, used to allow speed stepping or disable speed stepping. That setting can also be accessed from the Toshiba Hardware Utility. When set to "LOW" rather than speed stepping, the computer boots fine, and runs fine. I found this about 30 hours ago, and have been using the laptop and backing up the user's files via Carbonite since then without any repeat of the vexing problem.
This appears to be a driver problem in interfacing with the Intel processor, but could find no further information regarding this. I saw one post about an a205, where the user went from Vista to Win7 (no relief) to Win XP (worked, but finding drivers is a problem). My guess is that XP does not interface with stepping processors the same way, and that was what produced the cure.
You may want to see if safe mode operates normally, or just change the bios setting to non-stepping, and see if that works for you.

Automating Weblogic Startup/Shutdown on Linux

hello and hope you fine
im using weblogic 10.3 with oracle db 11g on CentoOS 5.5
everything is working fine
but my problem is that i want to startup/shutdown weblogic on system start/shutdown
i defined weblogic as service ( i tried all levels) and it works but the problem is
when the system is booting it start weblogic but it stops continue system boot!
i also tries put the start weblogic on the .bash_profile
the system boot but when im trying to login it stops because the same problem
(weblogic startup and prevent contitnue the loginin )
i also tried to add startWeblogic in /etc/rc.d/rc.local
and the same problem when weblogic start system cant continue booting
i also tried using nohup
also the same problem
so how can i start/shutdown weblogic ?
and thanks for help
Edited by: user13113692 on Aug 2, 2010 3:22 AM

thank you for your replay
but its the same
when server is booting
the weblogic start and goes to the running state
it stops continue the other services and
the server boot could not continue
here is some of my script
#!/bin/sh
WEBLOGIC_HOME=/root/Oracle/Middleware/user_projects/domains/mydomain/
# source function library
. /etc/rc.d/init.d/functions
case "$1" in
start)
echo "Starting weblogic..."
     cd $WEBLOGIC_HOME
     su root $WEBLOGIC_HOME/bin/startWebLogic.sh &
stop)
echo "Stopping weblogic..."
     cd $WEBLOGIC_HOME
     su root $WEBLOGIC_HOME/bin/stopWebLogic.sh &
i also tried something like this to grape all the output to a log file
but the problem here is that the weblogic give me a exception about the paths
case "$1" in
start)
echo "Starting weblogic..."
     cd $WEBLOGIC_HOME
     su root $WEBLOGIC_HOME/bin/startWebLogic.sh ALL > ${WEBLOGIC_HOME}/logz/start.log 2>&1 &
stop)
echo "Stopping weblogic..."
     cd $WEBLOGIC_HOME
     su root $WEBLOGIC_HOME/bin/stopWebLogic.sh ALL >${WEBLOGIC_HOME}/logz/stops.log 2>&1 &
i also tried this with the standalone weblogic and its the same
any help will be appreciated

ORACLE DATABASE의 AUTOMATIC STARTUP/SHUTDOWN

제품 : ORACLE SERVER
작성날짜 : 1995-11-21
오라클 database의 AUTOMATIC STARTUP/SHUTDOWN
============================================
시스템이 startup 하면서 오라클도 함께 startup하거나 시스템을 shutdown
할 때 오라클도 같이 shutdown 하는 것이 가능하다. 그 방법은 OS마다 차이가
있는데 여기서는 UNIX 에 기반한 여러 플랫폼에 대해서 알아보기로 한다.
본 내용에서 가장 많이 사용되는 화일은 다음과 같다.
$ORACLE_HOME/bin/dbstart
$ORACLE_HOME/bin/dbshut
/etc/oratab 또는 /var/opt/oracle/oratab
dbstart 와 dbshut 은 오라클을 startup/shutdown 시키는 스크립트인데
이것은 automatic startup/shutdown 시에만 사용하도록 하고 평상 시의
경우에는 사용하지 않도록 한다.
oratab 화일은 일반 텍스트 화일로서 시스템에 설치된 오라클 인스턴스에
대한 정보를 가지고 있는데 보통 3개의 필드로 이루어져 있으며 첫번재
필드는 ORACLE_SID, 두번째 필드는 ORACLE_HOME, 세번째 필드는 Y 또는 N
으로 구성되어 있다. 해당 인스턴스를 autostartup 시키려면 꼭 Y로
세팅되어 있어야 한다.
SYSTEM V
System V 에 기반한 시스템은 /etc/rc<n>.d 디렉토리에 초기화 스크립트를
가지고 있다. 여기서 <n> 은 해당 스크립트의 run-level 을 의미한다.
일반적으로 run-level 0은 power shutdown mode 이고 run-level 2는 multi-user
mode 이다. 각각의 디렉토리에 들어있는 초기화 스크립트는 다음과 같은 형태의
이름을 갖고 있다.
K{two-digit number][descriptive filename]
예를 들면 S75cron, K30tcp 등이 있을 수 있다.
S로 시작되는 스크립트는 startup 시에 실행되는 것이고 K 로 시작하는 것은
shutdown 시에 실행된다.
two-digit number가 의미하는 것은 스크립트가 실행되는 순서인데 숫자가 작은
것부터 먼저 실행된다. 따라서 오라클 스크립트는 보통 다음과 같은 이름을 갖게 된다.
S99oracle, K01oracle
이와 같이 설정하면 시스템이 startup 될 때 모든 초기화가 끝난 후 마지막으로
오라클이 startup 되며 시스템을 shutdown 할 때에는 오라클을 가장 먼저 shutdown
하게 된다.
BSD UNIX
BSD 에 기반한 시스템은 시스템이 startup 될 때 초기화 화일로
/etc/rc*(예를 들면, /etc/rc, /etc/rc.local) 를 사용한다.
시스템을 shutdown 할 때에는 보통은 /etc/shutdown 만 실행하게 되므로
특별히 실행되는 스크립트가 없지만 /etc/rc.shutdown 이 실행되는
플랫폼도 있다.
이제 각 플랫폼별로 자세히 알아보기로 한다.
주의 : <oracle_owner> 는 oracle owner id 로 대체
<$ORACLE_HOME> 은 oracle home directory 명으로 대체
(1)SunOS 4.1.3
SunOS 4.1.3 에서는 /etc/rc.local 을 startup 스크립트로 사용한다. 즉
시스템이 startup 되면서 /etc/rc.local 이 실행된다. 따라서 이 화일의 끝에
다음과 같은 라인을 추가하면 된다.
su <oracle_owner> -c <$ORACLE_HOME>/bin/dbstart
예를 들어 oracle owner 가 oracle7 이고 $ORACLE_HOME 이 /home/oracle
이라면 다음과 같이 해주면 된다.
su oracle7 -c /home/oracle/bin/dbstart
여기서 /home/oracle 대신에 $ORACLE_HOME 과 같은 환경변수를 이용하여
세팅하면 안된다.
SunOS 에서는 시스템이 shutdown 될 때 실행되는 스크립트는 따로 없다.
따라서 dbshut 을 실행시키는 방법은 다음과 같은 스크립트를 만들어서
시스템을 shutdown 시킬 때 /etc/shutdown 을 실행시키지 말고 대신
이것을 실행시켜야 한다.
#!/bin/csh
su <oracle_owner> -c <$ORACLE_HOME>/bin/dbshut
/etc/shutdown $*
만약 오라클을 shutdown 하지 않고 시스템을 shutdown 하면 다음에
오라클을 startup 하려고 할 때 startup이 되지 않는다. 이 경우에는
$ORACLE_HOME/dbs/sgadef<SID>.dbf 화일을 지우고 startup 시키면 된다.
(2)OSF/1(DIGITAL UNIX)
/etc/inittab : 초기화 과정을 콘트롤
/sbin/rc3 : run-level 3 에서 사용되는 script
/sbin/rc0 : run-level 0 에서 사용되는 script
/sbin/rc3.d/S99oracle : /sbin/init.d/oracle 로 link
/sbin/rc0.d/K01oracle : /sbin/init.d/oracle 로 link
/etc/initab 화일에는 초기화 과정에 대한 정보가 들어 있다.
예를 들면 다음과 같다.
s3:3:wait:/sbin/rc3 < /dev/console > /dev/console 2>&1
이렇게 설정하면 run-level 3 일 경우 /sbin/rc3 스크립트가 실행된다.
/sbin/rc3 은 /sbin/rc3.d 디렉토리에 들어있는 스크립트를 실행한다. 만약
스크립트 이름이 K 로 시작하면 이것은 stop 파라미터를 갖고 실행되어서 이
스크립트에 지정된 프로세스를 정지시킨다. 한편, 스크립트가 S 로 시작하면
/sbin/rc3 는 이 스크립트에 startup 파라미터를 부여하고 여기서 지정된
프로세스를 실행시킨다. 따라서 /sbin/rc3.d/S99oracle 을 사용하여
dbstart를 실행한다.
shutdown 과정도 거의 비슷하다. /etc/inittab 에 다음과 같은 라인을 추가
한다.
s0:0:wait:/sbin/rc0 off < /dev/console > /dev/console 2>&1
이것은 /sbin/rc0 를 실행시키는데 /sbin/rc0 는 /sbin/rc0.d 디렉토리에
들어있는 스크립트를 실행시킨다. 스크립트의 이름이 S 로 시작하면 run
time parameter 로 start 를 사용하게 되고 K 로 시작하면 stop 을
사용한다.
따라서 /sbin/rc0.d/K01oracle 스크립트는 stop 파라미터를 갖고
실행되며 이 스크립트는 $ORACLE_HOME/bin/dbshut 스크립트를 실행시켜서
오라클을 shutdown 시킨다.
/sbin/rc3.d/S99oracle과 /sbin/rc0.d/K01oracle은 모두 /sbin/init.d/oracle
에 대한 symbolic link 이다. /sbin/init.d/oracle 에 대한 symbolic link 는
이들 외에 더 있을 수 있다.
(3)Solaris 2.3 & SCO UNIX
/etc/inittab : 초기화 과정을 콘트롤
/etc/rc2 : run-level 2 에서 사용되는 스크립트
/etc/rc0 : run-level 0 에서 사용되는 스크립트
/etc/rc2.d/S99dbstart : /etc/init.d/dbstart 에 대한 link
/etc/rc0.d/K01dbshut : /etc/init.d/dbshut 에 대한 link
/var/opt/oracle/oratab
Solaris 의 경우는 OSF/1 과 매우 유사하다. 차이점이라고 한다면 /sbin
디렉토리 대신에 /etc 디렉토리에 필요한 스크립트가 들어있다는 것이다.
rc0.d, rc2.d 같은 디렉토리는 실제로 /etc 디렉토리에 위치하고 있으며
rc0, rc2 와 같은 스크립트는 /etc/init.d 에 존재하는 같은 이름의 스크립트에
대한 symbolic link이다.
/etc/init.d/dbstart 와 /etc/init.d/dbshut 스크립트의 내용은 각각 다음과
같이 한줄로 구성되어 있다.
su - <oracle_owner> -c <$ORACLE_HOME>/bin/dbstart
su - <oracle_owner> -c <$ORACLE_HOME>/bin/dbshut
Solaris 에서는 start, stop 같은 파라미터는 /etc/init.d/dbstart,
/etc/init.d/dbshut 에서는 무시된다.
/etc/init.d/dbstart, /etc/init.d/dbshut 화일은 owner가 oracle owner id
이여야 한다.
/etc/init.d/README 를 읽어보면 좀 더 자세한 내용이 설명되어 있으니 참조하기
바란다.
(4)AIX
/etc/inittab : 시스템 초기화 화일
/etc/rc : 시스템 초기화 스크립트
/etc/mkitab : /etc/inittab 을 수정하는 유틸리티
/etc/shutdown : 시스템 shutdown 스크립트
AIX 에서는 오라클 autostartup 방법은 여러가지가 가능하지만 shutdown 은
한가지만 가능하다. 우선 autostartup 은 다음과 같은 방법 가운데 하나를
사용하면 된다.
a)/etc/mkitab 를 사용하여 /etc/inittab 에 entry 를 추가한다. 즉,
/etc/mkitab "<oracle_owner>:2:wait:/bin/su <oracle_owner> -c
<$ORACLE_HOME>/bin/dbstart > /dev/console 2>&1"
이렇게 하면 /etc/inittab 화일에 dbstart 기능이 추가된다. 이렇게 하면
시스템이 뜨면서 run-level 2일 경우 오라클이 자동으로 startup 된다.
b)다음과 같은 방법도 가능하다.
/etc/mkitab "rcoracle:2:wait:/etc/rc.oracle > /dev/console 2>&1"
그리고, root 소유의 /etc/rc.oracle 스크립트를 다음과 같이 작성한다.
su <oracle_owner> <<EOF
<$ORACLE_HOME>/bin/dbstart
EOF
c)/etc/rc 스크립트의 마지막에 다음을 추가한다.
/bin/su <oracle_owner> - c <$ORACLE_HOME>/bin/dbstart
AIX 에서 시스템 shutdown 은 /etc/shutdown 에 의한다. 시스템을 내릴 때
오라클을 shutdown 하려면 별도의 시스템 shutdown 스크립트(root 소유로)를
다음과 같이 만들어서 /etc/shutdown 을 사용하지 말고 이것을 사용해야 한다.
#!/bin/sh
/bin/su <oracle_owner> -c <$ORACLE_HOME>/bin/dbshut
/etc/shutdown $*
(5)HP/UX
/etc/rc : 시스템 startup 화일
/etc/shutdown : 시스템 shutdown 실행 화일
/etc/shutdown.d : 시스템 shutdown 디렉토리
HP/UX 에서는 시스템 startup 시에 /etc/rc 가 실행된다. 따라서 다음 라인을
/etc/rc 스크립트의 마지막에 추가하면 auto startup 이 가능해진다.
su <oracle_owner> -c <$ORACLE_HOME>/bin/dbstart
시스템의 shutdown 은 /etc/shutdown 화일을 실행하여 수행된다. 이 프로그램은
/etc/shutdown.d 디렉토리에 들어있는 스크립트를 실행시키는데 다음과 같은
세 가지 방법 가운데 하나로 auto shutdown 을 세팅할 수 있다.
a)$ORACLE_HOME/bin/dbshut 화일을 /etc/shutdown.d 디렉토리 아래에 copy
b)/etc/shutdown.d/dbshut 을 $ORACLE_HOME/bin/dbshut 으로 symbolic link 지정
c)다음과 같은 스크립트 작성
#!/bin/sh
su <oracle_owner> -c <$ORACLE_HOME>/bin/dbshut
단,이 스크립트는 root의 소유이고 root에 의해서만 실행 가능해야 한다.
만약 V6 와 V7 을 동시에 사용하는 경우라면 V7 에서 제공하는 dbshut을
사용하도록 한다.

Dear Alexdelarg,
First launch the "Services" applet from the Windows NT Control Panel. Double-click on the "OracleService<SID>" service and verify that "Startup Type" is set to "Automatic", "Log On As" is set to "System Account", and that the "Allow Service to Interact with Desktop" check box is disabled.
Then launch REGEDIT and check that the Value String ORA_<SID>AUTOSTART within the key My Computer\HKEYLOCAL_MACHINE\SOFTWARE\ORACLE is set to "TRUE".
If the above does not rectify your startup problem, try issuing the following command from the Command Prompt:
<ORACLE_HOME>\bin\oradim -edit -sid <SID> -startmode auto
where <ORACLE_HOME> is the full path of your Oracle8i Server software and <SID> is the Service Identifier of your database.
Hope this helps!

Oracle Startup/Shutdown with SQLPLUS and ORADIM in Windows...

I am a newbie to the Windows platform. SQLPLUS will not allow me to issue a STARTUP command. This is what I get when I attempt to SHUTDOWN IMMEDIATE and subsequently issue a STARTUP MOUNT/NOMOUNT or any STARTUP command for that matter. The SHUTDOWN command works successfully but the subsequent startup fails with an ORA-12514: TNS:listener does not currently know of service requested in connect descriptor message.
D:\>set ORACLE_SID=NMPC00
D:\>set ORACLE_HOSTNAME=TAX-DEV-ORA-01
D:\>set ORACLE_HOME=D:\app\oracle\product\11.2.0\dbhome_1
D:\>sqlplus sys@NMPC00 as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Sat Oct 23 11:41:56 2010
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
SQL>
When I look at the Windows service, it still reports 'Started' despite the fact that I shutdown the instance. What is the proper protocol for shutting down and starting up an Oracle instance in Windows. Do I have to coordinate these activities with the ORADIM -STARTUP / -SHUTDOWN commands?

I am also newbie to oracle and running into the similar problem when trying to start oracle database using windows command prompt and getting the below error:
Command prompt is being run as administrator on windows7 O/S
C:\ORACLE\product\11.2.0\dbhome_1\BIN>oradim -SHUTDOWN -SID O22BVGI -SHUTTYPE srvc,inst -SHUTMODE nornal
ORA-01031: insufficient privileges
The reason behind this to do it is , I need a batch script for stopping and restarting the oracle database instance using a Pfile which will contain the initialization parameters.
Please can someone help!
sqlnet.ora is:
SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOSTNAME)
Kind Regards
Sam
Edited by: 808116 on Nov 7, 2010 4:21 PM

Oracle Startup/Shutdown

Having trouble with EM in a windows server environment running 10G
When i startup/shutdown my server do i need to stop the listener, dbconsole and agent?
Everytime i reboot my TEST server EM stops working. I have checked the windows services start ok - all do with no errors. but i get the listeneer starting sometimes and sometime not. The agent and DB instance connection instances show failed on the http://myserver:1158/em page.
I have checked tnsnames and listener.ora.
Is there a process of things to start/stop when rebooting my server?
Also whe i try to start them manually a page is displayed saying enter logon credential but the credentials i enter .e.g. sys-password123 are not accepted. Does anyone have any idea what the credential i should be inputting here is it oracle-oralce or something?
Please note i have done loads of reading but can't find a solution to my problem thanks to all who take time to read/reply to what may seem a very basic question

By default the Oracle services are set to automatically start. When you reboot your server the services start and you should be able to connect. However if you try to connect right after the reboot, most probably this error will show up since the Enterprise Manager requires the database to be already registered against the listener, which may take a while (not more than 60 sec),
Verify this checklist:
1. The listener is up and running. LSNRCTL STATUS
2. The database is registered against the listener. You may issue the command LSNRCTL SERVICES.
3. You may force the database to be registered against the listener by issuing the ALTER SYSTEM REGISTER; command from a sqlplus prompt.
One more things you should take care of is the IP assignment method, if you have a dynamic IP address assignment you should configure a loopback adapter and and have the Loopback Adapter's IP address registered at the hosts file along with the hostname. If you fail to do so you may find EM will be requesting you for the logon credentials when you attempt to access the Performance tab or any other administrative task.
You may read this reference for further Enterprise Manager troubleshooting --> Enterprise Manager DB Control Console.
~ Madrid

Oracle 8i Automatic Startup/shutdown on NT

After installing Oracle 8.1.6 on Win NT/2000 and creating a database a new service is created too (OracleServiceSID). My problem is that this new service (which works like oradim starting srvc,inst) does not startup the db when rebooting the machine. I need always manual startup/shutdown with a script that uses svrmgrl while in Oracle guides it seems that would be enough to start the service. Every parameter in the registry is set according to these guides to permit automatic startup/shutdown but only the service, not the db, starts and stops automatically. Where is my error?
Thanks
Alex
null

Dear Alexdelarg,
First launch the "Services" applet from the Windows NT Control Panel. Double-click on the "OracleService<SID>" service and verify that "Startup Type" is set to "Automatic", "Log On As" is set to "System Account", and that the "Allow Service to Interact with Desktop" check box is disabled.
Then launch REGEDIT and check that the Value String ORA_<SID>AUTOSTART within the key My Computer\HKEYLOCAL_MACHINE\SOFTWARE\ORACLE is set to "TRUE".
If the above does not rectify your startup problem, try issuing the following command from the Command Prompt:
<ORACLE_HOME>\bin\oradim -edit -sid <SID> -startmode auto
where <ORACLE_HOME> is the full path of your Oracle8i Server software and <SID> is the Service Identifier of your database.
Hope this helps!

Startsap & stopsap on Linux startup & shutdown

Hy everyone!
I have a simple question: does anyone use startsap/stopsap scripts on Linux startup/shutdown run levels? I mean, when Linux starts up (init 5 run level) it must start SAP using startsap and stopsap on init 0 as well.
It seems to be no problem at all to do that but once that is not set up by default on Linux systems (not in mine for sure) I have decided to ask for a second opinion.
Thanx in advance for any help.
Paulo

Eric,
my goal is a little bit different that that: I'm looking for a way to quick shutdown or startup SAP system with the mininum possible effort during an emergency situation.
Let me explain the situation: we are constantly affected by power down issues, especially in summer time. When such situations occur, we have to quickly shut down as many servers as possible before the power turns completely off (by nobreak).
We are currently working on power infrastructure to avoid those "downs" issues, but until we have fully reached that, we need to get some safe systems shutdowns (at least for production servers).
So I was considering to include at least the stopsap script in init 0 run level on Linux.
What do you think about that?
Thanx for your help until now. It's good to have someone to discuss something like that and exchange experiences/ideas.
Paulo

Oracle Automatic Startup & Shutdown

My automatic Database startup/Shutdown script won't work while system reboot. I have Oracle 8.1.7/Sun solaris. When I ran the script by hand it works fine both for startup and shutdown but not while system reboot. I am putting the script in the proper run levels rc0.d and rc3.d.
even /etc/rc0.d/K01oracle and /etc/rc3.d/S90oracle is working fine.
Could someone please tell me what am i missing.
Appreciate your help
-Jay

Hi,
Have you settled your issue? I would think the problem was caused by the environment under which the script was run. Normally the rc scripts are run as root and the PATH will not be set to run Oracle executables. So inside the script if you run the startup script as the user who has execute permission to the Oracle executables and whose path is SET in .profile then it should work.

Tomcat remote startup/shutdown, remote console ???

Hi,
1. I have installed Tomcat in a remote server and I wonder if there is a predefined way to start the server up and shut it down remotely, or if I would have write it myself. Any ideas about writing it?
2. Is there a way I can see the Tomcat console remotely? I was thinking about creating a jsp page that can display that info for me (securely of course), but my problem is, how do I get that info?
3. By default a jsp page is accessed with the port number in the URL (http://host.domain:8800/index.jsp). Is there a way not to include the port number(http://host.domain/index.jsp)??
Thanks in advance....
Rafael

Hi carebearfren,
Thanks for your answer, but I'm afraid I might have not been clear. Tomcat is running in a server somewhere in the Internet and at the present I have no control over it, I can't even see the console to check out messages, warnings, etc (unless I'm infront of the server); however, I would like to be able to startup/shutdown Tomcat, and also to see the messages in the console from my PCs at home and work.
I have no idea how to see the messages in the console from my PCs, but I have some ideas about starting up and shutting down Tomcat. I was thinking about creating a small java program in the server that can execute the startup and shutdown scripts. I would control the java program remotely via RMI or JSP, but I don't know which one would be the best solution or if there is any predefined way to do it within Tomcat. I wouldn't like to reinvent the wheel.
Thanks,
Rafael

50 second startup, shutdown, internet connection etc. No new apps added in recent past

Problem: 50 second plus startup, shutdown, slow internet connections regardless of networks. have not added new apps recently. Tried removing startup items, holding down the left shift, option and control and the power button for 10 seconds, running disk utility, reducing number of files, nothing helped.
Am running 10.9.5 on a Macbook Pro, mid 2010. (see all specifics below)
EtreCheck version: 2.1.8 (121)
Report generated February 4, 2015 at 1:40:11 PM EST
Download EtreCheck from http://etresoft.com/etrecheck
Click the [Click for support] links for help with non-Apple products.
Click the [Click for details] links for more information about that line.
Hardware Information: ℹ️
    MacBook Pro (15-inch, Mid 2010) (Technical Specifications)
    MacBook Pro - model: MacBookPro6,2
    1 2.4 GHz Intel Core i5 CPU: 2-core
    8 GB RAM Upgradeable
        BANK 0/DIMM0
            4 GB DDR3 1067 MHz ok
        BANK 1/DIMM0
            4 GB DDR3 1067 MHz ok
    Bluetooth: Old - Handoff/Airdrop2 not supported
    Wireless: en1: 802.11 a/b/g/n
    Battery Health: Normal - Cycle count 244
Video Information: ℹ️
    Intel HD Graphics - VRAM: 288 MB
        Color LCD 1440 x 900
    NVIDIA GeForce GT 330M - VRAM: 256 MB
System Software: ℹ️
    OS X 10.9.5 (13F34) - Time since boot: 1:21:21
Disk Information: ℹ️
    Hitachi HTS545032B9SA02 disk0 : (320.07 GB)
        EFI (disk0s1) <not mounted> : 210 MB
        Macintosh HD (disk0s2) / : 319.21 GB (248.71 GB free)
        Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
    HL-DT-ST DVDRW GS23N
USB Information: ℹ️
    Apple Internal Memory Card Reader
    Apple Inc. BRCM2070 Hub
        Apple Inc. Bluetooth USB Host Controller
    Apple Inc. Apple Internal Keyboard / Trackpad
    Logitech USB Receiver
    Apple Inc. Built-in iSight
    Apple Computer, Inc. IR Receiver
Gatekeeper: ℹ️
    Mac App Store and identified developers
Kernel Extensions: ℹ️
        /System/Library/Extensions
    [not loaded]    com.wacom.kext.wacomtablet (6.3.7 - SDK 10.8) [Click for support]
Launch Agents: ℹ️
    [not loaded]    com.adobe.AAM.Updater-1.0.plist [Click for support]
    [running]    com.canon.MFManager.plist [Click for support]
    [running]    com.wacom.wacomtablet.plist [Click for support]
Launch Daemons: ℹ️
    [loaded]    com.adobe.fpsaud.plist [Click for support]
    [loaded]    com.adobe.SwitchBoard.plist [Click for support]
User Launch Agents: ℹ️
    [loaded]    com.adobe.AAM.Updater-1.0.plist [Click for support]
    [loaded]    com.adobe.ARM.[...].plist [Click for support]
    [loaded]    com.adobe.ARM.[...].plist [Click for support]
    [loaded]    com.google.keystone.agent.plist [Click for support]
User Login Items: ℹ️
    AirPort Base Station Agent    Application (/System/Library/CoreServices/AirPort Base Station Agent.app)
    WDSecurityHelper    Application (/Applications/WD Security.app/Contents/WDSecurityHelper.app)
Internet Plug-ins: ℹ️
    WacomNetscape: Version: 2.1.0-1 - SDK 10.8 [Click for support]
    Default Browser: Version: 537 - SDK 10.9
    WacomTabletPlugin: Version: WacomTabletPlugin 2.1.0.2 [Click for support]
    AdobePDFViewerNPAPI: Version: 11.0.10 - SDK 10.6 [Click for support]
    FlashPlayer-10.6: Version: 16.0.0.296 - SDK 10.6 [Click for support]
    Silverlight: Version: 5.1.20513.0 - SDK 10.6 [Click for support]
    Flash Player: Version: 16.0.0.296 - SDK 10.6 [Click for support]
    QuickTime Plugin: Version: 7.7.3
    iPhotoPhotocast: Version: 7.0 - SDK 10.7
    AdobePDFViewer: Version: 11.0.10 - SDK 10.6 [Click for support]
    CANONiMAGEGATEWAYDL: Version: 3.2.0.1 - SDK 10.6 [Click for support]
    GarminGpsControl: Version: 4.0.3.0 Release - SDK 10.6 [Click for support]
    JavaAppletPlugin: Version: 14.9.0 - SDK 10.7 Check version
User internet Plug-ins: ℹ️
    Move-Media-Player: Version: npmnqmp 071101000050 [Click for support]
3rd Party Preference Panes: ℹ️
    Flash Player [Click for support]
    WacomTablet [Click for support]
Time Machine: ℹ️
    Mobile backups: OFF
    Auto backup: NO - Auto backup turned off
    Volumes being backed up:
        Macintosh HD: Disk size: 319.21 GB Disk used: 70.50 GB
    Destinations:
        External HD [Local]
        Total size: 999.83 GB
        Total number of backups: 3
        Oldest backup: 2014-06-10 23:05:50 +0000
        Last backup: 2015-01-05 17:41:37 +0000
        Size of backup disk: Excellent
            Backup size 999.83 GB > (Disk size 319.21 GB X 3)
Top Processes by CPU: ℹ️
         6%    WindowServer
         3%    systemstatsd
         0%    fontd
         0%    AppleSpell
         0%    configd
Top Processes by Memory: ℹ️
    344 MB    com.apple.WebKit.WebContent
    172 MB    com.apple.IconServicesAgent
    146 MB    softwareupdated
    103 MB    mds_stores
    77 MB    systemstats
Virtual Memory Information: ℹ️
    4.78 GB    Free RAM
    2.16 GB    Active RAM
    616 MB    Inactive RAM
    1.04 GB    Wired RAM
    434 MB    Page-ins
    0 B    Page-outs
Diagnostics Information: ℹ️
    Feb 4, 2015, 12:17:24 PM    Self test - passed

Hello m4294SA,
Welcome to the Apple Support Communities!
I understand that your computer running Mavericks is running slower than expected. I also realize that you have completed a lot of good troubleshooting already. I would further suggest reading over and completing the steps in the attached article that you have not yet completed.
OS X Mavericks: If your Mac runs slowly
Have a great day,
Joe

HOWTO: Startup/Shutdown Sounds in Openbox

In this tutorial, I will show you how to add startup and shutdown sounds with Openbox, a light-weight window manager. In theory, this should work with any window manager that uses a startup script (or, if you use the startx command, .xinitrc could be used for the same effect); however, I will be focusing on Openbox, so you will have to adapt these instructions for use with other window managers.
We'll start with a quick background story: I was in a "tweaking" mood a few days ago, and I figured I'd try to set up some startup and shutdown noises for use with Openbox. After a few minutes of messing around, I got it working. I searched to see if there were any tutorials like this, and since there weren't, I figured I would share my knowledge--that's what tutorials are for, right?
NOTE: I originally posted this on ubuntuforums.org; therefore, there may be some differences (I tried to fix most of them). Even though I did this on Arch originally, I wrote it targeted toward Ubuntu users. I didn't get much of a response--there must not have been too many Ubuntu/Openbox users looking for that. Please point out any inconsistencies, and I'll fix them as soon as possible.
Now that we have that out of the way, let's get started.
Step 1: Installing the necessary application(s).
First off, we will be using a commandline program called play. It is part of the sox package, so let's install that first (you likely have most of its dependancies already).
# pacman -S sox
If you'd like, you can cd to a directory with music in it and type play name-of-sound-file.extension to test that it is working. If you don't have any files to try it on, you can do this later after downloading your desired sound files in step 3.
I also have sudo set up; you will need to set this up to run the shutdown commands from a script as I have them. There is a section in the ArchWiki that will help in setting it up if you want. As for the commands with sudo in them, you can just run them in a root terminal.
In addition to that, I will be working with obmenu, a program for editing Openbox's menu from a GUI; however, it will work just as well to edit the menu by hand. I assume you already have a preferred method of editing your menu, but if you want to try obmenu, it's only a pacman command away:
# pacman -S obmenu
Step 2: Setting up shutdown privileges.
For this section, I will be adapting a section from a great guide written by urukrama here. We're going to be running a shutdown command from a script, so we need to have it set up to work without any interaction--in this case, that means removing the need for a password for the shutdown command.
To do this, type in the following command into the terminal:
sudo visudo
This will open up the sudoers file, which is used to specifiy user permissions for actions that require root priveleges. For those of you unfamiliar with Vim (I'm with you ), just press i on your keyboard to enter interactive mode, which allows you to edit the file. Then, enter the following line at the end of the file:
%wheel ALL=NOPASSWD:/sbin/shutdown
Then press escape to exit interactive mode. Lastly, type in :wq followed by pressing enter to save and exit. Now you can use the sudo shutdown command without entering a password.
Step 3: Getting the desired sound files.
Now we come to the fun part of the guide--finding the sounds that we want.
There are plenty of startup and shutdown noises floating around the web; I went to gnome- and kde-look to check out theirs (the same are available at both sites). Here's a link to the System Sounds section at gnome-look. You can look through and download the ones that interest you; once you have listened to a few and found one that you like, go on. Just for reference, I chose the Dream pack. It fits very nicely with my current setup and theme.
Step 4: Setting up the shutdown/startup scripts.
If you haven't already (in the last step), extract the sound files from the package that they downloaded in. Then, look through the files and find the startup and shutdown noises. For me, they were titled Dream Intro.ogg and shutdown.ogg, respectively. Move these files into their own folder. I chose ~/.startup--on my Arch install, it was empty. You may want to put it into a different folder/sub-folder, preferably somewhere in your home folder. You can now remove all the other sound files--hypothetically speaking, it probably wouldn't be too hard to get other sounds (such as minimize, maximize, etc., if provided in the sounds package you chose) working with Openbox, but that is beyond the scope of this tutorial. Now, go to the folder in which you placed the startup and shutdown noises. For simplicity's sake, we're going to place the scripts in this same folder.
We're going to be making two scripts here--one for reboot and one for shutdown. Open up your text editor of choice here and enter the following line (replacing the "/path/to/file.extension" with the path to your shutdown sound):
play /path/to/file.extension && sudo shutdown -r now
For me, it looked like this:
play ~/.startup/shutdown.ogg && sudo shutdown -r now
What this does is play the sound file specified and, once that is done, moves on to the reboot process (that's what && does). Save this as reboot.sh. Now make a new file, this time for the actual shutdown. It will be the same as the first except the shutdown command will now be sudo shutdown -h now. Here's what mine looks like:
play ~/.startup/shutdown.ogg && sudo shutdown -h now
Save that one as shutdown.sh. At this point, we have completed the scripts for both shutdown commands. Next, open up your Openbox autostart script (should be in /home/<user>/.config/openbox/autostart.sh, where <user> is your username) with the text editor of your choice. You probably already have a few different things in here; if not, it doesn't really matter. Just add the following line to your autostart file (as you can see, I used quotes around this one because this file had a space in its name--you'll want to do the same. You can also use a backslash before the space):
play "/home/<user>/.startup/Dream Intro.ogg"&
Make sure you keep the ampersand (&) in tact; otherwise, the script will wait until the sound is done playing before completing the rest of the processes. I recommend that you place the sound file at the beginning of the script so that it starts first--the way I have it set up, everything is ready to go by the time the login sound ends (sooner, actually). Now that we've come this far, we're almost done.
Step 5: Adding the shutdown options to the Openbox menu.
At this point, the login sound will be working; however, we still need to set up the shutdown sounds. To do this, we will add a section to the Openbox menu that runs the two scripts we made in the last step.
Either open up obmenu or use your preferred text editor and open up menu.xml (should be in ~/.config/openbox/menu.xml). As I said, we will be adding two items: one for rebooting and another for shutting down. In obmenu, you can add a new submenu wherever you want (I chose the bottom of the menu) and name it Power (or whatever else you'd like). The first we'll add is named Restart. For the execute line, add the following:
bash /path/to/reboot.sh
For me, this path is ~/.startup/reboot.sh. As for the second, name it Shut Down and for the execute command put the following:
bash /path/to/shutdown.sh
Again, for me this is ~/.startup/shutdown.sh. Here is what the section in my obmenu looks like:
As for the pure XML, here it is (I replaced my name with <user> ):
<item label="Restart">
<action name="Execute">
<execute>bash /home/<user>/.startup/reboot.sh</execute>
</action>
</item>
<item label="Shut Down">
<action name="Execute">
<execute>bash /home/<user>/.startup/shutdown.sh</execute>
</action>
</item>
With obmenu, just save it, and your menu will be refreshed. When hand-editing the menu.xml file, you have to remember to Reconfigure Openbox (it will be in your menu unless you've removed it).
And with that, you should have working startup and shutdown sounds. You can test it by right clicking on your desktop and selecting one of your new shutdown options. You should have a sound play followed by the normal shutdown routine. Then when your computer starts back up, you will have a pleasant noise after logging on.
I hope that helped you! Please point out any errors that you see, and I'll correct them as soon as possible.

Nice tutorial. I was wondering, I noticed you have a games tab. Do you know how to properly execute games. I am trying to get steam games working also Call of duty 4 as tabs under obmenu. Could you help me out?
Thanks!

How im suppose to fix the auto shutdown problem in my iphone 3gs after updating to ios 5.1.1 this problem has made me a mobile ****** in my house and an loser in thing care so if any solution to this problem let me know

how im suppose to fix the auto shutdown problem in my iphone 3gs after updating to ios 5.1.1 this problem has made me a mobile ****** in my house and an loser in thing care so if any solution to this problem let me know

What "auto shutdown problem" are you talking about?

Random shutdown problem on G5 dual 2.3 GHz w/OS 10.4.7

Hello,
I’m using a dual 2.3 GHz G5, and it’s been working flawlessly since I bought it about a year ago. Until yesterday, I was running OS 10.4.5. Yesterday I upgraded to 10.4.7, and as soon as I booted up after the install, I started having a maddening problem with my computer randomly shutting down. (Not sleeping, but a complete power down.)
At first, the shutdown would happen immediately after powering up; my computer wouldn’t even make it to the blue progress bar. I zapped the PRAM and tried something I found online about unplugging the computer for 15 seconds, then plugging it back in. It now boots up, and I can log in, but the computer still shuts down randomly.
There seems to be no pattern to the shutdowns. I tried taxing the processor by opening and resampling huge Photoshop files while lots of other apps were open, and things were fine. Then it would conk out while I was composing an email.
I’ve heard of this random shutdown problem affecting Macbooks, but I have yet to find anything about G5 towers and OS 10.4.7. Does anyone have any info/advice?
Many thanks.
G5 dual 2.3 GHz Mac OS X (10.4.7) 2.5 GB RAM, 250 GB HD
G5 dual 2.3 GHz Mac OS X (10.4.7) 2.5 GB RAM, 250 GB HD

Thanks for the advice. I did check the system.log in Console and found the following altert:
PMU FORCED SHUTDOWN, CAUSE = -122
Now, since my computer is just over a year old, and since this problem happened immediately after applying the 10.4.7 OS update, I found it hard to believe that my hardware could be responsible. After 2 days of troubleshooting, I was stumped; after a 2-hour service call, so was Apple tech support. I ended up doing an archive and install back down to 10.4.5, and all is well.
I tested this issue on other machines running 10.4.7 and had no problems. It seems that the following specific combination of elements triggered the problem:
• PowerMac G5 dual 2.3 GHz (dual 1.8 machines did not exhibit the same problem)
• OS 10.4.7
• Logging in with Open Directory/Active Directory mobile profiles
• iTunes 7
Bottom line: if you’re using a dual 2.3 GHz PowerMac with mobile OD/AD profiles, do not update to 10.4.7, and steer clear of iTunes 7, at least until there is a patch update available.
(And Apple wants to be taken seriously in the enterprise market?)
G5 dual 2.3 GHz Mac OS X (10.4.7) 2.5 GB RAM, 250 GB HD

Clock problem and shutdown problem! Are they related?

Having a problem with my Dual 2 GHz Power Mac G5
A few days ago I noticed that my clock was not showing in the menu bar in the upper right corner of my desktop.
I went into System Preferences and went to Date & Time. Under the clock tab “Show Date and Time in Menu Bar” the box was not checked off. I checked it off and went to the “Date and Time” tab. The date and time was correct. I then checked the box “Click the lock to prevent further changes” to lock it. The date and time did not show up in the menu bar. I then went back to the tab “Show Date and Time in Menu Bar” and the box I checked was not checked off even thought the lock was still locked.
I then moved my cursor up to the menu bar in the upper right corner to see what would happen and the spinning beach ball started up but only for the original icons such as Bluetooth, Mobile Me (which I do not use), Time Machine, Spaces (doesn’t indicated the number when I switch Spaces, etc. The icons Norton Anti Virus and Tech Tool Pro in the menu bar are okay.
Also, when I attempt to shut down my computer the system clears the icons from my desktop except for a picture I have on my desktop and I get a gray wheel spinning and the system just hangs until I press and hold the on/off switch. I don’t know if the clock and shutdown problems are related.
The only new software I loaded recently was Skype with Logitech WebCam for the Mac and Quicken 2007 (Had a problem with Quicken 2006). They both are working okay.
And ideas on why I cannot get my clock to show up and my computer to shutdown?

You may have to consider a new post in the Hardware forum area for the computer
model and build/year; if there is a possibility of some basis the matter could be in
the machine and not the software running within it.
Your last two/three posts are in the Leopard 10.5(.8) forum area and do indicate
some kind of problem where troubleshooting the computer to discover if the matter
at hand would be either hardware or software based, may be the way to go.
The link to the 10.6 Snow Leopard forum won't be of help if your computer is a
PPC-based G5 tower, or other older pre-Intel configuration. And I remember
your earlier questions about the iMac G4 and some other issues in the past.
You may ask the moderators to put your post in a new thread of its own, in the
Leopard 10.5 area; so as to not 'piggy-back' another topic; even though some
of the odd issues you've had seem similar to this OP's topic line and appear to
be in the same general series of hardware. {The question here seems valid.}
The routine suggestions to check, test, verify, and perhaps repair or replace
the system; save a bootable clone to suitable external standalone device if
testing a suspect computer's viability is recommended; and the basics if not
already tried to help isolate the issue(s) as you've posted elsewhere, may be
of some help to try and do; so in that matter, a new thread of your own is best
for your own directed feedback. Since this kind of advice applies to most any
situation, including troubleshooting what may be hardware or software, I'm
adding my two and three-tenths cents worth here.
Your original included Apple Hardware Test may be of some help, in the process
of elimination; but is not conclusive, so other methods would be also suggested.
Some ideas appear to cover the same ground. However, system corruption or
disc failure can also manifest itself in odd ways & affect things indirectly for a time.
• OS X Maintenance And Troubleshooting
http://www.macattorney.com/ts.html
• Mac OS X BASIC TROUBLESHOOTING & MAINTENANCE
http://www.gballard.net/macrant/osx_troubleshooting.html
• Troubleshooting Tips for computers:
http://www.stcdio.org/offices/cem/mediaandtechnology/cem-computer-classes/troubl eshooting.html
So, at the risk of inadvertently alienating the OP, I am posting this as
a general help to following readers at some later time; and it may not
be too simple for a refresh course.
Some software issues can be resolved by repairing disk permissions,
and re-applying the last OS X update Combo file over the same one
already in the system; or if not up-to-date already, check & repair all
the general items and then apply the last Combo update.
A too-full hard disk drive can compromise the system integrity, so that
is a matter of course to keep up on what resources exist and remain
for the OS X to function correctly and for apps to multi-task together.
However that works out...
Good luck & happy computing!

XI 3.0: Startup/Shutdown problem

Similar Messages

Maybe you are looking for