Ssh does not start at boot

Hi All
As my title explains, ssh does not start when I reboot.
I can start it like: ./usr/lib/ssh/sshd
So my question is: how can I change this behaviour and let ssh start at boot ?
Thanks a lot in advance
Luca

thnx a lot!!!!
Luca

Similar Messages

Windows does not start at boot

Hello,
Windows does not start at boot, how? 'Safe Mode either )

If your system is not properly booting then you must press F8 when start the system then there are two option
Repair Window,start window normally if not properly work then you will install again operating system.

SSH does not start after reboot

Hi, I have a problem with my sshd daemon. I have updated my OS, I have changed the .pacnew files and tested service with "systemctl start sshd.service" and it worked good. I have run command "systemctl enable sshd.service" and command executed good. But after reboot service does not start.
I have run "systemctl status sshd.service" and result is that service is loaded, but in Activa line it is inactive (dead).
I dont know what is happening, why is it inactive if it is loaded?
Thank you for you help.

These are outputs:
$ systemctl status sshd.service
* sshd.service -OpenSSH Daemon
Loaded: loaded (/usr/lib/systemd/system/ssh.service: enabled)
Active: inactive (dead)
$ systemctl status sshd.socket
* sshd.socket
Loaded: loaded (/usr/lib/systemd/system/ssh.socket: enabled)
Active: active (listening) since Fri 2014-05-30 09:57:52 COT; 12min ago
Listen: [::]:22 (Stream)
Accepted: 0; Connected: 0
It looks that socket is working, but service isn't. I have reviewed "journalctl -b" and sshd service isn't shown it.
Last edited by mams827 (2014-05-30 15:25:18)

LaunchDaemon does not start at boot, but manually

Hi all
I have a LaunchDaemon entry for apache that does not start at system boot.
It contains the following keys that might affect the behaviour.
<key>OnDemand</key>
<false/>
<key>RunAtLoad</key>
<true/>
I can manually load the script using
sudo launchctl load /LibraryLaunchDaemomns/org.macports.svn.plist
Maybe I did not fully understand the LaunchDaemon concept. My program is
a wrapper that will start svnserve as a standalone server.
As I mentioned earlier it works fine manually, both "load" and "unload" successfully start and stop the service.
I'd appreciate any comments
Thanks a lot

Good evening
I want to startup my SVN service on a local RAID volume, but need to wait
until it is mounted. To do so I added the following to my daemons plist:
<key>KeepAlive</key>
<dict>
<key>PathState</key>
<string>/Volumes/RAID</string>
</dict>
Maybe this is useful to someone in this forum.
Cheers

[SOLVED]dhcpcd does not start on boot anymore

Hello,
I reinstalled Arch last night to try and be as to the letter as possible because I had three bad installs( or so I thought https://bbs.archlinux.org/viewtopic.php?id=195192 ) and it was going well. I tweaked some SSD Optimization configs and went to bed.
Today I wanted to install OpenBox so first I tried to update my system with pacman -Syu (without reading the change log or anything of course) and I couldn't download anything. A quick ping to google.com gave an unknown host error. Nothing has changed over night and I rebooted the machine last night a couple of times and I always had internet connection. The guide said that dhcpcd runs automatically on boot and I looked through the change logs at the places I understood and couldn't find anything about this being disabled on boot now. I do see that it was updated in the last 24 hours but again, nothing about auto run on boot being disabled.
Little things like this bug me, I can enable the service using systemctl and call it a day but I was wondering if I was the only one experiencing this. If I'm the only one then it probably isn't a good thing.
SOLVED: Did not read the Beginner's Guide within context of the installation medium.
Last edited by SirMyztiq (2015-03-29 01:20:49)

nullified wrote:
SirMyztiq wrote:I updated the packages and just went to bed.
What packages were upgraded? If I am understanding you correctly, dhcpcd was enabled and working fine before the upgrade, but after the upgrade dhcpcd appears to be disabled. Is that correct? Two bits of informaiton you should post here are the complete list of updated packages and the output of
systemctl status dhcpcd
SirMyztiq wrote:Nothing has changed over night and I rebooted the machine last night a couple of times and I always had internet connection.
You previously say you upgraded then went to bed, so that would be the change. I'm a little confused by these seemingly contradictory assertions.
I apologize for the confusion.
I'll give you the current list of packages as soon as I install a browser on my machine(I'm on my laptop) but I can tell you that all I had last night was the "base" and "base-devel" packages installed. I mainly did tweaking like setting the scheduler dynamically on my ssd to "deadline" following the SSD Optimization wiki and read a bit about OpenBox to make sure I get it right. I also rebooted the computer a couple of times to check for that "time out" bug I mentioned. It all checked out, so I went to bed.
I power her up today, try to do a system update and I wasn't able to. A ping to google.com gave me an "unknown host" error. I checked both the "status" and whether it was "enabled" with their respective systemctl commands and both gave me the feedback that it was not active nor was it enabled.
I'll edit the original post to be more clear and look like I have some grasp of English.

My iBook G4 does not start or boot. The screen does not light and the start up chime does not sound. What should I do? Please help.

But I think it still works since I hear noises inside the machine and the caps lock still lights up. It just won't start.

Hi, Toby. Welcome to Apple Support Communities.
Have you tried resetting the PMU?
http://support.apple.com/kb/HT1431?viewlocale=en_US
This is the first troubleshooting measure an Apple Authorized Service Provider would try.

WLS5.1 SP8 problem : weblogic does not start anymore : method getClassLoadNotify()Lweblogic/boot/ClassLoadNotify; not found

Hello,
I currently have a problem with the EJBException which does not give the
client the getCausedBy() Exception. I d' like to try the 5.1 sp8 to see if
the bug is fix.
Unfortunately, after having installed the sp8, my WLS 5.1 does not start
anymore : I get an invocationTargetException.
Does anyone have a clue ?
Best Regards.
dom
The WebLogic Server did not start up properly.
Exception raised: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException: java.lang.NoSuchMethodError:
weblogic.boot.ServerClassLoader: method
getClassLoadNotify()Lweblogic/boot/ClassLoadNotify; not found
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.jav
a:141)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.jav
a:113)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.jav
a:105)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader.<init>(Recurs
iveReloadOnModifyClassLoader.java:53)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader$SingleSlave.<
init>(RecursiveReloadOnModifyClassLoader.java:149)
at
weblogic.servlet.internal.ServletContextImpl.setClassLoader(ServletContextIm
pl.java:1571)
at
weblogic.servlet.internal.ServletContextImpl.<init>(ServletContextImpl.java:
539)
at
weblogic.t3.srvr.HttpServer.initServletContexts(HttpServer.java:523)
at weblogic.t3.srvr.HttpServer.start(HttpServer.java:418)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1312)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
at weblogic.NTServiceHelper.run(NTServiceHelper.java:19)
at java.lang.Thread.run(Thread.java:479)
java.lang.NoSuchMethodError: weblogic.boot.ServerClassLoader: method
getClassLoadNotify()Lweblogic/boot/ClassLoadNotify; not found
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.jav
a:141)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.jav
a:113)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.jav
a:105)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader.<init>(Recurs
iveReloadOnModifyClassLoader.java:53)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader$SingleSlave.<
init>(RecursiveReloadOnModifyClassLoader.java:149)
at
weblogic.servlet.internal.ServletContextImpl.setClassLoader(ServletContextIm
pl.java:1571)
at
weblogic.servlet.internal.ServletContextImpl.<init>(ServletContextImpl.java:
539)
at
weblogic.t3.srvr.HttpServer.initServletContexts(HttpServer.java:523)
at weblogic.t3.srvr.HttpServer.start(HttpServer.java:418)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1312)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
at weblogic.NTServiceHelper.run(NTServiceHelper.java:19)
at java.lang.Thread.run(Thread.java:479)
tel 02 38 64 37 95
mailto:[email protected]

