6 ms·

I love how deadpan the bug report is: Actual results: All files are deleted on the machine. Expected results: Squid is restarted. Not many de

by kevan 12y ago

I love how deadpan the bug report is: Actual results: All files are deleted on the machine. Expected results: Squid is restarted. Not many details yet but it sounds similar to the Steam bug [0] from last year. [0] https://github.com/valvesoftware/steam-for-linux/issues/3671 https://github.com/valvesoftware/steam-for-linux/issues/3671

stevenspasbo 12y ago
I started laughing at the lines Stopping squid: ................[ OK ] rm: cannot remove `/boot': Device or resource busy
blcknight 12y ago
Except the Valve bug passed their QE process if any and got out into the wild. This is for an unreleased version of RHEL, and was caught....
- TazeTSchnitzel 12y ago
  QE? Is that a misspelling of QA, or is there another meaning beyond Quantitative Easing?
  - blcknight 12y ago
    Quality engineering. It's Red Hat's term, as well as a few other software companies, but its QA.
    - TazeTSchnitzel 12y ago
      Oh I see. Thanks.
    - philk10 12y ago
      Though QA is Quality Assurance when really it's QC )Quality Control) that should have caught the error. QA puts processes into place that means there is a QC that can catch this. Sorry, going off-topic but as a tester I dislike being told to 'QA this'
viraptor 12y ago
I would bet on the issue being in the init script itself rather than squid. (I'm assuming squid doesn't run as root by default in rhel) If that's true then it's another point for more sane process managers (upstart/supervisord/systemd/...)
- 4ad 12y ago
  RHEL uses systemd.
  - bonzini 12y ago
    This is RHEL6.7, it doesn't use systemd.
    - 4ad 12y ago
      Oh, I see.
      - Xylakant 12y ago
        Specifically, this bug would not have happened with systemd since systemd does not leave the handling of pid-files and pid-dirs to shell-scripts.
        marcosdumay 12y ago
        That normally does not happen when handling pid-dirs, simply because those are standard and can be handled with standard tools. Every time I've seen such a bug (honestly, not many), it was created when cleaning a temporary dir.
        bandrami 12y ago
        No, but if an analogous bug happened (systemd forgot to set an internal squidroot variable before clearing the squidroot, for instance), it would be much, much harder to figure out what was going on. Which is really what everybody's complaints boil down to.
ams6110 12y ago
Note that: At the time of this writing, RHEL 6.7 is still pre-beta and this bug was found in an *UNRELEASED* update to squid. Bad enough, but not like it's out in production.

by kevan 12y ago

stevenspasbo 12y ago

I started laughing at the lines Stopping squid: ................[ OK ] rm: cannot remove `/boot': Device or resource busy

blcknight 12y ago

Except the Valve bug passed their QE process if any and got out into the wild. This is for an unreleased version of RHEL, and was caught....

TazeTSchnitzel 12y ago
QE? Is that a misspelling of QA, or is there another meaning beyond Quantitative Easing?
- blcknight 12y ago
  Quality engineering. It's Red Hat's term, as well as a few other software companies, but its QA.
  - TazeTSchnitzel 12y ago
    Oh I see. Thanks.
  - philk10 12y ago
    Though QA is Quality Assurance when really it's QC )Quality Control) that should have caught the error. QA puts processes into place that means there is a QC that can catch this. Sorry, going off-topic but as a tester I dislike being told to 'QA this'

viraptor 12y ago

I would bet on the issue being in the init script itself rather than squid. (I'm assuming squid doesn't run as root by default in rhel) If that's true then it's another point for more sane process managers (upstart/supervisord/systemd/...)

4ad 12y ago
RHEL uses systemd.
- bonzini 12y ago
  This is RHEL6.7, it doesn't use systemd.
  - 4ad 12y ago
    Oh, I see.
    - Xylakant 12y ago
      Specifically, this bug would not have happened with systemd since systemd does not leave the handling of pid-files and pid-dirs to shell-scripts.
      - marcosdumay 12y ago
        That normally does not happen when handling pid-dirs, simply because those are standard and can be handled with standard tools. Every time I've seen such a bug (honestly, not many), it was created when cleaning a temporary dir.
      - bandrami 12y ago
        No, but if an analogous bug happened (systemd forgot to set an internal squidroot variable before clearing the squidroot, for instance), it would be much, much harder to figure out what was going on. Which is really what everybody's complaints boil down to.

ams6110 12y ago

Note that: At the time of this writing, RHEL 6.7 is still pre-beta and this bug was found in an *UNRELEASED* update to squid. Bad enough, but not like it's out in production.