[SOLVED] Imapd does not start (only during boot process)

I'm running a courier-imap server.
A few days ago I noticed I did not receive any mails anymore. Then I found my imapd daemon was not running anymore.
I then stopped the daemon process together with the xinetd daemon (which lets me connect to my imap server via my local network).
I restart from a terminal both daemons (imapd an xinetd) and ... everything is up and running ! Note that I have to stop xinetd too because only stopping imapd and restarting doesn't help.
I reboot my PC ... again no imapd anymore. During the boot process I do not get any error message though ...
I'm completely puzzled
The problem started when I upgraded to the linux 3.0.1 kernel ...
Last edited by Strider (2011-08-14 07:59:41)

I managed to get the problem solved by removing and re-installing the courier-imap package. Don't know why that solved it though ...
Last edited by Strider (2011-08-14 07:59:05)

Similar Messages

[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?

Oracle 11g XE listener does not start automatically during boot

Hi,
This happened to me recently I just wanted to share it with you.
For development I was running Standard Edition, at some point I decided to run also XE on the same server for another reasons. Everything was working fine, except that after restart of the server, the XE listener is not starting automatically. Debugging the startup script I found that this happens because of a bug in the code, which assumes that XE listener is running if it finds the word LISTENER within the processes list. I didn't found any obligation in the docs for running XE without any other databases on the same host.
In file /etc/init.d/oracle-xe, at line 556 the code is failing:
1     + status='oracle 2889 1 0 May13 ? 00:00:05 /oracle/ora112se/bin/tnslsnr LISTENER -inherit'
2     + '[' 'oracle 2889 1 0 May13 ? 00:00:05 /oracle/ora112se/bin/tnslsnr LISTENER -inherit' == '' ']'
As you can see I have another listener(the one for SE) running and because of the XE startup script found the keyword LISTENER it’s supposing that the XE LISTENER is already running.
To fix this simply change line 556 from:
1     status=`ps -ef | grep tns | grep oracle`
To:
1     status=`ps -ef | grep tns | grep oracle | grep xe`
Now XE listener is started automatically during boot.
Sve
Blog: http://sve.to
Twitter: sgyurov

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

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

[Solved]Laptop does not start (not even bios)

Hi all,
I was about to install archlinux on my laptop. When I generate partitions (I used GPT), I saw something like this:
"If you have a BIOS motherboard (or plan on booting in BIOS compatibility mode) and you want to setup GRUB on a GPT-partitioned drive, you will need to create an extra BIOS Boot Partition of size 1 or 2 MiB and EF02 type code. Syslinux does not need one."
So, I was planning to make this. When I run cgdisk, I was that lthere was a 1007kb unusued(?) space. So I thought I can use this space for boot sector. Then I changed its type to EF02. When I did this, my laptop shutted down quickly and does not start again. When I press the power up button; I hear the usual starting noise, and then it shuts down again.
What did I do to my laptop?
What I tried:
Remove battery, wait for 5 minutes, try again
Remove hdd, try again
Unplug&plug bios battery, try again
Edit: Solved with a shame. Wall-charger was unplugged. This topic can be removed.
Last edited by firatakandere (2013-12-24 17:09:56)

firatakandere wrote:Wall-charger was unplugged. This topic can be removed.
Why? Others may learn for your experience
Welcome to Arch Linux.

[SOLVED] CUPS does not start

I don't know if this issue is a bug or if I'am doing something terribly wrong.
I've installed ArchLinux without GUI, just base, as a pure printserver a few weeks ago with only cups running and it worked.
But when I try to do exactly the same installation again on same PC (tried IPFire meanwhile) it is a mess!
First CUPS suddenly needs avahi to be running (enabled).
Without it, I get a 'core-dump' error:
systemd-coredump[###]: Process 255 (cupsd) dumped core.
systemd[1]: cups.service: main process exited, code=dumped, status=6/ABRT
Next cups does not start, does not offer shared printers and is not accessible through web interface until I start it manually.
Than everything works as supposed.
On reboot: same procedure!
Of course I edited 'cupsd.conf' on the server, added
Listen *:631
and
Allow from 192.168.XXX.XXX/24
to all <Loaction> entries.
Though I enabled cups (which in fact only enables the cups.socket) I do not get it to work.
So it seems to be a problem with this non reacting cups.socket, perhaps?
BTW: sshd.socket works.
There are no errors which I could post.
I've also reinstalled serveral times...
PS:
Menawhile I found a workaround:
# systemctl disable cups
# sudo ln -s '/usr/lib/systemd/system/cups.service' '/etc/systemd/system/multi-user.target.wants/cups.service'
but I still wonder, why the intitial configuration which worked till a few days suddenly stopped working...
Last edited by renegat (2013-02-27 14:28:14)

renegat wrote:
I don't know if this issue is a bug or if I'am doing something terribly wrong.
I've installed ArchLinux without GUI, just base, as a pure printserver a few weeks ago with only cups running and it worked.
But when I try to do exactly the same installation again on same PC (tried IPFire meanwhile) it is a mess!
First CUPS suddenly needs avahi to be running (enabled).
Without it, I get a 'core-dump' error:
systemd-coredump[###]: Process 255 (cupsd) dumped core.
systemd[1]: cups.service: main process exited, code=dumped, status=6/ABRT
Next cups does not start, does not offer shared printers and is not accessible through web interface until I start it manually.
Than everything works as supposed.
On reboot: same procedure!
Of course I edited 'cupsd.conf' on the server, added
Listen *:631
and
Allow from 192.168.XXX.XXX/24
to all <Loaction> entries.
Though I enabled cups (which in fact only enables the cups.socket) I do not get it to work.
So it seems to be a problem with this non reacting cups.socket, perhaps?
BTW: sshd.socket works.
There are no errors which I could post.
I've also reinstalled serveral times...
PS:
Menawhile I found a workaround:
# systemctl disable cups
# sudo ln -s '/usr/lib/systemd/system/cups.service' '/etc/systemd/system/multi-user.target.wants/cups.service'
but I still wonder, why the intitial configuration which worked till a few days suddenly stopped working...
Using the .socket will activate cups on access. Which is much better than keeping it running all the time. Unless you want it running all the time.. Up to you.
I'm curious what your cups.service acutally looks like.. since you shouldn't be having to make a symlink manually.. That's what systemctl enable is for, as you probably know. And why not paste the socket too while you're at it.. Mine are at the bottom of this reply. I also added the cups.path so you can compare and see if anything went wrong there.. Mine works great on 3.7.9-1 kernel.
I'm not sure why you're linking cups.service to multi-user.target.wants/ but it should be WantedBy=printer.target.. Have a look below.
* enabling cups.service should create symlinks for the service unit and the path
* enabling cups.socket should only create the symlink for the socket.
╰─╼ cat cups.socket
[Unit]
Description=CUPS Printing Service Sockets
[Socket]
ListenStream=/var/run/cups/cups.sock
[Install]
WantedBy=sockets.target
╰─╼ cat cups.service
[Unit]
Description=CUPS Printing Service
[Service]
ExecStart=/usr/sbin/cupsd -f
PrivateTmp=true
[Install]
Also=cups.socket cups.path
WantedBy=printer.target
╰─╼ cat cups.path
[Unit]
Description=CUPS Printer Service Spool
[Path]
PathExistsGlob=/var/spool/cups/d*
[Install]
WantedBy=multi-user.target

[solved] LXDE does not start

I have installed lxde accoriding to the wiki (I was using xfce, which starts fine using the follwing configuration files, without the lines, marked by #new) and I have adopted the configuration files, but lxde does not start. I'm not using a login manager, x starts automatically.
~/.bash_profile
# ~/.bash_profile
export DESKTOP_SESSION=LXDE#new
[[ -f ~/.bashrc ]] && . ~/.bashrc
[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx
~/.xinitrc
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
#startxfce4 #old
exec startlxde #new
~/.bashrc
# ~/.bashrc
# If not running interactively, don't do anything
[[ $- != *i* ]] && return
alias ls='ls --color=auto'
alias ls='ls --color=auto'
alias reboot="sudo reboot"
alias poweroff="sudo poweroff"
alias halt="sudo halt"
alias skype='LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so skype'
PS1='[\u@\h \W]\$ '
Last edited by mumpf (2013-06-05 20:06:42)

So, when you login, startx is not executed? Or does X start and immediately exit/crash? Do other parts of .bash_profile get executed, i.e., if you echo $DESKTOP_SESSION, does it say LXDE, do you see the results of .bash_rc (prompt, aliases)? Then check if XDG_VTNR is set, and DISPLAY.
(After your edit:) If you only changed the exec line, then I assume X still starts, but startlxde fails? So X immediately exits or something? Do you get any useful messages in the logs?
Last edited by Raynman (2013-05-29 09:16:36)

[solved]firefox does not start anymore: (firefox:4358): Bonobo-WARNING

Hi All,
Firefox has always worked on the laptop of my girfrind, until yesterday. When I run firefox from the command line I get the following message, and firefox does not start.
ingeborg@laptop:/storage/home/ingeborg$ firefox
(firefox:4358): Bonobo-WARNING **: Bonobo must be initialized before use
ingeborg@laptop:/storage/home/ingeborg$
Versions:
ingeborg@laptop:/storage/home/ingeborg$ firefox -v
Mozilla Firefox 3.6.12, Copyright (c) 1998 - 2010 mozilla.org
$ uname -a
Linux laptop 2.6.35-ARCH #1 SMP PREEMPT Sat Oct 30 19:57:05 UTC 2010 i686 Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz GenuineIntel GNU/Linux
When I move .mozilla, firefox starts without problem, so there must be something wrong with the information in ~/.mozilla:
$ mv .mozilla/ .mozilla-moved
ingeborg@laptop:~$ firefox
(firefox:4852): Bonobo-WARNING **: Bonobo must be initialized before use
(firefox:4852): Bonobo-WARNING **: Bonobo must be initialized before use
(firefox:4852): Bonobo-WARNING **: Bonobo must be initialized before use
ingeborg@laptop:~$
Any Idea's how I can figure out what file is causing this problem in .mozilla?
What does code 4358 and 4852 from firefox mean?
Best regards,
Cedric
Last edited by cdwijs (2011-01-03 12:05:23)

I have reproduced the problem:
1)Move (or remove) ~/.mozilla
2)goto this website : http://toolbar.zynga.com/install/farmville/
3)login with a valid facebook acount
4)Click install, and then click allow, install now, restart namoraka, restart, finish, and then click save and quit.
Now firefox does not start anymore.
Is it usefull when I make a tar file of .mozilla and post it here?
Best regards,
Cedric

Dhcpcd does not start automatically on boot

Hi everyone,
I have just installed Arch (64 bit) and am running on a dynamic, wired connection.
I followed the Beginners' Guide and enabled the dhcpcd service during the installation so that it would start automatically on boot.
systemctl enable [email protected]
However, I currently must issue the command "dhcpcd" each boot before the internet starts to work.
Does anyone know how I can automate this process or if I need to further configure my network connection?
Thank you in advance.
Last edited by Ipozya (2012-11-15 11:29:05)

foppe wrote:
Check the output from
# systemctl status [email protected]
to debug the issue you're experiencing.
% sudo systemctl status [email protected]
[email protected] - dhcpcd on eth0
Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled)
Active: failed (Result: exit-code) since Tue, 2012-11-15 20:38:16 GMT; 27 sec ago
Process: 244 ExecStart=/sbin/dhcpcd -A -q -w %I (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/[email protected]/eth0
Nov 15 20:37:47 arch dhcpcd[244]: eth0: sending IPv6 Router Solicitation
Nov 15 20:37:47 arch dhcpcd[244]: eth0: sendmsg: Cannot assign requested address
Nov 15 20:37:47 arch dhcpcd[244]: eth0: broadcasting for a lease
Nov 15 20:37:51 arch dhcpcd[244]: eth0: sending IPv6 Router Solicitation
Nov 15 20:37:55 arch dhcpcd[244]: eth0: sending IPv6 Router Solicitation
Nov 15 20:37:59 arch dhcpcd[244]: eth0: sending IPv6 Router Solicitation
Nov 15 20:37:59 arch dhcpcd[244]: eth0: no IPv6 Routers available
Nov 15 20:38:16 arch dhcpcd[244]: timed out
Nov 15 20:38:16 arch systemd[1]: Failed to start dhcpcd on eth0.
Nov 15 20:38:16 arch systemd[1]: Unit [email protected] entered failed state
Dhclient did not work automatically on boot either.
Others seem to have experienced similar issues but I don't see any real solutions in any of these posts, despite being marked as solved. For example, adding "-t 120" to the dhcpcd start line in /usr/lib/systemd/system/[email protected] did not work for me.
I also tried the following but it did not work either and I had to issue "dhcpcd" before internet started working.
Install and configure wired and wireless networking
# pacman -S netcfg ifplugd
# cd /etc/network.d
# ln -s examples/ethernet-dhcp .
Make sure the WIRED_INTERFACE and WIRELESS_INTERFACE lines is uncommented
# nano /etc/conf.d/netcfg
# systemctl enable net-auto-wired.service
# pacman -S wireless_tools wpa_supplicant wpa_actiond dialog
# systemctl enable net-auto-wireless.service
https://bbs.archlinux.org/viewtopic.php?pid=1176656
https://bbs.archlinux.org/viewtopic.php?pid=1189587
https://bbs.archlinux.org/viewtopic.php?pid=1180192
Last edited by Ipozya (2012-11-15 21:08:03)

Oracle 10 g OEM does not start after XP boot

Hallo!I am currently studying for the Oracle 10g Administration OCA
I installed Oracle 10 g on Windows XP but once I boot the OS and enter the OEM url on the browser,OEM does not load.
I am forced to go to the command prompt and manually start OEM via the command
emctl start dbconsole.
How can I configure my oracle to enable OEM to automatically start after booting the OS?
Thanks.

Hans Forbrich wrote:
user11114098 wrote:
During installation,the computer was connected to the internet via a modem that uses DHCP?So typical.
How do I resolve this issue?Microsoft Loopback Adapter. Force it to a static IP value, and enter that value in the hosts. table.
How?: Discussed more than a few times in these forums. Discussed in Microsoft forums. Discussed on internet.Also discussed in the Fine Installation Guide ... ;-)

