Hi Vasant, > Aug 9 01:28:43 abc systemd-udevd[19870]: Process '/bin/touch /var/lib/lsvpd/run.vpdupdate' failed with exit code 1.
What does the filesystem layout look like on this system? Is it possible that you see this failing because it's running before /var/lib is mounted? Alternatively, is it possible that it's being run while the root filesystem is still mounted read only? If you need to write a file during early boot before the filesystem is guaranteed to be set up, it would be better to use /run for this instead of /var/lib. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1682774 Title: [systemd-udevd] Process '/bin/touch /var/lib/lsvpd/run.vpdupdate' failed with exit code 1 Status in systemd package in Ubuntu: New Bug description: == Comment: VASANT HEGDE <hegdevas...@in.ibm.com> - 2017-04-13 11:14:43 == Problem description : systemd-udevd daemon failed to execute udev rules. Aug 9 01:28:43 abc systemd-udevd[19870]: Process '/bin/touch /var/lib/lsvpd/run.vpdupdate' failed with exit code 1. Rules file : ----------- root@abc:/lib/udev/rules.d# cat 60-libvpd-2.2-2.rules KERNELS=="*", ACTION=="*", DEVPATH=="/devices/*", RUN+="/bin/touch /var/lib/lsvpd/run.vpdupdate" If I restart the systemd-udevd daemon then it works fine. - systemctl restart systemd-udevd journalctl -u systemd-udevd -- Logs begin at Wed 2017-04-12 07:19:26 CDT, end at Thu 2017-04-13 11:11:16 CDT. -- Apr 12 07:19:26 w37l systemd[1]: Starting udev Kernel Device Manager... Apr 12 07:19:27 w37l systemd[1]: Started udev Kernel Device Manager. Apr 12 07:19:27 w37l systemd-udevd[544]: Process '/bin/touch /var/lib/lsvpd/run.vpdupdate' failed with exit code 1 systemctl show systemd-udevd Type=notify Restart=always NotifyAccess=main RestartUSec=0 TimeoutStartUSec=1min 30s TimeoutStopUSec=1min 30s RuntimeMaxUSec=infinity WatchdogUSec=3min WatchdogTimestamp=Thu 2017-04-13 10:56:39 CDT WatchdogTimestampMonotonic=57706791 FailureAction=none PermissionsStartOnly=no RootDirectoryStartOnly=no RemainAfterExit=no GuessMainPID=yes MainPID=489 ControlPID=0 FileDescriptorStoreMax=0 NFileDescriptorStore=0 StatusText=Processing with 72 children at max StatusErrno=0 Result=success UID=4294967295 GID=4294967295 ExecMainStartTimestamp=Wed 2017-04-12 07:19:26 CDT ExecMainStartTimestampMonotonic=4652319 ExecMainExitTimestampMonotonic=0 ExecMainPID=489 ExecMainCode=0 ExecMainStatus=0 ExecStart={ path=/lib/systemd/systemd-udevd ; argv[]=/lib/systemd/systemd-udevd ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 } Slice=system.slice ControlGroup=/system.slice/systemd-udevd.service MemoryCurrent=18446744073709551615 CPUUsageNSec=18446744073709551615 TasksCurrent=1 Delegate=no CPUAccounting=no CPUWeight=18446744073709551615 StartupCPUWeight=18446744073709551615 CPUShares=18446744073709551615 StartupCPUShares=18446744073709551615 CPUQuotaPerSecUSec=infinity IOAccounting=no IOWeight=18446744073709551615 StartupIOWeight=18446744073709551615 BlockIOAccounting=no BlockIOWeight=18446744073709551615 StartupBlockIOWeight=18446744073709551615 MemoryAccounting=no MemoryLow=0 MemoryHigh=18446744073709551615 MemoryMax=18446744073709551615 MemorySwapMax=18446744073709551615 MemoryLimit=18446744073709551615 DevicePolicy=auto TasksAccounting=yes TasksMax=18446744073709551615 UMask=0022 LimitCPU=18446744073709551615 LimitCPUSoft=18446744073709551615 LimitFSIZE=18446744073709551615 LimitFSIZESoft=18446744073709551615 LimitDATA=18446744073709551615 LimitDATASoft=18446744073709551615 LimitSTACK=18446744073709551615 LimitSTACKSoft=8388608 LimitCORE=18446744073709551615 LimitCORESoft=0 LimitRSS=18446744073709551615 LimitRSSSoft=18446744073709551615 LimitNOFILE=4096 LimitNOFILESoft=1024 LimitAS=18446744073709551615 LimitASSoft=18446744073709551615 LimitNPROC=372260 LimitNPROCSoft=372260 LimitMEMLOCK=65536 LimitMEMLOCKSoft=65536 LimitLOCKS=18446744073709551615 LimitLOCKSSoft=18446744073709551615 LimitSIGPENDING=372260 LimitSIGPENDINGSoft=372260 LimitMSGQUEUE=819200 LimitMSGQUEUESoft=819200 LimitNICE=0 LimitNICESoft=0 LimitRTPRIO=0 LimitRTPRIOSoft=0 LimitRTTIME=18446744073709551615 LimitRTTIMESoft=18446744073709551615 OOMScoreAdjust=-1000 Nice=0 IOScheduling=0 CPUSchedulingPolicy=0 CPUSchedulingPriority=0 TimerSlackNSec=50000 CPUSchedulingResetOnFork=no NonBlocking=no StandardInput=null StandardOutput=journal StandardError=inherit TTYReset=no TTYVHangup=no TTYVTDisallocate=no SyslogPriority=30 SyslogLevelPrefix=yes SyslogLevel=6 SyslogFacility=3 SecureBits=0 CapabilityBoundingSet=18446744073709551615 AmbientCapabilities=0 DynamicUser=no RemoveIPC=no MountFlags=524288 PrivateTmp=no PrivateDevices=no ProtectKernelTunables=no ProtectKernelModules=no ProtectControlGroups=no PrivateNetwork=no PrivateUsers=no ProtectHome=no ProtectSystem=no SameProcessGroup=no UtmpMode=init IgnoreSIGPIPE=yes NoNewPrivileges=no SystemCallErrorNumber=0 RuntimeDirectoryMode=0755 MemoryDenyWriteExecute=yes RestrictRealtime=yes RestrictNamespace=2114060288 KillMode=mixed KillSignal=15 SendSIGKILL=yes SendSIGHUP=no Id=systemd-udevd.service Names=systemd-udevd.service Requires=system.slice Wants=systemd-udevd-kernel.socket systemd-udevd-control.socket WantedBy=friendly-recovery.service systemd-udev-trigger.service sysinit.target Before=friendly-recovery.service sysinit.target plymouth-start.service systemd-networkd.service After=systemd-sysusers.service systemd-tmpfiles-setup-dev.service systemd-journald.socket system.slice systemd-udevd-kernel.socket systemd-udevd-control.socket TriggeredBy=systemd-udevd-kernel.socket systemd-udevd-control.socket Documentation=man:systemd-udevd.service(8) man:udev(7) Description=udev Kernel Device Manager LoadState=loaded ActiveState=active SubState=running FragmentPath=/lib/systemd/system/systemd-udevd.service UnitFileState=static UnitFilePreset=enabled StateChangeTimestamp=Wed 2017-04-12 07:19:27 CDT StateChangeTimestampMonotonic=5890643 InactiveExitTimestamp=Wed 2017-04-12 07:19:26 CDT InactiveExitTimestampMonotonic=4652377 ActiveEnterTimestamp=Wed 2017-04-12 07:19:27 CDT ActiveEnterTimestampMonotonic=5890643 ActiveExitTimestampMonotonic=0 InactiveEnterTimestampMonotonic=0 CanStart=yes CanStop=yes CanReload=no CanIsolate=no StopWhenUnneeded=no RefuseManualStart=no RefuseManualStop=no AllowIsolate=no DefaultDependencies=no OnFailureJobMode=replace IgnoreOnIsolate=no NeedDaemonReload=no JobTimeoutUSec=infinity JobTimeoutAction=none ConditionResult=yes AssertResult=yes ConditionTimestamp=Wed 2017-04-12 07:19:26 CDT ConditionTimestampMonotonic=4651243 AssertTimestamp=Wed 2017-04-12 07:19:26 CDT AssertTimestampMonotonic=4651252 Transient=no Perpetual=no StartLimitIntervalSec=10000000 StartLimitBurst=5 StartLimitAction=none InvocationID=8c9f082d6b5146fdb05b417857c6efae Hello Canonical, I'm not clear why first time (during system boot) it fails to execute rules. Can someone from systemd side take a look and explain why first time it fails to execute rules? -Vasant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp