Dbus[359]: [system] Activation via systemd failed for unit 'dbus-org.b

from journalctl -b, I get some warning messages like this.
Oct 26 12:52:48 myhost dbus-daemon[359]: dbus[359]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Oct 26 12:52:48 myhost dbus[359]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Oct 26 12:52:48 myhost dbus-daemon[359]: dbus[359]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.
Oct 26 12:52:48 myhost dbus[359]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service fail
Oct 26 12:52:48 myhost pulseaudio[1234]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.ListAdapters() failed: org.freedesktop.systemd1.Lo
Oct 26 12:52:49 myhost rtkit-daemon[1235]: Successfully made thread 1260 of process 1260 (/usr/bin/pulseaudio) owned by '1000' high priority
Oct 26 12:52:49 myhost rtkit-daemon[1235]: Supervising 2 threads of 2 processes of 1 users.
Oct 26 12:52:49 myhost pulseaudio[1260]: [pulseaudio] pid.c: Daemon already running.
I want to disalbe bluez.service,but failed,
#systemctl disable dbus-org.bluez.service
Failed to issue method call: No such file or directory
I have no bluetooth device in my laptop, how to resolve this porblem?
Thanks in advance.
Last edited by eastpeace (2012-10-26 06:12:53)

AND additional information
# systemctl status dbus-org.bluez.service
dbus-org.bluez.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)

Similar Messages

Weird system log error: EV_DELETE failed for file watcher

I just did a clean install of Snow Leopard (erased my hard disk before the installation using Disk Utility). I've run all the updates. I was experiencing some weird delay between the appearance of the blue screen and the appearance of the login window. The delay went away, but when I shutdown or restart, my system log has errors like this:
an 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 25
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 21
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 20
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 19
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 18
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 16
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 24
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 17
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 23
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 35
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 31
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 30
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 29
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 28
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 26
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 34
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 27
Jan 4 17:53:54 Musa com.apple.notifyd[11]: EV_DELETE failed for file watcher 33
Does anyone know what these mean? These do turn up on a Google search, but under systems prior to Snow Leopard! Remember that this is a completely clean system with no third-party software installed yet.

I get a series of eight EV_DELETE errors when ejecting my external FW800 drive. But not when mounting.
The drive also has a USB interface which I rarely use since the FW is much faster. I just tried mounting it using USB. Same behavior - no errors on the mount, but 8 EV_DELETE errors when I eject the drive.
The must be something sketchy with the file structure of the external drive (which is a SuperDuper clone of my internal hard drive).
SL 10.6.5, MacBook Pro with an external FW800/USB 500 GB drive (WiebeTech enclosure).

Patch download via wget fails for some patchid's

Hi,
downloading via wget(1) from http://sunsolve.sun.com/private-cgi/pdownload.pl?target=<patchid> fails with "ERROR 404: Not Found" for certain patchid's (i.e. 119689 or 125081), for these, one now has to specify also the patch's revision (i.e. 119689-04), it seems like patchid links to its latest patches are missing. (btw, I've also mention this along with other patch problems in another post at the administration/maintenance forum)
Would there be a reason/explaination for this?
Thanks.

Please note this forun is for issue with Sun Update Connection-System / Hosted, Patch Manager & PatchPro software products. To get help with wget please use the from below:
http://sunsolve.sun.com/show.do?target=feedback_form

Managed System Configuration: SSO setup failed for Solution Manager 7.1 sp11

Hi Folks,
While doing Managed System Configuration for Soman system i am getting error in SSO Setup
Currently I am in
8. Configure Automatically :Single Sign On Setup
This is i am going for managed System (Solution Manager System Itself)
Below is error log..
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
Screen shot attached.
Found SID for SSO ACL entry : SMP
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
The SSO ticket Certificate <OU=J2EE,CN=SMP> has been successfully imported into ticket Keystore
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
The SSO ticket Certificate <CN=SMP> has been successfully imported into ticket Keystore
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Exception
java.rmi.RemoteException: Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:160)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
at com.sap.engine.services.security.exceptions.BaseSecurityException.writeReplace(BaseSecurityException.java:349)
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:331)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:910)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1024)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1344)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1316)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1260)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1065)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:282)
at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:147)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:338)
... 8 more
Regards,
San

Hi Sandeep,
It seems authorization issue. Please check the below SAP Note :
1988642 - Warning 'caller not authorized' in Step 'Single Sign On Setup'
Hope this helps.
Thanks & Regards,
Nisha