[SOLVED] Arch does not start into gnome desktop

I installed arch from the scratch into a new hard drive due to a disk failure in the old one. After installing it, I booted into gnome3 desktop without problems.
Today I have upgraded it by performing:
#pacman -Syu
and also I have installed some other no important packages mplayer, banshee, etc... also I have seen that my kernel has been upgraded into 3.11.4-1-ARCH fro 3.10.10-1-ARCH.
After rebooting, my arch does not boot, even in fallback mode. It starts cleaning blocks from the partitions, and then after it is done, cursor is blinking and no other messages are printed out. It stays with cursor blinking forever. I have a GUID Partition table and a LVM2 where all paritions are made.
I can log in into console by pressing CTRL+ALT+F2. Once I have prompted I have no network interfaces, only lo (loopback). If I do:
#ip link show
#ip addr list
I only get lo (loopback) interface listed, others like wifi and ethernet cable does not appear.
If I perform below:
#journalctl -xn
I do not see any problematic message, only this one:
Failed to open private bus connection
Any ideas why arch is not booting and get into gnome session (login window)?
UPDATED:
The problem is that once I have performed the full system update with:
#pacman -Syu
My kernel images has been upgraded and successfully generated into 3.11.4-1-ARCH but I have seen that my kernel, after log in to console and performing:
$uname -r
it says kernel version continues being 3.10.10-1-ARCH so at startup images genereated into 3.11.4-1-ARCH do not match so cursor remains blinking forever....
I am trying to update the kernel but now I have no internet connection, no network interfaces are shown.... so how to do this now? chrooting?
Last edited by toni (2013-10-12 18:32:10)

