[SOLVED]udev doesn't execute my custom rule

Here is my device info:
XSign rules.d # udevadm info -a -n /dev/sdb1
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb/sdb1':
KERNEL=="sdb1"
SUBSYSTEM=="block"
DRIVER==""
ATTR{ro}=="0"
ATTR{size}=="15685569"
ATTR{stat}==" 240 1120 1906 320 0 0 0 0 0 320 320"
ATTR{partition}=="1"
ATTR{start}=="63"
ATTR{discard_alignment}=="0"
ATTR{alignment_offset}=="0"
ATTR{inflight}==" 0 0"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb':
KERNELS=="sdb"
SUBSYSTEMS=="block"
DRIVERS==""
ATTRS{ro}=="0"
ATTRS{size}=="15685632"
ATTRS{stat}==" 255 1123 2050 330 0 0 0 0 0 330 330"
ATTRS{range}=="16"
ATTRS{discard_alignment}=="0"
ATTRS{events}=="media_change"
ATTRS{ext_range}=="256"
ATTRS{events_poll_msecs}=="-1"
ATTRS{alignment_offset}=="0"
ATTRS{inflight}==" 0 0"
ATTRS{removable}=="1"
ATTRS{capability}=="51"
ATTRS{events_async}==""
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0':
KERNELS=="8:0:0:0"
SUBSYSTEMS=="scsi"
DRIVERS=="sd"
ATTRS{rev}=="1.00"
ATTRS{type}=="0"
ATTRS{scsi_level}=="0"
ATTRS{model}=="USB SD Reader "
ATTRS{state}=="running"
ATTRS{queue_type}=="none"
ATTRS{iodone_cnt}=="0x1dd"
ATTRS{iorequest_cnt}=="0x1dd"
ATTRS{timeout}=="30"
ATTRS{evt_media_change}=="0"
ATTRS{max_sectors}=="240"
ATTRS{ioerr_cnt}=="0x2"
ATTRS{queue_depth}=="1"
ATTRS{vendor}=="Generic "
ATTRS{device_blocked}=="0"
ATTRS{iocounterbits}=="32"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0':
KERNELS=="target8:0:0"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8':
KERNELS=="host8"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0':
KERNELS=="1-1.1:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="usb-storage"
ATTRS{bInterfaceClass}=="08"
ATTRS{bInterfaceSubClass}=="06"
ATTRS{bInterfaceProtocol}=="50"
ATTRS{bNumEndpoints}=="02"
ATTRS{supports_autosuspend}=="1"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceNumber}=="00"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1':
KERNELS=="1-1.1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="1.1"
ATTRS{idVendor}=="090c"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="8"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="500mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0100"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="12345678901234567890"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="1264"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Silicon Motion, Inc."
ATTRS{removable}=="removable"
ATTRS{idProduct}=="6200"
ATTRS{bDeviceClass}=="00"
ATTRS{product}=="Generic USB2.0 card "
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1':
KERNELS=="1-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="01"
ATTRS{devpath}=="1"
ATTRS{idVendor}=="8087"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="2"
ATTRS{configuration}==""
ATTRS{bMaxPower}==" 0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="6"
ATTRS{bcdDevice}=="0000"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="130"
ATTRS{ltm_capable}=="no"
ATTRS{removable}=="fixed"
ATTRS{idProduct}=="0020"
ATTRS{bDeviceClass}=="09"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="0"
ATTRS{idVendor}=="1d6b"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{authorized_default}=="1"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{configuration}==""
ATTRS{bMaxPower}==" 0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="3"
ATTRS{bcdDevice}=="0308"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="0000:00:1a.0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="26"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 3.8.3-2-ARCH ehci_hcd"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0002"
ATTRS{bDeviceClass}=="09"
ATTRS{product}=="EHCI Host Controller"
looking at parent device '/devices/pci0000:00/0000:00:1a.0':
KERNELS=="0000:00:1a.0"
SUBSYSTEMS=="pci"
DRIVERS=="ehci-pci"
ATTRS{irq}=="23"
ATTRS{subsystem_vendor}=="0x17aa"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x0c0320"
ATTRS{companion}==""
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="ff"
ATTRS{device}=="0x3b3c"
ATTRS{uframe_periodic_max}=="100"
ATTRS{enable}=="1"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-7"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x2163"
ATTRS{d3cold_allowed}=="1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
and rule:
XSign rules.d # cat 100-usb.rules
KERNEL=="sd*", SUBSYSTEMS=="scsi", ATTRS{model}=="USB SD Reader", SYMLINK+="test_%n", OPTIONS+="all_partitions"
and the test:
XSign rules.d # udevadm test /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb/sdb1
calling: test
version 198
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
=== trie on-disk ===
tool version: 198
file size: 5544030 bytes
header size 80 bytes
strings 1242254 bytes
nodes 4301696 bytes
load module index
Skipping overridden file: /usr/lib/udev/rules.d/80-net-name-slot.rules.
read rules file: /etc/udev/rules.d/01-razer-udev.rules
read rules file: /usr/lib/udev/rules.d/10-dm.rules
read rules file: /usr/lib/udev/rules.d/10-vboxdrv.rules
read rules file: /etc/udev/rules.d/100-usb.rules
read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
read rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
read rules file: /usr/lib/udev/rules.d/40-hpet-permissions.rules
read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
read rules file: /usr/lib/udev/rules.d/50-udev-default.rules
read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
read rules file: /usr/lib/udev/rules.d/60-fprint-autosuspend.rules
read rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
read rules file: /usr/lib/udev/rules.d/60-rfkill.rules
read rules file: /usr/lib/udev/rules.d/60-vboxguest.rules
read rules file: /usr/lib/udev/rules.d/61-accelerometer.rules
read rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
read rules file: /usr/lib/udev/rules.d/64-btrfs.rules
read rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
read rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
IMPORT found builtin 'usb_id --export %p', replacing /usr/lib/udev/rules.d/69-cd-sensors.rules:85
read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
read rules file: /usr/lib/udev/rules.d/70-infrared.rules
read rules file: /usr/lib/udev/rules.d/70-power-switch.rules
read rules file: /usr/lib/udev/rules.d/70-uaccess.rules
read rules file: /usr/lib/udev/rules.d/71-seat.rules
read rules file: /usr/lib/udev/rules.d/73-seat-late.rules
read rules file: /usr/lib/udev/rules.d/75-net-description.rules
read rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
read rules file: /usr/lib/udev/rules.d/75-tty-description.rules
read rules file: /usr/lib/udev/rules.d/78-sound-card.rules
read rules file: /usr/lib/udev/rules.d/80-drivers.rules
read rules file: /etc/udev/rules.d/80-net-name-slot.rules
read rules file: /usr/lib/udev/rules.d/80-udisks.rules
read rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
read rules file: /etc/udev/rules.d/91-fingerprint-gui-upek.rules
read rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
read rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
read rules file: /usr/lib/udev/rules.d/95-keyboard-force-release.rules
read rules file: /usr/lib/udev/rules.d/95-keymap.rules
read rules file: /usr/lib/udev/rules.d/95-udev-late.rules
read rules file: /usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules
read rules file: /usr/lib/udev/rules.d/99-laptop-mode.rules
read rules file: /usr/lib/udev/rules.d/99-systemd.rules
rules contain 49152 bytes tokens (4096 * 12 bytes), 20074 bytes strings
3343 strings (40625 bytes), 2291 de-duplicated (21604 bytes), 1053 trie nodes used
GROUP 6 /usr/lib/udev/rules.d/50-udev-default.rules:40
LINK 'disk/by-id/usb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1' /usr/lib/udev/rules.d/60-persistent-storage.rules:43
LINK 'disk/by-path/pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1' /usr/lib/udev/rules.d/60-persistent-storage.rules:57
IMPORT builtin 'blkid' /usr/lib/udev/rules.d/60-persistent-storage.rules:70
probe /dev/sdb1 raid offset=0
LINK 'disk/by-uuid/1DFC8855338F968C' /usr/lib/udev/rules.d/60-persistent-storage.rules:76
LINK 'disk/by-label/Hacksign\x27s\x20Documents\x20Disk' /usr/lib/udev/rules.d/60-persistent-storage.rules:77
IMPORT 'udisks-part-id /dev/sdb1' /usr/lib/udev/rules.d/80-udisks.rules:84
starting 'udisks-part-id /dev/sdb1'
'udisks-part-id /dev/sdb1' [2444] exit with return code 0
handling device node '/dev/sdb1', devnum=b8:17, mode=0660, uid=0, gid=6
preserve permissions /dev/sdb1, 060660, uid=0, gid=6
preserve already existing symlink '/dev/block/8:17' to '../sdb1'
found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-id\x2fusb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1'
creating link '/dev/disk/by-id/usb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1' to '/dev/sdb1'
preserve already existing symlink '/dev/disk/by-id/usb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1' to '../../sdb1'
found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-label\x2fHacksign\x5cx27s\x5cx20Documents\x5cx20Disk'
creating link '/dev/disk/by-label/Hacksign\x27s\x20Documents\x20Disk' to '/dev/sdb1'
preserve already existing symlink '/dev/disk/by-label/Hacksign\x27s\x20Documents\x20Disk' to '../../sdb1'
found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-path\x2fpci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1'
creating link '/dev/disk/by-path/pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1' to '/dev/sdb1'
preserve already existing symlink '/dev/disk/by-path/pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1' to '../../sdb1'
found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-uuid\x2f1DFC8855338F968C'
creating link '/dev/disk/by-uuid/1DFC8855338F968C' to '/dev/sdb1'
preserve already existing symlink '/dev/disk/by-uuid/1DFC8855338F968C' to '../../sdb1'
ACTION=add
DEVLINKS=/dev/disk/by-id/usb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1 /dev/disk/by-label/Hacksign\x27s\x20Documents\x20Disk /dev/disk/by-path/pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1 /dev/disk/by-uuid/1DFC8855338F968C
DEVNAME=/dev/sdb1
DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb/sdb1
DEVTYPE=partition
ID_BUS=usb
ID_DRIVE_FLASH_SD=1
ID_FS_LABEL=Hacksign_s_Documents_Disk
ID_FS_LABEL_ENC=Hacksign\x27s\x20Documents\x20Disk
ID_FS_TYPE=ntfs
ID_FS_USAGE=filesystem
ID_FS_UUID=1DFC8855338F968C
ID_FS_UUID_ENC=1DFC8855338F968C
ID_INSTANCE=0:0
ID_MODEL=USB_SD_Reader
ID_MODEL_ENC=USB\x20\x20SD\x20Reader\x20\x20
ID_MODEL_ID=6200
ID_PART_ENTRY_DISK=8:16
ID_PART_ENTRY_NUMBER=1
ID_PART_ENTRY_OFFSET=63
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_SIZE=15685569
ID_PART_ENTRY_TYPE=0x87
ID_PART_TABLE_TYPE=dos
ID_PATH=pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0
ID_PATH_TAG=pci-0000_00_1a_0-usb-0_1_1_1_0-scsi-0_0_0_0
ID_REVISION=1.00
ID_SERIAL=Generic_USB_SD_Reader_12345678901234567890-0:0
ID_SERIAL_SHORT=12345678901234567890
ID_TYPE=disk
ID_USB_DRIVER=usb-storage
ID_USB_INTERFACES=:080650:
ID_USB_INTERFACE_NUM=00
ID_VENDOR=Generic
ID_VENDOR_ENC=Generic\x20
ID_VENDOR_ID=090c
MAJOR=8
MINOR=17
SUBSYSTEM=block
TAGS=:systemd:
UDISKS_PARTITION=1
UDISKS_PARTITION_ALIGNMENT_OFFSET=0
UDISKS_PARTITION_NUMBER=1
UDISKS_PARTITION_OFFSET=32256
UDISKS_PARTITION_SCHEME=mbr
UDISKS_PARTITION_SIZE=8031011328
UDISKS_PARTITION_SLAVE=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb
UDISKS_PARTITION_TYPE=0x87
UDISKS_PRESENTATION_NOPOLICY=0
USEC_INITIALIZED=7735553
It seems that 100-usb.rules doesn't be executed~
Am I anywhere wrong ?
Last edited by Hacksign (2013-04-09 02:15:13)

