[SOLVED] wicd-gui starts on boot, although not in rc.conf

Hello,
since I seem to can#t find the solution I quickly ask here for some help.
I was using wicd as network manager. But then I switched to the gnome networkmanager.
Thus, I removed wicd from the daemons and added networkmanager.
However, now networkmanager works as wanted, but the wicd-gui still starts after boot (wicd is not running).
Where do I nee to change the config in order to disable not only wicd but also wicd-gui?
Thx!
Last edited by Jankosevic (2012-02-18 10:24:16)

hadrons123 wrote:Try removing it from startup , by going to 'gnome-session-properties' in your terminal.
Thx! That worked.

Similar Messages

Weblogic Server not starting up: Boot identity not valid

Hi All,
I am trying to start the weblogic server and the following error appears:
####<May 28, 2010 12:05:53 PM IST> <Notice> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275028553504> <BEA-090082> <Security initializing using security realm myrealm.>
####<May 28, 2010 12:05:53 PM IST> <Critical> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275028553535> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
####<May 28, 2010 12:05:53 PM IST> <Critical> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553535> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:959)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
     at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:243)
     at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
     at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
     at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
     at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
     at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
     at $Proxy16.login(Unknown Source)
     at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:91)
     at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
     at $Proxy34.authenticate(Unknown Source)
     at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
     at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:347)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:929)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<May 28, 2010 12:05:53 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553567> <BEA-000365> <Server state changed to FAILED>
####<May 28, 2010 12:05:53 PM IST> <Error> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553567> <BEA-000383> <A critical service failed. The server will shut itself down>
####<May 28, 2010 12:05:53 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553567> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<May 28, 2010 12:05:53 PM IST> <Info> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275028553582> <BEA-000236> <Stopping execute threads.>
Kindly help me regarding
Thanks in advance

Just to add some more details here which will help in diagnosing the problem. I deleted the boot.properties file and the command prompt asked me for the username and password. I provided the correct details but still the server could not start up. Here are the details from the log file:
####<May 28, 2010 12:45:47 PM IST> <Notice> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275030947053> <BEA-090082> <Security initializing using security realm myrealm.>
####<May 28, 2010 12:45:47 PM IST> <Critical> <Security> <CALTP8BB14> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1275030947084> <BEA-090403> <Authentication for user weblogic denied>
####<May 28, 2010 12:45:47 PM IST> <Critical> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947084> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
     at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:243)
     at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
     at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
     at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
     at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
     at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
     at $Proxy16.login(Unknown Source)
     at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:91)
     at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
     at $Proxy34.authenticate(Unknown Source)
     at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
     at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:347)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:929)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<May 28, 2010 12:45:47 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947116> <BEA-000365> <Server state changed to FAILED>
####<May 28, 2010 12:45:47 PM IST> <Error> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947116> <BEA-000383> <A critical service failed. The server will shut itself down>
####<May 28, 2010 12:45:47 PM IST> <Notice> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947116> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<May 28, 2010 12:45:47 PM IST> <Info> <WebLogicServer> <CALTP8BB14> <AdminServer> <main> <<WLS Kernel>> <> <> <1275030947131> <BEA-000236> <Stopping execute threads.>

[SOLVED ]Automatic Xsession starting for two users not working

Trying to have two Xsession running in the same time, started automatically after login on two consoles. When I start the second manually at tty8, it is running flawless. When trying to do the same with .xinitrc, it is completelly ignored and still talks bullshit about Xsession running for display 0.
Make me feel there is some configuration file somewhere where it should not definitelly exist which takes controll everytime but when starting Xsession manually…
Last edited by Behemot (2011-10-15 18:55:37)

karol wrote:Not sure I get it, but .bashrc_profile!is executed when you log in, so you basically want to start X every time, right?
Yep exactly, computer for lames, the second user is just for english-speaking, first one will be for native Czech. As soon as this will work, I will even set automatic logon with mingetty for both users.
karol wrote:
exec ck-launch-session dbus-launch startxfce4 -- :1 tty7
For the second user change this to
exec ck-launch-session dbus-launch startxfce4 -- :0 tty8
:0 instead of :1 (or you can use :2 etc.)
I think I've already tried, tried again now and still the same result.
Last edited by Behemot (2011-10-15 14:25:46)

Trying to create a service that starts at boot

