Results 1 to 2 of 2
When I shutdown Linux '/usr/share/unattended-upgrades' is ran, which gives me an error that says something along the lines of "apt_pkg not found in 'unattended-upgrades.lock'".
I viewed the content of '/usr/share/unattended-upgrades' ...
- 07-09-2011 #1Just Joined!
- Join Date
- Jul 2011
- Posts
- 1
Ever seen an error message like this before?
When I shutdown Linux '/usr/share/unattended-upgrades' is ran, which gives me an error that says something along the lines of "apt_pkg not found in 'unattended-upgrades.lock'".
I viewed the content of '/usr/share/unattended-upgrades' and found "/var/run/unattended-upgrades.lock", so I went to that location, but the file does not exist.
I also checked out another Ubuntu system which is close to default install, and '/var/run/unattended-upgrades.lock' doesn't exist on it either, but that Ubuntu system doesn't get the error message.
Has anyone ever got an error like this before?
Is there a log file that has shutdown verbose so I can say exactly what the error message is?
- 07-10-2011 #2Just Joined!
- Join Date
- May 2011
- Posts
- 44
*.lock files are created when a program/application creates a lock to prevent other files from modifying config files etc.
Without seeing the error message it's really hard to say, my guess is you have a stalled lock file, e.g.: you were running apt-get and killed it without allowing it shut down properly. (apt-get is merely an example here, plenty of other programs vreate .lock files.)
>> I viewed the content of '/usr/share/unattended-upgrades' and found "/var/run/unattended-upgrades.lock", so I went to that location, but the file does not exist.
are you sure? '/usr/share/unattended-upgrades/' is a directory on Ubuntu systems. (which consequentially has the auto shutdown script that runs at shutdown: '/usr/share/unattended-upgrades/unattended-upgrade-shutdown')
'/usr/bin/unattended-upgrades' is the path to the system command.
>> I also checked out another Ubuntu system which is close to default install, and '/var/run/unattended-upgrades.lock' doesn't exist on it either, but that Ubuntu system doesn't get the error message.
The lock file is only created when '/usr/bin/unattended-upgrades' is running.
>> Has anyone ever got an error like this before?
The sort answer is yes, but it is hard to say without seeing the error.
>> Is there a log file that has shutdown verbose so I can say exactly what the error message is?
check:
/var/log/dmesg
and
/var/log/syslog
Though I don't believe shutdown messages are logged... (Please, someone correct me on this)
Probably a better solution would be to run unattended-upgrades and post any error messages here.
you can also run:Code:$ sudo unattended-upgrades
Though I don't remember the difference. I'm sure through some easy googleing you could find the difference, though I believe it to be trivial.Code:sudo /usr/share/unattended-upgrades/unattended-upgrade-shutdown


Reply With Quote