Pasted another example of my usb sd card reader.
there is no test_X symbol link in /dev/ directory after i un-pluged sd card reader and re-pluged it in on my computer
oh, I use systemd of course:
XSign rules.d # cat /boot/grub/menu.lst
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/disk/by-label/root resume=/dev/sda7 ro vga=0x361 init=/usr/lib/systemd/systemd quiet
initrd /boot/kernel26.img
Hacksign wrote:
brebs wrote:You're mixing the hierarchy levels (i.e. subsystems) - can't do that. See working example.
no, I dont think I mixed te hierarchy level.
SUBSYSTEM=="input" matched '/devices/platform/i8042/serio1/serio2/input/input24/mouse2'
and
SUBSYSTEMS=="usb", ATTR{idVendor}=="1532",
matched its parent
and I'm so sorry that I pasted a wrong device tree...
sorry

Similar Messages

[Solved] udev won't trig my simple rule (jscal gamepad calibration)

Hello,
I want the system to automatically calibrate my gamepad whenever I plug it in. As adviced in the Wiki (https://wiki.archlinux.org/index.php/Ga … alibration), I've written a udev rule:
florian@flobox:~$ cat /etc/udev/rules.d/85-jscal.rules
SUBSYSTEM=="input", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="028e", ATTRS{serial}=="1E6674E", ACTION=="add", RUN+="jscal -s 8,1,0,-5000,4500,19423,19078,1,0,-5500,128,19781,16513,1,0,127,127,4227201,4227201,1,0,-4000,5500,18745,19781,1,0,-3000,3000,18113,18113,1,0,127,127,4227201,4227201,1,0,0,0,536854528,536854528,1,0,0,0,536854528,536854528 /dev/input/by-id/usb-©Microsoft_Corporation_Controller_1E6674E-joystick"
It seems udev doesn't run the jscal command as my gamepad isn't calibrated when I plug in it.
The attributes seem correct though:
florian@flobox:~$ udevadm info --attribute-walk --name /dev/input/by-id/usb-©Microsoft_Corporation_Controller_1E6674E-joystick
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input15/js0':
KERNEL=="js0"
SUBSYSTEM=="input"
DRIVER==""
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input15':
KERNELS=="input15"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{name}=="Microsoft X-Box 360 pad"
ATTRS{phys}=="usb-0000:00:1a.0-1.1/input0"
ATTRS{uniq}==""
ATTRS{properties}=="0"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0':
KERNELS=="1-1.1:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="xpad"
ATTRS{bInterfaceClass}=="ff"
ATTRS{bInterfaceSubClass}=="5d"
ATTRS{bInterfaceProtocol}=="01"
ATTRS{bNumEndpoints}=="02"
ATTRS{supports_autosuspend}=="0"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceNumber}=="00"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1':
KERNELS=="1-1.1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="ff"
ATTRS{bDeviceProtocol}=="ff"
ATTRS{devpath}=="1.1"
ATTRS{idVendor}=="045e"
ATTRS{speed}=="12"
ATTRS{bNumInterfaces}==" 4"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="8"
ATTRS{busnum}=="1"
ATTRS{devnum}=="3"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="500mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="a0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0114"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="1E6674E"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="1081"
ATTRS{ltm_capable}=="no"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="028e"
ATTRS{bDeviceClass}=="ff"
ATTRS{product}=="Controller"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1':
KERNELS=="1-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="01"
ATTRS{devpath}=="1"
ATTRS{idVendor}=="8087"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="2"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="6"
ATTRS{bcdDevice}=="0000"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="50"
ATTRS{ltm_capable}=="no"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0020"
ATTRS{bDeviceClass}=="09"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="0"
ATTRS{idVendor}=="1d6b"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{authorized_default}=="1"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="2"
ATTRS{bcdDevice}=="0314"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="0000:00:1a.0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="24"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 3.14.43-2-lts ehci_hcd"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0002"
ATTRS{bDeviceClass}=="09"
ATTRS{product}=="EHCI Host Controller"
looking at parent device '/devices/pci0000:00/0000:00:1a.0':
KERNELS=="0000:00:1a.0"
SUBSYSTEMS=="pci"
DRIVERS=="ehci-pci"
ATTRS{irq}=="16"
ATTRS{subsystem_vendor}=="0x1043"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x0c0320"
ATTRS{companion}==""
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000000f"
ATTRS{device}=="0x3b3c"
ATTRS{uframe_periodic_max}=="100"
ATTRS{enable}=="1"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-3"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x8383"
ATTRS{numa_node}=="-1"
ATTRS{d3cold_allowed}=="1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
I must be missing something basic. I've even tried and removed all the attributes, but it didn't help.
What did I do wrong?
Last edited by monsieur moche (2015-06-09 20:43:32)

