[systemd-udevd] Process '/bin/touch /var/lib/lsvpd/run.vpdupdate' failed with exit code 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
High
|
Canonical Foundations Team | ||
libvpd (Debian) |
Fix Released
|
Unknown
|
|||
libvpd (Ubuntu) |
Fix Released
|
High
|
Dimitri John Ledkov |
Bug Description
== Comment: VASANT HEGDE <email address hidden> - 2017-04-13 11:14:43 ==
Problem description :
systemd-udevd daemon failed to execute udev rules.
Aug 9 01:28:43 abc systemd-
Rules file :
-----------
root@abc:
KERNELS=="*", ACTION=="*", DEVPATH=
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/
systemctl show systemd-udevd
Type=notify
Restart=always
NotifyAccess=main
RestartUSec=0
TimeoutStartUSe
TimeoutStopUSec
RuntimeMaxUSec=
WatchdogUSec=3min
WatchdogTimesta
WatchdogTimesta
FailureAction=none
PermissionsStar
RootDirectorySt
RemainAfterExit=no
GuessMainPID=yes
MainPID=489
ControlPID=0
FileDescriptorS
NFileDescriptor
StatusText=
StatusErrno=0
Result=success
UID=4294967295
GID=4294967295
ExecMainStartTi
ExecMainStartTi
ExecMainExitTim
ExecMainPID=489
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/lib/
Slice=system.slice
ControlGroup=
MemoryCurrent=
CPUUsageNSec=
TasksCurrent=1
Delegate=no
CPUAccounting=no
CPUWeight=
StartupCPUWeigh
CPUShares=
StartupCPUShare
CPUQuotaPerSecU
IOAccounting=no
IOWeight=
StartupIOWeight
BlockIOAccounti
BlockIOWeight=
StartupBlockIOW
MemoryAccounting=no
MemoryLow=0
MemoryHigh=
MemoryMax=
MemorySwapMax=
MemoryLimit=
DevicePolicy=auto
TasksAccounting=yes
TasksMax=
UMask=0022
LimitCPU=
LimitCPUSoft=
LimitFSIZE=
LimitFSIZESoft=
LimitDATA=
LimitDATASoft=
LimitSTACK=
LimitSTACKSoft=
LimitCORE=
LimitCORESoft=0
LimitRSS=
LimitRSSSoft=
LimitNOFILE=4096
LimitNOFILESoft
LimitAS=
LimitASSoft=
LimitNPROC=372260
LimitNPROCSoft=
LimitMEMLOCK=65536
LimitMEMLOCKSof
LimitLOCKS=
LimitLOCKSSoft=
LimitSIGPENDING
LimitSIGPENDING
LimitMSGQUEUE=
LimitMSGQUEUESo
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=
LimitRTTIMESoft
OOMScoreAdjust=
Nice=0
IOScheduling=0
CPUSchedulingPo
CPUSchedulingPr
TimerSlackNSec=
CPUSchedulingRe
NonBlocking=no
StandardInput=null
StandardOutput=
StandardError=
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPref
SyslogLevel=6
SyslogFacility=3
SecureBits=0
CapabilityBound
AmbientCapabili
DynamicUser=no
RemoveIPC=no
MountFlags=524288
PrivateTmp=no
PrivateDevices=no
ProtectKernelTu
ProtectKernelMo
ProtectControlG
PrivateNetwork=no
PrivateUsers=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallError
RuntimeDirector
MemoryDenyWrite
RestrictRealtim
RestrictNamespa
KillMode=mixed
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=systemd-
Names=systemd-
Requires=
Wants=systemd-
WantedBy=
Before=
After=systemd-
TriggeredBy=
Documentation=
Description=udev Kernel Device Manager
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=
UnitFileState=
UnitFilePreset=
StateChangeTime
StateChangeTime
InactiveExitTim
InactiveExitTim
ActiveEnterTime
ActiveEnterTime
ActiveExitTimes
InactiveEnterTi
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualSta
RefuseManualStop=no
AllowIsolate=no
DefaultDependen
OnFailureJobMod
IgnoreOnIsolate=no
NeedDaemonReload=no
JobTimeoutUSec=
JobTimeoutActio
ConditionResult=yes
AssertResult=yes
ConditionTimest
ConditionTimest
AssertTimestamp=Wed 2017-04-12 07:19:26 CDT
AssertTimestamp
Transient=no
Perpetual=no
StartLimitInter
StartLimitBurst=5
StartLimitActio
InvocationID=
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
tags: | added: architecture-ppc64le bugnameltc-144627 severity-high targetmilestone-inin1610 |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
affects: | ubuntu → systemd (Ubuntu) |
Changed in libvpd (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → Dimitri John Ledkov (xnox) |
importance: | Undecided → High |
milestone: | none → ubuntu-17.05 |
tags: | added: ubuntu-17.04 |
Changed in ubuntu-power-systems: | |
importance: | Undecided → High |
tags: | added: triage-a |
tags: |
added: triage-r removed: triage-a |
Changed in libvpd (Debian): | |
status: | Unknown → New |
Changed in ubuntu-power-systems: | |
status: | Fix Committed → Fix Released |
tags: |
added: triage-g removed: triage-r |
Changed in ubuntu-power-systems: | |
assignee: | nobody → Canonical Foundations Team (canonical-foundations) |
tags: |
added: targetmilestone-inin1710 removed: targetmilestone-inin1610 |
Changed in libvpd (Debian): | |
status: | New → Fix Released |
tags: | added: id-599c6a42fa3d9228afba11d5 |
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.