Enabling services via systemd only for certain targets

Hi everyone,
I have been searching and searching and I struggled through manpages but found nothing...
How can you enable services using systemd for a certain target?
Something like "systemd enable --target.graphical gdm".
My idea is to have 2 grub entries, one that boots into target.multi-user and the other that boots into target.graphical.
Then I would enable the gdm and other services I want for target.graphical but not for target.multi-user. That way I could choose on bootup if I want gnome this time or not and have a custom fallback/high performance mode.
I hope I'm not just utterly blind and wasting erverybodys time but I didn't find any information on this whatsoever.
Thanks in advance guys!
Last edited by Ch33f (2014-07-31 13:23:55)

Oh god this one almost hidden sentence:
If you make use of those it is suggested that you make a new named systemd target as /etc/systemd/system/your target that takes one of the existing runlevels as a base (you can look at /usr/lib/systemd/system/graphical.target as an example), make a directory /etc/systemd/system/your target.wants, and then symlink the additional services from /usr/lib/systemd/system/ that you wish to enable.
Ok thats a start.
But there is no parameter in "systemd enable" that I could use to do it?
Last edited by Ch33f (2014-07-31 13:43:49)

Colord-sane.service systemd FAILED

Hi!
Today, as of systemd 187-2, i had this issue. I got a fail from this service, that i never activated.
I saw that it is "static", so i cannot disable it
systemctl is-enabled colord-sane.service
static
And this is what journalctl says:
journalctl | grep colord
Jul 31 12:55:09 arch dbus-daemon[198]: dbus[198]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Jul 31 12:55:09 arch dbus[198]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Jul 31 12:55:11 arch dbus-daemon[198]: dbus[198]: [system] Activating via systemd: service name='org.freedesktop.colord-sane' unit='colord-sane.service'
Jul 31 12:55:11 arch dbus[198]: [system] Activating via systemd: service name='org.freedesktop.colord-sane' unit='colord-sane.service'
Jul 31 12:55:11 arch systemd[281]: Failed at step NETWORK spawning /usr/lib/colord/colord-sane: Invalid argument
Jul 31 12:55:11 arch systemd[1]: colord-sane.service: main process exited, code=exited, status=225
Jul 31 12:55:11 arch systemd[1]: Unit colord-sane.service entered failed state.
Jul 31 12:55:36 arch dbus-daemon[198]: dbus[198]: [system] Failed to activate service 'org.freedesktop.colord-sane': timed out
Jul 31 12:55:36 arch dbus[198]: [system] Failed to activate service 'org.freedesktop.colord-sane': timed out
Jul 31 12:55:36 arch colord[204]: (colord:204): Cd-WARNING **: failed to contact colord-sane: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.colord-sane timed out
I thought i haven't colord installed, but a quick
pacman -Q colord
colord 0.1.21-2
told me i'm wrong.
So, why is this service static, and why i get this strange error?
Any idea?
Thanks in advance!

The error appears to be from within systemd, when it tries to spawn colord-sane. I.e., probably nothing is wrong with sane itself. My guess is that this has something to do with your network setup, as colord-sane has PrivateNetwork=yes (i.e., systemd should block colord from accessing the network). I have colord-sane on my system too, and I'm not able to reproduce this error, so sorry that I cannot be more helpful.
As to disabling colord-sane: you can mask the service:
# systemctl mask colord-sane.service
This means that when dbus tries to start colord-sane, it will just fail. Obviously, that means that cups might not be very happy, I don't know how graciously it handles this situation.

Acknowledgement handling failed for type SystemAck.

Hi I have a scanario where i have a BPM which expects a transport acknowledgement . I have sent a message and in the MDT of the Adapter Engine the message status is seen to be successful/Delivered but when i see the Audit log it says that error occured while handling the system acknowledgement
Acknowledgement handling failed for type SystemAck. Reason: com.sap.aii.af.ra.ms.api.ConfigException: Some of the IS access information is not available. SLDAcess property may be set to true, but SLD is not available.
Even though the message is delivered the BPM in the message monitor is still waiting for the acknowledgement with the stadtus of "Still awaiting acknowledgement". How do i make my bpm continue with the procress.
regards
Nilesh Taunk.

It looks like the adapter engine don't know the url of integration server... it may be caused for serveral causes.
Let's start check in the SLD if the Business System of XI (the BS of integration server) has a right "Pipeline URL".
Something like <i>http://<serverName>:<port>/sap/xi/engine?type=entry</i>
Sandro