You didn't follow the rules.
udev(7) wrote: RUN{type}
Add a program to the list of programs to be executed after processing all the rules for a specific event, depending on "type":
"program"
Execute an external program specified as the assigned value. If no absolute path is given, the program is expected to live in /usr/lib/udev; otherwise, the absolute path must be specified.
This is the default if no type is specified.

[Solved] udev rules: serial for persistent device naming disappeared

Hello,
since the latest upgrade of udev and kmod I cant't mount my external e-SATA hard disk with my working udev rules.
This is my udev rule:
$ cat /etc/udev/rules.d/66-persistent_esata.rules
KERNEL=="sd?1", SUBSYSTEMS=="block", ENV{ID_SERIAL_SHORT}=="S1VSJ1LS301247", NAME="aluguard"
When plugged in, I could decrypt and mount it with "sudo cryptsetup luksOpen /dev/aluguard aluguard && mount /mnt/aluguard".
Since the update above I get "Device /dev/aluguard doesn't exist or access denied."
While I re-checked https://wiki.archlinux.org/index.php/Ma … _with_udev, I discovered, that the serial entry in the output of udevadm has vanished:
$ udevadm info -a -p $(udevadm info -q path -n /dev/sdg)
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg':
KERNEL=="sdg"
SUBSYSTEM=="block"
DRIVER==""
ATTR{range}=="16"
ATTR{ext_range}=="256"
ATTR{removable}=="0"
ATTR{ro}=="0"
ATTR{size}=="1953525168"
ATTR{alignment_offset}=="0"
ATTR{discard_alignment}=="0"
ATTR{capability}=="50"
ATTR{stat}==" 96 24 762 780 0 0 0 0 0 780 780"
ATTR{inflight}==" 0 0"
ATTR{events}==""
ATTR{events_async}==""
ATTR{events_poll_msecs}=="-1"
looking at parent device '/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0':
KERNELS=="3:0:0:0"
SUBSYSTEMS=="scsi"
DRIVERS=="sd"
ATTRS{device_blocked}=="0"
ATTRS{type}=="0"
ATTRS{scsi_level}=="6"
ATTRS{vendor}=="ATA "
ATTRS{model}=="SAMSUNG HD103SI "
ATTRS{rev}=="1AG0"
ATTRS{state}=="running"
ATTRS{timeout}=="30"
ATTRS{iocounterbits}=="32"
ATTRS{iorequest_cnt}=="0xa2"
ATTRS{iodone_cnt}=="0x98"
ATTRS{ioerr_cnt}=="0xc"
ATTRS{evt_media_change}=="0"
ATTRS{queue_depth}=="31"
ATTRS{queue_ramp_up_period}=="120000"
ATTRS{queue_type}=="simple"
looking at parent device '/devices/pci0000:00/0000:00:09.0/host3/target3:0:0':
KERNELS=="target3:0:0"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:09.0/host3':
KERNELS=="host3"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:09.0':
KERNELS=="0000:00:09.0"
SUBSYSTEMS=="pci"
DRIVERS=="ahci"
ATTRS{vendor}=="0x10de"
ATTRS{device}=="0x0554"
ATTRS{subsystem_vendor}=="0x1849"
ATTRS{subsystem_device}=="0x0554"
ATTRS{class}=="0x010601"
ATTRS{irq}=="23"
ATTRS{local_cpus}=="00000000,00000003"
ATTRS{local_cpulist}=="0-1"
ATTRS{numa_node}=="0"
ATTRS{dma_mask_bits}=="64"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{enable}=="1"
ATTRS{broken_parity_status}=="0"
ATTRS{msi_bus}==""
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
What is the reason for this strange behaviour, and how can I get back the serial entry?
Thank in advance!
Last edited by indianahorst (2012-01-31 13:03:20)

