similar to: bug in smbclient (?) 4.2.x

On Wed, 2017-01-04 at 23:07 +0100, Stefan G. Weichinger via samba wrote: > Am 2017-01-04 um 22:40 schrieb Stefan G. Weichinger via samba: > > > > > I currently compile (gentoo linux) samba-4.2.14 and will test > > backing up > > the problematic shares asap. > > still problems with samba-4.2.14: > > ? smbclient: tar:943  Fatal: Can't translate

On Wed, 2017-01-04 at 23:31 +0100, Stefan G. Weichinger wrote: > Am 2017-01-04 um 23:23 schrieb Andrew Bartlett: > > > > > > > > > I will also report that to amanda-users-ml, don't want to bark at > > > the > > > wrong tree ;-) > > > > If you could re-try with Samba 4.5 or bisect back to what change > > between Samba 4.1 and

Hi, Samba-Users, this morning I found some strange-looking lines in my report-emails. At one of my customers I have an installation of Amanda running fine. Yesterday I decided to add a Windows-share to the systems to be backed up. This morning I looked at the logs and there was stuff like this: ....[snip] ? SUCCESS - 0 opening remote file \GKKDFU\Eldawin.hlp (\GKKDFU\) ? SUCCESS - 0 opening

Would anyone have any ideas with smbclient sits at FUTEX_WAIT in below message? Typing: strace smbclient -d 5 shows it sitting at: futex(0x2aaaabdf2dc0, FUTEX_WAIT, 2, NU. SUSE 9.3 x86_64, Samba RPMS from main Samba site rpm -q samba-client samba-client-3.0.23a-0.1.34 -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E

Hi, Thanks for the tip. I went to the Netherlands last week so didn't get a chance to try this out until this week. I upgraded to samba 2.2.3a and that helped. The bad news is that it only solved some of the problems. The file link to the floppy backs up now as the translation of the link is consistent somehow, but the character translation on the $ (dollar sign) and ? (pound sign) is not

Ok.. I've tried tweaking several settings on Samba (1.9.18p4) in order to try to keep it from killing several machines that get backed up weekly via Amanda (using smbclient). What always appears to happen is that for one reason or another, Samba is booking along copying files and then all of a sudden NT stops communication and smbclient ends up hanging forever (regardless of the keepalive

Hi all, I am using Amanda and smbtar for backing up Windows machines. However, in addition to the errors I get on open files (which is to be expected), I am getting errors on files that should be fine to access. Here is a snippet from the Amanda log which contains smbclient errors: ? code 0 opening remote file \ebsco-1064\cueanalysisnew.zip (\ebsco-1064\) ? Expected SMBtrans2 response, got

I am trying to configure a samba with openldap as a PDC on SuSE9.1 with samba-3.0.4, openldap2-2.2.6, samba-winbind-3.0.4, following the book Samba-3 By Example, by John H. Terpstra. I am getting errors "NT_STATUS_LOGON_FAILURE" from smbclient commands and "The username or password was not correct." from 'net' commands. Anonymous smbclient access seems to work, and I

Hi Robert - I'm running it successfully on C7 using xinetd.? Do you have documentation for running it directly from systemd?? Working xinetd configuration: cat /etc/xinetd.d/amanda # default: off # description:? The client for the Amanda backup system.\ #?????????????? This must be on for systems being backed up\ #?????????????? by Amanda. service amanda { ??? disable???????? = no ???

hello puppet list My puppet server is now working quite wonderfully. Thanks go out to all who have assisted in getting it to this point. At this point in time my config is now correctly installing packages according to arch,os and release. Centos is working quite well as of now, but I am attempting to get the ubuntu side of things to work as well. I am frankly more familiar with RHEL under

I am trying to get amanda backup going on a CentOS 7 system and things are not working: sharky4.deepsoft.com% sudo systemctl start amanda-udp [sudo] password for heller: Job for amanda-udp.service failed because a configured resource limit was exceeded. See "systemctl status amanda-udp.service" and "journalctl -xe" for details. sharky4.deepsoft.com% sudo systemctl status -l

I''ve been working up my first puppet module, one that will make Amanda configurations consistently. In general, I''d like the following to happen: - Each Amanda server should make sure all its holding disks are configured properly; this should only happen once per server, per puppetd run. Definitely not on a per-configuration basis. - Each Amanda server should keep its

CentOS Errata and Bugfix Advisory 2015:0748 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0748.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6028eb7fd61883f440b98464a64e4ea9046b940fb71ca21910403d76d1ec1f9a amanda-2.6.1p2-9.el6_6.i686.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://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

hello list, I am attempting to ssh via a user account setup for amanda backups from the backup server to the test backup client. AFAIK everything is setup correctly yet when I ssh as the user to the client I have to type the password. the public key is in the authorized_keys file of the client and permissions all seem correct. Here is a verbose output of the ssh session [amandabackup at

CentOS Errata and Bugfix Advisory 2013:0427 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0427.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 3bbffdc2b0f669627853199868cf58cc3397e0f108fb856b54421271399359d9 amanda-2.6.1p2-8.el6.i686.rpm 4e1e14f387dfbb9d2658aec76eb9585edca1de73e0600e245da0eb4a395dd884

Hello, we are using amanda for backup with 2 tape libraries. Last days we made CentOS 7 update to CentOS Linux release 7.6.1810 (Core) Includes from base repository: amanda-client-3.3.3-21.el7.x86_64 amanda-server-3.3.3-21.el7.x86_64 amanda-3.3.3-21.el7.x86_64 amanda-libs-3.3.3-21.el7.x86_64 deleted: version 3.3.3-17 Before the update (= version 3.3.3-17) we run to configs in parallel without

Has anyone noticed that there appears to be a few problems with regards to Samba and in particular the usage of smbclient, which can do one of the following : 1) Complete & udder death of the NT networking subsystem (which requires a reboot to cure) 2) smbclient appears to lose its connection with the host being contacted and eventually needs to be killed. I'm not too sure how

CentOS Linux release 7.1.1503 (Core) amanda-3.3.3-13.el7.x86_64 amanda-client-3.3.3-13.el7.x86_64 amanda-libs-3.3.3-13.el7.x86_64 dump-0.4-0.22.b44.el7.x86_64 Hi, I have been using amanda backup for quite a long time now. I'm busy migrating some older hosts to CentOS 7 but have found that the available amanda packages (see above) have not been compiled on a host that has the 'dump'

Hello everybody, I'm having problems trying to get smbclient give me right size for amanda backup. I'll give two examples: a 3.6GB w95 share and a 500MB nt4.0 share. With w95 smbclient gives inconsistent results (I saw in your maillists' archives that it may be that w95 can't handle that big partitions). This is what amanda is using to get the size: smbclient