3 ms·

This reminds me of "whoopsie" when I first came across it after upgrading my servers to 12.04. Its a program that resides in the ram, automatically homes in the

by nivla 13y ago

This reminds me of "whoopsie" when I first came across it after upgrading my servers to 12.04. Its a program that resides in the ram, automatically homes in the crash reports and would have to be explicitly disabled. At first I din't mind, but after watching it eat through my ram I had it disabled. As far as privacy goes, who knows what those sent in memory dumps might have.

rlpb 13y ago
whoopsie doesn't send anything without your permission.
- nivla 13y ago
  Yes it does, how is it going to ask for my permission in a server environment? It automatically sets "report_crashes=true" under (/etc/default/whoopsie) when Ubuntu is first installed. Here are some resources with more people reporting the same: [1] http://blog.retep.org/2012/07/05/whoopsie-how-to-disable-it-on-ubuntu-12-04-or-mint-13/ http://blog.retep.org/2012/07/05/whoopsie-how-to-disable-it-... [2] http://glog.procrasstination.com/index.php?/archives/47-Ubuntu-What-is-Whoopsie-and-HOWTO-disable-it.html http://glog.procrasstination.com/index.php?/archives/47-Ubun... [3] http://ubuntuforums.org/showthread.php?t=2000108 http://ubuntuforums.org/showthread.php?t=2000108
  - rlpb 13y ago
    It's vestigal on a server. It's there because the server installation and the desktop installation share that component. But since there's no UI for you to approve transmission, currently the crash reports sit on the server awaiting (local) examination and do nothing. All the resources you pointed appear to be people who have found a setting and do not understand that it does not do anything. Like my posts elsewhere on this thread, it's open source. Take a look for yourself, or ask someone who can.
    - nivla 13y ago
      >It's vestigal on a server. Do you have any source for that? If it is vestigial, why would it need to suck up so much ram? Unless I explicitly activate it, what is point of draining the power and filling up the ram by default. Not everyone does and know how to inspect the crash dump, they are mostly useful to the OS manufacturer and the developer of the crashing application. > currently the crash reports sit on the server awaiting (local) examination and do nothing. So Ubuntu (Canonical) doesn't collect any crash data from servers but only from desktops despite having the technology built-in and activated? Highly unlikely.
      - rlpb 13y ago
        > Do you have any source for that? Yes. "apt-get source whoopsie". What other source would you prefer? Canonical, who it seems that you don't trust and won't believe anyway? > So Ubuntu (Canonical) doesn't collect any crash data from servers but only from desktops despite having the technology built-in and activated? Correct, because the server end is not implemented. A summary of the gathered data is at https://errors.ubuntu.com/ https://errors.ubuntu.com/. You may see "server" packages there, but if this is true then this is only because you can install these packages on the desktop, too, and desktop users can agree to send crash reports for crashes on server packages. But the numbers on this site speak for themselves. Clearly server crash reports are not being reported there.
    - crististm 13y ago
      Ca you fix it, please?
    - laumars 13y ago
      > It's vestigal on a server. It's there because the server installation and the desktop installation share that component. But since there's no UI for you to approve transmission, currently the crash reports sit on the server awaiting (local) examination and do nothing. Aside eating up 8GB of RAM on one file server I'd built. I couldn't believe it when I saw that. Wooopsie is just one of many reasons why I always recommend vanilla Debian over Ubuntu Server.

by nivla 13y ago

rlpb 13y ago

whoopsie doesn't send anything without your permission.

nivla 13y ago
Yes it does, how is it going to ask for my permission in a server environment? It automatically sets "report_crashes=true" under (/etc/default/whoopsie) when Ubuntu is first installed. Here are some resources with more people reporting the same: [1] http://blog.retep.org/2012/07/05/whoopsie-how-to-disable-it-on-ubuntu-12-04-or-mint-13/ http://blog.retep.org/2012/07/05/whoopsie-how-to-disable-it-... [2] http://glog.procrasstination.com/index.php?/archives/47-Ubuntu-What-is-Whoopsie-and-HOWTO-disable-it.html http://glog.procrasstination.com/index.php?/archives/47-Ubun... [3] http://ubuntuforums.org/showthread.php?t=2000108 http://ubuntuforums.org/showthread.php?t=2000108
- rlpb 13y ago
  It's vestigal on a server. It's there because the server installation and the desktop installation share that component. But since there's no UI for you to approve transmission, currently the crash reports sit on the server awaiting (local) examination and do nothing. All the resources you pointed appear to be people who have found a setting and do not understand that it does not do anything. Like my posts elsewhere on this thread, it's open source. Take a look for yourself, or ask someone who can.
  - nivla 13y ago
    >It's vestigal on a server. Do you have any source for that? If it is vestigial, why would it need to suck up so much ram? Unless I explicitly activate it, what is point of draining the power and filling up the ram by default. Not everyone does and know how to inspect the crash dump, they are mostly useful to the OS manufacturer and the developer of the crashing application. > currently the crash reports sit on the server awaiting (local) examination and do nothing. So Ubuntu (Canonical) doesn't collect any crash data from servers but only from desktops despite having the technology built-in and activated? Highly unlikely.
    - rlpb 13y ago
      > Do you have any source for that? Yes. "apt-get source whoopsie". What other source would you prefer? Canonical, who it seems that you don't trust and won't believe anyway? > So Ubuntu (Canonical) doesn't collect any crash data from servers but only from desktops despite having the technology built-in and activated? Correct, because the server end is not implemented. A summary of the gathered data is at https://errors.ubuntu.com/ https://errors.ubuntu.com/. You may see "server" packages there, but if this is true then this is only because you can install these packages on the desktop, too, and desktop users can agree to send crash reports for crashes on server packages. But the numbers on this site speak for themselves. Clearly server crash reports are not being reported there.
  - crististm 13y ago
    Ca you fix it, please?
  - laumars 13y ago
    > It's vestigal on a server. It's there because the server installation and the desktop installation share that component. But since there's no UI for you to approve transmission, currently the crash reports sit on the server awaiting (local) examination and do nothing. Aside eating up 8GB of RAM on one file server I'd built. I couldn't believe it when I saw that. Wooopsie is just one of many reasons why I always recommend vanilla Debian over Ubuntu Server.