$ udevadm info -q all -n /dev/sdg1
P: /devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg/sdg1
N: sdg1
S: disk/by-id/ata-SAMSUNG_HD103SI_S1VSJ1LS301247-part1
S: disk/by-id/scsi-SATA_SAMSUNG_HD103SIS1VSJ1LS301247-part1
S: disk/by-id/wwn-0x50024e900136a03e-part1
S: disk/by-path/pci-0000:00:09.0-scsi-3:0:0:0-part1
S: disk/by-uuid/bb024e1b-78a5-4ed0-9e80-aaa7633aa493
E: DEVLINKS=/dev/disk/by-id/ata-SAMSUNG_HD103SI_S1VSJ1LS301247-part1 /dev/disk/by-id/scsi-SATA_SAMSUNG_HD103SIS1VSJ1LS301247-part1 /dev/disk/by-id/wwn-0x50024e900136a03e-part1 /dev/disk/by-path/pci-0000:00:09.0-scsi-3:0:0:0-part1 /dev/disk/by-uuid/bb024e1b-78a5-4ed0-9e80-aaa7633aa493
E: DEVNAME=/dev/sdg1
E: DEVPATH=/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg/sdg1
E: DEVTYPE=partition
E: ID_ATA=1
E: ID_ATA_DOWNLOAD_MICROCODE=1
E: ID_ATA_FEATURE_SET_AAM=1
E: ID_ATA_FEATURE_SET_AAM_CURRENT_VALUE=254
E: ID_ATA_FEATURE_SET_AAM_ENABLED=1
E: ID_ATA_FEATURE_SET_AAM_VENDOR_RECOMMENDED_VALUE=254
E: ID_ATA_FEATURE_SET_APM=1
E: ID_ATA_FEATURE_SET_APM_ENABLED=0
E: ID_ATA_FEATURE_SET_HPA=1
E: ID_ATA_FEATURE_SET_HPA_ENABLED=1
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_PUIS=1
E: ID_ATA_FEATURE_SET_PUIS_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=194
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=194
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_SATA=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=1
E: ID_BUS=ata
E: ID_FS_TYPE=crypto_LUKS
E: ID_FS_USAGE=crypto
E: ID_FS_UUID=bb024e1b-78a5-4ed0-9e80-aaa7633aa493
E: ID_FS_UUID_ENC=bb024e1b-78a5-4ed0-9e80-aaa7633aa493
E: ID_FS_VERSION=1
E: ID_MODEL=SAMSUNG_HD103SI
E: ID_MODEL_ENC=SAMSUNG\x20HD103SI\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_PART_ENTRY_TYPE=0x83
E: ID_PART_TABLE_TYPE=dos
E: ID_PATH=pci-0000:00:09.0-scsi-3:0:0:0
E: ID_PATH_TAG=pci-0000_00_09_0-scsi-3_0_0_0
E: ID_REVISION=1AG01131
E: ID_SCSI_COMPAT=SATA_SAMSUNG_HD103SIS1VSJ1LS301247
E: ID_SERIAL=SAMSUNG_HD103SI_S1VSJ1LS301247
E: ID_SERIAL_SHORT=S1VSJ1LS301247
E: ID_TYPE=disk
E: ID_WWN=0x50024e900136a03e
E: ID_WWN_WITH_EXTENSION=0x50024e900136a03e
E: MAJOR=8
E: MINOR=97
E: PART_ENTRY_DISK=8:96
E: PART_ENTRY_NUMBER=1
E: PART_ENTRY_OFFSET=63
E: PART_ENTRY_SCHEME=dos
E: PART_ENTRY_SIZE=1953520002
E: SUBSYSTEM=block
E: UDEV_LOG=3
E: UDISKS_PARTITION=1
E: UDISKS_PARTITION_ALIGNMENT_OFFSET=0
E: UDISKS_PARTITION_NUMBER=1
E: UDISKS_PARTITION_OFFSET=32256
E: UDISKS_PARTITION_SCHEME=mbr
E: UDISKS_PARTITION_SIZE=1000202241024
E: UDISKS_PARTITION_SLAVE=/sys/devices/pci0000:00/0000:00:09.0/host3/target3:0:0/3:0:0:0/block/sdg
E: UDISKS_PARTITION_TYPE=0x83
E: UDISKS_PRESENTATION_NOPOLICY=0
E: USEC_INITIALIZED=6897248001
OK, there is the serial.... but the problem persists - udev doesn't execute the rule and doesn't create /dev/aluguard.