People,
I'm trying to create a service that will start at boot (in single-user mode, actually). I am up and running but I do NOT want to run the service now. I only want to run the service when the machine reboots.
I've been rummaging around all day trying to figure this out but I'm stuck. I can create a service that runs. I can create an XML file in /var/svc/manifest/site/patch-install.xml that will be read when I boot- because after I boot, I can list the service:
svcs -a | grep patch
disabled       18:23:23 svc:/site/patch-install:defaultI have inserted the following in my xml:
<create_default_instance enabled='true' />and also
<create_default_instance enabled='false' />but it makes no difference. Anyone have any idea? What is the purpose of create_default_instance? I don't understand; item 9 on http://www.sun.com/bigadmin/content/selfheal/sdev_intro.html seems rather opaque to me.
Also, what exactly is the purpose of /var/svc/profile/ ? I tried putting some code to enable my xml but it didn't do anything. Just wondering if this might fit into the picture.
BTW, I do not want the login prompt to appear until my method is complete.
Thanks.
-mschwage
Here fyi is my /var/svc/manifest/site/patch-install.xml file:
<?xml version="1.0"?>
<!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1">
<service_bundle type='manifest' name='Patches:patch-install'>
<service
        name='site/patch-install'
        type='service'
        version='1'>
        <create_default_instance enabled='false' />
        <single_instance />
        <dependent
                name='patch-install_single-user'
                grouping='require_all'
                restart_on='none'>
                <service_fmri value='svc:/milestone/single-user' />
        </dependent>
        <exec_method
                type='method'
                name='start'
                exec='/var/tmp/S92delay'
                timeout_seconds='86400' />
        <exec_method
                type='method'
                name='stop'
                exec=':true'
                timeout_seconds='0' />
        <property_group name='startd' type='framework'>
                <propval name='duration' type='astring' value='transient' />
        </property_group>
        <stability value='External' />
        <template>
                <common_name>
                        <loctext xml:lang='C'>
                        Install patchset upon boot.
                        </loctext>
                </common_name>
        </template>
</service>
</service_bundle>