ewaller wrote:Check the output of uname -a and of pacman -Qi linux and ensure that the versions match. If they don't, you are somehow starting using the wrong kernel and it cannot find its modules.
You are right, see my updated post, for some reason image were successfully generated into 3.11.4-1-ARCH but kernel has not been updated and it remains in 3.10.10-1-ARCH.... so they do not match and arch does not boot.... so cursor remains blinking forever....

Oracle 11g Windows 64 Bit 2008 Does Not Start on Next Boot

Hi all
We have Windows 2008 Standard Server R2 64 Bit. We installed Oracle 10g 64 Bit thru using download of
win64_11gR2_Database
It works perfectly OK when installed. We are able to create tablespace, schemas , import our database etc. and works as desired.
But on the Reboot of the Server - It does not work
Kindly advise some method to setup the path of default spfile where it should be defined
Suresh Bansal

Suresh Bansal wrote:
Hi all
We have Windows 2008 Standard Server R2 64 Bit. We installed Oracle 10g 64 Bit thru using download of
win64_11gR2_Database
It works perfectly OK when installed. We are able to create tablespace, schemas , import our database etc. and works as desired.
But on the Reboot of the Server - It does not work
Kindly advise some method to setup the path of default spfile where it should be defined
Are you having the DHCP used for the networking ? My best guess is that either you have the service of the database set to Manual which is not letting the db to be started when the machine is rebooted . What is the error message coming when you are trying to start the db?
HTH
Aman....