[SOLVED] udev rules: cannot run command

I want to run a scipt everytime I plug in my external harddrive. I read the documentation and create a file called /etc/udev/rules.d/extern_hd.rules:
SUBSYSTEMS=="usb", SYSFS{serial}=="33504D315647585A", SYMLINK+="ExternHD", RUN+="/root/scripts/test.sh"
The symlink "ExternHD" gets created. The permissions of test.sh are rwxr-xr-x root root, but it never gets executed. What am I doing wrong?
Last edited by Kei (2007-09-18 11:30:35)

Solution was easy... Udev doesn't want to start anything from within /root, so I put a hardlink to /usr/local/bin/ and now everything works fine.

Udev problems still - 060-3 won't process my custom rules

Following the problems with 060-1, I went back to 058-4 - everything was fine, as expected. When I saw 060-2 and then 060-3 in current, I figured I'd give it another shot. It looked fine initially i.e. it didn't break my network. However, none of my custom rules for USB devices are working under 060-3.
So I'm back to 058-4 - and everything's fine again.

i have two rules files in /etc/udev/rules.d :
00-perso.rules
10-udev.rules
all my usb stick rules are in my perso files.
even if the pero file should be treated first, my usb sticks and ipod were not detected and treated according to my perso rules.
I had to comment out most of the scsi rules in 10-udev.rules for it to work:
# scsi block devices
#BUS="scsi", KERNEL="sd[a-z]", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
#BUS="scsi", KERNEL="sd[a-z][0-9]*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
#BUS="scsi", KERNEL="sd[a-i][a-z]", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
#BUS="scsi", KERNEL="sd[a-i][a-z][0-9]*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
#BUS="scsi", KERNEL="s[grt][0-9]*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
#BUS="scsi", KERNEL="scd[0-9]*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
#BUS="scsi", KERNEL="st[0-9]*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
#BUS="scsi", KERNEL="nst[0-9]*", PROGRAM="/etc/udev/scripts/scsi-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
only after that my usb sticks were detected and processed by udev with my own rules.
I just installed ARCH for the first time a few days ago so i don't know if this problem was due to the new udev version or not.
hope this helps