Plain user and systemd: dependency failed for local file system

I tried to switch to systemd, but ended up in a maintenance console (Enter root password or Ctrl-D to continue):
Enter password.
journalctl -b as suggested yields "Dependency failed for local file system".
I couldn't find a systemd troubleshooting page in the Wiki. So, can someone point me to such a page? Anyone willing to give some hints?
What I did so far: Did what https://wiki.archlinux.org/index.php/Systemd tells one should do to switch to systemd.
In the boot menu pressed e, moved one down to the line starting with "kernel", pressed e again, and appended init=/bin/systemd.
Somewhere I read that "mkinitcpio -p linux" should be issued to make systemd work. No (positive) effects.
Paul
P.S.: Shouldn't there be a topic "systemd" in "Pacman Upgrades, Packaging & AUR"?

skunktrader wrote:
poseidon wrote:In the boot menu pressed e, moved one down to the line starting with "kernel", pressed e again, and appended init=/bin/systemd.
According to the wiki you are supposed to append init=/usr/lib/systemd/systemd if you are using the "Mixed systemd/sysvinit/initscripts installation" mode. In all other configurations you should NOT have an init=.... entry since init becomes a symlink to systemd
As far as I know, the init= entry doesn't hurt anything - it just isn't necessary.
EDIT: Of course, it will hurt if the path was wrong...
Also, at least on my system, /bin/systemd symlinks to /usr/lib/systemd/systemd.
Last edited by cfr (2012-11-19 23:53:55)

Systemd timer for rkhunter fails to run

Hello.
I created a timer to run weekly the rkhunter script but the
systemctl status timer_rkhunter
returns :
timer_rkhunter.service - Timer script to run rkhunter
Loaded: loaded (/etc/systemd/system/timer_rkhunter.service; static)
Active: failed (Result: exit-code) since Mon 2014-11-10 23:47:46 EET; 1 day 15h ago
Main PID: 21978 (code=exited, status=1/FAILURE)
The .timer file :
[Unit]
Description=Script to run rkhunter
[Timer]
# Time to wait after booting before we run first time
OnBootSec=10min
# Time between running each consecutive time
OnUnitActiveSec=1w
Unit=timer_rkhunter.service
Persistent=true
[Install]
WantedBy=multi-user.target
and the .service file
[Unit]
Description=Timer script to run rkhunter
[Service]
Type=simple
ExecStart=/usr/bin/rkhunter --cronjob --update --quiet
If i execute the /usr/bin/rkhunter --cronjob --update --quiet in a terminal everything works properly.

rkhunter is a rootkit scanner
Here are the results without --quiet
# journalctl -xn
-- Logs begin at Thu 2012-11-01 00:35:38 EET, end at Thu 2014-11-13 16:27:06 EET. --
Nov 13 16:14:07 nucleus.cell.org udisks-daemon[895]: **** REMOVING /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-8/2-8:1.0/host7/target7:0:0/7:0:0:0/block/sdb
Nov 13 16:14:07 nucleus.cell.org udisks-daemon[895]: **** EMITTING REMOVED for /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-8/2-8:1.0/host7/target7:0:0/7:0:0:0/block/sdb
Nov 13 16:14:07 nucleus.cell.org udisks-daemon[895]: **** scsi_host IGNORING REMOVE /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-8/2-8:1.0/host7/scsi_host/host7
Nov 13 16:26:23 nucleus.cell.org udisks-daemon[895]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
Nov 13 16:26:23 nucleus.cell.org udisks-daemon[895]: helper(pid 18433): launched job udisks-helper-ata-smart-collect on /dev/sda
Nov 13 16:26:23 nucleus.cell.org udisks-daemon[895]: helper(pid 18433): completed with exit code 0
Nov 13 16:26:23 nucleus.cell.org udisks-daemon[895]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
Nov 13 16:27:06 nucleus.cell.org systemd[1]: timer_rkhunter.service start operation timed out. Terminating.
Nov 13 16:27:06 nucleus.cell.org systemd[1]: Failed to start Timer script to run rkhunter.
-- Subject: Unit timer_rkhunter.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit timer_rkhunter.service has failed.
-- The result is failed.
Nov 13 16:27:06 nucleus.cell.org systemd[1]: Unit timer_rkhunter.service entered failed state.
# systemctl status timer_rkhunter
● timer_rkhunter.service - Timer script to run rkhunter
Loaded: loaded (/etc/systemd/system/timer_rkhunter.service; static)
Active: failed (Result: timeout) since Thu 2014-11-13 16:27:06 EET; 1min 21s ago
Process: 29377 ExecStart=/usr/bin/rkhunter --cronjob --update (code=killed, signal=TERM)
Main PID: 26027 (code=exited, status=1/FAILURE)
Nov 13 16:27:06 nucleus.cell.org systemd[1]: timer_rkhunter.service start operation timed out. Terminating.
Nov 13 16:27:06 nucleus.cell.org systemd[1]: Failed to start Timer script to run rkhunter.
Nov 13 16:27:06 nucleus.cell.org systemd[1]: Unit timer_rkhunter.service entered failed state.