[SOLVED] Rhythmbox does not start

I have rhythmbox 2.90.1.git20110528-1 and when I try to start it I get this error:
rhythmbox: symbol lookup error: /usr/lib/libwebkitgtk-3.0.so.0: undefined symbol: UCNV_FROM_U_CALLBACK_ESCAPE_46
I tried unistalling / reinstalling it but it does not work.
do you have any ideas?
thanks,
Last edited by arriagga (2011-06-10 11:51:50)

No problem, glad to hear you've got it working. I noticed the rhythmbox package does depend on libwebkit3. I'm just pointing this out to show there isn't a bug in the rhythmbox package, it must have been in dependency checking when you install rhythmbox.
My next guess would be that you had rhythmbox installed and working, then another package removed/replaced libwebkit3 which broke rhythmbox.
All in all, glad it's working for you!

[SOLVED] samba does not start properly

I have three machines ( desktop, laptop, and a mini-itx "homeserver" ), and I use samba shares on all the three machines.
The homeserver is headless, does not have a DE, and launches samba properly any time.
On the other machines, the samba service launches ( I can see it on the screen as arch starts ) but does not really start.
I found that smbd is always running, but nmbd never starts when arch starts up.
When the startup is complete, I type "/etc/rc.d/samba restart", and it launches the samba service properly, on both machines.
The smb.conf file is identic on all the machines, except for the server string and the specific machine's share location/name
What can be wrong? Why does nmbd not start on both machines? (Or why does it on the third?)
Last edited by scar (2012-07-12 13:57:46)

Samba is in my daemons array in rc.conf. I've already tried to start it in backround too ( @ ). Did not work.
I've already tried the /etc/rc.local thing, but not with a sleep before the service start command.
Will try it.
Currently I'm using my laptop ( Wicd, not networkmanager , and the first post (skrooge) did not work.
I'll try it this evening with nm.

[solved] kgpg does not start

hey,
kgpg is not starting. every time when i'm going to launch it in konsole I'll receive this error message:
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
how can i fix it?
Regards,
John
Last edited by newcomer008 (2012-02-05 12:57:24)

Ok - I've reinstalled the package and now it works like a charm - Maybe it was an upgrade error.
Sorry for the inconvenience you may have been caused.
Regards,
john

[SOLVED] Imapd does not start (only during boot process)

Similar Messages

Maybe you are looking for