[SOLVED]udev: execute command on usb unplug (em28xx_dvb WinTV_HVR-900)

Hi all.
I've a known bug with a dvbt usb device.
The problem is that if i unplug and replug it, em28xx_dvb module hangs in dvb_init() and a reboot is needed to use the device again.
A manual workaround exists, it is sufficient to rmmod em28xx_dvb before replug the device again, but if i forgot it, i'm f*****
So here comes a question:
Does udev reacts to the unplug event? and if yes, how can i trigger the action of removing that module?
I'm a little noob with udev rules, so please be patient and thanks!
Last edited by kokoko3k (2011-05-17 11:52:33)

I got it working; if anyone cares, here's the udev rule:
ACTION=="remove", SUBSYSTEM=="usb", ENV{ID_MODEL}=="WinTV_HVR-900", RUN+="/sbin/rmmod em28xx_dvb"
ENV{ID_MODEL}=="WinTV_HVR-900" is the key, my previous attempts to use ATTR{product}=="WinTV HVR-900" failed because it seems that udev doesn't trig any event on device removal (works on device plug),
while it does using id_model.
-EDIT-
If anyone uses this device, here's other tricks i made to make it work (without ir):
#> cat /etc/modprobe.d/tv.conf
options em28xx disable_ir=1
#> cat /etc/udev/rules.d/50-WinTv.rules
ACTION=="remove", SUBSYSTEM=="usb", ENV{ID_MODEL}=="WinTV_HVR-900", RUN+="/sbin/rmmod em28xx_dvb""
Before hibernation:
# rmmod em28xx_dvb em28xx dvb_core tuner tvp5150 v4l2_common videodev videobuf_vmalloc videobuf_core tveeprom zl10353 ir_lirc_codec lirc_dev ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder rc_core tuner_xc2028
On resume from hibernation:
# hwdetect --load-modules
...man, it wasnt 'easy'
Last edited by kokoko3k (2011-05-17 12:08:16)

CPS-Job - Reply on Console doesn't execute the chosen action

Dear Developers
We have a job chain in which we have as default postcondition "On Error
Action CONSOLE RESTART". Now we have a step on status CONSOLE but a
reply doesn't execute the chosen action. This is not the first time we
experience this behaviour.
Any ideas to solve that problem or any workaround?
Regards,
Stephan Gross, RAIcps
Here our system info:
DB-Version Info:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Productio
NLSRTL Version 10.2.0.4.0 - Production
Redwood-Repository Info:
JCS Object Database,7.0.3.33
JCS Modules,7.0.3
JCS PM4W,7.0.3
JCS Redwood &module Module,7.0.2

Hello Stephan,
7.0.3.33 has a known issue where the reply of console is not always carried out.
If this is the same issue as you are experiencing, then the issue is solved in patch 7.0.3.38.
I would advise you to create an OSS message to have checked if this is indeed the same issue.
Kind regards,
Miek

WS20000050 - Custom rule in step 372 - Error during execution

I have attached a custom rule in Step 372 of workflow WS20000050
WS20000050 works fine with standard rule (168)
Custom rule is tested and simulated and it returns the Person 'P' and User 'US'
WS20000050 genarates fine with no errors (4 information only)
Errors after execution in SWIA is
Error when processing node '0000000372' (ParForEach index 000000)
Error when creating a component of type 'Step'
Error when creating a work item
Agent determination for step '0000000372' failed
Error in resolution of rule 'AC92000002' for step '0000000372'
Element OBJID is not available in the container
next node in error
Work item 000000426198: Object FLOWITEM method EXECUTE cannot be executed
Error when processing node '0000000372' (ParForEach index 000000)
I tried to delete OBJID from the binding for the rule but the same error repeats
Any help is appreciated

Element OBJID is not available in the container
Make proper binding from workflow to rule, the value OBJID is not reaching the rule conatiner.
Error in resolution of rule 'AC92000002' for step '0000000372'
Rule is not returning any agent chek that?

