similar to: amanda broken pipe

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

Helo, we have had well runnung amanda tape backup with 3.3.3.-17 in CentOS 7. Two weeks ago we updated the server und got the new release. Now LEOM will no longer be correct recognized. Other experince? How to downgrade? amanda is part of base repository and no former release will be found by yum search. -- Viele Gr??e Helmut Drodofsky Internet XS Service GmbH He?br?hlstra?e 15 70565

(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

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

hey centos long time no hear! :) I'm having a small issue where the backup jobs that I set to run in the crontab of the backup user do not appear to be running. Here's how I set it up (with crontab -e as the backup user): run amanda every night (check at 2:45 and backup at 3) 45 2 * * * /usr/sbin/amcheck /var/log/amanda/crontab/amcheck.log * 3 * * * /usr/sbin/amdump

I've taken you as far as I can go. ?Now you will have to experiment a bit for your use case. ?I should point out that at least in my system, the link with the serial number in it shows up even with the line commented in the rules file. As always, YMMV. On Thu, 2019-02-07 at 22:29 +0100, Helmut Drodofsky wrote: > Hello Ron, > > sounds good. I have 2 tape changer. I persume, udev

yum update was run 23.10.19 and then 05.11.19 to the beginning of the update 5.11.2019 kernel logging to /var/log/messages was ok. During the update at 5.11.2019 logging to /var/log/messages finished. I persume, this bug began during processing updates. yum-log shows: ........... Nov 05 14:56:54 Installed: virt-viewer-5.0-15.el7.x86_64 Nov 05 15:59:28 Installed: nbdkit-1.8.0-1.el7.x86_64

Hello Ron, sounds good. I have 2 tape changer. I persume, udev creates the same link for both. Can I modify SYMLINK+="changer-$env{ID_SERIAL}" The serial should be unique. Viele Gr??e Helmut Drodofsky Internet XS Service GmbH He?br?hlstra?e 15 70565 Stuttgart Gesch?ftsf?hrung Helmut Drodofsky HRB 21091 Stuttgart USt.ID: DE190582774 Fon: 0711 781941 0 <tel:+497117819410> Fax:

our new Server with AMD EPYC and super micro board reboots ramdonly. There is no error message before the reboot in /var/log/messages. we are running 2 Server with VMWare workstation without any problem. The new server should run KVM. older servers with AMD (before EPYC) running KVM without any problem. any idea or recommendation? -- Viele Gr??e Helmut Drodofsky Internet XS Service GmbH

Hello, mtx and therefor amanda use generic device /dev/sg<x> for tape changer. These devices change on reboot. How to make them persistent? /dev/sch0 and /dev/sch1 seem to be persistent. /dev/tape/by-id/ shows links from WWID to generic device An UDEV rule could help? I have not found any example. -- Viele Gr??e Helmut Drodofsky Internet XS Service GmbH He?br?hlstra?e 15 70565

migrated or moved? I move vm from C6 to C7 without any problem, C5 guests too. - copy disk files (rsync or scp) - create in virtual manager - change HWADDR in nic start guest Viele Gr??e Helmut Drodofsky Internet XS Service GmbH He?br?hlstra?e 15 70565 Stuttgart Gesch?ftsf?hrung Helmut Drodofsky HRB 21091 Stuttgart USt.ID: DE190582774 Fon: 0711 781941 0 <tel:+497117819410> Fax: 0711

Hi, never testet by myself: usage of virt-p2v Viele Gr??e Helmut Drodofsky Internet XS Service GmbH He?br?hlstra?e 15 70565 Stuttgart Gesch?ftsf?hrung Helmut Drodofsky HRB 21091 Stuttgart USt.ID: DE190582774 Fon: 0711 781941 0 <tel:+497117819410> Fax: 0711 781941 79 Mail: info at internet-xs.de www.internet-xs.de Am 07.07.2020 um 06:22 schrieb Philip Prindeville: > Hi all, > >

I'm doing yum update in CentOS 7 since some 10 hours. Last terminal message is: Updating?? : gitlab-ci-multi-runner-9.5.1-1.x86_64 ps aux: root???? 15296? 0.3? 2.5 1554608 204988 pts/0? S+?? 06:23?? 2:01 /usr/bin/python /bin/yum update to kill yum is not a good idea. Alternative? for what is yum waiting? can I stop an application process? systemctl stop gitlab-runner does not help, same

For me it's a new problem. I have never had problems like this: kernel:XFS: mysqld(112843) possible memory allocation deadlock size 65552 in kmem_realloc (mode:0x250) My first server with soft raid1 and NVMee. CentOS 7.5. Are there special recommendations for configuring XFS with NVMe's? -- Viele Gr??e Helmut Drodofsky Internet XS Service GmbH He?br?hlstra?e 15 70565 Stuttgart

> our new Server with AMD EPYC and super micro board reboots ramdonly. > There is no error message before the reboot in /var/log/messages. Anything in the hardware logs of the server like memory error or so? Any watchdog on the servers acting bad? We run CentOS 7 and KVM on AMD Opteron and AMD EPYC servers without issues. Regards, Simon > > we are running 2 Server with VMWare

2016-07-08 4:19 GMT+08:00 Helmut Drodofsky <drodofsky at internet-xs.de>: > Helo, > > update is in EPEL repository. > > on startup, clamd does not further create clamd.sock and clamd.pid > > clamd service stops without any message - even in debug mode. > > Comment out "AllowSupplementaryGroups" in config clamd.conf and try restart again > It's a

Helmut Drodofsky wrote: > Hello, > > there is one route missing: > > 128.0.0.0/1. > Did you mean 127.0.0.0? mark > config client: > route-nopull > redirect-gateway def1 bypass-dhcp > > best regards > Helmut > > Viele Gr??e > Helmut Drodofsky > > Internet XS Service GmbH > He?br?hlstra?e 15 > 70565 Stuttgart > > Gesch?ftsf?hrung

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

Helo, we use recent to control ip traffic. kernel 2.6.18-308.13.1.el5 : all is OK kernel 2.6.18-308.16.1.el5 : the first recent statement causes an error. E.g.: iptables -A INPUT -m state --state NEW -m recent --set -p tcp --dport 80 iptables: Unknown error 18446744073709551615 The man pages say: recent is supported. CentOS 6: is OK Knows anyone more? Best regards Helmut Drodofsky -- Viele

Hello, njab.org will discontinue blacklist services. On 1. March 2013 Apache published: Bug 6913; Disabled rules/scores for njabl.org See: http://svn.apache.org/viewvc?view=revision&revision=1451776 Will there be an update from CentOS? Best regards Helmut Drodofsky -- Viele Gr??e Helmut Drodofsky Internet XS Service GmbH He?br?hlstra?e 15 70565 Stuttgart Gesch?ftsf?hrung