Too early to tell. Dealing with one bug at a time ;)
_____ From: Jason Hensley [mailto:[email protected]] Sent: 20 October 2010 15:41 To: 'WISPA General List' Subject: Re: [WISPA] Mikrotik Dude 2GB Limitation How is v4 working for you other than the potential 2GB issue? I’ve been hesitant to move to it since it’s still beta. From: [email protected] [mailto:[email protected]] On Behalf Of Paul Hendry Sent: Tuesday, October 19, 2010 3:02 PM To: wireless Subject: Re: [WISPA] Mikrotik Dude 2GB Limitation The majority of the data is traffic statistics. In V4 you can set the dude to store much more historical data than in V3 so instead of having a monthly graph that shows averaged data you can have a daily or hourly graph that goes back months and therefore gives a much more accurate historical view of network usage. Unfortunately, downgrading back to V3 will loose much of this functionality so isn’t really an option either. Many thanks, Paul. _____ From: Josh Luthman [mailto:[email protected]] Sent: 19 October 2010 19:45 To: WISPA General List Subject: Re: [WISPA] Mikrotik Dude 2GB Limitation Yes I did. I was unaware that in the migration to v4 it utilized SQLite instead of file storage. Perhaps you can load up another box and downgrade to 3.6 and see if you run into this issue. Are you holding a lot of NPKs for upgrades? I found this was an issue when I tried to back up. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Oct 19, 2010 at 3:33 PM, Paul Hendry <[email protected]> wrote: Josh, Did you actually read the original post? The latest dude beta versions run a backend database not files. The backend database is SQLite and it is when the database reaches a file size of 2GB that Dude stops working. The question remains, which element is causing this bottleneck and is there a work around? Paul. _____ From: Josh Luthman [mailto:[email protected]] Sent: 19 October 2010 19:18 To: WISPA General List Subject: Re: [WISPA] Mikrotik Dude 2GB Limitation I gave you a work around, change to RouterOS. I'm not sure where SQlite is involved, but you don't have any options with Dude in terms of storage. It simply stores it in files. I don't see how you're hitting 2GB for the Dude, where are you seeing this number? Can you load a demo copy of RouterOS and import your backup and see if the issue is seen there as well? Some linux distro? Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Oct 19, 2010 at 3:14 PM, Paul Hendry <[email protected]> wrote: Hi guys, I don’t want to suggest this thread has been hijacked but can we get back to the original question? Does anyone know if the 2GB limit is OS, SQLite or Dude related and if there is any work around? Many thanks, Paul. _____ From: Josh Luthman [mailto:[email protected]] Sent: 19 October 2010 17:15 To: WISPA General List Subject: Re: [WISPA] Mikrotik Dude 2GB Limitation I read something complaining updates were released every Tuesday for 6 weeks. Updates are definitely good, but on servers you have to manually intervene. I don't want to use my time on that. Biggest patch Tuesday ever was last week or week before, too. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Oct 19, 2010 at 12:12 PM, Greg Ihnen <[email protected]> wrote: Second Tuesday of the month, except for out-of-cycle patches, no? Greg On Oct 19, 2010, at 11:38 AM, Josh Luthman wrote: Every Tuesday for Windows. How often for RouterOS? I still have 2.9.x boxes out there. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Oct 19, 2010 at 12:00 PM, David E. Smith <[email protected]> wrote: On Tue, Oct 19, 2010 at 10:23, Josh Luthman <[email protected]> wrote: This is what I was referring to. I don't want to spend my nights updating Windows. Spending your nights updating FreeBSD or Linux isn't any better. No matter what you're running, it probably will need occasional updates. I almost always try to schedule those updates for after-midnight, to minimize the number of users affected by whatever-it-is being down. The only exception to this is if something is fairly redundant. I'm willing to do work on one of the incoming mail servers or DNS servers, for instance, since there are several of those and one being down for a few minutes during the day won't even be noticed. David Smith MVN.net ------------------------------------------------------------------------ -------- WISPA Wants You! Join today! http://signup.wispa.org/ ------------------------------------------------------------------------ -------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ ------------------------------------------------------------------------ -------- WISPA Wants You! Join today! http://signup.wispa.org/ ------------------------------------------------------------------------ -------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ ------------------------------------------------------------------------ -------- WISPA Wants You! Join today! http://signup.wispa.org/ ------------------------------------------------------------------------ -------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------------------------------------------------------------------------ -------- WISPA Wants You! Join today! http://signup.wispa.org/ ------------------------------------------------------------------------ -------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------------------------------------------------------------------------ -------- WISPA Wants You! Join today! http://signup.wispa.org/ ------------------------------------------------------------------------ -------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
-------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
