similar to: [Bug 1674] New: ebtables causing packet loss

Displaying 20 results from an estimated 200 matches similar to: "[Bug 1674] New: ebtables causing packet loss"

2018 Feb 09
3
Failed to get quota limits
Hello, I am running GlusterFS 3.10.7 and just noticed by doing a "gluster volume quota <volname> list" that my quotas on that volume are broken. The command returns no output and no errors but by looking in /var/log/glusterfs.cli I found the following errors: [2018-02-09 19:31:24.242324] E [cli-cmd-volume.c:1674:cli_cmd_quota_handle_list_all] 0-cli: Failed to get quota limits for
2018 Feb 12
0
Failed to get quota limits
Hi, Can you provide more information like, the volume configuration, quota.conf file and the log files. On Sat, Feb 10, 2018 at 1:05 AM, mabi <mabi at protonmail.ch> wrote: > Hello, > > I am running GlusterFS 3.10.7 and just noticed by doing a "gluster volume quota <volname> list" that my quotas on that volume are broken. The command returns no output and no errors
2018 Feb 13
2
Failed to get quota limits
Hi Hari, Sorry for not providing you more details from the start. Here below you will find all the relevant log entries and info. Regarding the quota.conf file I have found one for my volume but it is a binary file. Is it supposed to be binary or text? Regards, M. *** gluster volume info myvolume *** Volume Name: myvolume Type: Replicate Volume ID: e7a40a1b-45c9-4d3c-bb19-0c59b4eceec5 Status:
2018 Feb 13
2
Failed to get quota limits
Thank you for your answer. This problem seem to have started since last week, so should I also send you the same log files but for last week? I think logrotate rotates them on a weekly basis. The only two quota commands we use are the following: gluster volume quota myvolume limit-usage /directory 10GB gluster volume quota myvolume list basically to set a new quota or to list the current
2018 Feb 13
2
Failed to get quota limits
Were you able to set new limits after seeing this error? On Tue, Feb 13, 2018 at 4:19 PM, Hari Gowtham <hgowtham at redhat.com> wrote: > Yes, I need the log files in that duration, the log rotated file after > hitting the > issue aren't necessary, but the ones before hitting the issues are needed > (not just when you hit it, the ones even before you hit it). > > Yes,
2018 Feb 13
0
Failed to get quota limits
Hi, A part of the log won't be enough to debug the issue. Need the whole log messages till date. You can send it as attachments. Yes the quota.conf is a binary file. And I need the volume status output too. On Tue, Feb 13, 2018 at 1:56 PM, mabi <mabi at protonmail.ch> wrote: > Hi Hari, > Sorry for not providing you more details from the start. Here below you will > find all
2018 Feb 23
2
Failed to get quota limits
Hi, There is a bug in 3.10 which doesn't allow the quota list command to output, if the last entry on the conf file is a stale entry. The workaround for this is to remove the stale entry at the end. (If the last two entries are stale then both have to be removed and so on until the last entry on the conf file is a valid entry). This can be avoided by adding a new limit. As the new limit you
2018 Feb 27
2
Failed to get quota limits
Hi Mabi, The bugs is fixed from 3.11. For 3.10 it is yet to be backported and made available. The bug is https://bugzilla.redhat.com/show_bug.cgi?id=1418259. On Sat, Feb 24, 2018 at 4:05 PM, mabi <mabi at protonmail.ch> wrote: > Dear Hari, > > Thank you for getting back to me after having analysed the problem. > > As you said I tried to run "gluster volume quota
2025 Feb 17
2
Cannot access domain member from trusted domain user
I'm not able to access a samba file server that I recently created and joined to a domain. I have two domains with an external trust: BRANDLILAW and BRANDLI. The server is joined to BRANDLILAW. I am trying to access it from a user on the BRANDLI domain. This worked with the prior server that the new server is replacing. All domain controllers and the server are Debian backports (21.3).
2018 Feb 13
0
Failed to get quota limits
Yes, I need the log files in that duration, the log rotated file after hitting the issue aren't necessary, but the ones before hitting the issues are needed (not just when you hit it, the ones even before you hit it). Yes, you have to do a stat from the client through fuse mount. On Tue, Feb 13, 2018 at 3:56 PM, mabi <mabi at protonmail.ch> wrote: > Thank you for your answer. This
2018 Feb 13
0
Failed to get quota limits
I tried to set the limits as you suggest by running the following command. $ sudo gluster volume quota myvolume limit-usage /directory 200GB volume quota : success but then when I list the quotas there is still nothing, so nothing really happened. I also tried to run stat on all directories which have a quota but nothing happened either. I will send you tomorrow all the other logfiles as
2018 Feb 24
0
Failed to get quota limits
Dear Hari, Thank you for getting back to me after having analysed the problem. As you said I tried to run "gluster volume quota <VOLNAME> list <PATH>" for all of my directories which have a quota and found out that there was one directory quota which was missing (stale) as you can see below: $ gluster volume quota myvolume list /demo.domain.tld Path
2018 Feb 27
0
Failed to get quota limits
Hi, Thanks for the link to the bug. We should be hopefully moving soon onto 3.12 so I guess this bug is also fixed there. Best regards, M. ? ??????? Original Message ??????? On February 27, 2018 9:38 AM, Hari Gowtham <hgowtham at redhat.com> wrote: > ?? > > Hi Mabi, > > The bugs is fixed from 3.11. For 3.10 it is yet to be backported and > > made available. >
2013 Nov 06
1
R help-classification accuracy of DFA and RF using caret
Hi, I am a graduate student applying published R scripts to compare the classification accuracy of 2 predictive models, one built using discriminant function analysis and one using random forests (webpage link for these scripts is provided below). The purpose of these models is to predict the biotic integrity of streams. Specifically, I am trying to compare the classification accuracy (i.e.,
2018 Oct 26
2
classicupgrade
On Fri, 26 Oct 2018 16:23:32 +0200 Corrado Ravinetto via samba <samba at lists.samba.org> wrote: > > > Il 26/10/2018 15:59, Rowland Penny via samba ha scritto: > > Did you test the upgrade process in a separate network ? > yes i have installed 2 new vm with centos 7 from dvd > > Did you carry out the upgrade on the original PDC or on a new > > computer ? >
2013 Apr 07
2
group data in classes
Hello all! I have a problem to group my data (years) in 10 years classes. For example for year year decade 1598 1590-1600 1599 1590-1600 1600 1590-1600 1601 1600-1610 --- my is like this> [1] 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 [16] 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 [31] 1628 1629 1630 1631 1632 1633
2023 Jun 09
7
[Bug 1689] New: Resetting the timeout counter for a named set element
https://bugzilla.netfilter.org/show_bug.cgi?id=1689 Bug ID: 1689 Summary: Resetting the timeout counter for a named set element Product: nftables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: enhancement Priority: P5 Component: nft Assignee: pablo at
2005 Mar 08
2
Asterisk Management API
Hi all, I am trying to write an application to monitor queues using the Asterisk Management API. So far I have had some level of sucess, basically reverse engineering the protocol and the event messages using ethereal etc. I know there are a couple of pages on the Wiki that attempt (no dis-respect to who ever did it as it has been a great help) to document the API and was wondering if there
2002 Aug 17
1
Pxelinux: File not found during boot, HELP
Hi, I am trying to boot the PXEclient via pxeserver and I am getting an error "file not found", following are me setup in the /tftpboot: /tftpboot: initrd.img linuz pxelinux.0 /tftpboot/pxelinux.cfg default (lower case) in the default file: # This is the default pxelinux config file. LABEL test KERNEL vmlinuz APPEND
2010 Apr 01
1
predicted time length differs from survfit.coxph:
Hello All, Does anyone know why length(fit1$time) < length(fit2$n) in survfit.coxph output? Why is the predicted time length is not the same as the number of samples (n)? I tried: example(survfit.coxph). Thanks, parmee > fit2$n [1] 241 > fit2$time [1] 0 31 32 60 61 152 153 174 273 277 362 365 499 517 518 547 [17] 566 638 700 760 791