Well... I've made a big classpath mistake.
It works indeed.
dom
"Dominique Jean-Prost" <[email protected]> a écrit dans le
message news: [email protected]...
Hello,
I currently have a problem with the EJBException which does not give the
client the getCausedBy() Exception. I d' like to try the 5.1 sp8 to see if
the bug is fix.
Unfortunately, after having installed the sp8, my WLS 5.1 does not start
anymore : I get an invocationTargetException.
Does anyone have a clue ?
Best Regards.
dom
The WebLogic Server did not start up properly.
Exception raised: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException: java.lang.NoSuchMethodError:
weblogic.boot.ServerClassLoader: method
getClassLoadNotify()Lweblogic/boot/ClassLoadNotify; not found
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.jav
a:141)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.jav
a:113)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.jav
a:105)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader.<init>(Recurs
iveReloadOnModifyClassLoader.java:53)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader$SingleSlave.<
init>(RecursiveReloadOnModifyClassLoader.java:149)
at
weblogic.servlet.internal.ServletContextImpl.setClassLoader(ServletContextIm
pl.java:1571)
at
weblogic.servlet.internal.ServletContextImpl.<init>(ServletContextImpl.java:
539)
at
weblogic.t3.srvr.HttpServer.initServletContexts(HttpServer.java:523)
at weblogic.t3.srvr.HttpServer.start(HttpServer.java:418)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1312)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
at weblogic.NTServiceHelper.run(NTServiceHelper.java:19)
at java.lang.Thread.run(Thread.java:479)
java.lang.NoSuchMethodError: weblogic.boot.ServerClassLoader: method
getClassLoadNotify()Lweblogic/boot/ClassLoadNotify; not found
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.jav
a:141)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.jav
a:113)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.jav
a:105)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader.<init>(Recurs
iveReloadOnModifyClassLoader.java:53)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader$SingleSlave.<
init>(RecursiveReloadOnModifyClassLoader.java:149)
at
weblogic.servlet.internal.ServletContextImpl.setClassLoader(ServletContextIm
pl.java:1571)
at
weblogic.servlet.internal.ServletContextImpl.<init>(ServletContextImpl.java:
539)
at
weblogic.t3.srvr.HttpServer.initServletContexts(HttpServer.java:523)
at weblogic.t3.srvr.HttpServer.start(HttpServer.java:418)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1312)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
at weblogic.NTServiceHelper.run(NTServiceHelper.java:19)
at java.lang.Thread.run(Thread.java:479)
tel 02 38 64 37 95
mailto:[email protected]

[Solved] Network does not starts on every boot

Yet another problem on fresh arch...
Network service does not starts every time I booting my headless. For every 10 attempts service starts 5 or 6 times only.
Ping says: Networking unreachable.
systemctl status network:
network.service - Static IP Connectivity
Loaded: loaded (/etc/systemd/system/network.service; enabled)
Active: inactive (dead)
'systemctl start network' just hangs. In order to get it start I have to reboot the box hoping next boot service will start.
I am not using dhcp (if it makes a sence). Service was configured as described in wiki for static IP assigning.
The config itself:
[Unit]
Description=Static IP Connectivity
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-enp4s1.device
After=sys-subsystem-net-devices-enp4s1.device
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/sbin/ip link set dev enp4s1 up
ExecStart=/sbin/ip addr add 192.168.1.5/24 dev enp4s1
ExecStart=/sbin/ip route add default via 192.168.1.1
ExecStop=/sbin/ip addr flush dev enp4s1
ExecStop=/sbin/ip link set dev enp4s1 down
[Install]
WantedBy=multi-user.target
What's wrong?
Thanks in advance for any help.
Last edited by chord (2013-06-03 17:04:55)

Thaks for your reply.
I got this interface name from ip addr, how it should be named if 'enp4s1' is wrong?
journalctl is here: http://bpaste.net/show/104083/
I found only one string realted to this device name:
Jun 03 15:18:23 localhost systemd[1]: Expecting device sys-subsystem-net-devices-enp4s1.device...
Is there some other logs where it can be checked?

WebAnalysis does not start after workspace is set on Windows Authentication