Hushpuppy wrote:
People,
I'm trying to create a service that will start at boot (in single-user mode, actually). I am up and running but I do NOT want to run the service now. I only want to run the service when the machine reboots.I'd probably create the service now (by importing the manifest manually rather than waiting for the reboot), then set general/enabled in the default instance to be be true with svcprop. That should tell it to start at boot, but not enable it immediately.
I've been rummaging around all day trying to figure this out but I'm stuck. I can create a service that runs. I can create an XML file in /var/svc/manifest/site/patch-install.xml that will be read when I boot- because after I boot, I can list the service:Yes, that's the default. Or you can load it immediately to create the service now.
# svccfg import patch-install.xml
I have inserted the following in my xml:
<create_default_instance enabled='true' />and also
<create_default_instance enabled='false' />but it makes no difference. Anyone have any idea? What is the purpose of create_default_instance? I don't understand; item 9 on http://www.sun.com/bigadmin/content/selfheal/sdev_intro.html seems rather opaque to me.There's a difference between a "service" like network/smtp or console-login and an "instance" like network/smtp:sendmail or console-login:default. In most cases, you just want a single "default" instance of your service. The above line sets the default instance 'enabled' property to true or false. When I import your manifest as is, the service comes in as 'disabled'. If I set it to true, it comes in as 'maintenance' (almost certainly because it was enabled, tried to start, and couldn't find the start method on my machine).
Also, what exactly is the purpose of /var/svc/profile/ ? I tried putting some code to enable my xml but it didn't do anything. Just wondering if this might fit into the picture.'profiles' are loaded exactly once, and they are mainly used to set certain services to enabled or disabled.
3 of them are loaded if present, platform.xml, generic.xml, and site.xml. The last is not generated by the OS, but left for you to use. But it's usually only useful as a "first boot" type thing. Because if you make changes to it, it will not be reread. This isn't usually a problem because after first boot you're in control of the services. The usual thing is that at first boot the manifests load to create services, then the profiles are loaded to set then enabled or disabled. This isn't possible before that point because there's no service to modify yet.
BTW, I do not want the login prompt to appear until my method is complete.Any login prompt like a network login, or only the console login prompt? If the latter, then you'll want a dependency so that system-console-login depends on your service. But if your service has a problem at boot time, you'd make it difficult to log in.
Darren

[solved] systemd services not starting at boot (or at all)

On my router, some systemd services fail to start at boot.
The services are :
adsl (pppoe connetction on the wan interface)
shorewall (funny again for a router)
logind (brings up only tty1, and not the others with a 'timeout' error)
adsl starts fine manually after booting up
the others don't work, I have to launch shorewall with the old sysvinit rc script (and it works)
I really don't know, what happened to logind...
Last edited by scar (2012-11-30 10:20:44)

cups: avahi client failed
adsl: timeout (ppp0 running on eth0, the service did not found eth0)
shorewall: did not work by the systemctl command, only with the old rc script
I'm not sure if there was an error with logind, but I've had only tty1, not all the others (I have not touched /etc/inittab)
since this was a very old install (but up to date), I've decided to reinstall the whole thing,
Everything works
(But reinstalling does not solve any problem, it erases the problems...)
Last edited by scar (2012-11-30 10:21:20)

[Solved] vsftpd not starting on boot

Hi,
I have problems running vsftpd via systemd on boot.
What I did: Install vsftpd, configure it properly, enable and start vsftpd.service. It works fine, but it won't start on boot; I need to start it manually.
This is what systemctl status vsftpd sais:
$ systemctl status vsftpd.service
vsftpd.service - vsftpd daemon
Loaded: loaded (/usr/lib/systemd/system/vsftpd.service; enabled)
Active: failed (Result: exit-code) since Wed 2014-01-01 21:28:21 CET; 7s ago
Process: 866 ExecStart=/usr/bin/vsftpd (code=exited, status=2)
Main PID: 866 (code=exited, status=2)
CGroup: /system.slice/vsftpd.service
However, starting it manually works fine and vsftpd is running then. I already read another topic, where a user had exactly the same problem. Unfortunately, that solution (adding network.target to service file) does not work for me. (topic: https://bbs.archlinux.org/viewtopic.php?pid=1251823)
This is what my vsftpd.service file looks like:
$ cat /usr/lib/systemd/system/vsftpd.service
[Unit]
Description=vsftpd daemon
Requires=network.target
After=network.target
[Service]
ExecStart=/usr/bin/vsftpd
ExecReload=/bin/kill -HUP $MAINPID
KillMode=process
[Install]
WantedBy=multi-user.target
I recently added the Requires= field, it did not change anything. Further I tried adding NetworkManager.service and NetworkManager-wait-online.service, it did not change anything as well. Any idea how I might fix that?
Last edited by vibee (2014-01-09 12:31:21)

After boot:
$ systemctl list-units
vsftpd.service loaded failed failed vsftpd daemon
$ systemctl list-unit-files
vsftpd-ssl.service disabled
[email protected] static
vsftpd.service enabled
[email protected] static
I am wondering that network.target is not shown when doing systct list-dependencies; vsftpd.service only depends on default.target and multi-user.target. Why is network.target not shown?
$ systemctl list-dependencies
default.target
├─gdm.service
└─multi-user.target
├─avahi-daemon.service
├─cpupower.service
├─cronie.service
├─cups.path
├─dbus.service
├─dkms.service
├─hddtemp.service
├─httpd.service
├─iked.service
├─mysqld.service
├─NetworkManager-wait-online.service
├─NetworkManager.service
├─radicale.service
├─rpc-mountd.service
├─rpc-statd.service
├─smbd.service
├─sshd.service
├─svnserve.service
├─systemd-ask-password-wall.path
├─systemd-logind.service
├─systemd-user-sessions.service
├─verynice.service
├─vsftpd.service
├─basic.target
│ ├─alsa-restore.service
│ ├─alsa-state.service
│ ├─paths.target
│ ├─slices.target
│ │ ├─-.slice
│ │ └─system.slice
│ ├─sockets.target
│ │ ├─avahi-daemon.socket
│ │ ├─cups.socket
│ │ ├─dbus.socket
│ │ ├─dmeventd.socket
│ │ ├─lvmetad.socket
│ │ ├─systemd-initctl.socket
│ │ ├─systemd-journald.socket
│ │ ├─systemd-shutdownd.socket
│ │ ├─systemd-udevd-control.socket
│ │ └─systemd-udevd-kernel.socket
│ ├─sysinit.target
│ │ ├─dev-hugepages.mount
│ │ ├─dev-mqueue.mount
│ │ ├─kmod-static-nodes.service
│ │ ├─proc-sys-fs-binfmt_misc.automount
│ │ ├─sys-fs-fuse-connections.mount
│ │ ├─sys-kernel-config.mount
│ │ ├─sys-kernel-debug.mount
│ │ ├─systemd-ask-password-console.path
│ │ ├─systemd-binfmt.service
│ │ ├─systemd-journal-flush.service
│ │ ├─systemd-journald.service
│ │ ├─systemd-modules-load.service
│ │ ├─systemd-random-seed.service
│ │ ├─systemd-sysctl.service
│ │ ├─systemd-tmpfiles-setup-dev.service
│ │ ├─systemd-tmpfiles-setup.service
│ │ ├─systemd-udev-trigger.service
│ │ ├─systemd-udevd.service
│ │ ├─systemd-update-utmp.service
│ │ ├─systemd-vconsole-setup.service
│ │ ├─cryptsetup.target
│ │ ├─local-fs.target
│ │ │ ├─-.mount
│ │ │ ├─mnt-serverdisk.mount
│ │ │ ├─mnt-windows.mount
│ │ │ ├─systemd-remount-fs.service
│ │ │ └─tmp.mount
│ │ └─swap.target
│ │ ├─dev-disk-by\x2did-ata\x2dST3000DM001\x2d1CH166_Z1F23A7C\x2dpart2.swap
│ │ ├─dev-disk-by\x2did-wwn\x2d0x5000c5004f7babf3\x2dpart2.swap
│ │ ├─dev-disk-by\x2dpartuuid-e8647b5a\x2de808\x2d41a8\x2d86e7\x2d353410f0a4bb.swap
│ │ ├─dev-disk-by\x2duuid-3a4d745f\x2d7d88\x2d48ad\x2dba59\x2d261410fcbb8a.swap
│ │ ├─dev-disk-by\x2duuid-3a4d745f\x2d7d88\x2d48ad\x2dba59\x2d261410fcbb8a.swap
│ │ └─dev-sdb2.swap
│ └─timers.target
│ └─systemd-tmpfiles-clean.timer
├─getty.target
│ └─[email protected]
└─remote-fs.target
And one more strange thing: If I want to start vsftpd manually by hitting systemctl start, vsftpd.service does not appear via auto-completion.
Last edited by vibee (2014-01-02 15:59:08)

[SOLVED]Wicd not working

Hi, for the client i get
$ wicd-client
(process:8315): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
Importing pynotify failed, notifications disabled.
Has notifications support False
Loading...
Connecting to daemon...
Can't connect to the daemon, trying to start it automatically...
Then a gui ask's for root, after hitting it in I get this:
Could not connect to wicd's D-Bus interface. Check the wicd log for error messages.
Before that I did this:
bash-3.2# /etc/rc.d/network stop
:: Stopping Network [DONE]
bash-3.2# nano /etc/rc.conf
bash-3.2# /etc/rc.d/dbus restart
:: Stopping D-BUS system messagebus [DONE]
:: Starting D-BUS system messagebus [DONE]
bash-3.2# /etc/rc.d/wicd restart
:: Stopping wicd Daemon [DONE]
:: Starting wicd Daemon [DONE]
bash-3.2#
Last edited by jerik (2009-06-27 20:55:08)

This is my rc.conf file:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="nb_NO.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="Europe/Oslo"
KEYMAP="no-latin1"
CONSOLEFONT="lat1-12"
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(!soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="myhost"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
eth0="dhcp"
INTERFACES=(!eth0 !wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng hal netfs crond wicd oss)

Start-up problem with hp pavilion dv6t-7000‏: "Boot Device Not Found. Hard Disk (3F0)" error

I started getting start-up problems with my hp pavilion dv6t-7000‏. It happens intermittently.
The boot error is:
Boot Device Not Found
   Please install an operating system on your hard disk.
   Hard Disk (3F0)
   F2 System Diagnostics
   For more information, please visit: www.hp.com/go/techcenter/startup
Could a faulty BIOS update cause this problem?
Anyone else who may have experienced a similar problem?
I'd appreciate any help about this problem. Thanks.

Hi
Please find the link given below might help you to fix your issue.
Resolve Boot Device not Found Error Message
Let us know how it goes!
"I work for HP."
****Click the (purple thumbs up icon in the lower right corner of a post) to say thanks****
****Please mark Accept As Solution if it solves your problem****
Regards
Manjunath

Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved. It started with the last upgrade to 10.8

Lightroom 4 crashes when trying to open the slideshow module. I spent over three hours with both Adobe and Apple tech support and we know it is a permission issue but have not been able to get it solved. It started with the last upgrade to 10.8

Back up all data.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -Rh $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
The first step should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary.
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
resetpassword
That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

[SOLVED - partly] Minidlna won't start on boot, but OK otherwise

I am using an up-to-date system as of 2012-11-13. The problem is that minidlna fails to start on boot:
minidlna.service - minidlna server
Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled)
Active: failed (Result: exit-code) since Tue, 2012-11-13 07:53:55 CET; 1h 33min ago
Process: 401 ExecStart=/usr/sbin/minidlna -P /var/run/minidlna/minidlna.pid (code=exited, status=255)
CGroup: name=systemd:/system/minidlna.service
Nov 13 07:53:59 earth minidlna[401]: [2012/11/13 07:53:54] minidlna.c:754: fatal: No IP address automatically detected!
So I guess it has to do something with the network, I am using DHCP, with systemd + net-auto-wired.service.
I have found this: https://ask.fedoraproject.org/question/ … r-dhcp-has
They have solved the problem by changing the after part in the unit by adding: dbus-org.freedesktop.NetworkManager.target
Since I do not use networkmanager, this is not an option for me. The current, unmanipulated state of the minidlna unit is:
[Unit]
Description=minidlna server
After=network.target
[Service]
Type=forking
User=nobody
ExecStart=/usr/sbin/minidlna -P /var/run/minidlna/minidlna.pid
PIDFile=/var/run/minidlna/minidlna.pid
[Install]
WantedBy=multi-user.target
What I have noticed is that it refers to a network.target in the after section, but it seems to me that I don't have one.
I only have:
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
12 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Edit: having run the command again with the --all prefix:
Notice: network.target loaded inactive dead Network
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
emergency.target loaded inactive dead Emergency Mode
final.target loaded inactive dead Final Step
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded inactive dead Network
nss-lookup.target loaded inactive dead Host and Network Name Lookups
nss-user-lookup.target loaded inactive dead User and Group Name Lookups
remote-fs.target loaded active active Remote File Systems
rescue.target loaded inactive dead Rescue Mode
shutdown.target loaded inactive dead Shutdown
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
syslog.target loaded inactive dead Syslog
umount.target loaded inactive dead Unmount All Filesystems
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
21 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
My question is what should I add to the after part to make minidlna work upon booting? Wouldn't a graphical.target be an overkill?
Thanks in advance.
Last edited by szebenyib (2012-12-02 16:45:26)

szebenyib wrote:(However I cannot access the internet that way, maybe because of a bad network file. Honestly I have some space to improve my network knowledge.)
In the case of the possible bad network file. here is what it expects. First, you need to know the router's IP address. In the following I will assume 192.168.0.1 for the router's IP address.
192.168.0.1 is common for D-Link routers, but it does vary by router manufacturer and model. I believe 192.168.1.1 is common for Linksys.
/etc/conf.d/network
interface=eth0 # ethernet port to activate, usually eth0
address=192.168.0.110 # IP address you want the minidlna computer to have. the first 3 triads must be the same as the router's IP addr in this case 192.168.0 the fourth triad can be from 5 to 250
netmask=24
broadcast=192.168.0.255 # the first 3 triads must be the same as the router's IP address and the fourth triad should be 255
gateway=192.168.0.1 # the IP address of your router
In a terminal window, enter:
systemctl restart network.service
ping -c5 127.0.0.1
which is localhost. The -c5 means ping 5 times then quit. If you get: 5 packets transmitted, 5 received, 0% packet loss then the ping was successful, which means
that the ethernet port (usually eth0) is active. If this ping is not successful, go back and check the syntax and spelling in both /etc/conf.d/network and /etc/systemd/system/network.service
If the ping is successful:
ping -c5 192.168.0.1
and ping the router.
If you cannot ping the router's IP address, then there is still something wrong in one of the two involved files. or the router's settings need to be changed.
If you can ping the router's IP address successfully and still cannot get to the internet, you probably have DNS server issues.
ping -c5 google.com
ping -c5 8.8.8.8
If you cannot ping google.com but can ping 8.8.8.8 then you have DNS problems, see Arch WIKI resolv.conf
My network is a mixture of DHCP and STATIC IP addresses. In my router, I have the DHCP server enabled to give IP addresses between 192.168.0.10 and 192.168.0.60
this gives the router 50 DHCP addresses to work with which is more that enough for my home network. The rest of the addresses between 192.168.0.61 and 192.168.0.250
can be used as static addresses. Just an example, this can be changed as necessary.
HTH
Pudge

Openntpd won't start at boot [SOLVED]

Hi all!
My system clock is perpetually off by 4 hours, and I've narrowed it down to an issue with Openntpd; it seems to be refusing to start at boot time. Here are the relevant lines from daemon.log:
Sep 1 21:30:26 raskolnikov ntpd[1440]: Terminating
and the output of ps aux | grep ntpd:
[raskolnikov@raskolnikov ~]$ ps aux | grep ntpd
ntp 1323 0.0 0.0 3184 700 ? S 17:32 0:00 /usr/sbin/ntpd -s
root 1332 0.0 0.0 3292 256 ? Ss 17:32 0:00 /usr/sbin/ntpd -s
1000 1412 0.0 0.0 3616 800 pts/0 S+ 17:33 0:00 grep ntp
I can manually restart the daemon via /etc/rc.d/openntpd restart, which works fine, and the time is set correctly. However, when I reboot, the adjustments are wiped out, and the daemon does not start again (same message in daemon.log). I have the default ntpd.conf. I have found very little helpful information on Google, I would greatly appreciate it if someone could point me in the right direction, I've wasted quite a few hours this evening working on this problem! Thanks!
Edit: Just in case it's helpful, here is my daemons array from rc.conf:
DAEMONS=(syslog-ng !network acpid eee hal networkmanager netfs crond openntpd bitlbee)
Last edited by happycodemonkey (2009-09-02 03:55:46)

I've had this problem too, although I do not use networkmanager. I've found that openntpd fails to configure itself properly if the network is not up when it starts (in my case this happens when I background the network daemon and start openntpd in the daemons array).
My current working solution* is to add this line to rc.local:
(sleep 300 && /etc/rc.d/openntpd start) &
That will wait 5 minutes before starting the openntpd daemon which gives the network more than sufficient time to start. An alternative would be run "/etc/rc.d/openntpd restart" in an hourly cronjob if your network settings change often.
* Why not just unbackground the network daemon you ask? If the network isn't up then it takes a while to timeout and I don't want to wait to boot in that case.
Last edited by Xyne (2009-09-02 02:05:52)

[solved] Start X at Login not working for me

I'm stripping down my system and decided to get rid of my login manager (slim) and just make the system boot straight into the GUI on boot-up. I followed directions found at https://wiki.archlinux.org/index.php/St … sh_profile , but it's not working on this system. I just get dumped at a command prompt login when I reboot the system and, after having logged in, no X gets started. The system just sits there awaiting input at the prompt. If I enter startx, the GUI starts. But it's not starting at login as I'd like. Actually, it'd be even better if the system automatically logged me in and started X--like we used to do using inittab, once, etc. But that method's obviated now because of systemd, no? My WM is jwm, by the way. Tips on resolving this issue will be appreciated.
James
Last edited by jamtat (2013-01-25 21:59:42)

You can still set up automatic login ("like we used to do using inittab, once, etc"): https://wiki.archlinux.org/index.php/Au … al_console
As for your original question, I assume you are using bash, and you have added the correct information to your ~/.bash_profile? ("but it's not working on this system" is a little vague). This works for me.
[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx
Last edited by 2ManyDogs (2013-01-25 20:31:30)

[SOLVED] can't start wicd-client. python errors

when i run wicd-client it gives the following errors, but i can browse internet and such, because is like wicd works right, it seems that only the gui is broken...
[aleyscha@aleyscha 1 ~ 00:25]$ wicd-client
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Traceback (most recent call last):
File "/usr/lib/wicd/wicd-client.py", line 50, in <module>
import wicd.gui as gui
File "/usr/lib/python2.6/site-packages/wicd/gui.py", line 2006, in <module>
setup_dbus()
File "/usr/lib/python2.6/site-packages/wicd/gui.py", line 174, in setup_dbus
proxy_obj = bus.get_object("org.wicd.daemon", '/org/wicd/daemon')
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 244, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 241, in __init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 183, in activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 281, in start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 622, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.wicd.daemon was not provided by any .service files
Last edited by leo2501 (2009-02-25 22:21:40)

Yep, seems like lots of us are getting this.
I thought it was actually stopping scrot though the screen shot does occur. The message looks like it's fatal though.
i would have thought that scrot didn't start 'till i found screenshots.
wicd working here on fresh 2009.02.
I guess it'll be one of those that jst resolves itself soon.
Pretty certain you've seen all most all of these though put 'em here anyways:
http://lists.freedesktop.org/archives/x … 39132.html
http://lists.freedesktop.org/archives/x … 39131.html
http://bugs.archlinux.org/task/13223
http://bbs.archlinux.org/post.php?tid=66199
http://bbs.archlinux.org/viewtopic.php?id=65403
Last edited by yvonney (2009-02-25 20:09:33)

My Xserve does not wake up every Saturday from a cold start / cold boot up.

Hello, everyone,
This is my first time using this Apple Discussions Forum here and so hope any expert out there who can solve my problem, I'd deeply appreciated. Basically the problem is like this.
I configured Xserve to
wake up 8:50 am wake up every morning.
shut down system 1:00 am every morning.
There are two places to be configured here:
1. System Preferences' Energy Saver
2. Workgroup Manager>Computer List>Preferences> Schedules>Mac OS X Server.
The time schedules in those two places are ensured to be at the same setting.
(does anyone know which is the main one?)
Furthermore,
I have a clock timer set to 2:00 am to shut down the main power supply to the Xserve. And so,
Power Supply timer provides power to Xserve:
8:40 am every morning (before scheduled Xserve waking up time, 8:50 am)
Power supply cut down the power to Xserve:
2:00 am every morning (after scheduled Xserve shutting down time, 1:00 am)
Why am I doing this? Because I think it is good for Xserve's power supply fan. If I let Xserve's power supply run 24/7 for years, the motor is wearing down soon. It also saves some energy for me.
Normally the power supply would first provides the power to Xserve before Xserve would boot up as scheduled.
Now, this setting works pretty well for me for months until recently.
My Xserve will not boot up every Saturday morning as scheduled. I cannot figure out why it does this weird behavior.
I tried to search forums and google many many places, and find no solution.
Here are a list of things I have tried:
I changed 2 new PRAM battery twice in one month.
I have tried to reset SMC.
I have tried to reset PRAM.
I tried to reset PRAM before SMC reset. I also tried to reset SMC before PRAM reset.
Worse yet, on Saturday morning, Xserve is like in a deep coma, I tried to remotely boot it up by LOM, it does not even respond to my LOM waking up call. It is like a naughty kid refusing to wake up in the Saturday morning. The only way to wake it up is that I I have to take a long walk and physically go to my Xserve and hold the power button for 5 seconds and press it again and so it wakes up. Note that if I just press the power button once, it does not boot up neither. Why?
Then the next day, it is normal again for another 6 days until next Saturday. I could not figure out why it does this. Why just Saturday? Why not Sunday or any other day between Monday to Friday?
Funny and strange behavior.
The problem is periodic and so I believe it has something to do with the software and/or the PRAM caching the alarm time, which may influence the SMC setting.
Note: the Apple website says SMC controls the waking time while Apple manual also says PRAM is responsible for alarm clock.
I would normally
shut down system
unplug the cable
hold the power button for 5 seconds and let it go
plug back the power cable.
Xserve should either boot up by itself or stay cold for me to boot up.
note: the manual just say unplug the cable for 5 sec but did not say hold the power button for 5 second, and I think that is wrong; you have indeed have to hold the power button for 5 seconds as the Apple website said. Otherwise when I cut down power supply every day, my SMC is reset by itself every day.
I have a voltage regulator before my Xserve's power supply and so the voltage is very stable.
Any Xserve experts out there has the same problem like I do??

Hi, MrHoffman , I couldn't agree more with your view point. Xserve not only reacts poorly to sudden power shortage, its HDDs may also get hurt during sudden power removal. Therefore, I was extremely careful when resetting SMC. Bad SMC procedure can hurt HDD.
MrHoffman , my problem is not totally solved and you knew I will come back, right? I do accidentally find your blog. Is the site yours?
http://labs.hoffmanlabs.com/node/976
Your blog and threads from here has inspired me to investigate in the direction on LOM issue. Thank you.
http://discussions.apple.com/thread.jspa?messageID=11911509
http://discussions.info.apple.com/message.jspa?messageID=11902981
http://discussions.apple.com/thread.jspa?messageID=11255905&#11255905
I've come to narrow down the problem and suspect the root cause is LOM bug. Basically this is what happens in the last 4 days.
After nearly 3 weeks of monitoring my Xserve, it was running perfectly normal until 4 days ago. Suddenly, my Xserve fails to wake up for 4 days in a row. I almost made it---a perfect run for 1 month without ever having to reset SMC once! This time, the failed waking-up event took place during normal weekdays. So it is still a mystery to me that why my Xserve previously fails to wake up only on Saturday (perhaps, hackers prefer Saturday because that's when they are free?---just kidding). However, at least I now know the problem can take place at anytime.
Maybe I should first list my Xserve's specification.
Xserve Late 2006 Model
2.0 GHz Dual-Core Intel Xeon
8G RAM
Mac OS X Leopard Server 10.5.8 (Build 9L34)
Boot ROM: XS11.0080.B01
LOM version: 1.2.8
I am only using en0 for both LAN and LOM.
So since I was not able to wake up my Xserve remotely by LOM, it is intuitive to check Server Monitor on Xserve side.
On my Xserve side, I had
Name: Nothing (it was localhost)
IP Address: 127.0.0.1
Status Summary: Software is not installed properly on server.
At this point, I was wondering where did my Status Summary go? So as an incentive move, I delete the 127.0.0.1 from Server Monitor list and go to >Server Monitor>Server>Configure Local Machine, trying to re-add the localhost server back to Server Monitor list. Then it is when all of the troubles occur.
The Server Monitor simply hangs there. When check Finder>Force Quit Applications, I see Server Monitor (not responding).
So I was questioning myself that if this failed waking-up event is a software issue or a hardware sensor issue. Before answering to this question, as a good habit, let me post my log file.
Jul 31 13:27:06 xserve01 kernel[0]: AppleKCS::waitForIBF timed out!
Jul 31 13:27:36: --- last message repeated 4 times ---
Jul 31 13:27:40 xserve01 kernel[0]: AppleKCS::waitForIBF timed out!
Jul 31 13:28:10: --- last message repeated 4 times ---
Jul 31 13:28:15 xserve01 kernel[0]: AppleKCS::waitForIBF timed out!
Jul 31 13:28:45: --- last message repeated 4 times ---
Jul 31 13:28:49 xserve01 kernel[0]: AppleKCS::waitForIBF timed out!
Jul 31 13:29:19: --- last message repeated 4 times ---
Jul 31 13:29:23 xserve01 kernel[0]: AppleKCS::waitForIBF timed out!
Jul 31 13:29:53: --- last message repeated 4 times ---
Jul 31 13:29:58 xserve01 kernel[0]: AppleKCS::waitForIBF timed out!
Jul 31 13:30:21: --- last message repeated 3 times ---
Jul 31 13:30:21 xserve01 /usr/sbin/spindump[2056]: process 2006 is being monitored
Jul 31 13:30:23 xserve01 /usr/sbin/spindump[2056]: process 2006 is being force quit
Jul 31 13:30:26 xserve01 kernel[0]: AppleKCS::waitForIBF timed out!
Jul 31 13:30:29 xserve01 /usr/sbin/spindump[2056]: process 2006 is being no longer being monitored
Jul 31 13:30:33 xserve01 kernel[0]: AppleKCS::waitForIBF timed out!
Jul 31 13:30:32 xserve01 com.apple.launchd[250] ([0x0-0x27027].com.apple.servermonitor[2006]): Exited: Killed
Hardly can I find any reference about AppleKCS::waitForIBF timed out! on Google. So any senior Apple Xserve engineer please helps!

SAP GUI 7.20 PL5 - Does NOT start

Hi there,
I just installed PL5 for SAP GUI for Windows 7.20. I hoped this would fix the problem with the centralized saplogontree.xml as said in several notes.
But after I installed the patch, the GUI doesnt start anymore. The screen with the version number and the two people appears and after a few seconds disappears. The GUI doesnt start and I cant connect to our systems. There is no process running the GUI. I tried to reboot too, no success.
Any ideas? Possibly a bug?!
Anyone else having problems with the patch?

After I corrected the adress for the saplogon.ini in the saplogontree.xml file on the webserver the GUI starts up normally. My fault was that I typed in the absolute path "http:://domain.tld/saplogon.ini" instead of just "domain.tld/saplogon.ini". The XML-file then linked to http://http://domain.tld/saplogon.ini
After I corrected the entry, the GUI starts normal.
Regards,
Jann

[SOLVED] wicd-gui starts on boot, although not in rc.conf

Similar Messages

Maybe you are looking for