Storage system verify or repair failed,cannot download system updates,in ColorSynk found 4 bad profiles, in ITunes I still see my old Apple ID. What I can to do ,please identify it for me.

I have changed my Apple ID and may be anything wrong did with Disk Utility.
So , I could not download system updates by normal way and downloaded them from Apple site via Folx and have them installed thus.
I have tried check out condition of Toshiba disk and got messages of errors.
What can I do in this situation?
In Disk Utility:
Storage system verify or repair failed.
Problems were found with the partition map which might prevent booting.
Problems were encountered during repair of partition map
S.M.A.R.T status verified
In ColorSynk Utility:
Searching for profiles...
Checking 64 profiles...
/Library/Application Support/Adobe/Color/Profiles/RedBlueYelllow.icc
   Tag 'pseq': Required tag is not present.
/Library/Application Support/Adobe/Color/Profiles/Smokey.icc
   Tag 'pseq': Required tag is not present.
/Library/Application Support/Adobe/Color/Prosystem ufiles/TealMagentaGold.icc
   Tag 'pseq': Required tag is not present.
/Library/Application Support/Adobe/Color/Profiles/TotalInkPreview.icc
   Tag 'pseq': Required tag is not present.
Verify done - found 4 bad profiles.
In ITunes :
I see my old email as Apple ID
I going to change Lion OS to Mountain Lion OS ,is there any troubles ahead because of problems described above? And how to fix all that ?
Thank you in advance.
Message was edited by: TatianaTia

PS
In Disk Utility all looks so:
Verifying partition map for “TOSHIBA MK5065GSXF Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Checking Core Storage Physical Volume partitions
Checking storage system
Problems were found with the partition map which might prevent booting
Error: Storage system verify or repair failed.Verifying and repairing partition map for “TOSHIBA MK5065GSXF Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Reviewing boot support loaders
Checking Core Storage Physical Volume partitions
Checking storage system
Problems were encountered during repair of the partition map
Error: Storage system verify or repair failed.
I will be greatly appreciated for any considerations or advise (*.*)

Lookup of alternativeServiceIdentifier via CPA-cache failed for channel

Hi,
In RFC(ECC) to File(PI) scenaio i am facing the following error in sender CC:
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel SND_RFC
-CC' (f455868123qq3bba4c3dc3dbf93ed1b, party '', schema 'TechnicalSystem', identifier 'ECC#110')
I have done the following for RFC to File scenario:
ECC side:
1. Created a RFC and tagged it to BAPI
2. In the ABAP program, i am calling the RFC like below:
CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
IN BACKGROUND TASK DESTINATION 'Z_HR_OUTBOUND_DATA2'
EXPORTING
INTERFACE =
IMPORTING
FILENAME = FILENAME
RETURN = RETURN
TABLES
ITAB10 = ITAB10
P_STATUS = P_STATUS
COMMIT WORK.
3. Created a RFC destination using SM59
RFC detination : Z_HR_OUTBOUND_DATA2
Connection type : TCP/IP
Enabled Registered Server Program
Program ID : ECCTOPI_OUTBOUND
Gateway host : ECC's host number
Gateway service : ECC's service number.
In PI side:
I have created :
1 DT for File Rcvr
1 MT for File Rcvr
1 SI for File Rcvr (async)
1 MM (sender RFC and receiver File)
1 OM
1 CC with RFc as sender with the following parameters:
Communication component : ECC's component
application server (gateway) : ecc's gateway
application server service(Gateway) : ecc's service number
Program id : ECCTOPI_OUTBOUND
inital connections 1
max. connections 1
And also gave ecc's details in application server , s/y number, auth. mode, logon user ,
pwd, ecc's client number
1 CC with File adapter and file content conversion
1 receiver determination
1 interface determination
1 sender agreement
1 receiver agreement
When i am executing the ABAP program in R/3 I am getting the following error:
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel SND_RFC
-CC' (f455868123qq3bba4c3dc3dbf93ed1b, party '', schema 'TechnicalSystem', identifier 'ECC#110')
Please let me know if any of my steps are wrong and how to rectify this error and make
the scenario working.
Thanks for your help.

