similar to: cron jobs fail to run

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

Am 21.12.18 um 16:47 schrieb Peter Eriksson via samba: >> What is "Unable to initialize messaging context"? >> >> I see a patch back in July, related to "Fix bug 13465", >> https://lists.samba.org/archive/samba-technical/2018-July/129186.html but it >> is unclear why the message is still being issued? > > Because that patch for bug 13465

Hi List, Happy New Years and I was hoping to get some help on an ssh issue that I am having. For some reason I am unable to scp to hosts on this network using RSA keys. Here is what I am doing/what is going on; scp the public key to remote host [amandabackup at VIRTCENT18 ~]$ scp ~/.ssh/id_rsa_amdump.pub amandabackup at lb1:~ amandabackup at lb1's password: id_rsa_amdump.pub

Hi, I am trying to create a Samba share on /media/winshare with the owner as amandabackup instead of root. But as soon as I mount the Samba share on to the mount point, the permissions for the owner get reverted back to root instead of amandabackup. Attaching a snapshot of how it looks like. http://www.nabble.com/file/p10894282/samba%2Bquery.jpg -- View this message in context:

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 ???

OK, after beating my head against the wall for an hour or so, I finally figured out why I could not ssh from a MacMini (running MacOSX 10.11.6) to my Linux Desktop (running CentOS 6), using the amandabackup account with public key authentification. SELinux! It seems the SELinux won't allow this if the target user's "home" directory is does not have a <mumble>_home_t

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

I'm slowly getting everything back to normal here after swapping motherboards on my server. I also took the opportunity to bring the server up to CentOS 5. I'm still getting services working but I have one oddity with amanda. Ever since I upgraded the server to CentOS 5, amcheck dies and gives me a backtrace if there are no available tapes. amcheck works fine if the expected next

On Sunday 12 May 2019 02:41:02 pm Charles Lepple wrote: > /lib/nut/usbhid-ups -a myups -DD gene at coyote:~$ /lib/nut/usbhid-ups -a myups -DD Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 Can't open /etc/nut/ups.conf: Can't open /etc/nut/ups.conf: Permission denied lemme see who owns that. huh? amandabackup:nut what the h? Who is supposed to own

(of course I'm working through all of this as I type this note, and I did resolve it, I'm sending it on anyway so that others might benefit). Greetings, I am relatively new to samba. samba-2.2.3a-6 (RedHat 7.3) Trying to get Amanda to back up an XP client via smb. (XP SP1). (yes, our environment is a wild mix of hardware and OS - typical consulting shop). Amcheck tries: smbclient

Sambadevs, I don't know if this is a bug or just a spurious error message when using smbclient (on a standalone config), but checking smbclient, I get: 02:47 2pi:~> smbclient -U% -Llocalhost Unable to initialize messaging context Sharename Type Comment --------- ---- ------- samba Disk 2pi - Law IPC$ IPC

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

Hi all, Has anyone used amanda in combination with samba to back up an NT4 server system? I'm able to connect to the server with both smbclient and smbtar on the command line, but I can't get amanda to connect. Supposedly amanda uses smbclient and smbtar to perform the backups. I'm continually getting the following error from amcheck: ERROR: amanda: [PC SHARE //servername/share

Hi, I am trying to mount a Linux directory onto the Windows box. The smb.conf file looks like this: Load smb config files from /etc/samba/smb.conf Processing section "[homes]" Processing section "[profiles]" Processing section "[users]" Processing section "[groups]" Processing section "[winshare]" Loaded services file OK. WARNING: passdb expand

On Wed, 2 Jan 2019 09:32:55 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 21.12.18 um 16:47 schrieb Peter Eriksson via samba: > > >> What is "Unable to initialize messaging context"? > >> > >> I see a patch back in July, related to "Fix bug 13465", > >>

Hello All, I''ve run into an issue where an array that''s being passed into a defined type is being "flattened" when it''s inclosed in double quotes and I''m not sure how to get around this. This is happening a the pdxcat/amanda module and I''ve raised an github issues for this but wanted to query the community as a whole. The issue and my branch

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

At the bottom is what I got returned from AMANDA 2.3.0.5 after patching Samba 1.9.16p11 to give estimates. Any idea what I might not have done yet? My disklist reads: shokk \\thor\depot nocomp-user-gnutar To connect successfully to that server with smbclient, I have to do this, giving the same password that I now have in /etc/amandapass: smbclient \\\\THOR\\DEPOT -U BACKUP Also, the

After the large update from 7.2 -> 7.3 there is one major problem, the amanda backup packages. Strange situation, the host is the amanda server is working fine at backing up all my remote clients. But it has an error backing up itself. The amanda packages did not change version (3.3.3) and I've done no configuration change. I'm not looking for help debugging this at the moment.

hello list!! I am still having some file sharing issues with this puppet server and I was hoping someone would have an opinion they could share on this situation ## puppet errors err: //basefiles/File[/etc/yum/pluginconf.d/priorities.conf]: Failed to retrieve current state of resource: Error 400 on SERVER: Not authorized to call find on /file_metadata/acadaca/yum/pluginconf.d/priorities.conf