similar to: Upgrading *

On Mon, 2020-05-04 at 23:18 +0200, pavlos wrote: > @Andrew, > > Samba master - what do you mean? A clean compile and install from > genuine samba.org sources? As a matter of fact, I was thinking about > it.... Yes. > Let me do the tests now, with tcpdump. Will send some logs > and outputs later on. > > You've asked previously - this is the smbstatus, already on

OK, have repeated the test: - samba logs: http://www.mediafire.com/file/jy4qcyvqg6z39zu/logs.tar.gz/file - tcpdump log: http://www.mediafire.com/file/qzex3kxf2vzd87n/tcpdump_all.tar.gz/file The tcpdump log covers the whole period of testing time, from starting to stopping smb and nmb services. Previous logs deleted from mediafire. Now waiting for any advice from you, or let's

@Andrew Unfortunately I didn't make notes on exact time of errors when doing my tests... But, I've spend last couple of hours on building samba from master: - Have made a clone of the virtual machine, with new name and network interface mac address, and a new dynamic IP assigned by my router. - Uninstalled Arch packages: samba, smbclient and cifs-tools (depending on

Did you note the very second you saw the offending error message? That time would help a lot, I can't see the error packet. But all that said, I'm not the person who needs to look at this, I just hoped I could help get you the information they would need. The only other suggestion, other than the build on master in the hope this has already been fixed, is if you do find you can build

Hallo, yes this is an "ls -lAh" on the samba fileserver side in the corresponding directory. Downgrading to 4.19 does not remove the weird directories and files. But it prevents new weird ones being created... Looking at the timestamps these seem to be created when (heavy?) filesystem operations are being done. There is a cronjob that imports images at 1oo and it runs for around

@Andrew, Samba master - what do you mean? A clean compile and install from genuine samba.org sources? As a matter of fact, I was thinking about it.... Let me do the tests now, with tcpdump. Will send some logs and outputs later on. You've asked previously - this is the smbstatus, already on the latest kernel/samba versions. The problem is persistent, no wonder... [root at arch1 /]#

It is interesting to see two members of the Samba Team disagree. Though I really appreciate the support provided by Rowland a lot, I definitely favor Andrew?s "If something isn't being cleaned up then that's a bug". Best Regards, Joachim -----Urspr?ngliche Nachricht----- Von: samba <samba-bounces at lists.samba.org> Im Auftrag von Rowland penny via samba Gesendet: Monday,

Thanks for getting back to us, On Mon, 2020-05-04 at 22:57 +0200, pavlos via samba wrote: > @Rowland, > Installing and changing to LTS kernel 5.4.38-1-lts doesn't help. > Downgrading samba and smbclient to 4.11.3 DOES help. > > @Andrew, let me first clean up with kernel/samba versions, set log > level to > 10 and log limit to 0, delete all logs and repeat the whole

17.07.2024 10:54, Matthias K?hne | Ellerhold Aktiengesellschaft via samba wrote: > Hello lovely samba-people, Hi! :) > after upgrading to 4.20 some file shares randomly get weird directories > and files in them: > > drwxrwx---+ 3 AD-ELLERHOLD\user AD-ELLERHOLD\group 4.0K May 29 01:14 ''$'\352' > drwxrwx---+ 3 AD-ELLERHOLD\user AD-ELLERHOLD\group 4.0K May

This is the smbstatus with 4.11.x. No problems on clients. Using LC_ALL=C because have Polish locale set up. [root at arch1 ~]# LC_ALL=C smbstatus Samba version 4.11.3 PID Username Group Machine Protocol Version Encryption Signing

Forgot to add the tcpdump command used: tcpdump -p -s 0 -n -w /root/tcpdump_all.txt Pawel. wt., 5 maj 2020 o 00:01 pavlos <pavlos.audiofreak at gmail.com> napisa?(a): > OK, have repeated the test: > > - samba logs: > http://www.mediafire.com/file/jy4qcyvqg6z39zu/logs.tar.gz/file > - tcpdump log: >

Hi, all. My name is Kenichiro Ochi, in Oracle Japan Support. Customer examines upgrading OCFS from 1.0.9-12 to 1.0.14-1. And customer asked us a question about the way of downgrading to 1.0.9-12. (customer presumes a case in case after the upgrade.) We tested the following... 0.After the upgrade 1.umount OCFS volume on all nodes 2.uninstall rpm (V1.0.14-1) # rpm -e ocfs-tools-1.0.10-1 # rpm

Release Announcements ===================== This is the second release candidate of Samba 4.11. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.11 will be the next version of the Samba suite. UPGRADING ========= AD Database compatibility

Release Announcements ===================== This is the second release candidate of Samba 4.11. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.11 will be the next version of the Samba suite. UPGRADING ========= AD Database compatibility

(sorry for my previous message, I sent it by mistake before finishing it) Hello, We have a production mail server running dovecot 0.99 (dovecot-0.99.14-1.rf). We are getting several errors corrected in dovecot 1.x versions: * corrupted inboxes (garbage at beggining of mbox files), * corrupted index files (Error: Corrupted file index /home/jsmith/.imap/Drafts/.imap.index: Sequence 6 not

@Rowland, Installing and changing to LTS kernel 5.4.38-1-lts doesn't help. Downgrading samba and smbclient to 4.11.3 DOES help. @Andrew, let me first clean up with kernel/samba versions, set log level to 10 and log limit to 0, delete all logs and repeat the whole exercise. Please advice how to get a network capture, I am not that expert... Regards, Pawel. pon., 4 maj 2020 o 22:50 Andrew

I'm starting to see the following error when upgrading from 2.2.27 to 2.2.29. doveadm(ip.add.re.ss): Error: doveadm client disconnected before handshake: SSL_accept() failed: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher Downgrading from 2.2.27 resolves, error still persists in 2.2.28. I'm using openssl 1.1.0.f and an ec cert/key with the following curve.

Has anybody successfully (or I guess unsuccessfully for that matter) implemented Cisco Call Manager and used an * box for voicemail? I checked the wiki and google and I see some references to Call Manager Express and *, but CME is completely different than CM. If anybody has done this or has any insight, it would be appeciated. We are trying to migrate ~ 300 users off of Cisco Unity and

Release Announcements ===================== This is the third release candidate of Samba 4.11. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.11 will be the next version of the Samba suite. UPGRADING ========= AD Database compatibility

Guys, I'm running into a dependecy issue running through the process of building a system for Openbravo. My test system's running CentOS 4.4, i386. Openbravo requires... - Jakarta-Tomcat version 5.5. It can be downloaded from http://tomcat.apache.org/ - Java (TM) 2 Platform Standard Edition 5.0. It can be downloaded from http://java.sun.com/j2se/1.5.0/download.jsp - Oracle(r) 10g