I have mentioned the Adapter specific parameters properly.
It contains :
For ECC s/y(i.e for RFC)
   Logical system : DECCLNT120
   R/3 system ID : DEC
   Client 120
For PI (i.e for File)
   Logical system : DPICLNT100
   R/3 system ID : DPI
   Client 100
Since i am sending the Response of the RFc to the file, i have used a Service interface where i am passing the RFC.Response as Request.
if i am passing the RFC directly as i/p in Source operation of Operation mapping then it doesn't pick up the response in the souce message of the mapping program present in Operation mapping.
So i am passing the same SI_Sender_RFC in the Sender Agreement and it gives the error:
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService 'DEC_RFC', toParty '', toService '', interface 'Z_HR_OUTBOUND_DATA2', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_LOTUSNOTES_OUTBOUND_SND_RFC' (channelId c78f5a88787131a09384c07c2db0e93b)
why is it so?

"senderAgreement not found: lookup of binding via CPA-cache failed for..."

Hi,
     I have configured asynchronous sender RFC to JDBC scenario and when I execute RFC I get short dump "senderAgreement not found: lookup of binding via CPA-cache failed for..."
     My scenario configurations, RFC destination, are all okey..
A Hint:
     Our XI Server is "LARA"
     Our R/3 4.6C Server is "ZULIA"
This are the RFC Sender Communication Channel on LARA:
     RFC Server Parameter
     Application Server (Gateway):           ZULIA
     Application Server Service (Gateway):      sapgw00
     Program ID:                     DEV210
     SNC:                          NOT CHECKED
     UNICODE:                     NOT CHECKED
     Inital Connections:               10
     Maximum Connections:               10
     Advanced Mode:                    NOT CHECKED
     RFC Metada Repository Parameter
     Load Balancing:                NOT CHECKED
     Application Server:               ZULIA
     System Number:                    00
     Authentication Mode:               Use Logon Data for SAP System
     Logon User:                    ldiego
     Logon Password:                    **********
     Logon Language:                    ES
     Logon Client:                    210
     Adapter-Specific Message Attributes
     Set Adapter-Specific Message Attributes: NOT CHECKED
This are the configuration of RFC Destination on ZULIA:
     RFC Destination Name:                XI_RFC
     Connection Type:               T
     ID Program:                    DEV210
     Host Gateway:                    ZULIA
     TCP Service                    sapgw00
Must I create the RFC Destination on the JCo RFC Provider in Visual Administrator?

<i>Is the RFC destination created in the R/3 is pointing correctly to the XI system and vice -versa. Test the connection.</i>
I tested my RFC Destination from R/3 system and the response was successful. What do you mean about vice-versa? How do I test it in the other way?.
I recreate my Sender Agreement. And my Business System is correct.
This are the parameters of my Sender Agreement:
Service:     DES210_DEV
Interface:     Z_DATOS_SAP
Namespace:     urn:sap-com:document:sap:rfc:functions
Sender Communnication Channel: cc_s_rfc_dataCom
When I execute the FM in R/3 the dump now is:
Wrong Sender Agreement:The Sender agreement does not have channel

SLDCHECK fails for XI server - SLD on separate system

Dear All,
I have SLD configured on my solution manager system. All systems including XI are updating data in SLD -> Technical Systems.
My problem
When I execute SXMB_IFR, SLD web page opens up fine. But in transaction log is see following:
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code 4
=> Check whether the SLD is running!
Also, when I try to execute Runtime Workbench, is throws following errors:
5 Message(s) : SLD agent unable to specify domain - Error class com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during communication with System Landscape Directory: User credentials are invalid or user is denied access - Attempt to create JCo connection object failed for domain domain.00.zonexid - Integration Server unable to specify a JCo client - No component names available from Integration Server -
I have checked authorizations for all users, PIRWBUSER, PIAPPLUSER (used in SLDAPICUST) etc, but couldn't solve it.
Post installation, I changed client setting for integration server after client copy and followed "Wizard-based basic configuration" for PI steps.
Can anyone pls point out where I'm failing.
regards, Sean.