I've used [doc Hyperion System 9.3.x Configuring the BI+ Workspace for Single Sign-On (SSO) with Internet Information Services (IIS) [ID 1100096.1] to configure SSO for workspace users. It works fine. Though since then the WA service does not start anymore. The error message which is raised sounds very very familar but still I am not able to tackle it. The message in the log or the analysis console is "[WARN] [STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' com.hyperion.analyzer.utils.general.HYAUtil - Wait for workspace [
[WARN] Timer-2 com.hyperion.analyzer.utils.general.HYAUtil - ."
I am very sure it had something to do with rights/ permissions, but also after playing around with IIS and ntfs permissions for hours I can't get SSO en WA both working at the same time.
As soon as I set my workspace aplication in IIS on windows integrated, the SSO is working but as soon as a I restart the WA service it fails to start. When I set the workspace application IIS on anonymous the WA service start fine but then the SSO is not working anymore.
It drives me crazy.
Hopefully its a small matter for you to solve!
Thanks in advance.

Dont know exactly whats happened but I presume something went wrong during the update procedure.
If you will be not able to start the notebook in the safe mode or to boot the notebook then user the Toshiba recovery CD to gets the notebook working!

Message bean does not start automatically during application server startup

I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
Thanks,
Bill
#1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
#1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
#1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
#1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
#1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
#1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
#1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
#1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
#1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                ... 12 more
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                ... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                ... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                ... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
#1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
#1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                ... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                ... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                ... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
                at java.lang.Class.getDeclaredConstructors0(Native Method)
                at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
                at java.lang.Class.getConstructor0(Class.java:1930)
                at java.lang.Class.newInstance0(Class.java:278)
                at java.lang.Class.newInstance(Class.java:261)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
                at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
                at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
                at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
                at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
                at java.security.AccessController.doPrivileged(Native Method)
                at javax.security.auth.Subject.doAs(Subject.java:379)
                at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
                at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
                at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
                at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
I've could change that yes, but the startup script doesn't seemed to have this mind.
Regards,
Sve

Jenkins not deploying on Tomcat; SSH Service not starting

So I've had a couple of problems happening. My first problem is that even though sshd.service and sshd.socket are enabled with systemctl, it does not automatically start. There are no errors reported in journalctl, it just does not start. When issuing systemctl status sshd.service and systemctl status sshd.socket, there is nothing to report. Once I manually start them, there are no errors reported, and everything works as expected.
sshd.socket
[Unit]
Conflicts=sshd.service
Wants=sshdgenkeys.service
[Socket]
ListenStream=22
Accept=yes
[Install]
WantedBy=sockets.target
sshd.service
[Unit]
Description=OpenSSH Daemon
Wants=sshdgenkeys.service
After=sshdgenkeys.service
After=network.target
[Service]
ExecStart=/usr/bin/sshd -D
ExecReload=/bin/kill -HUP $MAINPID
KillMode=process
Restart=always
[Install]
WantedBy=multi-user.target
# This service file runs an SSH daemon that forks for each incoming connection.
# If you prefer to spawn on-demand daemons, use sshd.socket and [email protected].
The second problem is my tomcat service. It won't start the Jenkins. I've linked the jenkins.war file to the webapps folder. When I start tomcat using systemctl start tomcat8, this is the output of journalctl -xn
-- Logs begin at Sat 2014-08-30 06:46:59 PDT, end at Sun 2014-09-14 15:45:38 PDT. --
Sep 14 15:45:15 localhost jsvc.exec[1344]: Sep 14, 2014 3:45:15 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-nio-8080"]
Sep 14 15:45:16 localhost jsvc.exec[1344]: Sep 14, 2014 3:45:16 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["ajp-nio-8009"]
Sep 14 15:45:16 localhost jsvc.exec[1344]: Sep 14, 2014 3:45:16 PM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-nio-8080"]
Sep 14 15:45:16 localhost jsvc.exec[1344]: Sep 14, 2014 3:45:16 PM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["ajp-nio-8009"]
Sep 14 15:45:27 localhost systemd[1]: [/usr/lib/systemd/system/systemd-journal-upload.service:20] Unknown lvalue 'After' in section 'Install'
Sep 14 15:45:38 localhost systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
Sep 14 15:45:38 localhost jsvc[28476]: Cannot locate Java Home
Sep 14 15:45:38 localhost systemd[1]: tomcat8.service: control process exited, code=exited status=1
Sep 14 15:45:38 localhost systemd[1]: Failed to start Tomcat 8 servlet container.
-- Subject: Unit tomcat8.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit tomcat8.service has failed.
-- The result is failed.
Sep 14 15:45:38 localhost systemd[1]: Unit tomcat8.service entered failed state.
Here is the tomcat8.service file before my changes, as suggested here
[Unit]
Description=Tomcat 8 servlet container
After=network.target
[Service]
Type=forking
PIDFile=/var/run/tomcat8.pid
Environment=CATALINA_PID=/var/run/tomcat8.pid
Environment=TOMCAT_JAVA_HOME=/usr/lib/jvm/java-7-openjdk
Environment=CATALINA_HOME=/usr/share/tomcat8
Environment=CATALINA_BASE=/usr/share/tomcat8
Environment=CATALINA_OPTS=
ExecStart=/usr/bin/jsvc \
-Dcatalina.home=${CATALINA_HOME} \
-Dcatalina.base=${CATALINA_BASE} \
-Djava.io.tmpdir=/var/tmp/tomcat8/temp \
-cp /usr/share/java/commons-daemon.jar:/usr/share/java/eclipse-ecj.jar:${CATALINA_HOME}/bin/bootstrap.jar:${CATALINA_HOME}/bin/tomcat-juli.jar \
-user tomcat8 \
-java-home ${TOMCAT_JAVA_HOME} \
-pidfile /var/run/tomcat8.pid \
-errfile SYSLOG \
-outfile SYSLOG \
$CATALINA_OPTS \
org.apache.catalina.startup.Bootstrap
ExecStop=/usr/bin/jsvc \
-pidfile /var/run/tomcat8.pid \
-stop \
org.apache.catalina.startup.Bootstrap
[Install]
WantedBy=multi-user.target
And after
[Unit]
Description=Tomcat 8 servlet container
After=network.target
[Service]
Type=forking
PIDFile=/var/run/tomcat8.pid
Environment=CATALINA_PID=/var/run/tomcat8.pid
Environment=TOMCAT_JAVA_HOME=/usr/lib/jvm/java-7-openjdk
Environment=CATALINA_HOME=/usr/share/tomcat8
Environment=CATALINA_BASE=/usr/share/tomcat8
Environment=CATALINA_OPTS=-DJENKINS_HOME=/usr/share/java/jenkins
ExecStart=/usr/bin/jsvc \
-Dcatalina.home=${CATALINA_HOME} \
-Dcatalina.base=${CATALINA_BASE} \
-Djava.io.tmpdir=/var/tmp/tomcat8/temp \
-cp /usr/share/java/commons-daemon.jar:/usr/share/java/eclipse-ecj.jar:${CATALINA_HOME}/bin/bootstrap.jar:${CATALINA_HOME}/bin/tomcat-juli.jar \
-user tomcat8 \
-java-home ${TOMCAT_JAVA_HOME} \
-pidfile /var/run/tomcat8.pid \
-errfile SYSLOG \
-outfile SYSLOG \
$CATALINA_OPTS \
org.apache.catalina.startup.Bootstrap
ExecStop=/usr/bin/jsvc \
-pidfile /var/run/tomcat8.pid \
-stop \
org.apache.catalina.startup.Bootstrap
[Install]
WantedBy=multi-user.target
EDIT:
The SSHD problem is fixed. I read more closely at the sshd.socket config, and it clearly states it conflicts with sshd.service. I disabled service and everything works fine. But I am still having trouble getting Jenkins to work with Tomcat.
Last edited by ZMoore (2014-09-15 00:33:18)

Thank you, but the problem is a little different from that. These are
exploded web apps outside the applications dir. I deployed them
through the console initially; on the other servers, when WL restarts,
the apps are deployed back to their targets just fine. It's only this
box that loses sense of the targets on WL restart.
We're on 6.1, so a few people have suggested upgrading to 6.1 sp4 --
they've said they've seen this problem, and the sp corrects it.
That said, this is a production box and upgrading it is a hassle. I'll
get started on scheduling that, but if anyone has any ideas in the
meantime, I'd greatly appreciate it. If not, thanks anyway. :)
Rob
"Deepak Vohra" <[email protected]> wrote in message news:<3eebae8e$[email protected]>...
WLServer should start in development mode for a application
in the applications dir to deploy.
STARTMODE=false
[email protected] (Rob Young) wrote:
On one of our production servers (just one), when I restart weblogic,
my web applications are not deploying; I have to deploy them manually.
This is bad, obviously, because the server won't restore properly
after a restart.
After a while, I get target="box,box,box,box" that represents the
multiple times I've deployed that application to the target "box".
From config.xml:
<Application Deployed="true" Name="revx" Path="F:\revx">
<WebAppComponent Name="revx"
Targets="giocm,giocm,giocm,giocm,giocm,giocm,giocm"
URI="revx"/>
</Application>
The operating system is Windows 2000 5.00.2195 ... everything was
working fine until I re-installed the Windows service this weekend.
I've checked permissions on the folder, on the file, and who the
service is running as. I've manually edited config.xml to remove the
duplicate target entries.
I've seen some other posts from people who have also experienced
applications not deploying on WL restart, but I don't see any
resolutions.
Rob

Can not update tiger and safari does not start

Hi everybody,
I have actually two but probably interrelated problems: First, safari does not start and second, I can not update tiger.
It all started a few days ago on my MacBook (Intel). Somehow, Safari produced an error (I only guess that it was Safari because I was downloading a movie clip) and Tiger was frozen. After rebooting, the whole system had problems (e.g., Safari and Skype were not starting). I tried to reinstall and archive mac os x but with no success. The problems were growing actually even worse (e.g., slow) and at some point in time, Tiger was not even starting. Thus, I did a full new installation of 10.4.8 (delete and install). Afterwards, it worked first but after the automatic software update, the system told me that their was an input/output error (???) during the 10.4.10 update. Afterwards, the whole system had again problems (slow and problems with even booting)!! Thus, the software update made it even worse. So, I did again a full installation (delete and install).
I have to update my 10.4.8 system, because I also have iLife08 that needs at least 10.4.9. However, I don't know what to do to avoid again these update problems??
In addition, despite the full installation, Safari is not starting. Thus, there is still some problems but I have now clue where this comes from as it is newly installed?!
Any ideas?? Thanks...
Crobus

Crobus, welcome, since you are starting from scratch with each re-install why not try Kappy's Extended Hard Drive Preparation.
http://discussions.apple.com/thread.jspa?messageID=5203987&#5203987
Do all steps from 1 thru 6, it is by far a more maintenance oriented than an Erase and Install. After the preparation, install OS 10 from your DVD, then download the OS 10.4.10 Combo Updater.
Joe

MacBook pro does not start. How can I back to Mac OS X Lion?

I have a MacBook Pro. On my MacBook i made three partition, then I installed window 8. After that I started windos and try to delete third partition by Administrator tool from windows operating system. After that my MacBook does not start. How can I back to Mac OS X Lion?
After that I again install windows 8 from a DVD. Windows start well, but I can not start Mac OS system, may be it was 10.6. Sever times I tried to install OS X Lion 10.7 thought DVD, I could not. On MacBook I have a lot of important data.
What can I do. I want to a complete suggestion. Please help me to solve the problem.
My MacBook Pro model no. A1286.

You installed Windows improperly the result of which was to wipe out the bootloader for OS X. You can give this a try:
Boot Using OPTION key:
1. Restart the computer.
2. Immediately after the chime press and hold down the
"OPTION" key.
3. Release the key when the boot manager appears.
4. Select the OS X disk icon from which you want to boot.
5. Click on the arrow button below the icon.
If you are still unable to boot from the OS X volume then you will need to reinstall OS X:
Reinstall OS X without erasing the drive
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install Mac OS X 10.6.8 Update Combo v1.1.
This will destroy the Windows bootloader so you cannot boot into Windows. The solution is to remove all the partitions on the drive except the OS X partition, then expand the OS X partition to take up the entire drive.
Use Boot Camp Assistant in the Utilities folder to create a Windows partition on which you can install Windows. You cannot have any other partitions on the drive besides these two.
Now given all the above you may be able to install a third-party bootloader that would work with the setup you now have: Boot Runner 1.4.

My database does not start automatically

i am using windows 2000 server and oracle 9.0.1, my database does not start automatically when i am booting the system.
in regedit autostart is there, my service is getting started automatically and i used startmode auto in my oradim command but still i have to manually log in to start the database, PLS help!!!
another issue is that i want to startup/shutdown the database using a user other than sysdba, pls tell which permission shud i grant as dba, connect, resource permissions are not doing the required job

spfile concept is introduced from Oracle 9i. You can call it system parameter file. Benefits of having spfile concept is that what ever changes u make to system through commands
alter system set ??? = ????
get automatically saved in the spfile???.ora which is managed by Oracle.
Main idea behind that as thought by Oracle is that previously u needed to change that parameter in init.ora file then start the database again after shutdown. Now u are doing everything online. spfile???.ora takes priority in the new Oracle concept.
If u delete spfile???.ora file, then it needs some specific init.ora which need to told to Oracle which can be through command like
startup pfile='complete patah .............'
Bansal

Tomcat5 still does not start automatically

Hello,
Novell-tomcat5 still does not start automatically at boot although it is set to do so.
This is from beginning of the oes2/SBE2.5 installation (without simba).
It is still the same behavior after applying OES2/SP2 and SLES10/SP3 patches.
After booting at terminal console:
/etc/init.d/novell-tomcat5 status shows unused
/etc/init.d/novell-tomcat5 start starts tomcat5 without errors
In my boot.msg I found the following error:
____START______
<notice>'novell-nss start' exits with status 0
<notice>novell-tomcat5 start
Starting Tomcat (/var/opt/novell/tomcat5/)<notice>checkproc: /sbin/klogd 4842
<notice>checkproc: /sbin/syslog-ng 4839
<notice>checkproc: /sbin/klogd 4842
<notice>checkproc: /sbin/syslog-ng 4839
<notice>checkproc: /usr/sbin/slpd 7030
<notice>checkproc: /usr/sbin/slpd 7030
<notice>checkproc: /sbin/portmap 6200
<notice>checkproc: /sbin/portmap 6200
<notice>checkproc: /usr/sbin/sshd 6915
<notice>checkproc: /usr/sbin/sshd 6915
<notice>checkproc: /usr/sbin/nmbd 5530
<notice>checkproc: /usr/sbin/nmbd 5530
<notice>checkproc: /usr/sbin/smbd 6900
<notice>checkproc: /usr/sbin/smbd 6900
<notice>checkproc: /usr/sbin/namcd 8495
<notice>checkproc: /usr/sbin/namcd 8495
<notice>checkproc: /usr/sbin/ntpd 7000
<notice>checkproc: /usr/sbin/ntpd 7000
<notice>checkproc: /usr/sbin/slpd 7030
<notice>checkproc: /usr/sbin/slpd 7030
<notice>checkproc: /sbin/klogd 4842
<notice>checkproc: /sbin/syslog-ng 4839
<notice>checkproc: /sbin/klogd 4842
<notice>checkproc: /sbin/syslog-ng 4839
<notice>checkproc: /usr/sbin/slpd 7030
<notice>checkproc: /usr/sbin/slpd 7030
<notice>checkproc: /sbin/portmap 6200
<notice>checkproc: /sbin/portmap 6200
<notice>checkproc: /usr/sbin/sshd 6915
<notice>checkproc: /usr/sbin/sshd 6915
<notice>checkproc: /usr/sbin/nmbd 5530
<notice>checkproc: /usr/sbin/nmbd 5530
<notice>checkproc: /usr/sbin/smbd 6900
<notice>checkproc: /usr/sbin/smbd 6900
<notice>checkproc: /usr/sbin/namcd 8495
<notice>checkproc: /usr/sbin/namcd 8495
<notice>checkproc: /usr/sbin/ntpd 7000
<notice>checkproc: /usr/sbin/ntpd 7000
<notice>checkproc: /usr/sbin/slpd 7030
<notice>checkproc: /usr/sbin/slpd 7030
failed
<notice>'novell-tomcat5 start' exits with status 7
<notice>novell-xregd start
Starting novell-xregd...done
<notice>'novell-xregd start' exits with status 0 ....
_______END______________
Of course it es even a cosmetic problem I don't want to start tomcat manually everytime when booting up.
Has anybody an idea what could be wrong?
Yours sincerely
OliverN

Originally Posted by revilo
Hello,
Novell-tomcat5 still does not start automatically at boot although it is set to do so.
This is from beginning of the oes2/SBE2.5 installation (without simba).
It is still the same behavior after applying OES2/SP2 and SLES10/SP3 patches.
After booting at terminal console:
/etc/init.d/novell-tomcat5 status shows unused
/etc/init.d/novell-tomcat5 start starts tomcat5 without errors
Of course it es even a cosmetic problem I don't want to start tomcat manually everytime when booting up.
Has anybody an idea what could be wrong?
Yours sincerely
OliverN
Hi Oliver,
If you are manually installing the component products then this is no longer a "NOWS SBE" installation. Any issues you encounter are related solely to the component products. OES Linux Installation questions should be directed to: OES-L: Install
In the mean time, to see if it is configured to start automatically use "chkconfig". For instructions:
Code:
man chkconfig
Is it configured to start automatically?
Code:
server:~ # chkconfig --list | grep novell-tomcat5
novell-tomcat5 0:off 1:off 2:off 3:on 4:off 5:on 6:off
The response from the above command shows that novell-tomcat5 should start automatically for runlevels 3 and 5.
If it is not set to start automatically on your server, you can make it start by:
Code:
chkconfig novell-tomcat5 on
I am by no means a Linux expert. If this doesn't resolve your issue, I suggest you post in the appropriate forum where you will find knowledgeable people willing to help.

Ssh does not start at boot

Similar Messages

Maybe you are looking for