Re: [Bug 1729536] Re: InnoDB: Failing assertion: sym_node->table != NULL

2017-12-06 Thread Olaf van der Spek
2017-12-06 9:15 GMT+01:00 Eric Fjøsne <1729...@bugs.launchpad.net>: > What can I do next to further investigate this in order to provide > feedback over here in an efficient way ? Thinking aloud: 1. Share table structure 2. Copy table to another name, add optimize table for the copy and see if it

Re: [Bug 1729536] Re: InnoDB: Failing assertion: sym_node->table != NULL

2017-12-01 Thread Olaf van der Spek
2017-12-01 10:32 GMT+01:00 Eric Fjøsne <1729...@bugs.launchpad.net>: > I reactivated one set of optimize queries for this night and it crashed > with the exact same backtrace. So I can confirm this is indeed related > to this specific set. However, there is nothing fancy about them at all. Nice! I

Re: [Bug 1729536] Re: InnoDB: Failing assertion: sym_node->table != NULL

2017-11-30 Thread Olaf van der Spek
2017-11-30 9:12 GMT+01:00 Eric Fjøsne <1729...@bugs.launchpad.net>: > @Olaf: it wasn't available anymore unfortunately. > > After deactivating the OPTIMIZE statements and changing the TRUNCATE > statement to DELETE FROM in our pre-production scripts, I can happily > confirm there was no outage on o

Re: [Bug 1729536] Re: InnoDB: Failing assertion: sym_node->table != NULL

2017-11-29 Thread Olaf van der Spek
2017-11-29 10:46 GMT+01:00 Eric Fjøsne <1729...@bugs.launchpad.net>: > @ChristianEhrhardt > Thanks for your replies and initiatives. Much appreciated. > I did indeed notice the install package we could rollback to using apt-get > install mysql-server=XXX was 5.7.11, but this version is more than a

[Bug 1729536] Re: InnoDB: Failing assertion: sym_node->table != NULL

2017-11-29 Thread Olaf van der Spek
Hi, > I thought it was related specifically to replication, but according to your message, it seems it can happen for some other reason as well ? Yes, we're not using replication at all. I think the assert is a low-level one. Something before, probably unrelated to this stacktrace, goes wrong an

Re: [Bug 1729536] Re: InnoDB: Failing assertion: sym_node->table != NULL

2017-11-03 Thread Olaf van der Spek
2017-11-03 10:55 GMT+01:00 ChristianEhrhardt <1729...@bugs.launchpad.net>: > Hi Olaf, > there seem to be some related known issues in percona/mysql, see bug 1399471 > for more details and follow referenced further bugs from there. > > I'll explicitly subscribe Lars to take a look, but as printed i

[Bug 1729536] [NEW] InnoDB: Failing assertion: sym_node->table != NULL

2017-11-02 Thread Olaf van der Spek
Public bug reported: V: 5.7.20-0ubuntu0.16.04.1 I think it was when I added a field to a table (via phpMyAdmin). 2017-11-02 09:36:47 0x7fdc38ff9700 InnoDB: Assertion failure in thread 140583825807104 in file pars0pars.cc line 822 InnoDB: Failing assertion: sym_node->table != NULL InnoDB: We in

[Bug 376715]