OLSP not working for custom rule criteria to filter BWKEY

Hi,
I am using PC10.0.
I created a rule criteria for BWKEY values and assigned. I assigned it the table T001K and the connector to the target system.
I then assigned it to custom made OLSP. However when the results come out, it doesn't consider the values I entered within the filter for BWKEY.
The filters for the rule criteria that I created don't work. However the filters for the SAP provided rule criteria; 'COMPANY CODE' works.
The tables in my configurable subscenario include MBEW and T001K, both of which have BWKEY. The business rules don't use the same filters as that of the OLSP.
I can't find any error. The OLSP filter just doesn't want to work when I run the job. Certain BWKEY records within MBEW remain within the job results.
I've attached images of the rule criteria.
What could be the problem and how can I resolve it?
Thank you.

Based from what I've found, OLSP seems to only work for:
Sales Org
Plant
Company Code
Purchase Org.
Is there an SAP note that can be used to get OLSP created from custom rule criteria to work in PC10.0?

OTL Time Card Explosion based on custom rules

Hi,
I am working on a customization in which the users are setting up some custom rules thru some custom form. They want the Time card to be exploded based on these rules.
Can someone please suggest me some API which i can use to explode the time card. And also does this explosion move the data to HXT tables ?
would I need to run the transfer to BEE program? or the API would automatically move the data to BEE.
Thanks
PS

Hi,
I will answering your doubts no 3 and 4
Instead of using XML template, I would suggest you to use WED Adi, which can be called from the OTL page
button. And at that time the only thing u have to upload server with the WebAdi template.
Here you will not need to build a custom table, a view will solve the purpose. And there is not need of further maintenance
For the file to be read only you can include it in the code while extending your respective controller class.
But Oracle recommend not to extend controller class. Let the client be aware of it, that it requires the extension
of controller class of the page. If he thumps up the extension of controller class then your life becomes pretty simple.
Regards,
Pankaj Kedia

Action doesn't execute in player

In the app I'm working on (AS 2.0) I have several buttons. I've added an action to each of those buttons:
on (release)
gotoAndPlay("fr_test");
When in Flash, if I enable (Control) Simple Buttons and Simple Actions, this action works like it should. If I test the movie or publish it, the action doesn't execute.
I've tried another approach with one button. I added an empty layer for actions only, and added the following code:
this.test_btn.onRelease=function()
gotoAndPlay("fr_test");
This doesn't work at all, nor in Flash nor in the player. I wonder what I'm doing wrong here. Changing fr_test to the frame number does not change anything.

I solved this by starting over with a new flash app. I created buttons and actions, and they worked like I wanted. Then I tried to apply this on the old movie, but that didn't work. So I recreated the movie in the new app. I'm using some very complex drawings, and I messed around quite a bit. I don't know where it went wrong, but it works now for me.

Doesn't execute my user exit codes.

Hello Experts,
I have created user exit ZXF05U01 to validate Tax Number1 field and activated. (txn fk02)
Then Execute the transaction CMOD.
Created a project ZFIAPVEN
In "Enhancement assignments" added SAPMF02K as enhancement.
Saved it.
Then in the initial screen of cmod I've activated the project.
Doesn't execute 'MODULE EXIT_KREDITOR AT EXIT-COMMAND.' When I ran the txn fx02 in debug mode it.
Regards
Naz

I think I took the wrong path to validate the New Zealand specific tax number. Is it possible to set some rules in PRST1_005 in table T005.
If this is possible then please pass me the steps description.
Thanks.
Naz

Custom Rule - Problem in passin values From Rule Container to WF Container?

Hi Guys,
I am having hard time passing values back from my custom rule. I have created a custom rule to determine the agents in PFAC which takes in the Person number as import element of container. It determines the Manager as agent and I am passing Managers Person Number back to workflow. If he dont approve the Request then it will be passed to his boss. In this case I will pass this imported Mangers Person number back to rule so that his boss will be determined as agent. I have created ZRULE function module. I am passing value back from Rule container to Workflow Container using following code.
swc_set_element ac_container 'SUPERPERNR' lf_super_pernr.
I have created a element SUPERPERNR on rule container and workflow container as well .The problem is in the Rule container I am not able to create SUPERPERNR as export parameter. The tick mark is grayed out and there is no option for setting it as export.
My question is do I have create a Export element on Rule container or Not? If i just write the code
( swc_set_element ac_container 'SUPERPERNR' lf_super_pernr ) will it set the value in WF container? In my case it is not setting. I have to bind the values from rule container to WF container and if My rule container element is not allowing me to click the tick mark as export how can i pass value of of rule container back to WF Container?
Please help me guys.
Thanks,
Manish.

Hi Manish,
     Same scenario I have developed in my system. This all steps I did in my system.
1) Created a Z function module which takes import parameter (Parameter name = 'EMP') in the
    format 'US100123'.
2) This in turn fetches back the supevisor or boss as an export parameter (Parameter name = 'BOSS') in
     the format 'US100245'.
3) This function module is attached to a BUS object(SWO1).
4) While attaching this function module to BUS object you need not do any manual coding it is done
    automatically.
5) Implement, release and generate this BUS object.
6) Create a new variable in your workflow (Parameter name = 'ZSUPERVISOR') for storing the value
    which is returned by the Z method.
