| 2011-04-04 15:07:50 |
ryokenau |
bug |
|
|
added bug |
| 2011-04-04 15:13:50 |
ryokenau |
description |
Binary package hint: squid
I'm running Ubuntu 10.04.2 LTS with latest version of squid 2.7.STABLE7-1ubuntu12.2. When I
shutdown or reboot the system, I get the following error:
* Unmounting local filesystems...
umount2: Device or resource busy
umount: /var: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
umount2: Device or resource busy
umount2: Device or resource busy
umount: /dev/mapper/vg01-usr busy - remounted read-only
[fail]
When the system starts up again, I can see the following message:
/dev/mapper/vg01-var: recovering journal
It appears the /var partition was not cleanly unmounted during shutdown. Obviously, there is a risk
of filesystem corruption here. FYI, i have /var and other important mountpoints as separate
partitions (using LVM and ext4).
To confirm my suspicions of squid still running during shutdown, I checked /var/log/squid/cache.log
and there is no indication that it received the signal to terminate. In fact, cache.log hints at
this problem while the system is being brought up again:
Rebuilding storage in /var/spool/squid (DIRTY)
Only when I manually ran "stop squid", then cache.log would report that squid stopped successfully:
Preparing for shutdown after 0 requests
Waiting 30 seconds for active connections to finish
FD 14 Closing HTTP connection
Shutting down...
FD 15 Closing ICP connection
Closing unlinkd pipe FD 12
... <skipped> ...
logfileClose: closing log /var/log/squid/store.log
logfileClose: closing log /var/log/squid/access.log
Squid Cache (Version 2.7.STABLE7): Exiting normally.
To test whether /var was locked by squid during shutdown, I added a script to run "ls /var/run |
grep squid" and "lsof | grep var" before filesystems are unmounted. And voila!
ls /var/run | grep squid:
squid.pid
lsof | grep var:
squid 971 proxy cwd DIR 251,4 4096 130613 /var/spool/squid
squid 971 proxy 5u REG 251,4 13617 128678 /var/log/squid/cache.log
squid 971 proxy 7w REG 251,4 0 128724 /var/log/squid/access.log
squid 971 proxy 9w REG 251,4 0 128789 /var/log/squid/store.log
squid 971 proxy 11w REG 251,4 48 130308 /var/spool/squid/swap.state
Hence, the next system startup would result in /var recovering journal again.
Finally, I tried running "stop squid" before issuing the shutdown command and it successfully
unmounts /var and I do not get /var recovering journal on the next system startup. |
Binary package hint: squid
I'm running Ubuntu 10.04.2 LTS with latest version of squid 2.7.STABLE7-1ubuntu12.2. When I shutdown or reboot the system, I get the following error:
* Unmounting local filesystems...
umount2: Device or resource busy
umount: /var: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
umount2: Device or resource busy
umount2: Device or resource busy
umount: /dev/mapper/vg01-usr busy - remounted read-only
[fail]
When the system starts up again, I can see the following message:
/dev/mapper/vg01-var: recovering journal
It appears the /var partition was not cleanly unmounted during shutdown. Obviously, there is a risk of filesystem corruption here. FYI, i have /var and other important mountpoints as separate partitions (using LVM and ext4).
To confirm my suspicions of squid still running during shutdown, I checked /var/log/squid/cache.log and there is no indication that it received the signal to terminate. In fact, cache.log hints at this problem while the system is being brought up again:
Rebuilding storage in /var/spool/squid (DIRTY)
Only when I manually run "stop squid", then cache.log would report that squid stopped successfully:
Preparing for shutdown after 0 requests
Waiting 30 seconds for active connections to finish
FD 14 Closing HTTP connection
Shutting down...
FD 15 Closing ICP connection
Closing unlinkd pipe FD 12
... <skipped> ...
logfileClose: closing log /var/log/squid/store.log
logfileClose: closing log /var/log/squid/access.log
Squid Cache (Version 2.7.STABLE7): Exiting normally.
To test whether /var was locked by squid during shutdown, I added a script to run "ls /var/run | grep squid" and "lsof | grep var" before filesystems are unmounted. And voila!
ls /var/run | grep squid:
squid.pid
lsof | grep var:
squid 971 proxy cwd DIR 251,4 4096 130613 /var/spool/squid
squid 971 proxy 5u REG 251,4 13617 128678 /var/log/squid/cache.log
squid 971 proxy 7w REG 251,4 0 128724 /var/log/squid/access.log
squid 971 proxy 9w REG 251,4 0 128789 /var/log/squid/store.log
squid 971 proxy 11w REG 251,4 48 130308 /var/spool/squid/swap.state
Hence, the next system startup would result in /var recovering journal again.
Finally, I tried running "stop squid" before issuing the shutdown command and it successfully unmounts /var and I do not get /var recovering journal on the next system startup. |
|
| 2011-04-04 15:15:03 |
ryokenau |
description |
Binary package hint: squid
I'm running Ubuntu 10.04.2 LTS with latest version of squid 2.7.STABLE7-1ubuntu12.2. When I shutdown or reboot the system, I get the following error:
* Unmounting local filesystems...
umount2: Device or resource busy
umount: /var: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
umount2: Device or resource busy
umount2: Device or resource busy
umount: /dev/mapper/vg01-usr busy - remounted read-only
[fail]
When the system starts up again, I can see the following message:
/dev/mapper/vg01-var: recovering journal
It appears the /var partition was not cleanly unmounted during shutdown. Obviously, there is a risk of filesystem corruption here. FYI, i have /var and other important mountpoints as separate partitions (using LVM and ext4).
To confirm my suspicions of squid still running during shutdown, I checked /var/log/squid/cache.log and there is no indication that it received the signal to terminate. In fact, cache.log hints at this problem while the system is being brought up again:
Rebuilding storage in /var/spool/squid (DIRTY)
Only when I manually run "stop squid", then cache.log would report that squid stopped successfully:
Preparing for shutdown after 0 requests
Waiting 30 seconds for active connections to finish
FD 14 Closing HTTP connection
Shutting down...
FD 15 Closing ICP connection
Closing unlinkd pipe FD 12
... <skipped> ...
logfileClose: closing log /var/log/squid/store.log
logfileClose: closing log /var/log/squid/access.log
Squid Cache (Version 2.7.STABLE7): Exiting normally.
To test whether /var was locked by squid during shutdown, I added a script to run "ls /var/run | grep squid" and "lsof | grep var" before filesystems are unmounted. And voila!
ls /var/run | grep squid:
squid.pid
lsof | grep var:
squid 971 proxy cwd DIR 251,4 4096 130613 /var/spool/squid
squid 971 proxy 5u REG 251,4 13617 128678 /var/log/squid/cache.log
squid 971 proxy 7w REG 251,4 0 128724 /var/log/squid/access.log
squid 971 proxy 9w REG 251,4 0 128789 /var/log/squid/store.log
squid 971 proxy 11w REG 251,4 48 130308 /var/spool/squid/swap.state
Hence, the next system startup would result in /var recovering journal again.
Finally, I tried running "stop squid" before issuing the shutdown command and it successfully unmounts /var and I do not get /var recovering journal on the next system startup. |
Binary package hint: squid
I'm running Ubuntu 10.04.2 LTS with latest version of squid 2.7.STABLE7-1ubuntu12.2. This is a default install - there have been no changes to /etc/squid.conf.
When I shutdown or reboot the system, I get the following error:
* Unmounting local filesystems...
umount2: Device or resource busy
umount: /var: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
umount2: Device or resource busy
umount2: Device or resource busy
umount: /dev/mapper/vg01-usr busy - remounted read-only
[fail]
When the system starts up again, I can see the following message:
/dev/mapper/vg01-var: recovering journal
It appears the /var partition was not cleanly unmounted during shutdown. Obviously, there is a risk of filesystem corruption here. FYI, i have /var and other important mountpoints as separate partitions (using LVM and ext4).
To confirm my suspicions of squid still running during shutdown, I checked /var/log/squid/cache.log and there is no indication that it received the signal to terminate. In fact, cache.log hints at this problem while the system is being brought up again:
Rebuilding storage in /var/spool/squid (DIRTY)
Only when I manually run "stop squid", then cache.log would report that squid stopped successfully:
Preparing for shutdown after 0 requests
Waiting 30 seconds for active connections to finish
FD 14 Closing HTTP connection
Shutting down...
FD 15 Closing ICP connection
Closing unlinkd pipe FD 12
... <skipped> ...
logfileClose: closing log /var/log/squid/store.log
logfileClose: closing log /var/log/squid/access.log
Squid Cache (Version 2.7.STABLE7): Exiting normally.
To test whether /var was locked by squid during shutdown, I added a script to run "ls /var/run | grep squid" and "lsof | grep var" before filesystems are unmounted. And voila!
ls /var/run | grep squid:
squid.pid
lsof | grep var:
squid 971 proxy cwd DIR 251,4 4096 130613 /var/spool/squid
squid 971 proxy 5u REG 251,4 13617 128678 /var/log/squid/cache.log
squid 971 proxy 7w REG 251,4 0 128724 /var/log/squid/access.log
squid 971 proxy 9w REG 251,4 0 128789 /var/log/squid/store.log
squid 971 proxy 11w REG 251,4 48 130308 /var/spool/squid/swap.state
Hence, the next system startup would result in /var recovering journal again.
Finally, I tried running "stop squid" before issuing the shutdown command and it successfully unmounts /var and I do not get /var recovering journal on the next system startup. |
|
| 2011-04-04 15:18:57 |
ryokenau |
description |
Binary package hint: squid
I'm running Ubuntu 10.04.2 LTS with latest version of squid 2.7.STABLE7-1ubuntu12.2. This is a default install - there have been no changes to /etc/squid.conf.
When I shutdown or reboot the system, I get the following error:
* Unmounting local filesystems...
umount2: Device or resource busy
umount: /var: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
umount2: Device or resource busy
umount2: Device or resource busy
umount: /dev/mapper/vg01-usr busy - remounted read-only
[fail]
When the system starts up again, I can see the following message:
/dev/mapper/vg01-var: recovering journal
It appears the /var partition was not cleanly unmounted during shutdown. Obviously, there is a risk of filesystem corruption here. FYI, i have /var and other important mountpoints as separate partitions (using LVM and ext4).
To confirm my suspicions of squid still running during shutdown, I checked /var/log/squid/cache.log and there is no indication that it received the signal to terminate. In fact, cache.log hints at this problem while the system is being brought up again:
Rebuilding storage in /var/spool/squid (DIRTY)
Only when I manually run "stop squid", then cache.log would report that squid stopped successfully:
Preparing for shutdown after 0 requests
Waiting 30 seconds for active connections to finish
FD 14 Closing HTTP connection
Shutting down...
FD 15 Closing ICP connection
Closing unlinkd pipe FD 12
... <skipped> ...
logfileClose: closing log /var/log/squid/store.log
logfileClose: closing log /var/log/squid/access.log
Squid Cache (Version 2.7.STABLE7): Exiting normally.
To test whether /var was locked by squid during shutdown, I added a script to run "ls /var/run | grep squid" and "lsof | grep var" before filesystems are unmounted. And voila!
ls /var/run | grep squid:
squid.pid
lsof | grep var:
squid 971 proxy cwd DIR 251,4 4096 130613 /var/spool/squid
squid 971 proxy 5u REG 251,4 13617 128678 /var/log/squid/cache.log
squid 971 proxy 7w REG 251,4 0 128724 /var/log/squid/access.log
squid 971 proxy 9w REG 251,4 0 128789 /var/log/squid/store.log
squid 971 proxy 11w REG 251,4 48 130308 /var/spool/squid/swap.state
Hence, the next system startup would result in /var recovering journal again.
Finally, I tried running "stop squid" before issuing the shutdown command and it successfully unmounts /var and I do not get /var recovering journal on the next system startup. |
Binary package hint: squid
I'm running Ubuntu 10.04.2 LTS with latest version of squid 2.7.STABLE7-1ubuntu12.2. This is a default install - there have been no changes to /etc/squid.conf.
When I shutdown or reboot the system, I get the following error:
* Unmounting local filesystems...
umount2: Device or resource busy
umount: /var: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
umount2: Device or resource busy
umount2: Device or resource busy
umount: /dev/mapper/vg01-usr busy - remounted read-only
[fail]
When the system starts up again, I see the following message:
/dev/mapper/vg01-var: recovering journal
It appears the /var partition was not cleanly unmounted during shutdown. Obviously, there is a risk of filesystem corruption here. FYI, i have /var and other important mountpoints as separate partitions (using LVM and ext4).
To confirm my suspicions of squid still running during shutdown, I checked /var/log/squid/cache.log and there is no indication that it received the signal to terminate. In fact, cache.log hints at this problem while the system is being brought up again:
Rebuilding storage in /var/spool/squid (DIRTY)
Only when I manually run "stop squid", then cache.log would report that squid stopped successfully:
Preparing for shutdown after 0 requests
Waiting 30 seconds for active connections to finish
FD 14 Closing HTTP connection
Shutting down...
FD 15 Closing ICP connection
Closing unlinkd pipe FD 12
... <skipped> ...
logfileClose: closing log /var/log/squid/store.log
logfileClose: closing log /var/log/squid/access.log
Squid Cache (Version 2.7.STABLE7): Exiting normally.
To test whether /var was locked by squid during shutdown, I added a script to run "ls /var/run | grep squid" and "lsof | grep var" before filesystems are unmounted. And voila!
ls /var/run | grep squid:
squid.pid
lsof | grep var:
squid 971 proxy cwd DIR 251,4 4096 130613 /var/spool/squid
squid 971 proxy 5u REG 251,4 13617 128678 /var/log/squid/cache.log
squid 971 proxy 7w REG 251,4 0 128724 /var/log/squid/access.log
squid 971 proxy 9w REG 251,4 0 128789 /var/log/squid/store.log
squid 971 proxy 11w REG 251,4 48 130308 /var/spool/squid/swap.state
Hence, the next system startup would result in /var recovering journal again.
Finally, I tried running "stop squid" before issuing the shutdown command and it successfully unmounts /var and I do not get /var recovering journal on the next system startup. |
|
| 2011-04-09 22:17:30 |
Clint Byrum |
marked as duplicate |
|
688541 |
|
| 2011-08-27 09:14:39 |
Clint Byrum |
removed duplicate marker |
688541 |
|
|
| 2011-08-27 09:18:38 |
Clint Byrum |
nominated for series |
|
Ubuntu Lucid |
|
| 2011-08-27 09:18:38 |
Clint Byrum |
bug task added |
|
squid (Ubuntu Lucid) |
|
| 2011-08-27 09:18:38 |
Clint Byrum |
nominated for series |
|
Ubuntu Maverick |
|
| 2011-08-27 09:18:38 |
Clint Byrum |
bug task added |
|
squid (Ubuntu Maverick) |
|
| 2011-08-27 09:18:48 |
Clint Byrum |
squid (Ubuntu): status |
New |
Fix Released |
|
| 2011-08-27 09:18:53 |
Clint Byrum |
squid (Ubuntu Lucid): status |
New |
Triaged |
|
| 2011-08-27 09:18:55 |
Clint Byrum |
squid (Ubuntu Lucid): importance |
Undecided |
High |
|
| 2011-08-27 09:18:58 |
Clint Byrum |
squid (Ubuntu Maverick): status |
New |
Triaged |
|
| 2011-08-27 09:19:01 |
Clint Byrum |
squid (Ubuntu Maverick): importance |
Undecided |
High |
|
| 2011-08-29 03:11:55 |
Chris Halse Rogers |
squid (Ubuntu Lucid): status |
Triaged |
Fix Committed |
|
| 2011-08-29 03:11:58 |
Chris Halse Rogers |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2011-08-29 03:12:01 |
Chris Halse Rogers |
bug |
|
|
added subscriber SRU Verification |
| 2011-08-29 03:12:03 |
Chris Halse Rogers |
tags |
|
verification-needed |
|
| 2011-08-29 03:47:55 |
Chris Halse Rogers |
squid (Ubuntu Maverick): status |
Triaged |
Fix Committed |
|
| 2011-08-29 04:11:21 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/lucid-proposed/squid |
|
| 2011-08-29 04:11:25 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/maverick-proposed/squid |
|
| 2011-08-29 16:23:16 |
Clint Byrum |
tags |
verification-needed |
verification-done-lucid verification-needed |
|
| 2011-09-21 06:21:19 |
Launchpad Janitor |
squid (Ubuntu Lucid): status |
Fix Committed |
Fix Released |
|
| 2011-09-21 22:36:23 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/lucid-updates/squid |
|
| 2011-10-13 05:58:04 |
Martin Pitt |
tags |
verification-done-lucid verification-needed |
verification-needed |
|
| 2011-11-01 03:43:56 |
Steve Beattie |
tags |
verification-needed |
verification-done |
|
| 2011-11-01 18:39:57 |
Launchpad Janitor |
squid (Ubuntu Maverick): status |
Fix Committed |
Fix Released |
|
