similar to: samba rpm deps - with yum downgrade = kind of a mayhem

On 25/01/17 14:26, Jonathan Billings wrote: > On Wed, Jan 25, 2017 at 11:32:16AM +0000, lejeczek wrote: >> hi guys, gals >> >> do you see this: >> >> ~]$ yum downgrade samba >> Resolving Dependencies >> [...] >> --> Processing Dependency: libtevent.so.0(TEVENT_0.9.9) for package: >> samba-client-libs-4.4.4 >> >> ..and process

On Wed, Jan 25, 2017 at 11:32:16AM +0000, lejeczek wrote: > hi guys, gals > > do you see this: > > ~]$ yum downgrade samba > Resolving Dependencies > [...] > --> Processing Dependency: libtevent.so.0(TEVENT_0.9.9) for package: > samba-client-libs-4.4.4 > > ..and process fails. > chained are i686 arch? Is it only us(centos) or redhat's bugzilla should

On Thu, Jan 26, 2017 at 11:44:06AM +0000, lejeczek wrote: > but Centos should, right? > Being able to downgrade can save you a day or a few. I know, for it did save > mine several times, eg. buggy samba new update and downgrade fixed it, etc. > We absolutely should be able to downgrade every rpm, if this is just a > matter of an opinion(I'd fail to see any other reasons to not

CentOS Errata and Bugfix Advisory 2017:0069 Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-0069.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: d04b5c04b305ec76be544f7484ce89fa76f79328234b48c1697246ab5b2ffd77 ctdb-4.4.4-12.el7_3.x86_64.rpm

CentOS Errata and Security Advisory 2017:1265 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-1265.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 87f3041a57ee5ae9cab106a52453c7448378af844d78cd9b5b4dc2e1edc074a8 ctdb-4.4.4-13.el7_3.x86_64.rpm

CentOS Errata and Security Advisory 2017:1270 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-1270.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 6e9e51cd9b9dd683ab359fe19754a5d7e72072fe3920372efd486afb110a18bb ctdb-4.4.4-14.el7_3.x86_64.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi, Over the weekend we updated a two server glusterfs 3.6.6 install to 3.10.2 We also updated samba and samba-vfs to the latest in CentOS. I enabled several of the newer caching features from gluster 3.9 for small file performance and samba, and we now seem to have some issues with accessing files from glusterfs. When users try to access some files, they get a Permission denied message. This

On 03-Jun-2017 3:27 AM, "Diego Remolina" <dijuremo at gmail.com> wrote: Hi everyone, Is there anything else we could do to check on this problem and try to fix it? The issue is definitively related to either the samba vfs gluster plugin or gluster itself. I am not sure how to pin it down futher. I don't think it is vfs plugin because you haven't updated samba packages

Hi everyone, Is there anything else we could do to check on this problem and try to fix it? The issue is definitively related to either the samba vfs gluster plugin or gluster itself. I am not sure how to pin it down futher. I went ahead and created a new share in the samba server which is on a local filesystem where the OS is installed, not part of gluster: # mount | grep home ]# ls -ld /home

Thanks for taking the time to look into this. Since we needed downtime due to the gluster update, we also updated the OS, including samba. We went from 4.2.x to 4.4.4 and many other packages for CentOS were updated as well. OS and samba updates were installed, then server rebooted, then gluster was updated. Created a new test samba share to minimize logs, etc: [VfsGluster] path = /vfsgluster

Trying to revive this old thread as problems continue. I have noticed from the gluster logs the following on m y volume called export: [2017-08-16 20:08:47.663908] I [MSGID: 109066] [dht-rename.c:1608:dht_rename] 0-export-dht: renaming /projects/ACTIVE/Automotive/JEEP/Brand Image Program June 2016/04_Western Region/Huntington Beach CDJR - Huntington Beach, CA/04 REVIT AND CAD/2017-08-16 CAD dwgs

Hi all, I am currently having some problems managing DNS on our Samba servers with bind9 backend. Whenever I try to access the AD domain zone from the MS DNS tool the DNS part crashes and services need to be restarted. After the crash DNS is not working anymore. I get the following in log.samba: [2019/09/20 09:39:10.681745,? 0]

Did the logs provide any hints as to what the issue may be? Diego On Sat, Jun 3, 2017 at 12:16 PM, Diego Remolina <dijuremo at gmail.com> wrote: > Thanks for taking the time to look into this. Since we needed downtime > due to the gluster update, we also updated the OS, including samba. We > went from 4.2.x to 4.4.4 and many other packages for CentOS were > updated as well. OS

Hello All, Is it possible to migrate from 4.2.14-SerNet-RedHat-23.el7 to samba-4.4.4-13.el7_3.x86_64 on centOS7? I've got two centos7 servers running sernet versions of samba. Both are AD DC's, with 600 users. If I run yum install samba4, I get a promising error back: Package samba-4.4.4-13.el7_3.x86_64 is obsoleted by 99:sernet-samba-4.2.14-23.el7.x86_64 which is already installed So,

Package: xen-utils-4.1 Version: 4.1.4-4 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem xenbaked crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/, we

Package: xen-utils-4.1 Version: 4.1.4-4 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem xenctx crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/, we include

Package: xen-utils-4.1 Version: 4.1.4-4 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem xentrace_setmask crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/,

Package: xen-utils-4.1 Version: 4.1.4-4 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem xentrace_setsize crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/,