7) Create a new task.
8) Put in your BUS object name, then your Z method name, select background processing checkbox.
9) Press save, it will ask for transfer of missing elements, select yes.
10) Then you will see a green button below your Z method name click on it.
11) Top portion contains your Z method variables, below to it you have the import parameter window in
      this window you should have &EMP& -> &EMP&., below to import parameter window you have
      export parameter window in this window you should have &BOSS& <- &BOSS&. (This is method
      binding).
12) Now click on enter button then click on back button it will generate the task binding automatically
     just press yes.
13) Now click on binding exist button.
14) Here you have the Workflow container variables as well as the system container variables.
15) In the import parameter window left portion is for your workflow variables and right portion is for your
      method variables. In my case i had sent workflow initiator and fetched his supervisor. The Import
      parameter binding was &WF_INTIATOR& -> &EMP&. and the export parameter binding part was
      &ZSUPERVISOR& <- &BOSS&.
16) Save the task and run the workflow.
Regards.
Vaibhav Patil.

Error during Portal Setup: An error occurred while executing a custom action:_GrantLocalPermissionsToWCSAccount

Error:
Configure Portal Setup
An error occurred while executing a custom action:_GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6
This upgrade attempt has failed before permanent modifications were made. Upgrade has successfully rolled back to the original state of the system. Once the correction are made, you can retry upgrade for this role.
Errors in the Log:
MSI (s) (38:14) [21:30:36:094]: NOTE: custom action _GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6 unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
CustomAction _GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (38:94) [21:30:36:115]: User policy value 'DisableRollback' is 0
MSI (s) (38:14) [21:30:36:094]: NOTE: custom action _GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6 unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
CustomAction _GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (38:94) [21:30:36:115]: User policy value 'DisableRollback' is 0
I cannot get past this error. I am running Sharepoint Foundation 2010 with Sp1. This is on a Windows Server 2008 R2 Server +Sp1.
Any ideas?
David Baur

I finally figured this out, The issue was that I had put in the Self Service Portal Computer Name and Service account into the Service Manager SQL as SysAdmin, once I removed it flew through just fine.
David Baur

SCSM2012 Beta installation problem: An error occurred while executing a custom action:_PopulateUserRoles

I'm installing the SCSM2012 Management Server
component on a SQL dev box. During the installation, the very last step (Import Management Packs) fails with this error:
An error occurred while executing a custom action:_PopulateUserRoles
This upgrade attempt has failed before permanent modifications were made. Upgrade has successfully rolled back to the original state of the system. Once the correction are made, you can retry upgrade for this role.
I've already verified that the account I'm logged in with has SA access to the SQL database. Windows 2008 R2 firewall is turned off.....
Has anybody else run into this problem?

I don't see anything indicative in the setup log. The setup seems to get all the way to the part where it installs the management packs. Then right after that is when the installation fails and it rolls back.
From the setup log, towards the end:
Property(S): ACTIONSUSER = NETWORK SERVICE
Property(S): ACTIONSDOMAIN = NT AUTHORITY
Property(S): ACTIONSUSER_FOR_DB = NETWORK SERVICE
Property(S): ACTIONSDOMAIN_FOR_DB = NT AUTHORITY
Property(S): SOURCEDIR = C:\SCSM\SCSM2012_Beta\Setup\Server\
Property(S): SourcedirProduct = {295201AE-EAB6-416C-8252-7C065243EF55}
Property(S): ProductToBeRegistered = 1
MSI (s) (9C:54) [17:33:22:951]: Note: 1: 1708
MSI (s) (9C:54) [17:33:22:951]: Product: Microsoft System Center Service Manager 2012 -- Installation failed.
MSI (s) (9C:54) [17:33:22:959]: Windows Installer installed the product. Product Name: Microsoft System Center Service Manager 2012. Product Version: 7.5.1354.0. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status:
1603.
MSI (s) (9C:54) [17:33:23:010]: Deferring clean up of packages/files, if any exist
MSI (s) (9C:54) [17:33:23:013]: MainEngineThread is returning 1603
MSI (s) (9C:20) [17:33:23:061]: RESTART MANAGER: Session closed.
MSI (s) (9C:20) [17:33:23:061]: No System Restore sequence number for this installation.
=== Logging stopped: 11/7/2011 17:33:22 ===
MSI (s) (9C:20) [17:33:23:065]: User policy value 'DisableRollback' is 0
MSI (s) (9C:20) [17:33:23:065]: Machine policy value 'DisableRollback' is 0
MSI (s) (9C:20) [17:33:23:065]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (9C:20) [17:33:23:065]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (9C:20) [17:33:23:066]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (9C:20) [17:33:23:067]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (9C:20) [17:33:23:067]: Restoring environment variables
MSI (s) (9C:20) [17:33:23:089]: Destroying RemoteAPI object.
MSI (s) (9C:28) [17:33:23:089]: Custom Action Manager thread ending.
MSI (c) (C8:B4) [17:33:23:144]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (C8:B4) [17:33:23:175]: MainEngineThread is returning 1603
=== Verbose logging stopped: 11/7/2011 17:33:23 ===

[SOLVED]udev doesn't execute my custom rule

Similar Messages

Maybe you are looking for