Hi,
Can you check this way.
in SMSY_SETUP --> Edit --> Expert Setting
Write Data Back into SLD
SLD Host <hostname>
Namespace in SLD sld/active
SLD Server Port 5??00
Passwort SLD <password>
SLD User XIAPPLUSER
And then schedule the data update again.
If you cannot find the Password SLD field follow the OSS note 757204 report YKSLDPW.
Report YKSLDPW.
TABLES SMSY_OPTIONS.
SMSY_OPTIONS-SYS_OPTION = 'SLD_PW'.
SMSY_OPTIONS-VALUE = 'Ihr SLD_PW'.
SMSY_OPTIONS-VISIBLE = 'X'.
SMSY_OPTIONS-EDITABLE = 'X'.
Modify SMSY_OPTIONS.
Report YKSLDPW helped us to set up an automatic data capture.
Regards,
Srini Nookala

RSYSLOG Dependency failed for System Logging Service [SOLVED]

when i do:
sudo systemctl start rsyslog
i get:
A dependency job for rsyslog.service failed. See 'journalctl -xn' for details.
so #journalctl -xn
jul 06 10:21:14 GA-990FXA-UD3 systemd[1]: Reloading.
jul 06 10:21:22 GA-990FXA-UD3 systemd[1]: Starting Syslog Socket.
-- Subject: Unit syslog.socket has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit syslog.socket has begun starting up.
jul 06 10:21:22 GA-990FXA-UD3 systemd[1]: Socket service syslog.service not loaded, refusing.
jul 06 10:21:22 GA-990FXA-UD3 systemd[1]: Failed to listen on Syslog Socket.
-- Subject: Unit syslog.socket has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Documentation: http://www.freedesktop.org/wiki/Softwar … e9d022f03d
-- Unit syslog.socket has failed.
-- The result is failed.
jul 06 10:21:22 GA-990FXA-UD3 systemd[1]: Dependency failed for System Logging Service.
-- Subject: Unit rsyslog.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Documentation: http://www.freedesktop.org/wiki/Softwar … e9d022f03d
-- Unit rsyslog.service has failed.
-- The result is dependency.
Tried official rsyslog and rsyslog-dev from aur. None of them works. I have checked with rsyslogd -d and stops at line "9430.793770992:7ff79a72d740: Checking pidfile '/var/run/rsyslogd.pid'". I also checked the config file with "rsyslog -f /etc/rsyslog.conf -n 1" and is ok.
Dunno what to do. Totally lost.
Last edited by polito (2013-07-06 23:00:16)

Thanks issue solved by this enabling rsyslog service..
# systemctl enable rsyslog.service
# journalctl -xn
-- The start-up result is done.
Mar 15 12:03:01 XXX CROND[42196]: (root) CMD (/bin/bash /usr/bin/XXX)
Mar 15 12:03:35 XXX systemd[1]: Started System Logging Service.
-- Subject: Unit rsyslog.service has finished start-up

Can't set up static IP with systemd: "Dependency failed for"

I bootstrapped Arch Linux into a free partition from an Ubuntu Server installation. It boots fine, but I can't seem to get the network working.
My router is weird in that the last number of the IP address has to be over 200 (so 192.168.1.[must be over 200]), so dhcpcd won't really work for me and I need to set up a static IP.
To do this, I decided to edit the systemd static IP template from this wiki page (leaving "Wireless" in the name but removing the actual wireless line, as I'm using a wired connection): <https://wiki.archlinux.org/index.php/Ne … IP_address>
Here's my modified script: <http://sprunge.us/BVRA>
However, when I run "systemctl start newnetwork [what I named the service]", I still can't ping either IP addresses or domain names. When I run "systemctl status newnetwork", I get "Dependency failed for Wireless Static IP Connectivity" and it says that the service is not running.
I have all of base and base-devel installed, so what could be the problem? It seems like the only other people who have encountered that systemd error message have had significantly different problems.
For what it's worth, I used this method to bootstrap the system: <https://wiki.archlinux.org/index.php/In … _Archlinux>
Thanks ahead of time for any help.

Welcome to the forums.
You can actually use dhcpcd to assign a static address too with the "-S" option.
My first guess for your error would be that the interface is not "eth0" (though the error message seems odd for that, yes).
Whats the output when you bring the connection up manually (description right above the wiki .service file you link)?

Dbus[359]: [system] Activation via systemd failed for unit 'dbus-org.b

Similar Messages

Maybe you are looking for