2012-03-30 Thread Olaf van der Spek
(In reply to Jim Porter (:squib) from comment #90) > For Windows, as of Win7, Microsoft explicitly recommends *against* doing > this: MS is silly :p I'm using Windows 7 and I'd still like to see a minimize to tray (with Escape as shortcut). I don't want to clutter my taskbar and alt-tab switcher.

[Bug 48734] Re: Home permissions too open

2011-03-19 Thread Olaf van der Spek
Ah, I assumed Opinion meant Wontfix. It'd still be nice if someone responded to the arguments. -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/48734 Title: Home permissions too open -- ubuntu-bugs ma

[Bug 48734] Re: Home permissions too open

2011-03-15 Thread Olaf van der Spek
** Changed in: adduser (Ubuntu) Status: Opinion => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/48734 Title: Home permissions too open -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubun

[Bug 48734] Re: Home permissions too open

2011-02-28 Thread Olaf van der Spek
A response to #38 and #39 is still missing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/48734 Title: Home permissions too open -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lis

[Bug 48734] Re: Home permissions too open

2011-02-21 Thread Olaf van der Spek
** Changed in: adduser (Ubuntu) Status: Opinion => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/48734 Title: Home permissions too open -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubun

[Bug 48734] Re: Home permissions too open

2011-02-17 Thread Olaf van der Spek
> status: New → Opinion That's silly, could someone at least respond to the arguments so we can have a proper discussion? -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/48734 Title: Home permis

[Bug 48734] Re: Home permissions too open

2011-02-17 Thread Olaf van der Spek
** Changed in: adduser (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/48734 Title: Home permissions too open -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubun

[Bug 48734] Re: Home permissions too open

2011-02-17 Thread Olaf van der Spek
Sorry, that should read: "without defaulting to a world readable home dir." -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/48734 Title: Home permissions too open -- ubuntu-bugs mailing list ubuntu-b

[Bug 48734] Re: Home permissions too open

2011-02-17 Thread Olaf van der Spek
Somebody? Implementing a public dir for easy sharing can IMO be easily done with defaulting to a world readable home dir. -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/48734 Title: Home permissions

[Bug 48734] Re: Home permissions too open

2010-11-27 Thread Olaf van der Spek
@Colin, Mark: What about Principle of least privilege? Safe-by-default? Why does user www-data (for example) have access to my files? The defaults provide access to way more than other humans. You might at least want to use ACLs to limit it to other humans by default. It should be clear by now th

[Bug 675560] [NEW] Home dirs shouldn't be world readable

2010-11-15 Thread Olaf van der Spek
Public bug reported: Binary package hint: adduser By default, home dirs are world readable. From a privacy and security perspective, this should not be the case. ** Affects: adduser (Ubuntu) Importance: Undecided Status: New -- Home dirs shouldn't be world readable https://bugs.l

[Bug 109559] Re: Please don't change permissions of /var/log/lighttpd during upgrade

2010-06-01 Thread Olaf van der Spek
"chown www-data:www-data /var/log/lighttpd" is done unconditionally in postinst. It should only be done when that dir is created for the first time, but I've no idea how to implement that. -- Please don't change permissions of /var/log/lighttpd during upgrade https://bugs.launchpad.net/bugs/1095

[Bug 57091] Re: proc/sys/net/ipv4/tcp_syncookies=1 should be seriously considered to permit SYN flood defense...

2009-10-09 Thread Olaf van der Spek
Has this request been forwarded upstream (lkml)? -- proc/sys/net/ipv4/tcp_syncookies=1 should be seriously considered to permit SYN flood defense... https://bugs.launchpad.net/bugs/57091 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -

Re: [Bug 57091] Re: proc/sys/net/ipv4/tcp_syncookies=1 should be seriously considered to permit SYN flood defense...

2009-09-25 Thread Olaf van der Spek
On Fri, Sep 25, 2009 at 4:56 PM, Kees Cook wrote: > Olaf: that's why it is "fix released".  :)  It is enabled in Ubuntu now. Ah, nice. I kinda expected a link to the package version in which it got fixed. -- proc/sys/net/ipv4/tcp_syncookies=1 should be seriously considered to permit SYN flood

Re: [Bug 57091] Re: proc/sys/net/ipv4/tcp_syncookies=1 should be seriously considered to permit SYN flood defense...

2009-09-25 Thread Olaf van der Spek
Ah, nevermind, I can't read, it's at the bottom of that message. On Fri, Sep 25, 2009 at 5:18 PM, Olaf van der Spek wrote: > On Fri, Sep 25, 2009 at 4:56 PM, Kees Cook wrote: >> Olaf: that's why it is "fix released".  :)  It is enabled in Ubuntu now. > >

[Bug 57091] Re: proc/sys/net/ipv4/tcp_syncookies=1 should be seriously considered to permit SYN flood defense...

2009-09-25 Thread Olaf van der Spek
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520668 ** Bug watch added: Debian Bug tracker #520668 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520668 -- proc/sys/net/ipv4/tcp_syncookies=1 should be seriously considered to permit SYN flood defense... https://bugs.launchpad.net/bugs/5

[Bug 57091] Re: proc/sys/net/ipv4/tcp_syncookies=1 should be seriously considered to permit SYN flood defense...

2009-09-25 Thread Olaf van der Spek
Are there any updates on this issue? I don't see any counter arguments to the fact syn cookies only take effect after the queue is full. Ideally this would be changed upstream, maybe an Ubuntu kernel dev could contact upstream about this? -- proc/sys/net/ipv4/tcp_syncookies=1 should be seriousl

[Bug 317781] Re: Ext4 data loss

2009-03-13 Thread Olaf van der Spek
@Theodore Ts'o > 3.a) open and read file ~/.kde/foo/bar/baz > 3.b) fd = open("~/.kde/foo/bar/baz.new", O_WRONLY|O_TRUNC|O_CREAT) > 3.c) write(fd, buf-of-new-contents-of-file, size-of-new-contents-of-file) > 3.d) fsync(fd) --- and check the error return from the fsync > 3.e) close(fd) > 3.f) rename

[Bug 317781] Re: Ext4 data loss

2009-03-13 Thread Olaf van der Spek
@Michel Salim > You can only fsync given a file descriptor, but I think writing an fsync binary that opens the file read-only, fsync on the descriptor, and close the file, should work. Wouldn't that only guarantee the updates through that descriptor (none) are synced? -- Ext4 data loss https://

[Bug 103428] Re: if a firefox download is opened in e.g. openoffice, it is saved to /tmp, then deleted by bootclean script

2007-04-12 Thread Olaf van der Spek
> See comments... not really a bug. Then why not change it to a feature request? -- if a firefox download is opened in e.g. openoffice, it is saved to /tmp, then deleted by bootclean script https://bugs.launchpad.net/bugs/103428 You received this bug notification because you are a member of Ubu

[Bug 103428] Re: if a firefox download is opened in e.g. openoffice, it is saved to /tmp, then deleted by bootclean script

2007-04-12 Thread Olaf van der Spek
> They are saved in /tmp because they they are temp files ;). If you make any change to a file, you must save it using "Save as..." in OpenOffice. I think the file should be opened in such a state that it's unmodified (no question on close) but where Save works as Save As. -- if a firefox downlo